← Back to the carnage
FLY

🟑 Your Redis is experiencing what we call 'selective amnesia'β€”it's still there, just not talking to anyone. Fly and Upstash are playing tech support ping-pong while your connections contemplate the void. (Auto-resolved: no updates in 24h)

⏰ May 11, 2026 Fixed (for now) spotted via status_rss

// The official story

Upstash Redis Outage

// Status page says

May 11 , 14:36 UTC Investigating - We are working with Upstash to investigate issues with their Fly hosted Redis service. Users may see degraded or failing connections connecting to their Upstash Redis databases at this time.

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

https://status.flyio.net/incidents/vzh5tq5ddb48

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)