- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 22of 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 6h 59m it lasted.
Anything that failed between 2026-10-20 16:54 UTC and 2026-10-20 23:53 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 2
- identified
We're experiencing low host capacity in GRU. Creating or starting Machines in the region may fail at this time. Remote builders in GRU are also impacted. We're actively provisioning additional capacity. As a temporary remediation, customers may consider creating resources in EWR or IAD.
provider
- resolved
We have added host capacity to the region. Machine creates, starts and remote builds in GRU should now be functioning as 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-2900280479
Is Fly.io still down?
No, this incident was resolved 2026-10-20 23:53 UTC. For Fly.io's live state, see https://down.guide/fly.
How long did it last?
6h 59m, from 2026-10-20 16:54 UTC to 2026-10-20 23:53 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.