Resolved
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.
Posted Oct 31, 2025 - 12:45 EDT
Monitoring
We have implemented a fix for the issue and are monitoring the recovery.
Posted Oct 31, 2025 - 12:17 EDT
Identified
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
Posted Oct 31, 2025 - 11:51 EDT
Investigating
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.
Posted Oct 31, 2025 - 11:51 EDT
This incident affected: Tenable Vulnerability Management (AP-SYD-1, BR01, CA01, FRA, IN01, JP01, SING, UAE01, UK-LON-1, US-1A, US-2A, US-2B, US-3A, US-4A, US-5A, US07, US08, GOV01) and Tenable One (sing, us-1a, us-2a, us-2b, us-3a, us-4a, us-5a, mssp-us-1 (us07), us08, ap-syd-1, br01, ca01, fra, in01, jp01, uk-lon-1, gov01, uae01).