Live / Tenable / Incident
Tenable: Tenable Vulnerability Management: Scheduled Scans Not Launching
Tenable · tenable.comMajor incidentResolved2026-10-09 08:26 UTC
Public — what happened
Summary
Tenable reported a major problem in Tenable Vulnerability Management where scheduled scans were not starting for some users, beginning on October 8, 2026 at 19:10 UTC. Within minutes the company said it had found the cause, though it did not describe what that cause was, and by 19:52 UTC it said a fix was being rolled out. The incident was marked resolved on October 9, 2026 at 08:26.
Affected
US-1A, US-2A, US-3A, US-4A, US-5A, US07, US08, AP-SYD-1, BR01, CA01, FRA, IN01, JP01, UK-LON-1, SING, GOV01, ca02
Timeline
- Started — 2026-10-08 19:10 UTC
- Investigating — 2026-10-08 19:10 UTC (2 updates)
- Identified — 2026-10-08 19:52 UTC
- Resolved — 2026-10-09 08:26 UTC · 13h 16m 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 42, 2026, our weekly internet health report.