Live / F5 / Incident
F5: F5 Distributed Cloud - Service Degradation - Investigating Missing Metrics Impacting me1-mel RE - INC-20260928-517
F5 · volterra.ioMinor incidentResolved2026-09-29 01:19 UTC
Public — what happened
Summary
F5 reported a minor service degradation in its Distributed Cloud platform's Melbourne (me1) region, where metrics were not showing up in the customer dashboard and for Customer Edges. The problem began on 2026-09-28 at 16:10 UTC, and F5 did not share a cause in its update. The company said the issue was fully fixed by 01:19 on 2026-09-29, after a monitoring period confirmed the platform was stable and working normally.
Timeline
- Started — 2026-09-28 16:10 UTC
- Resolved — 2026-09-29 01:19 UTC · 9h 09m 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 41, 2026, our weekly internet health report.