RIPE Network Coordination Centre incident
Intermittent availability of RIPE Access, RPKI dashboard, and other services that require login
Resolved after 19 minutes, affecting Billing & Payments and RPKI Dashboard and 1 more, on May 27, 2026.
The root cause for this was an engineer from our supplier performing work on another fiber in the same manhole as ours, and affecting our fiber in the process, causing it to disconnect for a couple of minutes. Everything recovered automatically after the fiber connection was restored. Unfortunately it did take about 30 minutes to complete. Required options to improve will be part of our Infrastructure plans.
Affected components
Update timeline
- investigating May 27, 2026, 08:26 AM UTC
We are currently investigating this issue.
- identified May 27, 2026, 08:36 AM UTC
We have identified the issue, the [explain the issue] and we are working to resolve it.
- monitoring May 27, 2026, 08:37 AM UTC
We have resolved the issue and continue to monitor the situation closely. We will share an update when it has been fully resolved.
- monitoring May 27, 2026, 08:38 AM UTC
We are continuing to monitor for any further issues.
- resolved May 27, 2026, 08:46 AM UTC
May 27, 10:46 CEST Resolved - We had a fiber issue between our data centers which also caused network problems for RIPE Access. The fiber issues seems to be fixed now and RIPE Access has also recovered. May 27, 10:38 CEST Update - We are continuing to monitor for any further issues. May 27, 10:37 CEST Monitoring - We have resolved the issue and continue to monitor the situation closely. We will share an update when it has been fully resolved. May 27, 10:36 CEST Identified - We have identified the issue, the [explain the issue] and we are working to resolve it. May 27, 10:26 CEST Investigating - We are currently investigating this issue.
- resolved May 27, 2026, 08:46 AM UTC
We had a fiber issue between our data centers which also caused network problems for RIPE Access. The fiber issues seems to be fixed now and RIPE Access has also recovered.
- postmortem Jun 09, 2026, 08:12 AM UTC
The root cause for this was an engineer from our supplier performing work on another fiber in the same manhole as ours, and affecting our fiber in the process, causing it to disconnect for a couple of minutes. Everything recovered automatically after the fiber connection was restored. Unfortunately it did take about 30 minutes to complete. Required options to improve will be part of our Infrastructure plans.
Your product runs on more than RIPE Network Coordination Centre
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.