Live / ThousandEyes / Incident
ThousandEyes: Cloud and Enterprise Agents showing DNSSEC failures.
ThousandEyes · thousandeyes.comMajor incidentResolved2026-10-13 19:50 UTC
Public — what happened
Summary
ThousandEyes reported a major incident in which its Cloud and Enterprise Agents returned failure results on DNSSEC tests, which the company attributed to a problem with intermediate validation. ThousandEyes said the problem began at 14:00 UTC on October 11, 2026, posted its first update at 17:21 UTC, and said a fix was in place by 22:31 UTC that evening, after which it kept watching. On October 12 the company said further updates were going out to Enterprise Agents, noting that agents shown as online did not need action, while customers with offline Enterprise Agents were asked to contact standard support to update their settings by hand. The incident was marked resolved on October 13 at 19:50.
Affected
Agent Configuration and Data Collection, Cloud and Enterprise Agents: Data ingress
Timeline
- Started — 2026-10-11 17:21 UTC
- Identified — 2026-10-11 17:21 UTC (2 updates)
- Monitoring — 2026-10-11 22:31 UTC (2 updates)
- Resolved — 2026-10-13 19:50 UTC · 2 days 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 ThousandEyes 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 ThousandEyes: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the ThousandEyes report →
More from ThousandEyes
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.