Fly.io: Degraded Edge Performance

What to do

Check whether your product depends on Fly.io. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-10-22 19:26 UTC and 2026-10-22 18:00 UTC may need a replay.
Subscribe to Fly.io's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=fly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

resolvedOct 22, 2026, 6:00 PM UTC
Between ~18:00 - 18:10 UTC today we saw degraded edge performance across multiple regions. Customers may have noticed elevated numbers of dropped connections or longer than usual connection times reaching their apps during this period. A fix was applied and edge performance is back to normal levels.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Fly.io still down?

No, this incident was resolved 2026-10-22 18:00 UTC. For Fly.io's live state, see https://down.guide/fly.

How long did it last?

0m, from 2026-10-22 19:26 UTC to 2026-10-22 18:00 UTC, by the times Fly.io posted.

What caused it?

Fly.io hasn't published a root cause. If it does, it shows here.

Where does this come from?

Fly.io's official status page, https://status.flyio.net, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.