Live / RIPE NCC / Incident
RIPE NCC: RIPEstat APIs unavailable
RIPE NCC · ripe.netCritical outageResolved2026-11-09 06:47 UTC
Public — what happened
Summary
RIPE NCC said several RIPEstat APIs, including the looking-glass and ris-peers services, became unavailable starting 12:51 UTC on 8 November 2026, and it classed the incident as critical. The company said the database behind the RIS looking glass had hit a configured limit on open files, which caused an internal API to use up its processing capacity. It reported the database recovered by 13:39 UTC and RIPEstat API speeds and throughput returned to near normal, although the looking-glass data kept catching up, with about a tenth of the peers on RRC25 still delayed that evening. RIPE NCC marked the incident resolved at 06:47 UTC on 9 November.
Affected
RIPEstat
Timeline
- Started — 2026-11-08 12:51 UTC
- Investigating — 2026-11-08 12:51 UTC
- Identified — 2026-11-08 13:20 UTC
- Monitoring — 2026-11-08 13:39 UTC (2 updates)
- Resolved — 2026-11-09 06:47 UTC · 17h 56m after it started
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 seeCustomers 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
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.