Live / F5 / Incident
F5: F5 Distributed Cloud - Service Degradation - Configuration propagation delay - INC-20260930-519
F5 · volterra.ioMinor incidentResolved2026-10-01 03:49 UTC
Public — what happened
Summary
F5 reported a minor degradation in its Distributed Cloud service, first posted at 13:24 UTC on September 30, 2026, saying it had spotted potential impact across multiple regions starting at 1:17 PM UTC. The company said customers creating or changing Load Balancers saw delays before their configuration changes took effect, and some might get intermittent 5xx errors when applying or accessing configurations, while other services kept working normally. F5 did not publicly name a cause; by 20:30 UTC it said most regions had recovered and it was watching systems closely, and the incident was marked resolved on October 1 at 03:49.
Timeline
- Started — 2026-09-30 13:24 UTC
- Investigating — 2026-09-30 13:24 UTC (2 updates)
- Identified — 2026-09-30 15:58 UTC (2 updates)
- Monitoring — 2026-09-30 20:30 UTC
- Resolved — 2026-10-01 03:49 UTC · 14h 25m 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.