Live / Tenable / Incident
Tenable: Tenable Patch management: Possible GUI slowness along with 502/503 Errors Observed
Tenable · tenable.comMajor incidentResolved2026-10-14 18:02 UTC
Public — what happened
Summary
Tenable reported a major incident affecting its Patch Management product, saying some users were seeing a sluggish web interface along with 502 and 503 error messages. The company began investigating on October 12, 2026 at 17:11 UTC. By 22:54 UTC that same day, Tenable said it had put a fix in place and was watching to confirm things were recovering, though it did not share a cause. The incident was marked resolved on October 14, 2026 at 18:02.
Timeline
- Started — 2026-10-12 17:11 UTC
- Investigating — 2026-10-12 17:11 UTC
- Monitoring — 2026-10-12 22:54 UTC
- Resolved — 2026-10-14 18:02 UTC · 2 days 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 43, 2026, our weekly internet health report.