Live / RIPE NCC / Incident
RIPE NCC: RIS pipeline issue — not publishing update/bview files
RIPE NCC · ripe.netMinor incidentResolved2026-09-07 07:33 UTC
Public — what happened
Summary
RIPE NCC said its RIS data pipeline stopped publishing update and bview files for the RRC24 route collector, which is hosted at LACNIC in Uruguay, in an incident it rated minor that began on 2026-09-07 at 07:33 UTC. The company said the problem resembles one that hit the RRC18 collector over the preceding weekend and that it suspects the two share a cause, though it had not yet pinned that cause down. It also warned that other collectors could run into the same problem in the following hours or days. The status was still listed as investigating, although the facts give a resolution time of 2026-09-08 at 08:54.
Timeline
- Started — 2026-09-07 07:33 UTC
- Resolved — 2026-09-08 08:54 UTC · 25h 21m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach RIPE NCC against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for RIPE NCC: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the RIPE NCC report →
More from RIPE NCC
Covered in The Squid’s Ink, Week 38, 2026, our weekly internet health report.