Tenable incident

Login and Platform Issues - related to tenablecloud.cn

Major Resolved View vendor source →

Tenable experienced a major incident on January 22, 2026 affecting AP-SYD-1 and BR01 and 1 more component, lasting 3d 21h. The incident has been resolved; the full update timeline is below.

Started
Jan 22, 2026, 05:41 PM UTC
Resolved
Jan 26, 2026, 02:57 PM UTC
Duration
3d 21h
Detected by Pingoru
Jan 22, 2026, 05:41 PM UTC

Affected components

AP-SYD-1BR01singCA01us-1aFRAus-2aIN01us-2bJP01

Update timeline

  1. investigating Jan 22, 2026, 05:41 PM UTC

    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 related to tenablecloud.cn DNS. We will provide periodic updates as our engineers continue working on this issue.

  2. investigating Jan 22, 2026, 07:17 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jan 22, 2026, 07:52 PM UTC

    We are continuing to investigate this issue.

  4. investigating Jan 22, 2026, 07:55 PM UTC

    We are continuing to investigate this issue.

  5. identified Jan 22, 2026, 08:31 PM UTC

    The issue has been identified and a fix is being implemented.

  6. monitoring Jan 22, 2026, 10:44 PM UTC

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

  7. identified Jan 23, 2026, 02:49 PM UTC

    The issue has been identified and a fix is being implemented.

  8. identified Jan 24, 2026, 01:30 AM UTC

    The issue has been identified and a fix is being implemented.

  9. identified Jan 24, 2026, 08:26 AM UTC

    The issue has been identified and a fix is being implemented.

  10. identified Jan 24, 2026, 12:26 PM UTC

    The issue has been identified and a fix is being implemented.

  11. identified Jan 25, 2026, 01:31 AM UTC

    The issue has been identified and a fix is being implemented.

  12. identified Jan 25, 2026, 06:25 AM UTC

    The issue has been identified and a fix is being implemented.

  13. identified Jan 25, 2026, 10:45 AM UTC

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

  14. identified Jan 25, 2026, 03:08 PM UTC

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

  15. resolved Jan 26, 2026, 02:57 PM UTC

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