← Back to the carnage
FLY

🔴 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)

⏰ 5d ago Fixed (for now) spotted via status_rss

// The official story

LHR network issues

// Status page says

Status: Identified We are working to resolve an issue with our BGP announcements in LHR (London, UK) region. Regional anycast and static egress IPs are currently not functional and anycast traffic is being rerouted to nearby regions. Affected components LHR - London, United Kingdom (Partial outage)

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

https://status.flyio.net//incidents/01M4D0E2HPJYRMB4DJT4PKYTM5

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 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)
🟢 FLY Sep 26, 2026
🔴 AMS region discovered what it's like to be unplugged from reality. Fly is playing phone tag with upstream providers, hoping someone remembers where they left the internet. Your containers are just vibing in the void right now. (Auto-resolved: no updates in 24h)