Major incident
Tenable: Tenable One: Azure Cloud Connector Ingestion Issues
Sep 18, 2026, 10:02 UTC
started
11:26 UTC
resolved
1 h 24 min
duration
Affected: us-1a, us-2a, us-2b, us-3a, us-4a, us-5a, mssp-us-1 (us07), us08, ap-syd-1, br01, ca01, ca02, fra, in01, jp01, uk-lon-1, sing, gov01, uae01
Current status of Tenable: Partial outage — live Tenable status
Timeline
- Sep 18, 2026, 10:02 UTCinvestigatingWe 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.
- Sep 18, 2026, 10:22 UTCidentifiedWe have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
- Sep 18, 2026, 10:44 UTCmonitoringWe have implemented a fix for the issue and are monitoring the recovery.
- Sep 18, 2026, 11:26 UTCresolvedThe issue has been resolved. We are sorry for the disruption and inconvenience.
Updates as published by Tenable (original).
Other services with incidents at the same time
This was part of a wider event: 41 services reported incidents within the hour.
- ESET 10:20 UTC · ESET INSPECT Cloud instance is unavailable
- Sentry 10:17 UTC · Delays in spans ingestion
- Brandwatch 09:46 UTC · Labels Cannot Be Added to Content in Engage
- CP Public 09:41 UTC · September 18, 2026 - Drop in station reachability in NA region
More Tenable incidents
- October 21, 2026 Tenable Vulnerability Management: Scheduled Scans Not Launching
- October 17, 2026 Tenable Cloud Security: Service Degradation on All Sites
- October 14, 2026 Tenable Vulnerability Management: Unresponsive Cyber Exposure Feed
- October 14, 2026 Tenable One: Delay in Tenable Exposure Management data
- October 12, 2026 Tenable Patch management: Possible GUI slowness along with 502/503 Errors Observed
- October 12, 2026 Tenable Vulnerability Management: Scan processing and Explore Findings and Asset pages delays