outages.live
Live
Fly.ioIncident · 2026-10-03 08:01 UTC

Partial outage in AMS

ResolvedOfficial update

All impacted services are operational now.

The latest update from Fly.io.

State

Resolved

Started

29 d ago

2026-10-03 08:01 UTC

Lasted

57 min

until 2026-10-03 08:57 UTC

Worst impact

Major outage

Timeline

5 updates
08:0108:1508:2908:4308:57
Major outageUpdate postedTimes in UTC

Identified

19 min 33%

Monitoring

38 min 67%

Updates

Times in UTC

As posted by Fly.io

Resolved2026-10-03 08:57 UTC

All impacted services are operational now.

Monitoring2026-10-03 08:35 UTC

All MPG clusters have recovered. We are monitoring for additional impact.

Monitoring2026-10-03 08:19 UTC

All hosts are back online. MPGv2 control plane is fully operational now. Some MPGv1 clusters in AMS might be degraded while MPGv1's control plane recovers.

Identified2026-10-03 08:08 UTC

Those hosts are coming back online after a brief interruption. We are assessing the impact on MPG.

Identified2026-10-03 08:01 UTC

Some of our hosts are offline in AMS. Control plane for Managed Postgres v1 and v2 in AMS is unavailable as a result of this. MPG clusters should remain online but any control plane ops will fail. Some machines in AMS are also unavailable.

Fly.io in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

19

Days with an incident

15

Median duration

1 h 38 min

This incident

42% 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 38 min
90 days agoToday

Other Fly.io incidents

All incidents

Fly.io·Slow image pulls delaying Machine starts in IAD

Image pull times in IAD have returned to normal.

Resolvedresolved 1 d ago

Fly.io·Elevated issues with the Machines API

The incident has been resolved.

Resolvedresolved 2 d ago

Fly.io·Creating WireGuard peers in ARN is currently broken

The ARN WireGuard gateways are up

Resolvedresolved 3 d ago

Fly.io·Degraded networking to AWS IPs

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

Resolvedresolved 5 d ago

Fly.io·Packet loss in IAD

The congestion affecting our upstream provider has been resolved. We are observing a return to normal levels of networking performance in IAD region.

Resolvedresolved 6 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