- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 100
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 48m it lasted.
Anything that failed between 2026-10-29 20:40 UTC and 2026-10-29 21:28 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.
Updates from Fly.io 4
- investigating
We're currently investigating degraded performance with the Machines API.
provider
- identified
We've identified the problem and are working on a fix.
provider
- identified
We're continuing to work on a fix to resolve this incident.
provider
- resolved
The incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-2847b63ff5
Is Fly.io still down?
No, this incident was resolved 2026-10-29 21:28 UTC. For Fly.io's live state, see https://down.guide/fly.
How long did it last?
48m, from 2026-10-29 20:40 UTC to 2026-10-29 21:28 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.