Tenable Outage History

Tenable major outage · 1 active incident View live status →

Tenable had 67 outages in the last 2 years totaling 730h 20m of downtime — averaging 2.8 incidents per month.

There were 67 Tenable outages since October 13, 2025 totaling 730h 20m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tenable.com

Major March 26, 2026

Tenable Vulnerability Management: Scan Processing Delays (US2A,US5A,US08)

Detected by Pingoru
Mar 26, 2026, 05:10 AM UTC
Resolved
Mar 28, 2026, 07:27 PM UTC
Duration
2d 14h
Affected: US-2AUS-5AUS08
Timeline · 4 updates
  1. investigating Mar 26, 2026, 05:10 AM UTC

    We are aware of and actively investigating scan processing delays that are impacting scan times for certain users. We will provide periodic updates as our engineers continue working on this issue.

  2. investigating Mar 26, 2026, 07:11 AM UTC

    Our engineering team continues to investigate this issue.

  3. monitoring Mar 26, 2026, 06:17 PM UTC

    We have implemented a fix for the issue and are monitoring the recovery.

  4. resolved Mar 28, 2026, 07:27 PM UTC

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

Read the full incident report →

Major March 25, 2026

Tenable Vulnerability Management: Performance Degradation in Scan Management on US08

Detected by Pingoru
Mar 25, 2026, 09:47 AM UTC
Resolved
Mar 28, 2026, 07:27 PM UTC
Duration
3d 9h
Affected: US08
Timeline · 4 updates
  1. investigating Mar 25, 2026, 09:47 AM UTC

    We are aware of and actively investigating performance degradation that is impacting scan management. We will provide periodic updates as our engineers continue working on this issue.

  2. investigating Mar 25, 2026, 12:15 PM UTC

    Our engineering team continues to investigate this issue.

  3. monitoring Mar 25, 2026, 04:04 PM UTC

    We have implemented a fix for the issue and are monitoring the recovery.

  4. resolved Mar 28, 2026, 07:27 PM UTC

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

Read the full incident report →

Major March 24, 2026

Errors encountered while using Asset/Search functions

Detected by Pingoru
Mar 24, 2026, 02:47 PM UTC
Resolved
Mar 24, 2026, 06:45 PM UTC
Duration
3h 58m
Affected: AP-SYD-1BR01CA01FRAIN01JP01SINGUK-LON-1US-1AUS-2AUS-2BUS-3AUS-4AUS-5AUS07US08GOV01
Timeline · 5 updates
  1. investigating Mar 24, 2026, 02:47 PM UTC

    We are aware of and actively investigating customers seeing errors with Asset/Search functions. We will provide periodic updates as our engineers continue working on this issue.

  2. investigating Mar 24, 2026, 02:54 PM UTC

    We are continuing to investigate this issue.

  3. identified Mar 24, 2026, 04:17 PM UTC

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

  4. monitoring Mar 24, 2026, 04:22 PM UTC

    We have implemented a fix for the issue and are monitoring the recovery.

  5. resolved Mar 24, 2026, 06:45 PM UTC

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

Read the full incident report →

Major March 19, 2026

Elevated error rates

Detected by Pingoru
Mar 19, 2026, 04:54 PM UTC
Resolved
Mar 19, 2026, 06:07 PM UTC
Duration
1h 13m
Affected: US08
Timeline · 3 updates
  1. identified Mar 19, 2026, 04:54 PM UTC

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

  2. monitoring Mar 19, 2026, 04:55 PM UTC

    We have implemented a fix for the issue and are monitoring the recovery.

  3. resolved Mar 19, 2026, 06:07 PM UTC

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

Read the full incident report →

Major March 18, 2026

Tenable Vulnerability Management: API Degradation

Detected by Pingoru
Mar 18, 2026, 04:43 AM UTC
Resolved
Mar 18, 2026, 02:47 PM UTC
Duration
10h 3m
Affected: AP-SYD-1BR01CA01FRAIN01JP01SINGUAE01UK-LON-1US-1AUS-2AUS-2BUS-3AUS-4AUS-5AUS07US08GOV01
Timeline · 4 updates
  1. investigating Mar 18, 2026, 04:43 AM UTC

    We are aware of and actively investigating issues with asset bulk-jobs API endpoints that are impacting certain users.We will provide periodic updates as our engineers continue working on this issue.

  2. identified Mar 18, 2026, 06:19 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 18, 2026, 06:31 AM UTC

    We have implemented a fix for the issue and are monitoring the recovery.

  4. resolved Mar 18, 2026, 02:47 PM UTC

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

Read the full incident report →

Critical March 12, 2026

Tenable One, Tenable Vulnerability Manager: Onboarding issues with US08

Detected by Pingoru
Mar 12, 2026, 02:38 PM UTC
Resolved
Mar 12, 2026, 05:14 PM UTC
Duration
2h 36m
Affected: us08US08
Timeline · 2 updates
  1. investigating Mar 12, 2026, 02:38 PM UTC

    We are aware of and actively investigating issues with us08 site that are impacting onboarding for certain users. We will provide periodic updates as our engineers continue working on this issue.

  2. resolved Mar 12, 2026, 05:14 PM UTC

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

Read the full incident report →

Critical March 10, 2026

Tenable One, Tenable Vulnerability Management, Cloud Security: Authentication issues

Detected by Pingoru
Mar 10, 2026, 07:22 PM UTC
Resolved
Mar 10, 2026, 08:28 PM UTC
Duration
1h 5m
Affected: AP-SYD-1AE1BR01singAU1CA01BR1us-1aFRACA1us-2aIN01EU1us-2bJP01us-3aSINGIN1us-4aJP1UAE01us-5aUK-LON-1KR1mssp-us-1 (us07)US-1ASG1us08US-2AUK1ap-syd-1US-2BUS1br01US-3AUSGov1ca01US-4AfraUS-5Ain01US07jp01US08uk-lon-1GOV01gov01uae01
Timeline · 7 updates
  1. investigating Mar 10, 2026, 07:22 PM UTC

    We are aware of and actively investigating latency issues that are impacting Tenable.VM for users with SAML on multiple sites. We will provide periodic updates as our engineers continue working on this issue.

  2. investigating Mar 10, 2026, 07:22 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 10, 2026, 07:29 PM UTC

    We are continuing to investigate this issue.

  4. investigating Mar 10, 2026, 07:34 PM UTC

    We are continuing to investigate this issue.

  5. investigating Mar 10, 2026, 07:39 PM UTC

    We are continuing to investigate this issue.

  6. monitoring Mar 10, 2026, 08:08 PM UTC

    We have implemented a fix for the issue and are monitoring the recovery.

  7. resolved Mar 10, 2026, 08:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 6, 2026

Tenable One, Tenable Vulnerability Management, Cloud Security: Service Degradation on US-1A/US-2A

Detected by Pingoru
Mar 06, 2026, 07:59 PM UTC
Resolved
Mar 09, 2026, 05:30 PM UTC
Duration
2d 21h
Affected: us-1aus-2aUS-1AUS-2AUS1
Timeline · 3 updates
  1. investigating Mar 06, 2026, 07:59 PM UTC

    We are aware of and actively investigating service disruptions affecting periodic site access or scans / viewing results delays for certain users. We will provide periodic updates as our engineers continue working on this issue.

  2. monitoring Mar 06, 2026, 10:38 PM UTC

    We have implemented a fix for the issue and are monitoring the recovery.

  3. resolved Mar 09, 2026, 05:30 PM UTC

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

Read the full incident report →

Major February 13, 2026

Tenable Patch Management: SSO Not Working

Detected by Pingoru
Feb 13, 2026, 05:32 PM UTC
Resolved
Feb 13, 2026, 07:23 PM UTC
Duration
1h 51m
Timeline · 4 updates
  1. investigating Feb 13, 2026, 05:32 PM UTC

    We are aware of and actively investigating an issue with SSO not working for SaaS instances of Tenable Patch Management. We will provide periodic updates as our engineers continue working on this issue.

  2. identified Feb 13, 2026, 05:35 PM UTC

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

  3. monitoring Feb 13, 2026, 05:59 PM UTC

    We have implemented a fix for the issue and are monitoring the recovery.

  4. resolved Feb 13, 2026, 07:23 PM UTC

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

Read the full incident report →

Major February 12, 2026

Tenable Cloud Security: Tenable CS Web UI issues on EU1

Detected by Pingoru
Feb 12, 2026, 01:47 PM UTC
Resolved
Feb 12, 2026, 05:32 PM UTC
Duration
3h 44m
Affected: EU1
Timeline · 4 updates
  1. investigating Feb 12, 2026, 01:47 PM UTC

    We are aware of and actively investigating Web UI issues that are impacting certain users. We will provide periodic updates as our engineers continue working on this issue.

  2. identified Feb 12, 2026, 03:30 PM UTC

    We have identified the cause of the problem. Our engineering team is working with our downstream provider to fix the issue.

  3. monitoring Feb 12, 2026, 04:58 PM UTC

    A fix for the issue has been implemented and we are monitoring the recovery.

  4. resolved Feb 12, 2026, 05:32 PM UTC

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

Read the full incident report →

Major January 26, 2026

Connectors View not loading in T.EM

Detected by Pingoru
Jan 26, 2026, 02:04 PM UTC
Resolved
Jan 26, 2026, 03:23 PM UTC
Duration
1h 18m
Affected: singus-1aus-2aus-2bus-3aus-4aus-5amssp-us-1 (us07)us08ap-syd-1br01ca01frain01jp01uk-lon-1gov01uae01
Timeline · 3 updates
  1. investigating Jan 26, 2026, 02:04 PM UTC

    We are aware of and currently investigating an issue around the 'Connectors' view not loading correctly in Tenable Exposure Management. We will provide periodic updates as our engineers continue working on this issue.

  2. monitoring Jan 26, 2026, 02:05 PM UTC

    We have implemented a fix for the issue and are monitoring the recovery.

  3. resolved Jan 26, 2026, 03:23 PM UTC

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

Read the full incident report →

Major January 21, 2026

Tenable Vulnerability Management: Recast Rules processing issues

Detected by Pingoru
Jan 21, 2026, 12:53 PM UTC
Resolved
Jan 23, 2026, 01:17 AM UTC
Duration
1d 12h
Affected: AP-SYD-1BR01CA01FRAIN01JP01SINGUAE01UK-LON-1US-1AUS-2AUS-2BUS-3AUS-4AUS-5AUS07US08GOV01
Timeline · 6 updates
  1. investigating Jan 21, 2026, 12:53 PM UTC

    We are aware of and actively investigating issues with Recast Rule processing and management for certain users on all sites. Customers may experience delays in rules being applied to findings or errors when attempting to create/modify rules. We will provide periodic updates as our engineers continue working on this issue.

  2. investigating Jan 21, 2026, 12:54 PM UTC

    We are continuing to investigate this issue.

  3. identified Jan 21, 2026, 01:54 PM UTC

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

  4. monitoring Jan 21, 2026, 08:26 PM UTC

    We have implemented a fix for the issue and are monitoring the recovery.

  5. monitoring Jan 21, 2026, 09:34 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Jan 23, 2026, 01:17 AM UTC

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

Read the full incident report →

Major January 21, 2026

Tenable Vulnerability Management: Scan Processing delay

Detected by Pingoru
Jan 21, 2026, 06:50 AM UTC
Resolved
Jan 22, 2026, 03:03 PM UTC
Duration
1d 8h
Affected: FRAUS-1AUS-2AUS-3AUS07US08
Timeline · 3 updates
  1. investigating Jan 21, 2026, 06:50 AM UTC

    We are aware of and actively investigating delays with scan processing that are impacting for certain users. We will provide periodic updates as our engineers continue working on this issue.

  2. monitoring Jan 21, 2026, 10:46 AM UTC

    We have implemented a fix for the issue and are monitoring the recovery.

  3. resolved Jan 22, 2026, 03:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 18, 2026

Login issues

Detected by Pingoru
Jan 18, 2026, 03:17 AM UTC
Resolved
Jan 18, 2026, 04:06 AM UTC
Duration
48m
Affected: ca01
Timeline · 4 updates
  1. investigating Jan 18, 2026, 03:17 AM UTC

    We are aware of and actively investigating Login issues that are impacting logging in to cloud platform. We will provide periodic updates as our engineers continue working on this issue.

  2. identified Jan 18, 2026, 03:37 AM UTC

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

  3. monitoring Jan 18, 2026, 03:43 AM UTC

    We have implemented a fix for the issue and are monitoring the recovery.

  4. resolved Jan 18, 2026, 04:06 AM UTC

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

Read the full incident report →

Minor January 16, 2026

Scan processing delays for long running scans

Detected by Pingoru
Jan 16, 2026, 11:34 PM UTC
Resolved
Jan 17, 2026, 03:31 PM UTC
Duration
15h 57m
Affected: us-4a
Timeline · 5 updates
  1. investigating Jan 16, 2026, 11:34 PM UTC

    We are aware of and actively investigating scan latencies issues that are impacting scan processing on long running scans for certain users. We will provide periodic updates as our engineers continue working on this issue.

  2. investigating Jan 17, 2026, 02:14 AM UTC

    Our engineering team continues to investigate this issue.

  3. investigating Jan 17, 2026, 04:19 AM UTC

    Our engineering team continues to investigate this issue.

  4. investigating Jan 17, 2026, 06:51 AM UTC

    Our engineering team continues to investigate this issue.

  5. resolved Jan 17, 2026, 03:31 PM UTC

    Scan latencies issues impacting scan processing on long running scans for certain issues has now been resolved.

Read the full incident report →

Major January 13, 2026

Tenable Web Application Scanning: Scans stay in "Pending"

Detected by Pingoru
Jan 13, 2026, 11:09 AM UTC
Resolved
Jan 15, 2026, 01:07 AM UTC
Duration
1d 13h
Affected: AP-SYD-1BR01CA01FRAIN01JP01SINGUAE01UK-LON-1US-1AUS-2AUS-2BUS-3AUS-4AUS-5AUS07US08
Timeline · 8 updates
  1. investigating Jan 13, 2026, 11:09 AM UTC

    We are aware of and actively investigating an issue with WAS scans appearing to stay in "Pending" status for certain users. We will provide periodic updates as our engineers continue working on this issue.

  2. investigating Jan 13, 2026, 11:12 AM UTC

    We are continuing to investigate this issue.

  3. investigating Jan 13, 2026, 03:21 PM UTC

    We are continuing to investigate this issue.

  4. identified Jan 14, 2026, 01:25 AM UTC

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

  5. identified Jan 14, 2026, 08:38 AM UTC

    Our engineering team is continuing to work on a fix for this issue.

  6. identified Jan 14, 2026, 02:31 PM UTC

    We are continuing to work on a fix for this issue.

  7. monitoring Jan 14, 2026, 11:47 PM UTC

    We have implemented a fix for the issue and are monitoring the recovery.

  8. resolved Jan 15, 2026, 01:07 AM UTC

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

Read the full incident report →

Minor January 5, 2026

Vulcan Platform: Inability to Open Support Tickets Via Email

Detected by Pingoru
Jan 05, 2026, 11:42 AM UTC
Resolved
Jan 06, 2026, 07:18 AM UTC
Duration
19h 36m
Affected: USEU
Timeline · 3 updates
  1. investigating Jan 05, 2026, 11:42 AM UTC

    We are aware of and actively investigating erros that are impacting opening ticket to Vulcan support team via email. You may open tickets via the support form URL: https://support.vulcan.io/

  2. identified Jan 05, 2026, 05:04 PM UTC

    We have identified the issue and are currently working on a fix. You may also open tickets via the support form URL: https://support.vulcan.io/

  3. resolved Jan 06, 2026, 07:18 AM UTC

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

Read the full incident report →

Major January 1, 2026

Tenable Vulnerability Management: Scan Processing Delays on BR01

Detected by Pingoru
Jan 01, 2026, 05:38 AM UTC
Resolved
Jan 01, 2026, 11:31 PM UTC
Duration
17h 53m
Affected: BR01
Timeline · 3 updates
  1. investigating Jan 01, 2026, 05:38 AM UTC

    We are aware of and actively investigating an issue with scan processing delays. We will provide periodic updates as our engineers continue working on this issue.

  2. monitoring Jan 01, 2026, 07:44 AM UTC

    We have observed that system performance and error rates have returned to nominal levels. We are currently monitoring the services to ensure stability is maintained.

  3. resolved Jan 01, 2026, 11:31 PM UTC

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

Read the full incident report →

Major December 31, 2025

Tenable Vulnerability Management: Scan delays and Scan jobs aborting

Detected by Pingoru
Dec 31, 2025, 02:37 AM UTC
Resolved
Dec 31, 2025, 07:50 PM UTC
Duration
17h 13m
Affected: AP-SYD-1BR01CA01FRAIN01JP01SINGUAE01UK-LON-1US-1AUS-2AUS-2BUS-3AUS-4AUS-5AUS07US08GOV01
Timeline · 5 updates
  1. investigating Dec 31, 2025, 02:37 AM UTC

    We are aware of and actively investigating an issue with scan delays. We will provide periodic updates as our engineers continue working on this issue.

  2. investigating Dec 31, 2025, 03:47 AM UTC

    We are aware of and actively investigating scan delays and scan jobs aborting that are impacting Cloud Scanners for certain users. We will provide periodic updates as our engineers continue working on this issue.

  3. identified Dec 31, 2025, 04:19 AM UTC

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

  4. monitoring Dec 31, 2025, 05:34 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Dec 31, 2025, 07:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 22, 2025

Vulcan Platform: US Region Partial Outage

Detected by Pingoru
Dec 22, 2025, 03:13 PM UTC
Resolved
Dec 23, 2025, 04:27 PM UTC
Duration
1d 1h
Affected: US
Timeline · 6 updates
  1. investigating Dec 22, 2025, 03:13 PM UTC

    We are aware of and actively investigating UI issue that is impacting the findings, vulnerabilities and assets pages for certain users. We will provide periodic updates as our engineers continue working on this issue.

  2. investigating Dec 22, 2025, 04:21 PM UTC

    Our engineering team continues to investigate this issue.

  3. monitoring Dec 22, 2025, 05:24 PM UTC

    We have implemented a fix for the issue and are monitoring the recovery. The Findings, Vulnerabilities and Assets pages are currently available.

  4. monitoring Dec 23, 2025, 11:30 AM UTC

    The issue remains under investigation. We are closely monitoring the situation and continuing work toward a permanent fix.

  5. monitoring Dec 23, 2025, 01:57 PM UTC

    A fix has been deployed and we are monitoring it.

  6. resolved Dec 23, 2025, 04:27 PM UTC

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

Read the full incident report →

Major December 22, 2025

Tenable Vulnerability Management: Delays in scan processing

Detected by Pingoru
Dec 22, 2025, 02:57 PM UTC
Resolved
Dec 23, 2025, 05:52 PM UTC
Duration
1d 2h
Affected: US-1A
Timeline · 4 updates
  1. investigating Dec 22, 2025, 02:57 PM UTC

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

  2. investigating Dec 23, 2025, 01:21 AM UTC

    Our engineering team continues to investigate this issue.

  3. investigating Dec 23, 2025, 07:05 AM UTC

    Our engineering team continues to investigate this issue.

  4. resolved Dec 23, 2025, 05:52 PM UTC

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

Read the full incident report →

Major December 16, 2025

Tenable Vulnerability Management: Cloud Scanners aborting scan tasks on all sites

Detected by Pingoru
Dec 16, 2025, 09:48 AM UTC
Resolved
Dec 16, 2025, 02:12 PM UTC
Duration
4h 23m
Affected: AP-SYD-1BR01CA01FRAIN01JP01SINGUAE01UK-LON-1US-1AUS-2AUS-2BUS-3AUS-4AUS-5AUS07US08GOV01
Timeline · 4 updates
  1. investigating Dec 16, 2025, 09:49 AM UTC

    We are aware of and actively investigating aborted scans using Tenable Cloud Scanners that are impacting scans for certain users. We will provide periodic updates as our engineers continue working on this issue.

  2. identified Dec 16, 2025, 10:07 AM UTC

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

  3. monitoring Dec 16, 2025, 11:28 AM UTC

    We have implemented a fix for the issue and are monitoring the recovery.

  4. resolved Dec 16, 2025, 02:12 PM UTC

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

Read the full incident report →