Live / F5 / Incident
F5: F5 Distributed Cloud - Degraded Performance - Toronto, Canada PoP - INC-20261027-535
F5 · volterra.ioResolved2026-10-28 03:09 UTC
Public — what happened
Summary
F5 said its Distributed Cloud Services had degraded performance at the Toronto, Canada point of presence, and that customers might see response timeouts. The company began investigating at 18:29 UTC on October 27, 2026. It later said it had moved traffic away from the Toronto site at 18:18 UTC while its team checked the affected systems, then returned the site to service at 20:55 UTC and kept watching it. F5 marked the incident resolved at 03:09 UTC on October 28.
Affected
Toronto, Canada
Timeline
- Started — 2026-10-27 18:29 UTC
- Investigating — 2026-10-27 18:29 UTC
- Monitoring — 2026-10-27 22:54 UTC
- Resolved — 2026-10-28 03:09 UTC · 8h 40m 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 45, 2026, our weekly internet health report.