FLY

🟠 Fly deployed something that shouldn't have been deployed, now their secrets service is taking an unplanned sabbatical. Your apps are still running, but good luck spinning up anything new or changing your passwords—the service is too busy having an existential crisis to help. (Auto-resolved: no updates in 24h)

⏰ Aug 14, 2026 Fixed (for now) spotted via status_rss

// The official story

Secret service outage

// Status page says

Aug 14 , 19:30 UTC Identified - We are working to recover our secrets service after a failed deployment. Apps continue to run, but it is not possible to create new apps or update secrets at this time.

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

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

Fly's Greatest Hits

🟢 FLY 1d ago

⚪ 🎭 Turns out SSL certificates have commitment issues too. Fly's sprite subdomain decided to play hard-to-get with a certificate error, leaving developers staring at broken image tags for an hour. Romance was rekindled at 00:45 UTC. (Auto-resolved: no updates in 24h)

🟢 FLY 4d ago

🟠 Fly's sprite creation engine decided Europe was the only continent worth serving. Everyone else gets to experience the joy of failed deployments across all regions. Investigating why the infrastructure gods chose geographic discrimination today. (Auto-resolved: no updates in 24h)

🟢 FLY 5d ago

🔴 Fly's LHR datacenter discovered BGP is hard. Regional anycast and static IPs went dark while traffic gets rerouted to the continent like some kind of digital Brexit. Engineers identified the problem, which is tech-speak for 'we found where the fire is.'. (Auto-resolved: no updates in 24h)

🟢 FLY Oct 03, 2026

🟠 Fly's Amsterdam region decided to take an unscheduled nap. Management plane and AMS hosts are stumbling back online while engineers frantically assess the damage. MPG impact assessment in progress—translation: they're still counting the bodies. (Auto-resolved: no updates in 24h)