Live / Tenable / Incident
Tenable: Tenable Vulnerability Management: Delay in Findings
Tenable · tenable.comMajor incidentResolved2026-11-06 14:35 UTC
Public — what happened
Summary
Tenable reported a major incident in which vulnerability findings in Tenable Vulnerability Management were showing up late for some users. The company said it began investigating at 07:30 UTC on November 4, 2026, and about three hours later said it had identified the cause and was working on a fix. By 15:32 UTC that day Tenable said a fix was in place and it was watching the recovery, and the incident was marked resolved on November 6 at 14:35.
Affected
FRA
Timeline
- Started — 2026-11-04 07:30 UTC
- Investigating — 2026-11-04 07:30 UTC
- Identified — 2026-11-04 10:11 UTC
- Monitoring — 2026-11-04 15:32 UTC
- Resolved — 2026-11-06 14:35 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 46, 2026, our weekly internet health report.