Tenable Outage History

Tenable experienced data ingest delays affecting asset and finding ingestion for certain users on the US-2A component. The incident lasted 8 minutes and was classified as minor. Engineers actively investigated the delays and the issue was resolved.

Tenable Vulnerability Management experienced a major incident where plugins were incorrectly appearing as 'unknown' in the GOV01 environment, affecting vulnerability scanning and reporting capabilities. The issue persisted for 17.2 hours before engineers implemented a fix and confirmed resolution after monitoring. The service has been fully restored with normal plugin identification functionality.

Tenable Vulnerability Management experienced service degradation on the us08 region that caused scans and tags to process slowly for certain users over a 38.9-hour period. The performance issues impacted scan functionality and processing times. Engineers implemented a fix and monitored the results before confirming full resolution of the service disruption.

Tenable's Vulcan Platform experienced a major service disruption affecting automatic connector syncs for EU region customers for 45.9 hours. The issue prevented connectors from triggering automatic synchronization processes as expected. Engineers implemented a fix and monitored the recovery before fully resolving the incident.

Tenable Cloud Security experienced scan delays affecting Oracle Cloud Infrastructure (OCI) customers for 23.6 hours. The engineering team investigated the issue throughout the incident period. The problem was resolved with normal scanning operations restored.

Tenable Vulnerability Management experienced a major incident where tag assessments were failing and scans using tags as targets were aborting for certain users across multiple global regions. The issue affected 14 components including regions in Australia, Canada, Europe, Japan, Singapore, UK, US, India, Brazil, and government clouds. After 23.8 hours, engineers identified the root cause, implemented a fix, and fully resolved the service disruption.

Tenable One experienced a major incident where the Connectors view in Tenable Exposure Management failed to load correctly for users. The engineering team identified the root cause and implemented a fix to restore full functionality. The incident lasted 2.2 hours before being fully resolved.

Tenable's Cloud Security service experienced a major issue where Linux risks were being incorrectly mitigated for 10.4 hours on April 22, 2026. The engineering team identified the root cause and implemented a fix, with the service fully restored after a monitoring period.

Tenable Vulnerability Management experienced an issue where stale vulnerability findings were displayed in the Explore Findings page, impacting certain users for 6.2 hours. The affected component IN01 prevented users from seeing current vulnerability data. The issue was resolved after engineers deployed a fix and monitored the recovery.

Tenable experienced 503 errors that prevented certain users from accessing cloud.tenable.com and related services across multiple global regions including US, UK, Australia, Germany, Japan, Singapore, India, Brazil, Canada, and government instances. The incident affected Tenable One and Tenable Vulnerability Management platforms for 2 hours. Engineers identified the root cause, implemented a fix, and fully resolved the access issues.