← Back to the carnage
FLY
🟡 Fly discovered that some machines in Chicago suddenly can't speak IPv6. Engineers are speed-running a three-way conference call with upstream providers while affected apps contemplate their life choices in neighboring regions. (Auto-resolved: no updates in 24h)
// The official story
IPv6 outage for some machines in ORD
// Status page says
May 21 , 12:02 UTC Investigating - We're working with our upstream providers to investigate an IPv6 networking failure in ORD. Impacted apps may wish to temporarily provision additional capacity in nearby regions.
🔗 Official status page (for the PR-approved version)
https://status.flyio.net/incidents/nbgp330ss6k8Fly'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)