RRPproxy incident

Following the today's fibre cut incident

Notice Resolved View vendor source →

RRPproxy experienced a notice incident on February 27, 2026 affecting XRRP API and ccTLD Services and 1 more component, lasting 6d 1h. The incident has been resolved; the full update timeline is below.

Started
Feb 27, 2026, 03:30 PM UTC
Resolved
Mar 05, 2026, 05:07 PM UTC
Duration
6d 1h
Detected by Pingoru
Feb 27, 2026, 03:30 PM UTC

Affected components

XRRP APIccTLD ServicesEPP APIOngoing: .AISOAP APIXMLRPC APIHTTPS APIREST APIWeb InterfaceDNS resolution

Update timeline

  1. investigating Feb 27, 2026, 03:30 PM UTC

    Following today's fibre cut incident, we are investigating a signal degradation on the replacement fibre path, and have dispatched a field engineer to clean and test the optical connections. We will shut the affected connection down for maintenance to move all traffic to our secondary link. No service disruption is expected while we restore the primary path to optimal signal levels.

  2. resolved Mar 05, 2026, 05:07 PM UTC

    The issue has been successfully resolved, the signal levels have improved, and the interface has been re-enabled for production traffic.