- Level
- confirmed
- Worst impact
- Partial outage
- Components
- GRU - Sao Paulo, Brazil
- Regions
- latam
- Down Index
- 34of 100
What to do
Check whether you use Fly.io GRU - Sao Paulo, Brazil in latam. 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 40m it lasted.
Anything that failed between 2026-09-24 16:31 UTC and 2026-09-24 19:11 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 issues in GRU related to a migration of our distributed state database. Apps continue to run, but creating or updating machines in GRU region may fail. Connections to apps in GRU, or connections from clients near GRU region, may fail at this time
provider
- identified
We have identified a bug and are working on a fix.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This 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-ddc11063f0
Is Fly.io still down?
No, this incident was resolved 2026-09-24 19:11 UTC. For Fly.io's live state, see https://down.guide/fly.
How long did it last?
2h 40m, from 2026-09-24 16:31 UTC to 2026-09-24 19:11 UTC, by the times Fly.io posted.
What was affected?
Fly.io named GRU - Sao Paulo, Brazil in latam.
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.