Tenable Vulnerability Management / Tenable One / Nessus: Vulnerability Scan Issues Related to DNS Resolution
May 20, 19:07 UTCMay 21, 11:55 UTC
Duration
16h 49m
Impact
Major
Root cause
Not disclosed
Tenable, 90 days
28 incidents
Affected
US-1Aus-1aUS-2Aus-2aUS-2Bus-2bUS-3Aus-3aUS-4Aus-4aUS-5Aus-5aUS07mssp-us-1 (us07)
Final update
The issue has been resolved. We are sorry for the disruption and inconvenience.
Timeline
- Resolved · May 21, 11:55 UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
- Monitoring · May 20, 20:58 UTC
We have implemented a fix for the issue and are monitoring the recovery.
- Identified · May 20, 19:53 UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
- Investigating · May 20, 19:07 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.
More from Tenable
Full historyTenable Vulnerability Management: Unresponsive Cyber Exposure Feedlasted 0mTenable One: Delay in Tenable Exposure Management datalasted 2d 5hTenable Patch management: Possible GUI slowness along with 502/503 Errors Observedlasted 2dTenable Vulnerability Management: Scan processing and Explore Findings and Asset pages delayslasted 3h 39mTenable Patch management: Possible GUI slowness along with 502/503 Errors Observedlasted 3d 14hTenable Vulnerability Management: Scheduled Scans Not Launchinglasted 13h 16m