FLY

🔴 GRU edge nodes decided to BSOD themselves, taking critical services down with them. Traffic routing through São Paulo is now a game of roulette. Engineers are frantically rebooting things and pretending they knew this would happen. (Auto-resolved: no updates in 24h)

⏰ Jun 10, 2026 Fixed (for now) spotted via status_rss

// The official story

Ingress Traffic issues in GRU

// Status page says

Jun 10 , 19:39 UTC Identified - Some of our edge nodes in GRU has suffered an error that crashed some of the critical services. We're currently working to bring them back online. Some traffic entering through GRU (i.e. users connecting from around GRU) may be temporarily affected.

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

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

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)