Live / ThousandEyes / Incident
ThousandEyes: (FedRAMP) Usage and billing page data may experience delays
ThousandEyes · thousandeyes.comMinor incidentResolved2026-10-12 23:15 UTC
Public — what happened
Summary
ThousandEyes reported that its government (FedRAMP) service had a problem where the usage and billing page could display outdated information for some customers, which it rated as a minor issue. The company began investigating on October 9, 2026 at 20:14 UTC and said by 00:14 UTC on October 10 that it had put a fix in place and was watching the results. ThousandEyes said usage figures were then showing correctly with no further impact on customers, and it did not name a cause. The incident was marked resolved on October 12, 2026.
Affected
ThousandEyes Platform and API
Timeline
- Started — 2026-10-09 20:14 UTC
- Investigating — 2026-10-09 20:14 UTC
- Monitoring — 2026-10-10 00:14 UTC
- Resolved — 2026-10-12 23:15 UTC · 3 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.