Live  /  RIPE NCC  /  Incident

RIPE NCC: RIS bview/update files are delayed

RIPE NCC · ripe.netMinor incidentResolved2026-10-21 17:36 UTC
Public — what happened

Summary

RIPE NCC said its RIS service, which publishes routing data files, had delayed snapshot (bview) and update files, starting around 06:09 UTC on 20 October. The company said it found two separate problems: one with a storage component that affected copying the snapshot files, and one where some messages collected at the RRC25 location were clogging the data pipeline. It reported that update files were published by the evening of 20 October and that snapshot creation had mostly caught up by the morning of 21 October, with RRC12 still missing its latest midnight file. RIPE NCC marked the incident resolved at 17:36 on 21 October.

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 44, 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.