Fly.io: Emergency network maintenance on a subset of hosts in ORD

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 14m it lasted.
Anything that failed between 2026-11-04 05:01 UTC and 2026-11-04 05:15 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.

identifiedNov 4, 2026, 5:01 AM UTC
One of our upstream providers is performing emergency network maintenance on a subset of hosts in ORD. Some machines in ORD may be unreachable during the incident. A small subset of MPG clusters are running with reduced HA due to their replicas being on the affected hosts.
provider
resolvedNov 4, 2026, 5:15 AM UTC
The affected hosts are back online
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-11-04 05:15 UTC. For Fly.io's live state, see https://down.guide/fly.

How long did it last?

14m, from 2026-11-04 05:01 UTC to 2026-11-04 05:15 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.