outages.live
Live
Fly.ioIncident ยท

Emergency network maintenance on a subset of hosts in ORD

ResolvedOfficial update
0

Some machines in ORD were unreachable during emergency network maintenance on a subset of hosts. A small subset of MPG clusters ran with reduced HA. Fly.io reports that the affected hosts are back online and the incident is resolved. It lasted about 14 minutes.

State

Resolved

Started

Lasted

14 min

Worst impact

Degraded

Timeline

2 updates
05:0105:0505:0805:1205:15
DegradedUpdate postedTimes in UTC

Identified

14 min 100%

Updates

Times in UTC

As posted by Fly.io

Resolved

The affected hosts are back online

Identified

One of our upstream providers is performing emergency network maintenance on a subset of hosts in ORD. Some machines in ORD may be unreachable during the incident. A small subset of MPG clusters are running with reduced HA due to their replicas being on the affected hosts.

Fly.io in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

23

Days with an incident

18

Median duration

1 h 28 min

This incident

84% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

12 h 53 min
median 1 h 28 min
90 days agoToday

Other Fly.io incidents

All incidents

Fly.ioยทElevated Machine start failures in ARN

Fly.io reports elevated Machine start failures in the ARN region. The provider fixed the issue, and the incident is resolved. The outage lasted about 61 minutes. To work around the problem, replace affected machines with a new one using fly machine clone.

Resolved

Fly.ioยทEmergency maintenance in IAD

Fly.io reports an emergency network maintenance in the IAD region. Machines on some hosts were unreachable. Fly.io reports that the maintenance is resolved. It lasted 38 minutes.

Resolved

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

Outbound IPv4 connectivity failed for machines with static egress IPs in the ARN, JNB, and GRU regions. IPv6 connectivity was not affected. Fly.io resolved the incident on 1 November 2026 after 130 minutes.

Resolved

Fly.ioยทSlow image pulls delaying Machine starts in IAD

Image pull times in IAD have returned to normal.

Resolved

Fly.ioยทElevated issues with the Machines API

The incident has been resolved.

Resolved

Follow Fly.io

Your coding agent knows when Fly.io is down, and tells you when a failure is theirs, not yours. You can also get Fly.io incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "fly" and tell me if Fly.io has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=fly
Slack
/feed subscribe https://outages.cc/feed.xml?providers=fly

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane