Live / Incidents / F5
F5: F5 Distributed Cloud - Service Degradation - Configuration propagation delay - INC-20260930-519
F5 · volterra.ioImpact: minorResolved2026-10-01 03:49 UTC
Public — what happened
Summary
We are pleased to report that the configuration propagation delays affecting our Distributed Cloud systems have been completely resolved.
Our engineering teams have completed their recovery work, and after closely monitoring our platform, we can confirm that all systems are stable and processing traffic normally.
We know how important these services are to your business operations and truly appreciate your patience and partnership while we worked to put this right. If you have any remaining questions or need assistance, our support team is ready to help through your usual contact channels.
Sincerely,
F5 Distributed Cloud
Timeline
- Started — 2026-09-30 13:24 UTC
- Last update — 2026-10-01 03:49 UTC
- Resolved — 2026-10-01 03:49 UTC
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 →