Live  /  Providers  /  Tenable

Tenable

tenable.comReporting incidents

Independent assessment — SquidGrid is not affiliated with Tenable. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

Security & identity · SquidGrid tracks Tenable’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Tenable is reporting

Current & recent incidents

investigating

Tenable Vulnerability Management: Scan Processing Delays

Major impact · 2026-09-28 09:51 UTC

identified

Tenable Vulnerability Management: Recast Rule Delays

Major impact · 2026-09-28 09:00 UTC

identified

Tenable One, Tenable Vulnerability Management, Cloud Security: Login and Platform Issues on UAE

Major impact · 2026-06-17 15:02 UTC · still open per the provider’s page — may be stale

Resolved

Vulcan Platform: Connector Normalization Failure (EU)

Major impact · 2026-09-24 12:01 UTC

Resolved

Tenable Vulnerability Management: Asset Tagging Issues

Minor impact · 2026-09-22 13:44 UTC

Resolved

Tenable One: Azure Cloud Connector Ingestion Issues

Major impact · 2026-09-18 10:44 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what Tenable has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Tenable runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Tenable is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Tenable.