Live / Tenable / Incident
Tenable: Tenable Patch management: Possible GUI slowness along with 502/503 Errors Observed
Tenable · tenable.comMajor incidentResolved2026-10-12 11:53 UTC
Public — what happened
Summary
Tenable reported a major incident affecting its Patch Management product, saying some users could see a sluggish web interface along with 502 and 503 error messages. The company began investigating on October 8, 2026 at 21:04 UTC and said a minute later that it had found the problem and was working on a fix, though it did not describe the cause. Tenable said the fix was in place by 21:44 UTC that day, and after a period of monitoring the incident was marked resolved on October 12 at 11:53.
Timeline
- Started — 2026-10-08 21:04 UTC
- Investigating — 2026-10-08 21:04 UTC
- Identified — 2026-10-08 21:05 UTC
- Monitoring — 2026-10-08 21:44 UTC
- Resolved — 2026-10-12 11:53 UTC · 4 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 42, 2026, our weekly internet health report.