rewindex

CompaniesFly.ioIncidents

Fly.io: Degraded networking to AWS IPs

No impact listedStatus: resolvededitedStarted Resolved (6.1 h)7 updatesstatus.flyio.net (opens in new tab)

Timeline of updates

  1. investigating

    We are investigating reports of elevated networking issues between our network and AWS IPs. We are working to determine the source of the issue.

  2. investigating

    Our initial investigations indicate connection errors are occuring the return path from AWS IPs. We are escalating the issue with AWS and continuing to investigate.

    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.

  3. identified

    We are continuing to see connectivity issues from AWS IPs to a subset of our hosts. From our investigation these connections appear to be being blocked from the AWS side. We are continuing to work with our upstream networking partners and AWS on remediation.

    In the meantime impacted customers are recommended to allocate app-scoped static egress IPs using fly ips allocate-egress.

  4. identified

    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.

  5. identified

    AWS has implemented changes to unblock connections from their network from reaching our machines. We are seeing connectivity starting to resume on a host-by-host basis as these changes take effect.

  6. identified

    Connectivity from AWS to Fly.io on impacted hosts is continuing to recover. Approximately 80% of the hosts that were seeing connectivity issues are fully recovered at this time.

  7. resolved

    This incident has been resolved, connectivity from AWS to all of our hosts is back to normal.

Changes Rewindex caught on this incident

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.

Impact, status and times are the vendor’s own, as last archived. View on status.flyio.net (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Fly.io, started 2026-10-26 14:34 UTC, resolved after 6.1 h, 7 update(s); edited after publishing.

Title
Degraded networking to AWS IPs
Vendor
Fly.io
Date
URL
https://rewindex.com/company/fly-io/incidents/01M5WA55T284S335ZTE9MN8MWZ

Fly.io profileRecent Fly.io incidentsAll outages on October 26, 2026Fly.io in October 2026MarkdownJSON