RIPE Network Coordination Centre incident
delayed routing data in ripestat (except looking glass)
Resolved after 18 hours 33 minutes, affecting RIPEstat, on June 29, 2026.
The situation is improving. Some APIs are up to date. Other APIs (for example routing-status) still return stale or partial data. We will provide another update tomorrow morning.
Affected components
Update timeline
- monitoring Jun 29, 2026, 01:28 PM UTC
Jun 29, 15:28 CEST Identified - Most BGP data in RIPEstat, except for the Looking Glass, is currently delayed. This issue started on 26 June 2026. We have not processed new data since 26 June due to problems in our big data backend systems. A disruption in our ZooKeeper cluster prevented data from being processed. The zookeeper cluster was running, but a single type of data processing flow did not make progress. This affects the following RIPEstat APIs: * announced-prefixes * prefix-count * prefix-size-distribution * prefix-overview * prefix-routing-consistency * routing-history * routing-statistics * routing-status. Data processing has now resumed. We will share another update when we have an ETA for the backlog to clear. A monitoring gap delayed our detection of this issue. The RIS team is already working on improving the monitoring for the processing pipeline. We will also fix the monitoring gap for the ZooKeeper cluster that this issue uncovered.
- identified Jun 29, 2026, 01:28 PM UTC
Most BGP data in RIPEstat, except for the Looking Glass, is currently delayed. This issue started on 26 June 2026. We have not processed new data since 26 June due to problems in our big data backend systems. A disruption in our ZooKeeper cluster prevented data from being processed. The zookeeper cluster was running, but a single type of data processing flow did not make progress. This affects the following RIPEstat APIs: * announced-prefixes * prefix-count * prefix-size-distribution * prefix-overview * prefix-routing-consistency * routing-history * routing-statistics * routing-status. Data processing has now resumed. We will share another update when we have an ETA for the backlog to clear. A monitoring gap delayed our detection of this issue. The RIS team is already working on improving the monitoring for the processing pipeline. We will also fix the monitoring gap for the ZooKeeper cluster that this issue uncovered.
- identified Jun 29, 2026, 03:32 PM UTC
The situation is improving. Some APIs are up to date. Other APIs (for example routing-status) still return stale or partial data. We will provide another update tomorrow morning.
- resolved Jun 30, 2026, 08:02 AM UTC
Data processing has caught up. This incident has been resolved.
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.
Amazon Web Services