RRPproxy Outage History
RRPproxy is up right nowPingoru has recorded 31 incidents for RRPproxy: 4 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 1 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 1 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 96 (0%) |
Incidents, newest first
Notice May 5, 2026 DNS resolution issues for many .de domains 2h 52m
Started May 05, 2026, 09:28 PM UTC· resolved May 06, 2026, 12:20 AM UTC
- identified May 05, 2026, 09:28 PM UTC
We are currently aware of an issue affecting DNS resolution for many .de domains. Customers may experience issues reaching websites or services hosted on affected domains when using certain DNS resolvers. The root cause appears to be a zone signing issue at DENIC (the .de registry), which causes DNSSEC-validating resolvers to return an error when resolving affected domains. https://status.denic.de/ shows this as a "Service Disruption". The issue is outside our control and a report has been submitted to DENIC.
Notice February 27, 2026 Following the today's fibre cut incident 6d 1h XRRP API, ccTLD Services, EPP API, Ongoing: .AI and 12 more
Started Feb 27, 2026, 03:30 PM UTC· resolved Mar 05, 2026, 05:07 PM UTC
- 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.
- 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.
Notice February 27, 2026 Network Disruption – Fiber Cut –
Started Feb 27, 2026, 09:30 AM UTC· resolved Feb 27, 2026, 09:30 AM UTC
- resolved Feb 27, 2026, 09:30 AM UTC
Dear Clients, We experienced a brief network disruption due to a fiber cut affecting our upstream transit provider. This caused packet loss and temporarily disrupted some connections. The issue has been identified and fully resolved, and all systems are now operating normally. We apologize for any inconvenience. Thank you for your understanding.
Notice October 31, 2025 Issue with .CO registry – Registry
Started Oct 31, 2025, 08:26 PM UTC· resolved Oct 31, 2025, 08:26 PM UTC
- resolved Oct 31, 2025, 08:26 PM UTC
Dear customers, Recently we experience a short-time outage with .CO registry services. This issue was fixed by our technical team and it should work properly for now. We appreciate you being our customers and apologize for these inconveniences. Your patience and understanding are most appreciated.
Minor September 19, 2025 Performance degradation caused by intermittent package loss 1h 50m XRRP API, EPP API, SOAP API, XMLRPC API and 6 more
Started Sep 19, 2025, 11:28 AM UTC· resolved Sep 19, 2025, 01:18 PM UTC
- identified Sep 19, 2025, 11:28 AM UTC
Starting around 11:20 UTC, we observe intermittent packet loss affecting connectivity to our data center locations. Our upstream provider has acknowledged the issue and is actively implementing corrective measures to restore full service as quickly as possible.
- monitoring Sep 19, 2025, 11:37 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 19, 2025, 01:18 PM UTC
This incident has been resolved.
Major July 3, 2025 Centralnic Reseller Reachability Issues 9h 13m XRRP API, ccTLD Services, EPP API, Ongoing: .AI and 12 more
Started Jul 03, 2025, 07:09 PM UTC· resolved Jul 04, 2025, 04:22 AM UTC
- 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.
- investigating Jul 03, 2025, 07:40 PM UTC
We are continuing to investigate this issue.
- identified Jul 03, 2025, 08:55 PM UTC
We have identified the issue, and we are working towards its resolution.
- identified Jul 03, 2025, 09:11 PM UTC
We are continuing to work on a fix for this issue.
- 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.
- 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.
- identified Jul 04, 2025, 12:01 AM UTC
Work toward resolution is still underway. The next update will be provided in an hour.
- identified Jul 04, 2025, 01:00 AM UTC
Investigation and remediation efforts are ongoing. The next update will be provided in an hour.
- 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.
- identified Jul 04, 2025, 02:10 AM UTC
We are continuing to work on a fix for this issue.
- 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.
- identified Jul 04, 2025, 04:03 AM UTC
Our team is actively addressing the incident. The next update will be provided in an hour.
- 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