Live / Fly.io / Incident
Fly.io: Degraded networking to AWS IPs
Fly.io · fly.ioResolved2026-10-26 20:40 UTC
Public — what happened
Summary
Fly.io said it began investigating networking problems between its network and AWS addresses at 14:34 UTC on 2026-10-26. The company said connections coming back from AWS were failing on a subset of its hosts and appeared to be blocked on the AWS side, and it worked with AWS and upstream partners while suggesting affected customers set up static egress IPs. Fly.io said AWS made changes at 18:08 UTC and connectivity began returning host by host, with about 80% of affected hosts recovered by 19:23 UTC. The incident is marked resolved as of 20:40.
Timeline
- Started — 2026-10-26 14:34 UTC
- Investigating — 2026-10-26 14:34 UTC (2 updates)
- Identified — 2026-10-26 15:15 UTC (4 updates)
- Resolved — 2026-10-26 20:40 UTC · 6h 06m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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.