← Back to the carnage
FLY

🟠 Fly's Los Angeles region decided to experience a power outage because apparently the grid runs on hopes and prayers. Apps and Postgres clusters are now as responsive as a broken answering machine. Upstream datacenter forgot to pay the electric bill. (Auto-resolved: no updates in 24h)

⏰ Nov 12, 2026 Fixed (for now) spotted via status_rss

// The official story

LAX region outage

// Status page says

Status: Identified A subset of Apps and Managed Postgres clusters in the LAX region are unavailable due to an upstream datacenter power outage. Affected components LAX - Los Angeles, California (US) (Degraded performance)

πŸ”— Official status page (for the PR-approved version)

https://status.flyio.net//incidents/01M76HANB3XQC6WYKPA69WQN8Z

Fly's Greatest Hits

🟒 FLY Nov 06, 2026
🟠 Some Fly hosts in Ashburn decided IPv6 egress is overrated. Upstream provider ghosted them. Your internet-facing services are fine, but anything trying to leave? Stuck in the waiting room. (Auto-resolved: no updates in 24h)
🟒 FLY Nov 02, 2026
🟑 Fly's having a 'machines won't start' moment in ARNβ€”turns out telling users to clone their machines instead of, you know, fixing it, is peak engineering. Workaround: become your own DevOps. (Auto-resolved: no updates in 24h)
🟒 FLY Oct 16, 2026
🟠 Fly's metrics dashboard went dark because the host decided maintenance was more important than your observability. Good news: your actual logs and metrics are fine, just the viewing device is in timeout. Should be back in 20 minutes, assuming the infrastructure gods are feeling generous. (Auto-resolved: no updates in 24h)
🟒 FLY Oct 16, 2026
{ "skip": true } ``` This is scheduled/planned maintenance, so it gets skipped per the rules. (Auto-resolved: no updates in 24h)