Live / Incidents / F5
F5: F5 Distributed Cloud - Service Degradation - Investigating Missing Metrics Impacting me1-mel RE - INC-20260928-517
F5 · volterra.ioImpact: minorResolved2026-09-29 01:19 UTC
Public — what happened
Summary
The Distributed Cloud team is pleased to confirm that the issue in Melbourne (me1) region affecting display of metrics within the customer dashboard and Customer Edges has been fully resolved, and service is operating normally. We have completed our monitoring activities and confirmed platform stability.
If you have any questions or need assistance, please contact our Support team:
- Email support: [email protected]
- Phone support: For region-specific contact details, please visit:
https://my.f5.com/manage/s/article/K000135931
Thank you for your patience and understanding.
Sincerely,
F5 Distributed Cloud
Timeline
- Started — 2026-09-28 16:10 UTC
- Last update — 2026-09-29 01:19 UTC
- Resolved — 2026-09-29 01:19 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 →