Live  /  RIPE NCC  /  Incident

RIPE NCC: No new bview files being published

RIPE NCC · ripe.netMinor incidentResolved2026-08-25 21:20 UTC
Public — what happened

Summary

RIPE NCC reported a minor issue in which new bview files from its RIS routing data service stopped appearing, beginning on 2026-08-25 at 21:20 UTC. The organization said it learned from an outside notice that the 16:00 UTC files were missing, and acknowledged this exposed a weakness in its own monitoring that it plans to fix. According to RIPE NCC, the files had been created but were held back by a misconfigured part of its infrastructure after a failover. It said the problem was fixed and the missing files were being released, with the incident marked resolved on 2026-09-03 at 20:18 while still under monitoring.

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

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

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