- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 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 1h 28m it lasted.
Anything that failed between 2026-10-30 20:24 UTC and 2026-10-30 21:52 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 are investigating slow image pulls within Fly Machines in IAD. Newly created or updated Machines are taking longer to start, which may cause deployments to time out. Machines start successfully after the delay. Consider creating Machines in alternate regions, if possible, or running `fly deploy --wait-timeout 10m` to give Machines up to 10 minutes to prepare images and start.
provider
- identified
We have identified the cause of the issue and are working on a fix.
provider
- monitoring
We have implemented a fix and are monitoring results.
provider
- resolved
Image pull times in IAD have returned to normal.
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-641d709f21
Is Fly.io still down?
No, this incident was resolved 2026-10-30 21:52 UTC. For Fly.io's live state, see https://down.guide/fly.
How long did it last?
1h 28m, from 2026-10-30 20:24 UTC to 2026-10-30 21:52 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.