- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 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 2h 10m it lasted.
Anything that failed between 2026-11-01 18:50 UTC and 2026-11-01 21: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 4
- identified
We are working to resolve an issue with outbound IPv4 connectivity failures affecting machines with in the ARN, JNB, and GRU regions.
provider
- identified
We have identified the issue and are working to resolve in the affected regions. Newly created static egress IPs may continue to see problems while we roll out fixes.
provider
- monitoring
We've rolled out fixes to the affected regions and are monitoring for any additional issues.
provider
- resolved
We've fixed affected regions and everything is back 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-9115b35abe
Is Fly.io still down?
No, this incident was resolved 2026-11-01 21:00 UTC. For Fly.io's live state, see https://down.guide/fly.
How long did it last?
2h 10m, from 2026-11-01 18:50 UTC to 2026-11-01 21: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.