- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 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 0m it lasted.
Anything that failed between 2026-10-29 22:52 UTC and 2026-10-29 22: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.
Updates from Fly.io 1
- resolved
Between 22:00 and 22:30 UTC, we saw elevated errors provisioning Depot hosted Builders due to [an upstream incident impacting Depot's control plane](https://status.depot.dev/incidents/01M64NVFDKM930PX39YM4275DN). During this time customers may have seen deploys fail with an `internal error` message. Depot resolved the incident and deploys using Depot hosted builders are working as normal again.
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-71bb0e38a2
Is Fly.io still down?
No, this incident was resolved 2026-10-29 22:00 UTC. For Fly.io's live state, see https://down.guide/fly.
How long did it last?
0m, from 2026-10-29 22:52 UTC to 2026-10-29 22: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.