Outage in Fly.io
Degraded networking to AWS IPs
Resolved Minor
October 26, 2026 - Started about 11 hours ago
- Lasted about 6 hours
Incident Report
Summary AI Generated
Fly.io experienced 6 hours of degraded network connectivity between their infrastructure and AWS IP addresses, caused by AWS blocking return-path connections to a subset of Fly.io hosts. AWS implemented changes to unblock the connections, which restored connectivity on a rolling, host-by-host basis until full resolution. As a workaround during the incident, affected customers were advised to allocate app-scoped static egress IPs via `fly ips allocate-egress`.
We are investigating reports of elevated networking issues between our network and AWS IPs. We are working to determine the source of the issue.
Trusted by 1,000+ teams
The Status Page Aggregator with Early Outage Detection
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Latest Updates ( sorted recent to last )
RESOLVED
about 5 hours ago - at 10/26/2026 08:40PM
This incident has been resolved, connectivity from AWS to all of our hosts is back to normal.
IDENTIFIED
about 6 hours ago - at 10/26/2026 07:23PM
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.
IDENTIFIED
about 8 hours ago - at 10/26/2026 06:08PM
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.
IDENTIFIED
about 9 hours ago - at 10/26/2026 04:26PM
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.
IDENTIFIED
about 10 hours ago - at 10/26/2026 03:15PM
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.**
INVESTIGATING
about 11 hours ago - at 10/26/2026 02:54PM
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.
INVESTIGATING
about 11 hours ago - at 10/26/2026 02:34PM
We are investigating reports of elevated networking issues between our network and AWS IPs. We are working to determine the source of the issue.
Latest Fly.io outages
Packet loss in IAD - about 24 hours ago
MPGv2 IAD control plane is read-only - 1 day ago
Capacity issues in GRU region - 6 days ago
Fly-metrics.net Grafana Dashboard Outage - 10 days ago
Platform Wide Rolling Host Reboots - 10 days ago
The Status Page Aggregator with Early Outage Detection
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with
