Live  /  Fly.io  /  Incident

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

Fly.io · fly.ioMinor incidentResolved2026-11-01 21:00 UTC
Public — what happened

Summary

Fly.io said machines in its ARN, JNB, and GRU regions were having trouble making outbound connections over IPv4, starting at 18:50 UTC on 2026-11-01. About half an hour later the company said it had identified the issue and warned that newly created static egress IPs might still have problems while fixes were being rolled out. By 20:24 UTC Fly.io said fixes had been deployed to the affected regions and it was monitoring, and the incident was marked resolved at 21:00.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Fly.io against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Fly.io: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Fly.io report →

More from Fly.io

Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.

The full archive is on the Fly.io status & history page.

Related: Fly.io status & history. SquidGrid is not affiliated with Fly.io.