Live  /  Tenable  /  Incident

Tenable: Tenable One - Web Application Scanning: Scanner Management Filters Being Ignored

Tenable · tenable.comCritical outageResolved2026-11-13 01:58 UTC
Public — what happened

Summary

Tenable said that in its Tenable One Web Application Scanning product, filters were being disregarded when certain users managed their scanners, which could have affected bulk delete actions. The company began investigating at 16:40 UTC on 2026-11-12 and said it had identified the cause two minutes later. Tenable reported putting a fix in place at 21:17 UTC and monitoring it, and the incident was marked resolved at 01:58 UTC on 2026-11-13.

Affected

us-1a, us-2a, us-2b, us-3a, us-4a, us-5a, mssp-us-1 (us07), us08, ap-syd-1, br01, ca01, ca02, fra, in01, jp01, uk-lon-1, sing, gov01

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 47, 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.