Live / F5 / Incident
F5: F5 Distributed Cloud - Service Degradation - San Jose (SV10, b-SV10) Regional Edges - INC-20261107-542
F5 · volterra.ioMinor incidentResolved2026-11-07 23:55 UTC
Public — what happened
Summary
F5 reported an incident on its status page (rated minor). It has been resolved.
Affected
Customer Dashboard, San Jose (sv10), CA, United States, San Jose (b-sv10), CA, United States, HTTP Load Balancer
Timeline
- Started — 2026-11-07 15:59 UTC
- Investigating — 2026-11-07 15:59 UTC
- Identified — 2026-11-07 16:40 UTC
- Monitoring — 2026-11-07 19:40 UTC
- Resolved — 2026-11-07 23:55 UTC · 7h 56m 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 46, 2026, our weekly internet health report.