Live / F5 / Incident
F5: F5 Distributed Cloud - Service Degradation - Intermittent loss of Access Logs and Global Log Receiver in Mumbai (b-mb2) region - INC-20261001-521
F5 · volterra.ioMinor incidentResolved2026-10-01 16:31 UTC
Public — what happened
Summary
F5 said its Distributed Cloud service was intermittently dropping access logs and Global Log Receiver data in the Mumbai (b-mb2) region, with impact first detected at 04:25 UTC on October 1, 2026, and an advisory posted at 07:15 UTC. The company stated that customer traffic was not interrupted and that core Distributed Cloud Console services kept working normally throughout. F5 did not name a cause, but reported at 10:52 UTC that log streaming was back to normal and it was watching for stability, and the incident was marked resolved at 16:31.
Timeline
- Started — 2026-10-01 07:15 UTC
- Investigating — 2026-10-01 07:15 UTC (2 updates)
- Monitoring — 2026-10-01 10:52 UTC
- Resolved — 2026-10-01 16:31 UTC · 9h 17m 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.