Live  /  Providers  /  Fly.io

Fly.io

fly.ioNo open incidents

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

Cloud & hosting · SquidGrid tracks Fly.io’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 Fly.io is reporting

Current & recent incidents

Resolved

Network outage in AMS region

Critical impact · 2026-09-26 19:53 UTC

Resolved

State database issues in GRU

Major impact · 2026-09-24 19:11 UTC

Resolved

Private Networking issues (6PN)

Major impact · 2026-09-24 15:37 UTC

Resolved

Partial Sprites outage

Major impact · 2026-09-24 02:12 UTC

Resolved

Elevated private networking errors

Major impact · 2026-09-23 15:23 UTC

Resolved

Upstash unavailability in FRA region

Major impact · 2026-09-23 14:03 UTC

Resolved

IPv6 Networking Issues in DFW

Major impact · 2026-09-23 12:15 UTC

Resolved

Depot builder failures

Minor impact · 2026-09-15 04:51 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what Fly.io 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.

Fly.io 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 Fly.io is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Fly.io.