β Back to the carnage
FLY
{ "skip": true } ``` This is scheduled/planned maintenance, so it gets skipped per the rules. (Auto-resolved: no updates in 24h)
// The official story
Platform Wide Rolling Host Reboots
// Status page says
Status: Identified We will be imminently applying rolling restarts across all hosts in our fleet for a critical maintenance. Customer Machines, volumes, and MPG cluster instances on each host will be unavailable while their host reboots. Each host will be unavailable for 15 - 20 minutes during the restart, and multiple hosts in a region may be down at once. Users should expect a period of downtime or disruption for their apps, especially if they are running on a single machine
π Official status page (for the PR-approved version)
https://status.flyio.net//incidents/01M52RAWMVC0NKEBRDKC3VXT3KFly's Greatest Hits
π’ FLY
6d ago
π 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)
π’ 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)