Live / F5 / Incident
F5: F5 Distributed Cloud - Service Interruption - API Discovery Console Visibility and Configuration Delay - INC-20261114-548
F5 · volterra.ioMinor incidentmonitoring2026-11-14 20:49 UTC
Public — what happened
Summary
F5 said a problem in its Distributed Cloud Console affected the API Discovery feature, so customers might not have been able to create or change settings, and new discovery data or attack detections might not have shown up. F5 said existing settings kept working and that customer traffic, its web application firewall and API security protection were not affected. The company posted its first notice at 14:04 UTC on November 14, 2026, and said it had identified the issue by 14:37 UTC. By 20:49 UTC F5 said service had been restored and the root cause identified, and that it was still monitoring to make sure things stay stable.
Affected
Customer Dashboard
Timeline
- Started — 2026-11-14 14:04 UTC
- Investigating — 2026-11-14 14:04 UTC
- Identified — 2026-11-14 14:37 UTC
- Investigating — 2026-11-14 17:33 UTC
- Monitoring — 2026-11-14 20:49 UTC
- Ongoing at last check.
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.