Live / F5 / Incident
F5: F5 Distributed Cloud - Service Degradation - Delay in Access Console Logs - INC-20261008-528
F5 · volterra.ioMinor incidentResolved2026-10-09 01:10 UTC
Public — what happened
Summary
F5 reported a minor problem in its Distributed Cloud service that delayed or disrupted security and access logs, starting around 15:28 UTC on October 8, 2026, and initially described it as touching Global Log Relay and access logs across several regions. By 16:24 UTC the company said it had found the issue and finished mitigation work, with services recovering, though it did not publicly state a cause. At 19:48 UTC F5 said services were back to normal and noted that the core console and the Global Logs Receiver had kept working the whole time. The incident was marked resolved at 01:10 on October 9.
Affected
Customer Dashboard
Timeline
- Started — 2026-10-08 15:30 UTC
- Investigating — 2026-10-08 15:30 UTC
- Identified — 2026-10-08 16:24 UTC
- Monitoring — 2026-10-08 19:48 UTC
- Resolved — 2026-10-09 01:10 UTC · 9h 40m 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.