Live / Tenable / Incident
Tenable: Tenable Vulnerability Management: Scan Processing delays in FRA
Tenable · tenable.comMajor incidentResolved2026-11-14 09:14 UTC
Public — what happened
Summary
Tenable said its Vulnerability Management service was running slowly when processing scans on its FRA site, and it classed the incident as major. The company began investigating at 07:09 UTC on 2026-11-14 and said at 07:31 UTC that it had found the cause of the problem. It reported putting a fix in place at 08:44 UTC and watching the recovery, and the incident was marked resolved at 09:14 UTC.
Affected
FRA, fra, fra, fra
Timeline
- Started — 2026-11-14 07:09 UTC
- Investigating — 2026-11-14 07:09 UTC (2 updates)
- Identified — 2026-11-14 07:31 UTC
- Investigating — 2026-11-14 08:36 UTC
- Monitoring — 2026-11-14 08:44 UTC
- Resolved — 2026-11-14 09:14 UTC · 2h 05m 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 47, 2026, our weekly internet health report.