The issue has been resolved. We are sorry for the disruption and inconvenience.
Posted Dec 23, 2025 - 18:34 UTC
Update
We implemented a fix for the issue and continue to monitor the recovery.
Posted Dec 22, 2025 - 21:24 UTC
Update
We implemented a fix for the issue and continue to monitor the recovery.
Posted Dec 20, 2025 - 18:09 UTC
Monitoring
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.
Posted Dec 19, 2025 - 17:11 UTC
Update
Our engineering team is continuing to work on a fix for this issue.
Posted Dec 19, 2025 - 15:53 UTC
Update
Our engineering team is continuing to work on a fix for this issue.
Posted Dec 19, 2025 - 12:53 UTC
Update
Our engineering team is continuing to work on a fix for this issue.
Posted Dec 19, 2025 - 07:11 UTC
Update
Our engineering team is continuing to work on a fix for this issue.
Posted Dec 19, 2025 - 01:33 UTC
Update
We are continuing to work on a fix for this issue.
Posted Dec 18, 2025 - 22:39 UTC
Update
We are continuing to work on a fix for this issue.
Posted Dec 18, 2025 - 22:31 UTC
Update
We are continuing to work on a fix for this issue.
Posted Dec 18, 2025 - 22:31 UTC
Update
We are continuing to work on a fix for this issue.
Posted Dec 18, 2025 - 22:29 UTC
Update
Our engineering team is continuing to work on a fix for this issue.
Posted Dec 18, 2025 - 22:29 UTC
Update
Our engineering team is continuing to work on a fix for this issue.
Posted Dec 18, 2025 - 19:55 UTC
Identified
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
Posted Dec 18, 2025 - 17:01 UTC
Investigating
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.
Posted Dec 18, 2025 - 15:34 UTC
This incident affected: Tenable One (us-1a, us-2a, us-4a).