Tenable One: Azure Cloud Connector Ingestion Issues
Sep 18, 10:02 UTCSep 18, 11:26 UTC
Duration
1h 24m
Impact
Major
Root cause
Not disclosed
Tenable, 90 days
28 incidents
Affected
us-1aus-2aus-2bus-3aus-4aus-5amssp-us-1 (us07)us08ap-syd-1br01ca01ca02frain01
Final update
The issue has been resolved. We are sorry for the disruption and inconvenience.
Timeline
- Resolved · Sep 18, 11:26 UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
- Monitoring · Sep 18, 10:44 UTC
We have implemented a fix for the issue and are monitoring the recovery.
- Identified · Sep 18, 10:22 UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
- Investigating · Sep 18, 10:02 UTC
We are aware of and actively investigating ingestion issues that are impacting the Azure cloud connector 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