Live / Tenable / Incident
Tenable: Tenable Vulnerability Management: Scan Processing Delays
Tenable · tenable.comMinor incidentResolved2026-11-06 14:36 UTC
Public — what happened
Summary
Tenable said that Tenable Vulnerability Management had delays in processing scans, which held up updated results for certain users. The company began investigating on November 4, 2026 at 20:00 UTC and later that evening said it had found the cause and was working on a fix. Tenable reported that a fix was in place by 00:24 UTC on November 5 and that it was monitoring the results, and the incident is now marked resolved as of November 6 at 14:36.
Affected
US-1A, US-2A, US-2B, US-3A, US-4A, US-5A, US07, AP-SYD-1, CA01, FRA, IN01, JP01, UK-LON-1
Timeline
- Started — 2026-11-04 20:00 UTC
- Investigating — 2026-11-04 20:00 UTC (4 updates)
- Monitoring — 2026-11-05 00:24 UTC
- Resolved — 2026-11-06 14:36 UTC · 42h 36m 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 46, 2026, our weekly internet health report.