Live  /  RIPE NCC  /  Incident

RIPE NCC: Delayed bviews for rrc00

RIPE NCC · ripe.netMinor incidentResolved2026-11-11 06:35 UTC
Public — what happened

Summary

RIPE NCC said that routing data snapshots (bviews) for three of its collectors, rrc00, rrc03 and rrc24, would be delayed by several hours, and that update files for rrc00 and rrc03 were also affected. The company said the cause was a high volume of traffic from some peers, which it addressed by temporarily disconnecting some of them, and that an alerting gap outside office hours had hidden an earlier problem. By the evening of 10 November it reported the pipelines were recovering with only rrc00 bviews still delayed, and it planned a software change that week and a faster-recovery infrastructure change. The incident was marked resolved on 11 November at 06:35.

Affected

RIS (Routing Information Service)

As listed on RIPE NCC’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 47, 2026, our weekly internet health report.

The full archive is on the RIPE NCC status & history page.

Related: RIPE NCC status & history. SquidGrid is not affiliated with RIPE NCC.