Live / Tenable / Incident
Tenable: Tenable One: Delay in Tenable Exposure Management data
Tenable · tenable.comMajor incidentResolved2026-10-16 11:55 UTC
Public — what happened
Summary
Tenable said some users of Tenable One saw delayed data in Exposure Management, and it began investigating at 06:50 UTC on October 14. The company said the problem was related to an ongoing incident at its service provider. By 12:00 UTC Tenable said it had identified the cause and was working on a fix, and at 21:16 UTC it said a fix was in place and it was watching the recovery. The incident was marked resolved on October 16 at 11:55.
Affected
us-5a, us08
Timeline
- Started — 2026-10-14 06:50 UTC
- Investigating — 2026-10-14 06:50 UTC
- Identified — 2026-10-14 12:00 UTC (2 updates)
- Monitoring — 2026-10-14 21:17 UTC
- Resolved — 2026-10-16 11:55 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 Tenable 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 Tenable: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Tenable report →
More from Tenable
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.