Tenable had 67 outages in the last 2 years totaling 280h 19m of downtime — averaging 2.8 incidents per month.
There were 67 Tenable outages since October 13, 2025 totaling 280h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.
Dashboard data within Exposure Management has not updated in the past 24 hours. We are currently investigating this issue.
Our engineering team continues to investigate this issue.
This incident has been resolved.
Dashboards in Exposure Management are failing to load for non-admin users. We are currently investigating this issue.
Our engineering team continues to investigate this issue.
Our engineering team continues to investigate this issue.
The issue has been resolved. We are sorry for the disruption and inconvenience.
We are aware of and actively investigating login and performance issues currently impacting all functionality within all environments. The issue is related to an ongoing incident with our cloud service provider. We will provide periodic updates as our engineers continue working on this issue.
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
We have implemented a fix for the issue and are monitoring the recovery.
The issue has been resolved. We are sorry for the disruption and inconvenience.
We are aware of and actively investigating tag processing delays. We will provide periodic updates as our engineers continue working on this issue.
We are aware of and actively investigating tag processing delays. We will provide periodic updates as our engineers continue working on this issue.
We have implemented a fix for the issue and are monitoring the recovery.
We are continuing to monitor the recovery.
The issue has been resolved. We are sorry for the disruption and inconvenience.
We are aware of and actively investigating an issue with user counts showing as 0. We will provide periodic updates as our engineers continue working on this issue.
We have implemented a fix for the issue and are monitoring the recovery.
The issue has been resolved. We are sorry for the disruption and inconvenience.
We are aware of and actively investigating Tenable One Exposure Management third-party data connectors failing to sync. We will provide periodic updates as our engineers continue working on this issue.
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
We have implemented a fix for the issue and are monitoring the recovery.
We are continuing to monitor for any further issues.
The issue has been resolved. We are sorry for the disruption and inconvenience.
We are aware of and actively investigating an issue with scan processing delays in gov-01. We will provide periodic updates as our engineers continue working on this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
The issue has been resolved. We are sorry for the disruption and inconvenience.
We are aware of a delay in third party data processing and actively investigating the issue that is impacting certain users. We will provide periodic updates as our engineers continue working on this issue.
The issue has been resolved. We are sorry for the disruption and inconvenience.
We are aware of and actively investigating an issue causingscan vulnerability data to not show for certain users. We will provide periodic updates as our engineers continue working on this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are aware of and actively investigating an issue causing the number of licensed assets to temporarily display as 10,000 for certain users. We will provide periodic updates as our engineers continue working on this issue.
We are continuing to investigate this issue.
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
Our engineering team is continuing to work on a fix for this issue.
Our engineering team is continuing to work on a fix for this issue.
We have implemented a fix for the issue and are monitoring the recovery.
The issue has been resolved. We are sorry for the disruption and inconvenience.
We are aware of and actively investigating scan delays that are impacting for certain users in Azure. We will provide periodic updates as our engineers continue working on this issue. The issue is related to an ongoing incident with our cloud service provider.
We are continuing to investigate this issue.
Our cloud provider has identified the cause of the problem and is working to implement a fix for the issue.
We are continuing to work on a fix for this issue.
Our cloud provider has implemented a fix for the issue and we are now monitoring the recovery.
We are continuing to monitor for any further issues.
The issue has been resolved. We are sorry for the disruption and inconvenience.
We are aware of and actively investigating fields pertaining to Nessus Agents that do not have data for certain users. We will provide periodic updates as our engineers continue working on this issue.
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
We have implemented a fix for the issue and are monitoring the recovery.
Between 30/Oct 17:15UTC and 31/Oct 16:15UTC certain users may not have observed data in Nessus Agent last_connect and last_scanned fields. The issue has been resolved. We are sorry for the disruption and inconvenience.
We are aware of and actively investigating the HTTP 429 errors that are impacting the SentinelOne connector for certain customers. We will provide periodic updates as our engineers continue working on this issue.
The behavior observed earlier was limited in scope and did not reflect a platform-wide issue. While some functionality may be affected in limited scenarios, all core services remain available. Our teams are continuing to review and monitor the situation to ensure full and consistent performance.
We are aware of and actively investigating access issues resulting in 503's error messages that is impacting Attack Surface Management for certain users. We will provide periodic updates as our engineers continue working on this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
A fix has been implemented and we are monitoring the results.
The issue has been resolved. We are sorry for the disruption and inconvenience.
We are aware of and actively investigating login and performance issues currently impacting all functionality within environments us-1a, us-2a and us-2b. The issue is related to an ongoing incident with our cloud service provider. We will provide periodic updates as our engineers continue working on this issue.
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
We have implemented a fix for the issue and are monitoring the recovery.
We are continuing to monitor for any further issues.
We are aware of scan processing delays for some Tenable Vulnerability Management customers in us-2a and are also aware of degraded performance on us-1a and us-2a for some Tenable One customers.
We have implemented a fix for the issue and are monitoring the recovery.
The issue has been resolved. We are sorry for the disruption and inconvenience.