RIPE NCC: RIS: RRC12 MRT update files are not produced

RIPE NCC · ripe.netImpact: minoridentified2026-10-02 11:26 UTC

Public — what happened

Summary

At 1.30UTC, on October 2nd, 2026, a DE-CIX peer started sending an unusually high number of BGP messages to RRC12. Our processing pipeline consuming from kafka did not keep up with this volume of updates, causing a process to time out. When this process restarts, it times out again before making enough progress. We are now observing an impact on the production of other RRCs updates files, that are being delayed. We are troubleshooting this issue.

Timeline

Started — 2026-10-02 07:42 UTC
Last update — 2026-10-02 11:26 UTC
Ongoing at last check.

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.