outages.live
Live

Fly.io

Fly.io is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

20

Days with an incident

16

Median duration

1 h 49 min

Longest incident

12 h 53 min

Components

25
Customer Applications Operational
90 days agoNo incidentsToday
Dashboard Operational
90 days agoNo incidentsToday
Machines API Operational
90 days agoNo incidentsToday
AMS - Amsterdam, Netherlands Operational
90 days agoNo incidentsToday
ARN - Stockholm, Sweden Operational
90 days agoNo incidentsToday
BOM - Mumbai, India Operational
90 days agoNo incidentsToday
CDG - Paris, France Operational
90 days agoNo incidentsToday
DFW - Dallas, Texas (US) Operational
90 days agoNo incidentsToday
EWR - Secaucus, NJ (US) Operational
90 days agoNo incidentsToday
FRA - Frankfurt, Germany Operational
90 days agoNo incidentsToday
GRU - Sao Paulo, Brazil Operational
90 days agoNo incidentsToday
IAD - Ashburn, Virginia (US) Operational
90 days agoNo incidentsToday
JNB - Johannesburg, South Africa Operational
90 days agoNo incidentsToday
LAX - Los Angeles, California (US) Operational
90 days agoNo incidentsToday
LHR - London, United Kingdom Operational
90 days agoNo incidentsToday
NRT - Tokyo, Japan Operational
90 days agoNo incidentsToday
ORD - Chicago, Illinois (US) Operational
90 days agoNo incidentsToday
SIN - Singapore Operational
90 days agoNo incidentsToday
SJC - San Jose, California (US) Operational
90 days agoNo incidentsToday
SYD - Sydney, Australia Operational
90 days agoNo incidentsToday
YYZ - Toronto, Canada Operational
90 days agoNo incidentsToday
Persistent Storage (Volumes) Operational
90 days agoNo incidentsToday
Deployments Operational
90 days agoNo incidentsToday
Remote Builds Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Nov 1, 2026

Duration2 h 10 min18:50 to 21:00Outbound IPv4 connectivity failures in ARN, JNB, and GRUDegraded

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 after 2 hours and 10 minutes.

Oct 30, 2026

Duration1 h 28 min20:24 to 21:52Slow image pulls delaying Machine starts in IADDegraded

Image pull times in IAD have returned to normal.

Oct 29, 2026

Duration48 min20:40 to 21:28Elevated issues with the Machines APIDegraded

The incident has been resolved.

Duration4 h 48 min11:01 to 15:49Creating WireGuard peers in ARN is currently brokenNotice

The ARN WireGuard gateways are up

Oct 26, 2026

Duration6 h 6 min14:34 to 20:40Degraded networking to AWS IPsNotice

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

Duration2 h 33 min01:50 to 04:24Packet loss in IADDegraded

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

Oct 25, 2026

Duration17 min10:46 to 11:02MPGv2 IAD control plane is read-onlyDegraded

Control plane operations in IAD, including resizing and changing plans, are working normally again.

Oct 20, 2026

Duration6 h 59 min16:54 to 23:53Capacity issues in GRU regionDegraded

We have added host capacity to the region. Machine creates, starts and remote builds in GRU should now be functioning as normal.

Oct 16, 2026

Duration1 h 16 min18:08 to 19:24Fly-metrics.net Grafana Dashboard OutagePartial outage

The [fly-metrics.net](https://fly-metrics.net) hosted Grafana and log search instance is now fully reachable.

Duration12 h 53 min16:22 to 05:15Platform Wide Rolling Host RebootsPartial outage

All host restarts have been completed and the platform is operating normally. A small number of hosts remain degraded or offline for apps and for MPG. Those impacted can see further updates on the personalized status page viewable at

Oct 15, 2026

Duration2 h 4 min09:30 to 11:33Elevated errors creating apps and managing secretsDegraded

Between 06:40 and 09:50 UTC some app creation and secrets requests failed or timed out. Running apps and Machines were not affected.

Oct 13, 2026

Duration4 h 25 min09:25 to 13:50Historical logs are currently delayedDegraded

This has been resolved

Oct 8, 2026

Duration31 min21:23 to 21:54Sprite creates failingMajor outage

The issue has been resolved.

Duration20 min05:40 to 06:00LHR network issuesPartial outage

This incident has been resolved.

Oct 6, 2026

Duration3 min11:59 to 12:02Impaired IPv6 connectivity in ORDDegraded

IPv6 upstream issue was solved.

Oct 3, 2026

Duration57 min08:01 to 08:57Partial outage in AMSMajor outage

All impacted services are operational now.

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.live/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.live/feed.xml?providers=fly
Slack
/feed subscribe https://outages.live/feed.xml?providers=fly

Go from tracking outages to fixing production issues with Polylane.

Try Polylane