Live  /  Providers  /  F5

F5

volterra.ioReporting incidents

Independent assessment — SquidGrid is not affiliated with F5. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks F5’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what F5 is reporting

Current & recent incidents

Resolved

F5 Distributed Cloud - Service Degradation - BGP Sessions Flapping in Stockholm - INC-20261028-536

None impact · 2026-10-28 18:55 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 19 incidents from F5’s own status page since 2026-05-05: 18 in the last 90 days, against 0 in the 90 days before.

Recent incidents in the archive

Computed by SquidGrid from the incidents F5 published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what F5 has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

F5 runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of F5 is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with F5.