Live / F5 / Incident
F5: F5 Distributed Cloud - Service Degradation - Querétaro (QRO1), Mexico Region Isolated - INC-20261009-529
F5 · volterra.ioMinor incidentResolved2026-10-10 12:46 UTC
Public — what happened
Summary
F5 said it was looking into degraded service in its Distributed Cloud region in Querétaro, Mexico, with possible impact first noticed at 06:26 UTC on October 9, 2026. The company later said the problem stemmed from an infrastructure issue at a service provider and stated that customer traffic was not affected at any point. By 14:07 UTC that day F5 reported the provider's issue was resolved and services were back to normal, and the incident was marked resolved on October 10 after a period of monitoring.
Affected
Querétaro, Mexico
Timeline
- Started — 2026-10-09 06:42 UTC
- Investigating — 2026-10-09 06:42 UTC
- Identified — 2026-10-09 07:22 UTC (2 updates)
- Monitoring — 2026-10-09 14:07 UTC
- Resolved — 2026-10-10 12:46 UTC · 30h 04m 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 42, 2026, our weekly internet health report.