Tenable incident

Tenable Vulnerability Management: Failing Tag assessments and Aborted Scans using Tags

Major Resolved View vendor source →
Started
Apr 23, 2026, 07:25 PM UTC
Resolved
Apr 24, 2026, 07:08 PM UTC
Duration
23h 42m
Detected by Pingoru
Apr 23, 2026, 07:25 PM UTC

Affected components

AP-SYD-1BR01CA01FRAIN01JP01SINGUAE01UK-LON-1US-1AUS-2AUS-2BUS-3AUS-4AUS-5AUS07US08GOV01

Update timeline

  1. investigating Apr 23, 2026, 07:25 PM UTC

    We are aware of and actively investigating Tag assessment failing and scans aborting using tags as targets for certain users. We will provide periodic updates as our engineers continue working on this issue.

  2. identified Apr 23, 2026, 07:33 PM UTC

    We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.

  3. monitoring Apr 23, 2026, 08:50 PM UTC

    We have implemented a fix for the issue and are monitoring the recovery.

  4. monitoring Apr 24, 2026, 01:56 PM UTC

    We have implemented a fix for the issue and are continuing to monitor the recovery.

  5. resolved Apr 24, 2026, 07:08 PM UTC

    The issue has been resolved. We are sorry for the disruption and inconvenience.

Looking to track Tenable downtime and outages?

Pingoru polls Tenable's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Tenable reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Tenable alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Tenable for free

5 free monitors · No credit card required