RIPE Network Coordination Centre incident
rrc18 CATNIX, Barcelona: RIS update/bview files are not being published
Resolved after 2 days 15 hours, affecting RIS (Routing Information Service), on September 4, 2026.
The problem with RRC18 was resolved by restarting two services running in the backend, however the root cause is not clear yet. We keep troubleshooting. A similar problem is now affecting RRC24 at Montevideo, Uruguay.
Affected components
Update timeline
- monitoring Sep 04, 2026, 04:14 PM UTC
Sep 4, 18:14 CEST Investigating - RIS update files are not being published. The latest update file has a timestamp of September 4 at 13:35 UTC (updates.20260904.1335.gz)
- investigating Sep 04, 2026, 04:14 PM UTC
RIS update and bviews files are not being published. The latest update file has a timestamp of September 4 at 13:35 UTC (updates.20260904.1335.gz) The latest bview has a timestamp of September 4 at at 08:00 UTC (bview.20260904.0800.gz)
- investigating Sep 05, 2026, 09:54 AM UTC
Despite thorough analysis of the RRC18 message-processing pipeline, the root cause remains unidentified.
- monitoring Sep 05, 2026, 05:17 PM UTC
The missing RIS updates/bviews have been published. The pipeline for RRC18 is restored. We keep monitoring the situation.
- resolved Sep 07, 2026, 07:19 AM UTC
The problem with RRC18 was resolved by restarting two services running in the backend, however the root cause is not clear yet. We keep troubleshooting. A similar problem is now affecting RRC24 at Montevideo, Uruguay.
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