rewindex

ChangesFly.ioDegraded networking to AWS IPs

Fly.io: Incident updated: Degraded networking to AWS IPs

Incident updateNormal progress (rule, 100%)Changed status.flyio.net (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Fly.io removed; blue is what they added. Muted text is unchanged context.

AddedUpdateidentified#1
Before: not present
After: We are continuing to work with our upstream networking partners and AWS on remediation. Impacted customers are recommended to allocate app-scoped static egress IPs using fly ips allocate-egress. Customers seeing issues are encouraged to also contact AWS support or their AWS hosted vendors support with details of the connection errors and their fly machine IPs.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Monday, October 26

6 incident changes

Cite this

Incident updated: Degraded networking to AWS IPs on Fly.io’s status page, changed 2026-10-26 16:33 UTC (change 3 of 6).

Title
Incident updated: Degraded networking to AWS IPs
Vendor
Fly.io
Date
URL
https://rewindex.com/change/r747fb031d5de3a

All Fly.io changesFly.io profileMarkdownJSON