Live / Tenable / Incident
Tenable: Tenable Vulnerability Management: Scheduled Scans Not Launching
Tenable · tenable.comMajor incidentResolved2026-10-24 14:19 UTC
Public — what happened
Summary
Tenable reported a major problem with Tenable Vulnerability Management in which scheduled scans did not start for some users. The company said it began investigating on October 21, 2026 at 16:03 UTC, and by 19:28 UTC it said it had found the cause and was working on a fix. Tenable said it put a fix in place at 03:33 UTC on October 22 and was watching the recovery, and the incident was marked resolved on October 24 at 14:19.
Affected
US-1A, US-2A, US-2B, US-3A, US-4A, US08, CA01, IN01, JP01, UK-LON-1
Timeline
- Started — 2026-10-21 16:03 UTC
- Investigating — 2026-10-21 16:03 UTC
- Identified — 2026-10-21 19:28 UTC (2 updates)
- Monitoring — 2026-10-22 03:33 UTC
- Resolved — 2026-10-24 14:19 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 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 44, 2026, our weekly internet health report.