Live / F5 / Incident
F5: Incident Advisory: INC-20261014-531
F5 · volterra.ioResolved2026-10-14 11:53 UTC
Public — what happened
Summary
F5 said it was looking into degraded service affecting its Global Log Receiver and console access logs across several regions, with the problem first noticed around 10:35 UTC on October 14, 2026. By 11:20 UTC the company reported that the affected services were working normally again and that it was watching them to make sure they stayed stable. F5 did not share a cause in its updates, and the incident was marked resolved at 11:53.
Timeline
- Started — 2026-10-14 10:40 UTC
- Investigating — 2026-10-14 10:40 UTC
- Monitoring — 2026-10-14 11:20 UTC
- Resolved — 2026-10-14 11:53 UTC · 1h 13m 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 43, 2026, our weekly internet health report.