← Back to the carnage
FLY
🟡 Fly's Machines API decided to take an unscheduled siesta at 16:00 UTC, blessing users with 5xx errors and latency that makes dial-up look cutting edge. Engineers are currently in that special 'investigating' phase where they're really just refreshing logs and hoping something fixes itself. (Auto-resolved: no updates in 24h)
// The official story
Machines API issues
// Status page says
Feb 7 , 16:23 UTC Investigating - We are investigating widespread Machines API issues since 16:00 UTC. You may experience 5xx errors or higher latency at this time.
🔗 Official status page (for the PR-approved version)
https://status.flyio.net/incidents/w9dz70y1c6p6Fly'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)