Live / F5 / Incident
F5: F5 Distributed Cloud - Service Degradation - Delay in Access logs - INC-20261109-543
F5 · volterra.ioMinor incidentResolved2026-11-09 23:49 UTC
Public — what happened
Summary
F5 said it was looking into a minor problem with its Distributed Cloud service, where access logs shown in the web interface were arriving late. It reported the issue starting around 12:07 UTC on 2026-11-09 and said its main console services kept working normally. About an hour later, at 13:24 UTC, F5 said the delay had been fixed and it was watching to make sure things stayed stable. F5 later confirmed the logs were running normally, and the incident was marked resolved at 23:49 UTC; the company did not state a cause in the text provided.
Affected
Customer Dashboard
Timeline
- Started — 2026-11-09 12:07 UTC
- Investigating — 2026-11-09 12:07 UTC (2 updates)
- Monitoring — 2026-11-09 13:24 UTC (2 updates)
- Resolved — 2026-11-09 23:49 UTC · 11h 42m 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 47, 2026, our weekly internet health report.