LAX region outage
Fly.io reports a major outage in the LAX region. A subset of Apps and Managed Postgres clusters in LAX are unavailable. Fly.io identified an upstream datacenter power outage as the cause. Hosts are starting to come back online, but Apps and Managed Postgres clusters may still be unreachable.
State
Identified
Started
Ongoing for
42 min
Worst impact
Major outage
Timeline
4 updatesInvestigating
7 min 17%
Identified
35 min 83%
Updates
Times in UTCAs posted by Fly.io
We are seeing hosts start to come back online. Apps and Managed Postgres clusters may still be unreachable at this time.
A subset of Apps and Managed Postgres clusters in the LAX region are unavailable due to an upstream datacenter power outage.
A subset of Apps and Managed Postgres clusters in the LAX region are unavailable due to an upstream datacenter power outage.
We are investigating an upstream provider outage in LAX region. Apps and Managed Postgres clusters in LAX region may be unreachable at this time.
Fly.io in the last 90 days
Full historyIncidents in 90 days
25
Days with an incident
20
Median duration
1 h 22 min
This incident
48% shorter than the median
Other Fly.io incidents
All incidentsFly.ioยทIPv6 egress issues on a subset of IAD hosts
IPv6 egress did not work on a subset of IAD hosts in Fly.io. The issue came from an upstream provider. Fly.io reported that the incident is resolved and that all affected hosts are back to normal. The incident lasted 22 minutes.
Fly.ioยทEmergency network maintenance on a subset of hosts in ORD
Fly.io reports that some machines in ORD were unreachable. A small subset of MPG clusters ran with reduced HA. Fly.io says the incident is resolved and the affected hosts are back online. The incident lasted about 14 minutes.
Fly.ioยทElevated Machine start failures in ARN
Fly.io reported elevated Machine start failures in the ARN region. Fly.io fixed the problem and reports that the incident is resolved. The incident lasted 61 minutes.
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 complete and the incident is resolved. The incident lasted 38 minutes.
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 after 2 hours and 10 minutes.
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.
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.
https://outages.live/feed.xml?providers=fly/feed subscribe https://outages.live/feed.xml?providers=flyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane