Live  /  RIPE NCC  /  Incident

RIPE NCC: Issues with the RIPE Atlas probe controllig infrastructure

RIPE NCC · ripe.netMajor incidentResolved2026-11-11 15:12 UTC
Public — what happened

Summary

RIPE NCC reported a major incident affecting the infrastructure that controls RIPE Atlas probes, which began at 14:17 UTC on 2026-11-11. The company said it was investigating at first, and by 14:32 UTC it said a fix had been put in place and it was watching the results. RIPE NCC marked the incident resolved at 15:12, and its posts did not describe a cause.

Affected

RIPE Atlas

As listed on RIPE NCC’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 →

More from RIPE NCC

Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.

The full archive is on the RIPE NCC status & history page.

Related: RIPE NCC status & history. SquidGrid is not affiliated with RIPE NCC.