Live / Fly.io / Incident
Fly.io: LAX region outage
Fly.io · fly.ioCritical outageResolved2026-11-14 00:18 UTC
Public — what happened
Summary
Fly.io reported a critical outage in its LAX region starting at 00:08 UTC on 2026-11-12, during which some apps and Managed Postgres database clusters could not be reached. The company said the cause was a power outage at an upstream datacenter. Fly.io said hosts began returning within about half an hour, services were restarted, and by 01:15 UTC apps and databases were accessible again, though some app metrics were still recovering. The region was reported as running normally, but Fly.io said it kept monitoring because the datacenter had reduced redundancy and it was awaiting final confirmation from the provider; the incident is marked resolved as of 2026-11-14.
Timeline
- Started — 2026-11-12 00:08 UTC
- Investigating — 2026-11-12 00:08 UTC
- Identified — 2026-11-12 00:13 UTC (4 updates)
- Monitoring — 2026-11-12 01:15 UTC (3 updates)
- Resolved — 2026-11-14 00:18 UTC · 2 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Fly.io against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Fly.io: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Fly.io report →
More from Fly.io
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.