Minor impactResolvedCloud

Fly.io incident: Networking Issues in GRU

Fly.io reported this minor-impact incident on its official status page on Aug 28, 2026, 22:10 UTC. It was resolved after 26 min.

Right now Fly.io is operational. Live Fly.io status →

🔔 Get alerted when Fly.io has issuesFree · email alerts · no credit card
Aug 28, 2026, 22:10 UTC
started
Aug 28, 2026, 22:36 UTC
resolved
26 min
duration
Minor
impact
  1. resolvedAug 28, 2026, 22:36 UTC

    This incident has been resolved.

  2. identifiedAug 28, 2026, 22:36 UTC

    Our upstream provider has implemented a fix. Network performance in GRU has normalized.

  3. identifiedAug 28, 2026, 22:12 UTC

    We are seeing a recurrance in networking issues in GRU. Some apps in the region may experience increased latency or packet loss. We are working with our upstream networking provider to resolve.

  4. monitoringAug 28, 2026, 22:00 UTC

    Networking performance in GRU has normalized and we are no longer seeing issues. We are continuing to monitor to ensure a full recovery.

  5. investigatingAug 28, 2026, 21:56 UTC

    We are investigating networking issues impacting some hosts in GRU (São Paulo, Brazil) region. Some apps in GRU may experience increased latency or packet loss.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Fly.io's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Fly.io have incidents?

Fly.io reported 19 incidents in the last 90 days, 11 of them major or critical. A typical incident lasted 57 min. See Fly.io's uptime and incident history

Fly.io incident on Aug 28, 2026: Networking Issues in GRU · APIStatus.watch