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

As listed on Tenable’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Tenable status & history page.

Related: Tenable status & history. SquidGrid is not affiliated with Tenable.