Live / RIPE NCC / Incident
RIPE NCC: RIPE Database web application returning intermittent errors
RIPE NCC · ripe.netMinor incidentResolved2026-10-08 08:21 UTC
Public — what happened
Summary
RIPE NCC reported that some requests to its RIPE Database web application were intermittently failing with 502 errors, an issue it rated as minor. The company began investigating at 07:46 UTC on 2026-10-07 and said a minute later that it had put a fix in place and was watching the results. RIPE NCC did not say what caused the problem, and the incident was marked resolved on 2026-10-08 at 08:21.
Affected
RIPE Database
Timeline
- Started — 2026-10-07 07:46 UTC
- Investigating — 2026-10-07 07:46 UTC (2 updates)
- Monitoring — 2026-10-07 07:47 UTC
- Resolved — 2026-10-08 08:21 UTC · 24h 36m 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 42, 2026, our weekly internet health report.