← Back to the carnage
FLY

🟠 Someone's upstream provider decided 7am was prime time for emergency maintenance. AMS apps are experiencing the networking equivalent of a hiccup—some are fine, others are definitely not. Welcome to the fun zone. (Auto-resolved: no updates in 24h)

⏰ Feb 09, 2026 Fixed (for now) spotted via status_rss

// The official story

Degraded network in AMS

// Status page says

Feb 9 , 07:17 UTC Investigating - One of our upstream providers is performing an emergency DC maintenance. You may see degraded connectivity on some of your apps in AMS. Most apps in AMS are not affected.

🔗 Official status page (for the PR-approved version)

https://status.flyio.net/incidents/0vy3bbzc5fjz

Fly'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)