Live / F5 / Incident
F5: F5 Distributed Cloud - Service Degradation - Multiple Regional Edges - INC-20261026-533
F5 · volterra.ioMinor incidentResolved2026-10-31 06:52 UTC
Public — what happened
Summary
F5 said it began investigating on 2026-10-26 at 02:34 UTC after reports of degraded performance on its Distributed Cloud service across several regional edge sites, and that customers could see intermittent connection timeouts. The company did not name a cause in the updates provided, saying its engineers were working to find one through the morning. By 11:16 UTC it moved to monitoring, and by 20:38 UTC it said regional edges worldwide were operating normally. F5 kept monitoring through the next day and marked the incident resolved on 2026-10-31 at 06:52.
Affected
Ashburn (dc12), VA, United States, Sao Paulo, Brazil, Singapore, Singapore, Tokyo, Japan, Ashburn (b-dc12), VA, United States, Ashburn (c-dc12), VA, United States, London (tn2), United Kingdom, San Jose (sv10), CA, United States, San Jose (b-sv10), CA, United States, Madrid, Spain, Dallas (dal3), TX, United States, Stockholm, Sweden
Timeline
- Started — 2026-10-26 02:34 UTC
- Investigating — 2026-10-26 02:34 UTC (5 updates)
- Monitoring — 2026-10-26 11:16 UTC (3 updates)
- Resolved — 2026-10-31 06:52 UTC · 5 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 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 45, 2026, our weekly internet health report.