outages.live
Live
Fly.ioIncident ยท 2026-11-02 12:34 UTC

Elevated Machine start failures in ARN

ResolvedOfficial update
0

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.

State

Resolved

Started

1 h ago

2026-11-02 12:34 UTC

Lasted

1 h 1 min

until 2026-11-02 13:35 UTC

Worst impact

Degraded

Timeline

3 updates
12:3412:4913:0413:2013:35
DegradedNoticeUpdate postedTimes in UTC

Investigating

1 h 1 min 100%

Updates

Times in UTC

As posted by Fly.io

Resolved2026-11-02 13:35 UTC

We have fixed the underlying issue caused failed Machine starts in ARN

Investigating2026-11-02 12:45 UTC

We're currently investigating an elevated level of machine start failures. Workaround in the meantime would be to [replace affected machines ](https://docs.fly.io/apps/trouble-host-unavailable#apps-with-one-machine-and-no-volumes)with a new one: `fly machine clone `

Investigating2026-11-02 12:36 UTC

We're currently investigating an elevated level of machine start failures. Workaround in the meantime would be to [replace affected machines ](https://docs.fly.io/apps/trouble-host-unavailable#apps-with-one-machine-and-no-volumes)with a new one: `fly machine clone `

Fly.io in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

22

Days with an incident

17

Median duration

1 h 33 min

This incident

34% 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 33 min
90 days agoToday

Other Fly.io incidents

All incidents

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.

Resolvedresolved 2 h ago

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.

Resolvedresolved 17 h ago

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

Image pull times in IAD have returned to normal.

Resolvedresolved 3 d ago

Fly.ioยทElevated issues with the Machines API

The incident has been resolved.

Resolvedresolved 4 d ago

Fly.ioยทCreating WireGuard peers in ARN is currently broken

The ARN WireGuard gateways are up

Resolvedresolved 4 d ago

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