RIPE Network Coordination Centre incident

Delayed RIS updates for rrc00/rrc03, delayed bviews for rrc00/rrc03/rrc24

Ongoing since 08:13 AM UTC, affecting RIS (Routing Information Service).

identified Nov 10, 2026, 09:26 AM UTC

We realised update files for rrc00/rrc03 are also affected. We were aware of an earlier issue but assumed it recovered. However, in practice the issue was masked because of alerts not sending the message to chat outside office hours. Alerts are routed to mobile phones. Some alerts are office hours only. When writing the initial update this morning we did not realise that an office hours only alert was also masked from the chat channel that contains paging alerts. We are continuing to work on this issue.

Started
Nov 10, 2026, 08:13 AM UTC
Resolved
Ongoing
Duration
● 3h 46m
Detected by Pingoru
Nov 10, 2026, 08:13 AM UTC

Affected components

RIS (Routing Information Service)

Update timeline

  1. identified Nov 10, 2026, 08:13 AM UTC

    The next bviews (08:00 UTC) for rrc00, rrc03, and rrc24 will be delayed by multiple hours due to a high volume of traffic from some peers. We intervened by temporarily de-peering some peers yesterday. However, we are still processing a backlog of traffic.

  2. identified Nov 10, 2026, 09:26 AM UTC

    We realised update files for rrc00/rrc03 are also affected. We were aware of an earlier issue but assumed it recovered. However, in practice the issue was masked because of alerts not sending the message to chat outside office hours. Alerts are routed to mobile phones. Some alerts are office hours only. When writing the initial update this morning we did not realise that an office hours only alert was also masked from the chat channel that contains paging alerts. We are continuing to work on this issue.

Your product runs on more than RIPE Network Coordination Centre

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →