Live / Tenable / Incident
Tenable: Tenable Vulnerability Management: Cloud Scanner Plugin Update Issues
Tenable · tenable.comMinor incidentResolved2026-10-08 00:33 UTC
Public — what happened
Summary
Tenable reported a minor issue in Tenable Vulnerability Management in which the plugin sets on its cloud scanners appeared not to be updating, with the problem first posted at 20:09 UTC on October 6, 2026. Shortly afterward the company said its sites would go through roughly 15 minutes of maintenance and that users might need to retry manually launched scans once it ended. Tenable said it had found the cause by 20:16 UTC, and later that evening it stated the problem was only superficial and the cloud scanner plugin sets were in fact current. The incident was marked resolved on October 8, 2026.
Affected
US-1A, US-2A, US-2B, 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-06 20:09 UTC
- Investigating — 2026-10-06 20:09 UTC (2 updates)
- Identified — 2026-10-06 20:16 UTC (2 updates)
- Resolved — 2026-10-08 00:33 UTC · 28h 24m 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.