RIPE Network Coordination Centre incident
RIS dump files (bview) for some RRC are not being generated
Resolved after 9 days 3 hours, affecting RIPEstat and RIS (Routing Information Service), on October 8, 2025.
Data processing for RIS has caught up. We are still processing RIS datasets for RIPEstat.
Affected components
Update timeline
- investigating Oct 08, 2025, 08:58 AM UTC
RIS dumps files for a list of collectors (rrc00, rrc12, rrc20, rrc21, rrc25, rrc26) are not being produced. These files, MRT TABLE_DUMP_V2 format (RFC 6396), are normally generated every 8 hours, at 0:00, 8:00, and 16:00 UTC. The latest available bview files for the mentioned RRCs were produced at 16.00 UTC of Tuesday October 7th. We are investigating.
- identified Oct 08, 2025, 11:14 AM UTC
The problem is caused by the processing of malformed BGP updates. These malformed BGP updates contain a 1024 bytes-long optional transitive attribute (OTC, type code 35), whereas the length should be 4 bytes.
- monitoring Oct 10, 2025, 04:06 PM UTC
We patched our code to seamlessly handle the packets with malformed OTC attribute. The backlog of data is now being processed.
- monitoring Oct 13, 2025, 05:54 PM UTC
All systems have recovered. We are re-processing the final datasets affected by this issue.
- monitoring Oct 15, 2025, 08:47 AM UTC
Data processing for RIS has caught up. We are still processing RIS datasets for RIPEstat.
- resolved Oct 17, 2025, 12:23 PM UTC
Data processing for RIPEstat has fully caught up.
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