Minor impactResolvedCloud

Fly.io incident: Outbound IPv4 connectivity failures in ARN, JNB, and GRU

Fly.io reported this minor-impact incident on its official status page on Nov 1, 2026, 18:50 UTC. It was resolved after 2h 10m.

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

🔔 Get alerted when Fly.io has issuesFree · email alerts · no credit card
Nov 1, 2026, 18:50 UTC
started
Nov 1, 2026, 21:00 UTC
resolved
2h 10m
duration
Minor
impact

Timeline

updates from Fly.io's status page ↗
  1. resolvedNov 1, 2026, 21:00 UTC

    We've fixed affected regions and everything is back to normal.

  2. monitoringNov 1, 2026, 20:24 UTC

    We've rolled out fixes to the affected regions and are monitoring for any additional issues.

  3. identifiedNov 1, 2026, 19:24 UTC

    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.

  4. identifiedNov 1, 2026, 18:50 UTC

    We are working to resolve an issue with outbound IPv4 connectivity failures affecting machines with in the ARN, JNB, and GRU regions.

What APIStatus.watch saw

  • Nov 1, 2026, 18:54 UTCoperational → degraded
  • Nov 1, 2026, 21:04 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Fly.io have incidents?

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

← Previous: Slow image pulls delaying Machine starts in IAD (Oct 30, 2026)Next: Emergency maintenance in IAD (Nov 2, 2026) →