Tenable incident

Tenable Vulnerability Management / Tenable One / Nessus: Vulnerability Scan Issues Related to DNS Resolution

Major Resolved View vendor source →

Tenable experienced a major incident on May 20, 2026 affecting AP-SYD-1 and BR01 and 1 more component, lasting 16h 48m. The incident has been resolved; the full update timeline is below.

Started
May 20, 2026, 07:07 PM UTC
Resolved
May 21, 2026, 11:55 AM UTC
Duration
16h 48m
Detected by Pingoru
May 20, 2026, 07:07 PM UTC

Affected components

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

Update timeline

  1. investigating May 20, 2026, 07:07 PM UTC

    We are aware of and actively investigating issues with DNS resolution failures for checks related to log4j plugins for certain users. We will provide periodic updates as our engineers continue working on this issue.

  2. identified May 20, 2026, 07:53 PM UTC

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

  3. monitoring May 20, 2026, 08:58 PM UTC

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

  4. resolved May 21, 2026, 11:55 AM UTC

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