Tenable incident

Errors encountered while using Asset/Search functions

Major Resolved View vendor source →
Started
Mar 24, 2026, 02:47 PM UTC
Resolved
Mar 24, 2026, 06:45 PM UTC
Duration
3h 58m
Detected by Pingoru
Mar 24, 2026, 02:47 PM UTC

Affected components

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

Update timeline

  1. investigating Mar 24, 2026, 02:47 PM UTC

    We are aware of and actively investigating customers seeing errors with Asset/Search functions. We will provide periodic updates as our engineers continue working on this issue.

  2. investigating Mar 24, 2026, 02:54 PM UTC

    We are continuing to investigate this issue.

  3. identified Mar 24, 2026, 04:17 PM UTC

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

  4. monitoring Mar 24, 2026, 04:22 PM UTC

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

  5. resolved Mar 24, 2026, 06:45 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