RRPproxy incident

Centralnic Reseller Reachability Issues

Major Resolved View vendor source →

RRPproxy experienced a major incident on July 3, 2025 affecting XRRP API and ccTLD Services and 1 more component, lasting 9h 13m. The incident has been resolved; the full update timeline is below.

Started
Jul 03, 2025, 07:09 PM UTC
Resolved
Jul 04, 2025, 04:22 AM UTC
Duration
9h 13m
Detected by Pingoru
Jul 03, 2025, 07:09 PM UTC

Affected components

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

Update timeline

  1. investigating Jul 03, 2025, 07:09 PM UTC

    We are currently experiencing temporary technical issues, which may impact access to the platform. We apologise for the inconvenience and are working hard to restore our services as quickly as possible.

  2. investigating Jul 03, 2025, 07:40 PM UTC

    We are continuing to investigate this issue.

  3. identified Jul 03, 2025, 08:55 PM UTC

    We have identified the issue, and we are working towards its resolution.

  4. identified Jul 03, 2025, 09:11 PM UTC

    We are continuing to work on a fix for this issue.

  5. identified Jul 03, 2025, 09:59 PM UTC

    We're currently actively working on a resolution. The next update will be provided in an hour.

  6. identified Jul 03, 2025, 11:01 PM UTC

    We are continuing to work on resolving the issue. The next update will be provided in an hour.

  7. identified Jul 04, 2025, 12:01 AM UTC

    Work toward resolution is still underway. The next update will be provided in an hour.

  8. identified Jul 04, 2025, 01:00 AM UTC

    Investigation and remediation efforts are ongoing. The next update will be provided in an hour.

  9. identified Jul 04, 2025, 02:00 AM UTC

    Our team is actively working to restore service as quickly as possible. The next update will be provided in an hour.

  10. identified Jul 04, 2025, 02:10 AM UTC

    We are continuing to work on a fix for this issue.

  11. identified Jul 04, 2025, 03:06 AM UTC

    We are continuing to work on resolving the issue. The next update will be provided in an hour.

  12. identified Jul 04, 2025, 04:03 AM UTC

    Our team is actively addressing the incident. The next update will be provided in an hour.

  13. resolved Jul 04, 2025, 04:22 AM UTC

    The issue in our data centre has now been resolved. The system is now operational. We are closely monitoring all affected services