Live / F5 / Incident
F5: F5 Distributed Cloud - Service Degradation - Issue with NGINX One Console - INC-20261001-522
F5 · volterra.ioMajor incidentResolved2026-10-01 22:23 UTC
Public — what happened
Summary
F5 said it began looking into degraded service with its NGINX One Console at 12:32 UTC on October 1, 2026, noting it first detected possible impact at 12:28 PM UTC. The company later explained that the Console and its APIs were failing with 503 errors, so customers could not use it to change configurations or monitor their setups, though running NGINX instances and customer application traffic were not affected. By 15:17 UTC F5 reported the Console and APIs were working normally again and it was watching for stability; it did not name a cause, and the incident was marked resolved at 22:23.
Timeline
- Started — 2026-10-01 12:32 UTC
- Investigating — 2026-10-01 12:32 UTC (2 updates)
- Monitoring — 2026-10-01 15:17 UTC
- Resolved — 2026-10-01 22:23 UTC · 9h 51m 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 F5 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 F5: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the F5 report →
More from F5
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.