Tenable incident
TenableOne: last_connect and last_scanned fields are unavailable
Resolved after 54 minutes, affecting AP-SYD-1 and BR01 and 1 more, on October 31, 2025.
Between 30/Oct 17:15UTC and 31/Oct 16:15UTC certain users may not have observed data in Nessus Agent last_connect and last_scanned fields. The issue has been resolved. We are sorry for the disruption and inconvenience.
Affected components
Update timeline
- investigating Oct 31, 2025, 03:51 PM UTC
We are aware of and actively investigating fields pertaining to Nessus Agents that do not have data for certain users. We will provide periodic updates as our engineers continue working on this issue.
- identified Oct 31, 2025, 03:51 PM UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
- monitoring Oct 31, 2025, 04:17 PM UTC
We have implemented a fix for the issue and are monitoring the recovery.
- resolved Oct 31, 2025, 04:45 PM UTC
Between 30/Oct 17:15UTC and 31/Oct 16:15UTC certain users may not have observed data in Nessus Agent last_connect and last_scanned fields. The issue has been resolved. We are sorry for the disruption and inconvenience.
Your product runs on more than Tenable
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services