Tenable incident

Tenable One : Stale Cloud Security Data and Licensed Asset Count in Tenable One

Major Resolved View vendor source →

Tenable experienced a major incident on June 4, 2026 affecting sing and us-1a and 1 more component, lasting 7h 4m. The incident has been resolved; the full update timeline is below.

Started
Jun 04, 2026, 06:57 AM UTC
Resolved
Jun 04, 2026, 02:02 PM UTC
Duration
7h 4m
Detected by Pingoru
Jun 04, 2026, 06:57 AM UTC

Affected components

singus-1aus-2aus-2bus-3aus-4aus-5amssp-us-1 (us07)us08ap-syd-1

Update timeline

  1. investigating Jun 04, 2026, 06:57 AM UTC

    We are aware of and actively investigating the issue of stale Cloud Security Data and stale Licensed Asset Count within Tenable One that are impacting certain users. We will provide periodic updates as our engineers continue working on this issue.

  2. monitoring Jun 04, 2026, 07:14 AM UTC

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

  3. resolved Jun 04, 2026, 02:02 PM UTC

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