Resolved after 2 days, affecting RIS (Routing Information Service), on June 20, 2026.
We applied a mitigation and RIS update file production, including the backfill of affected data, recovered on Saturday, 20 June, at around 15:35 UTC. The root cause was a process that had become stuck. A gap in our monitoring after the recent migration means we did not detect this. We have now fixed that monitoring gap. This incident has been resolved.
Affected components
Update timeline
- monitoring Jun 20, 2026, 02:24 PM UTC
Jun 20, 16:24 CEST Investigating - We are seeing issues with the production of RIS update files for our RRCs. The issue is under investigation, we will resolve this problem and backfill data at our earliest convenience. Once more updates are available, we will share them here.
- investigating Jun 20, 2026, 02:24 PM UTC
We are seeing issues with the production of RIS update files for our RRCs. The issue is under investigation, we will resolve this problem and backfill data at our earliest convenience. Once more updates are available, we will share them here.
- resolved Jun 22, 2026, 02:34 PM UTC
We applied a mitigation and RIS update file production, including the backfill of affected data, recovered on Saturday, 20 June, at around 15:35 UTC. The root cause was a process that had become stuck. A gap in our monitoring after the recent migration means we did not detect this. We have now fixed that monitoring gap. 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