RIPE NCC Academy, NRO and ASO Websites Temporarily Unavailable
Last updateresolvedOct 23 · 12:32 UTC
All services are back online.
Reported by RIPE NCC on their status page.

checked Oct 25, 2026 11:47 PM UTC · RIPE NCC's official status page
RIPE NCC has disruptions affecting RIPEstat.
Operational: RPKI.
Statusfield watches RIPE NCC alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.
10 reports published by RIPE NCC in the last 30 days · 1 still open
When RIPE NCC breaks, it is typically resolved in 1d 5h — median across 4 resolved incidents over 30 days.
resolvedOct 23 · 12:32 UTC
All services are back online.
Reported by RIPE NCC on their status page.
identifiedOct 20 · 17:12 UTC
Some data in RIPEstat is delayed due to an issue with RIPE RIS. This issue has to resolve before all data in RIPEstat is up to date again. The tracking issue for the root cause is https://status.ripe.net/incidents/09t7rwvhgm7l The impact of the delay differs per API endpoint. The looking glass should be up to date for the majority (>90%) of the peers, with metadata indicating the worst delay out of all the data present.
Reported by RIPE NCC on their status page.
resolvedOct 21 · 17:36 UTC
This incident has been resolved.
Reported by RIPE NCC on their status page.
resolvedOct 8 · 08:21 UTC
This incident has been resolved.
Reported by RIPE NCC on their status page.
resolvedOct 7 · 09:18 UTC
This incident has been resolved at 21.53 UTC of October 6th, 2026. Bview files were created normally.
Reported by RIPE NCC on their status page.
resolvedOct 2 · 12:51 UTC
This incident has been resolved.
Reported by RIPE NCC on their status page.
resolvedOct 2 · 08:57 UTC
Downgrading the package resolved the issue. We will review our patching policy, as this incident shows that security updates of packages can contain behavioural changes that affect production services.
Reported by RIPE NCC on their status page.
resolvedOct 6 · 06:44 UTC
This incident has been resolved. After the initial process recovered, the bview and update files since 2 October were produced successfully. The incident trigger was a high volume of updates from one peer. This caused load in a single kafka partition. When that process restarted, it hit a latent bug where it tried to re-scan a large volume of data on startup. This scan repeatedly timed out, which prevented the process from making progress. Additionally, due to a misconfiguration in the code, this scan took an order of magnitude longer than it should. After fixing this configuration issue the process recovered. We will work on a structural fix for the latent bug in the next sprint.
Reported by RIPE NCC on their status page.
resolvedSep 30 · 12:49 UTC
This incident has been resolved.
Reported by RIPE NCC on their status page.
resolvedSep 30 · 07:47 UTC
Authentication / logins have been working correctly since the last update.
Reported by RIPE NCC on their status page.