История сбоев Rrpproxy

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.

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

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.

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.

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.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

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.

We are continuing to investigate this issue.

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

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

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

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

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

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

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

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

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

Time of Incident: Approximately 1 hour ago Current Status: Ongoing We are currently experiencing issues with our support platform where tickets from any non-verified users are not being parsed or displayed correctly. Please note that we have never required or been asked to verify users emailing us before, so this is an unexpected bug. Impact: There will be delays in our response to tickets from non-verified users. For urgent matters , we recommend reaching out via chat support for quicker assistance. Actions Taken: We have notified Zendesk of this issue and just completed a call with their support team. They have confirmed that this behavior is not normal functionality within their platform. Next Steps: We expect an update from Zendesk very soon and will provide more information on this status page as it becomes available. We will be requesting a postmortem from Zendesk once the issue is resolved to ensure that steps are taken to prevent similar issues in the future. Thank you for your patience as we work to resolve this issue.

Issue has been identified and resolution will be place within the hour.

Dear Customers, We are pleased to inform you that the issue affecting our support platform, where tickets from non-verified users were not being parsed or displayed correctly, has now been fully resolved. What Happened: Earlier today, we experienced a bug in our support platform that caused delays in processing tickets from non-verified users. This was an unexpected issue as we have never required verification for users emailing us. Resolution: Our team worked closely with Zendesk, and the issue was identified and resolved swiftly. Normal ticket processing has resumed, and we are catching up on any delayed responses. Next Steps: We have requested a detailed postmortem from Zendesk to ensure they take steps to prevent such issues from occurring in the future. If you have any outstanding issues or if your inquiry was affected by this incident, please don’t hesitate to reach out to us again. We sincerely apologize for any inconvenience this may have caused and appreciate your understanding. If you need any further assistance, our team is here to help. Thank you for your continued trust in our support.

This incident has been resolved.

Dear Customer, Unfortunately since about 12:00 UTC the login to CentralNic Control Panel is not possible any more. The issue already has been identified and we're busy bringing our services back to normal operation. Please excuse any inconvenience caused.

An update has been implemented, access is possible again. We continue monitoring the situation.

This incident has been resolved.

Due to issues connecting to a registry , there is currently a issue modifying / purchasing some TLD's Error during domain actions "DESCRIPTION": "Command failed due to server error. Client should try again; No response", "CODE":421, Registry Operator confirmed issue and work to resolve is ongoing

Issue resolved at registry

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

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

incident resolved , root cause to follow after log review.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

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

A fix has been implemented and we are monitoring the results.

the issue have been resolved , root cause to follow

We’re undergoing an unplanned maintenance on our firewall on Wednesday Dec 6th, 2023 from 08:00 - 16:00 UTC. During this timeframe you may experience packet losses while connecting to our API gateways and Control Panel for a short timeframe. Please excuse any inconvenience caused.

Firewall has been replaced and all systems are fully operational again.

We are currently investigating this issue.

Root Cause is being investigated , API issues seen from MST 22.08.2023 15:00 to 22.08.2023 16:20

This incident has been resolved.

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

At the moment our KeyDNS is not carrying out DNS Updates. This includes any updates to DNS zone files. Our system is continuing to accept commands, updates however are currently queued. All queries are working as expected. We're already busy implementing a fix. Thank you for your understanding.

DNS Updates are available again. A fix has been rolled out and DNS updates are available again. All queued commands are now processing. We keep monitoring the situation.

We are continuing to monitor for any further issues.

All operation is back to normal. This incident has been resolved.

We know of an ongoing incident in Anguilla where we believe their core Internet lines have been accidentally severed - directly affecting the .AI Registry. At this time, we have been getting some updates from the Registry. However, a resolution to .AI is unknown at this time. As soon as we have an update, we will post it here. This affects: Domain Name Registrations Domain Name Transfers Domain Name Updates Domain Name Renewals (we will aim to ensure no domain names are affected and believe the Registry will automatically extend expiry dates to prevent any issues with domains entering their end-of-life grace periods) We appreciate everyone's patience while we work with the Registry but do speak to Support if there are any outstanding queries. - Matt McLeary, Customer Care

The issue has been identified and a fix is being implemented.

The registry connection / Internet to Anguilla has been restored. Testing has confirmed that the following actions are now operating as normal: Domain Name Registrations Domain Name Transfers Domain Name Updates Domain Name Renewals Do contact support if there are any queries relating to this outage.

At the moment our KeyDNS is not carrying out DNS Updates. This includes any updates to DNS zone files. Our system is continuing to accept commands, updates however are currently queued. All queries are working as expected. We're already busy implementing a fix. Thank you for your understanding.

DNS Updates are available again. A fix has been rolled out and DNS updates are available again. All queued commands are now processing. We keep monitoring the situation.

All operation is back to normal. This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

On Thursday December 15th, 2023 between 12:40 and 13:10 UTC after performing DNS adjustments [rrpproxy.net](http://rrpproxy.net) and [api.rrpproxy.net](http://api.rrpproxy.net) showed in our monitoring as only partially available from some locations. Our services were running without interruption, however connection attempts may have failed in some occasions. We kindly ask to pardon for all inconveniences caused. ## Timeline ### 12:40 UTC * Applying changes for [rrproxy.net](http://rrproxy.net) zone. * Changes deployed and shortly after DNS resolution stopped from some locations, caused by DNSSEC issues. ### 13:04 UTC * Issues still ongoing. * Zones slowly recovering but still seeing issues from some locations and partial availability. ### 13:10 UTC * All zones fully available again.

A fix has been implemented and we are monitoring the results.

# Statement for DNS Outage on 08 Nov 2022 between 07:25 and 09:25 CET ## Description Our DNS services at CentralNic Reseller had a service degradation with impact on domains using this service. This incident occurred on 08 Nov 2022 between 06:25 and 08:25 UTC. The impact was that resolution for hostnames using our DNS service was not fully available during this timeframe. A fix for the underlying issue has been implemented and the services are resuming normal operations. We will continue to monitor to ensure that the impact has been fully mitigated. ## Impact on Security No data has been corrupted. ## Follow Up Actions Will be discussed internally if other fixes are required to the DNS service.

Unfortunately at the moment RRPproxy is unreachable due to network issues. Our APIs and Web Interface are currently not reachable.

Reachability is coming back to normal operations. RRPproxy APIs and Web Interface are becoming available again. We're closely monitoring the issue and will provider further updates.

RRPproxy APIs and Web Interface reachable again. We continue to monitor the situation.

The underlying issue has been resolved. RRPproxy is back to normal operations, APIs and Web Interface fully reachable again. Please excuse any inconvenience caused.

# Statement for short RRPproxy outage on July 7th between 08:35 and 09:10 UTC ## Issue Summary During our regular maintenance on RRPproxy's LIVE system, we noticed high database load. As a result, all queries experienced a higher response time, slowing down all commands. The following were directly affected by this; API, the Web Interface and login for issuing commands wasn't possible for a short time. All domains continued to resolve without interruption. ## Timeline and Detailed Description of Impact ### 2022-07-07 08:35 \+0000 Maintenance work started. ### 2022-07-07 08:47 \+0000 RRPproxy slowly becoming unavailable, connections were not working reliable. High database load noticed. ### 2022-07-07 09:10 \+0000 Issue resolved, load decreased and RRPproxy became fully available again. ## Remediation The cause for the high database load has been identified quickly and resolved. RRPproxy returned to normal operations, re-instating full operability. ## No Impact on Data Security The data integrity remained fully, at no point in time any data has been compromised. \_\_ As always, we remain dedicated to your success and hope this background information supports your understanding for all that transpired. If you have any questions or would like to connect with our team, please always contact us at [[email protected]](mailto:[email protected]) Your RRPproxy Team ❤️