Live / Tenable / Incident
Tenable: Tenable Cloud Security: Sync delays
Tenable · tenable.comMajor incidentResolved2026-11-03 09:27 UTC
Public — what happened
Summary
Tenable reported a major incident in which Tenable Cloud Security was slow to sync data for customers using AWS. The company said it began investigating at 12:03 UTC on 2026-11-02, and later that day, at 15:57 UTC, it said it had found the cause. About a minute afterward it said a fix was in place and it was watching the recovery, and the incident was marked resolved on 2026-11-03 at 09:27.
Affected
AE1, AU1, BR1, CA1, EU1, IN1, JP1, KR1, SG1, UK1, US1
Timeline
- Started — 2026-11-02 12:03 UTC
- Investigating — 2026-11-02 12:03 UTC
- Identified — 2026-11-02 15:57 UTC
- Monitoring — 2026-11-02 15:58 UTC
- Resolved — 2026-11-03 09:27 UTC · 21h 24m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Tenable against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Tenable: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Tenable report →
More from Tenable
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.