RIPE Network Coordination Centre incident
Reduced network redundancy following link failure
RIPE Network Coordination Centre experienced a minor incident on November 27, 2025 affecting RIPE Database and RPKI Dashboard and 1 more component, lasting 1d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Nov 27, 2025, 10:19 AM UTC
We are currently investigating this issue.
- investigating Nov 27, 2025, 10:21 AM UTC
We are continuing to investigate this issue.
- monitoring Nov 27, 2025, 10:29 AM UTC
Connectivity has been restored, and all services are operational. We are currently investigating the root cause.
- monitoring Nov 27, 2025, 10:57 AM UTC
The issue, caused by a network outage, has reoccurred. We are continuing to investigate this issue.
- monitoring Nov 27, 2025, 11:00 AM UTC
The issue, caused by a network outage, has reoccurred. We are continuing to investigate this issue.
- monitoring Nov 27, 2025, 12:01 PM UTC
We are continuing to monitor for any further issues.
- monitoring Nov 27, 2025, 01:21 PM UTC
We identified the likely underlying cause. A flapping link on one of our dark fibre connections between data centre locations disrupted our firewall cluster as well as other network components. The link subsequently failed completely. We are currently operating with reduced redundancy. An engineer from our dark fibre vendor is en route to verify the physical connection. We continue to monitor for any further issues.
- monitoring Nov 27, 2025, 03:40 PM UTC
We are awaiting further information from our dark fibre vendor.
- monitoring Nov 28, 2025, 10:23 AM UTC
The link has been fully restored, and the firewall cluster has recovered successfully. All systems are now operating normally, but we will keep monitoring them for the next few hours while we wait to receive a root‑cause explanation from the dark fibre vendor.
- resolved Nov 28, 2025, 11:57 AM UTC
The link is fully restored and services are stable. A post‑mortem will be published shortly.