Live / Tenable / Incident
Tenable: Tenable Vulnerability Management: Scan processing and Explore Findings and Asset pages delays
Tenable · tenable.comMajor incidentResolved2026-10-12 10:25 UTC
Public — what happened
Summary
Tenable reported a major incident in Tenable Vulnerability Management in which some users saw slowdowns in scan processing and in loading the Explore Findings and Asset pages, beginning at 06:47 UTC on October 12, 2026. About an hour later, the company said it had pinpointed the cause, though it did not describe what that cause was. Tenable said a fix was in place by 09:03 UTC, and after a period of watching the recovery, it marked the incident resolved at 10:25.
Affected
GOV01
Timeline
- Started — 2026-10-12 06:47 UTC
- Investigating — 2026-10-12 06:47 UTC
- Identified — 2026-10-12 07:47 UTC
- Monitoring — 2026-10-12 09:03 UTC
- Resolved — 2026-10-12 10:25 UTC · 3h 39m 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 43, 2026, our weekly internet health report.