RIPE NCC: No new bview files being published

RIPE NCC · ripe.netImpact: minorResolved2026-08-25 21:20 UTC

Public — what happened

Summary

We were notified that the 16:00 UTC RIS bview files had not been published. This highlighted a gap in our monitoring, which we will address as a priority. The files were generated but were not published due to an infrastructure misconfiguration following a failover. The issue has been resolved, and the missing files are now being published.

Timeline

Started — 2026-08-25 21:20 UTC
Last update — 2026-08-25 21:20 UTC
Resolved — 2026-09-03 20:18 UTC

Source of record: provider status page. Mirrored as reported; times in UTC.

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 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 →

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