Tenable incident

Tenable Cloud Security: Delay in Sync

Resolved after 23 hours 12 minutes, affecting AE1 and AU1 and 1 more, on March 30, 2026.

monitoring Mar 30, 2026, 02:38 PM UTC

the underlying cause has been addressed and sync operations are recovering

Started
Mar 30, 2026, 08:07 AM UTC
Resolved
Mar 31, 2026, 07:20 AM UTC
Duration
23h 12m
Detected by Pingoru
Mar 30, 2026, 08:07 AM UTC

Affected components

AE1AU1BR1CA1EU1IN1JP1KR1SG1UK1

Update timeline

  1. investigating Mar 30, 2026, 08:07 AM UTC

    We are aware of and actively investigating delays in sync operations that are impacting certain users. We will provide periodic updates as our engineers continue working on this issue.

  2. identified Mar 30, 2026, 10:09 AM UTC

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

  3. monitoring Mar 30, 2026, 02:38 PM UTC

    the underlying cause has been addressed and sync operations are recovering

  4. resolved Mar 31, 2026, 07:20 AM UTC

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

Your product runs on more than Tenable

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →