Fly.io: Networking Issues in GRU
Is it fixed? Yes.
Resolved after <1 min. First reported Aug 28, 22:36 UTC, resolved Aug 28, 22:36 UTC. The vendor posted it on its status page first.
What happened
A network issue affecting the GRU (Sao Paulo, Brazil) region has been resolved. No specific versions or commands are provided to mitigate this problem.
What caused it?
Under active investigation. No report has identified a root cause yet.
No verified workaround yet
This incident was resolved upstream without a reported workaround.
Official fixTimeline
- Investigating(done)
- Workaround available(skipped)
- Resolved(done)
- Archived
Evidence
1 report · 1 StatusShow
- [1]Status First reportNetworking Issues in GRU(opens official status page in a new tab)
Status: Resolved This incident has been resolved. Affected components GRU - Sao Paulo, Brazil (Operational)
by flyio status
FAQ
What happened in the Fly.io outage?
A network issue affecting the GRU (Sao Paulo, Brazil) region has been resolved. No specific versions or commands are provided to mitigate this problem.
What is affected by the Fly.io outage?
Fly.io.
When did the Fly.io outage start and end?
It started Aug 28, 22:36 UTC and was resolved Aug 28, 22:36 UTC, after <1 min.
How do I get alerts for Fly.io?
Subscribe to the Fly.io RSS feed for every new Fly.io incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Fly.io is down. Fly.io feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source, including the vendor’s own status page.