Live / F5 / Incident
F5: F5 Distributed Cloud - Service Degradation - Network - Melbourne (ME1) - INC-20261005-523
F5 · volterra.ioMinor incidentResolved2026-10-07 19:28 UTC
Public — what happened
Summary
F5 reported degraded network service for its Distributed Cloud platform in the Melbourne (ME1) region, posting its first notice on October 5, 2026 at 15:46 UTC and saying it had first detected possible impact at 03:42 PM UTC. The company said it was looking into a hardware problem with help from the equipment vendor, and that customer traffic was still flowing normally through backup paths. Over the next day F5 described ongoing work to restore the Melbourne Regional Edge while keeping extra monitoring in place, and the incident was marked resolved on October 7 at 19:28.
Affected
Melbourne, Australia
Timeline
- Started — 2026-10-05 15:46 UTC
- Investigating — 2026-10-05 15:46 UTC (2 updates)
- Identified — 2026-10-05 23:36 UTC (2 updates)
- Resolved — 2026-10-07 19:28 UTC · 2 days 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 42, 2026, our weekly internet health report.