Tenable incident
Tenable One - Exposure Management: Missing Attack Path Data
Tenable experienced a major incident on December 18, 2025 affecting us-1a and us-2a and 1 more component, lasting 5d 3h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Dec 18, 2025, 03:34 PM UTC
We are aware of and actively investigating missing attack path data for certain users. We will provide periodic updates as our engineers continue working on this issue.
- identified Dec 18, 2025, 05:01 PM UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
- identified Dec 18, 2025, 07:55 PM UTC
Our engineering team is continuing to work on a fix for this issue.
- identified Dec 18, 2025, 10:29 PM UTC
Our engineering team is continuing to work on a fix for this issue.
- identified Dec 18, 2025, 10:29 PM UTC
We are continuing to work on a fix for this issue.
- identified Dec 18, 2025, 10:31 PM UTC
We are continuing to work on a fix for this issue.
- identified Dec 18, 2025, 10:31 PM UTC
We are continuing to work on a fix for this issue.
- identified Dec 18, 2025, 10:39 PM UTC
We are continuing to work on a fix for this issue.
- identified Dec 19, 2025, 01:33 AM UTC
Our engineering team is continuing to work on a fix for this issue.
- identified Dec 19, 2025, 07:11 AM UTC
Our engineering team is continuing to work on a fix for this issue.
- identified Dec 19, 2025, 12:53 PM UTC
Our engineering team is continuing to work on a fix for this issue.
- identified Dec 19, 2025, 03:53 PM UTC
Our engineering team is continuing to work on a fix for this issue.
- monitoring Dec 19, 2025, 05:11 PM UTC
We have implemented a fix for the issue and are monitoring the recovery. Missing Attack Path data restoration is still in progress for affected customers.
- monitoring Dec 20, 2025, 06:09 PM UTC
We implemented a fix for the issue and continue to monitor the recovery.
- monitoring Dec 22, 2025, 09:24 PM UTC
We implemented a fix for the issue and continue to monitor the recovery.
- resolved Dec 23, 2025, 06:34 PM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.