> cat /var/log/failures.log

A comprehensive record of when things went wrong.

All the chaos openai (63) webflow (57) snyk (57) grafana (47) fly (38) fivetran (37) supabase (32) hashicorp (26) github (26) anthropic (26) aws (25) linear (20) jira (17) elastic (17) lovable (16)
🟢 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)
🟢 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)
🟢 FLY Sep 23, 2026
🟠 Fly's Sprites feature went from 'just San Jose' to 'everywhere' faster than a contagion. API calls getting the silent treatment while engineers pretend their mitigations are actually doing something. (Auto-resolved: no updates in 24h)
🟢 FLY Sep 23, 2026
🟡 Fly's having an identity crisis in San Jose—their API keeps ghosting users like a bad Tinder date. Intermittent failures plaguing the region while engineers frantically check if they accidentally unplugged something important. Spoiler: they did. (Auto-resolved: no updates in 24h)
🟢 FLY Sep 02, 2026
🟡 Fly's Sprites API is playing favorites with a partial outage. Some users getting the full visual experience, others staring at loading spinners. Engineers currently playing 'guess the bug' in production. (Auto-resolved: no updates in 24h)
🟢 FLY Aug 31, 2026
⚪ Someone flipped a config switch and HTTP/2 traffic ghosted Fly Machines for a few minutes. Managed Postgres got caught in the crossfire but your actual database connections slept through the whole thing like a drunk uncle at Thanksgiving. (Auto-resolved: no updates in 24h)
🟢 FLY Aug 20, 2026
🟠 Fly's ord-0 Kubernetes cluster decided to take an unscheduled nap, and now MPG clusters are stuck in an existential crisis trying to restart. The team's frantically Googling 'why won't my cluster wake up' while your deployments contemplate the void. (Auto-resolved: no updates in 24h)
🟢 FLY Aug 14, 2026
🟠 Fly's secrets management took a nap post-deployment. Your apps are still breathing, but good luck launching new ones or rotating credentials—the service decided this was a great time for introspection. (Auto-resolved: no updates in 24h)
🟢 FLY Aug 14, 2026
🟠 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)
🟢 FLY Jul 29, 2026
🟡 Fly's playing hide-and-seek with API latency while their database takes an unscheduled nap. 503 errors are the main event, but at least your deployed apps are still breathing. For now. (Auto-resolved: no updates in 24h)
🟢 FLY Jul 14, 2026
🟠 Fly's San Jose region decided some hosts needed an unscheduled vacation. Your app in SJC? Might be reachable, might not—it's a lucky dip. Engineers are currently checking if the servers are actually offline or just ignoring Slack messages. (Auto-resolved: no updates in 24h)
🟢 FLY Jul 03, 2026
🟡 Fly's Chicago data center decided to ghost its upstream provider, leaving machines catatonic and Postgres clusters playing dead. Deploys are experiencing the joy of quantum computing—simultaneously succeeding and failing until observed. (Auto-resolved: no updates in 24h)
🟢 FLY Jun 17, 2026
🟡 Fly's SIN region is playing hide-and-seek with network packets—some are winning. Apps in Singapore are currently auditioning for the role of 'unreachable,' and engineers are pretending they know what happened. Classic case of 'investigating' being corporate for 'we're checking Slack right now.'. (Auto-resolved: no updates in 24h)
🟢 FLY Jun 15, 2026
🟠 Macaroon auth system decided to stop working, taking the Machines API down with it. New deployments are DOA, but your already-running stuff is fine—for now. Engineers are sweating through the fix. (Auto-resolved: no updates in 24h)
🟢 FLY Jun 11, 2026
🟠 Fly discovered that their North American network routes have commitment issues—some packets are ghosting while others contemplate existence mid-transit. Engineers are playing whack-a-mole with 'impacted backbones' like they're herding cats made of fiber optics. (Auto-resolved: no updates in 24h)
🟢 FLY Jun 10, 2026
🔴 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)
🟢 FLY Jun 09, 2026
🔴 Managed Postgres control plane decided the IAD region needed a surprise reboot party. Some clusters are currently experiencing what engineers call 'temporary permanence.' Fly's working on convincing them to come back online. (Auto-resolved: no updates in 24h)
🟢 FLY May 22, 2026
🟡 Some machines in SIN woke up and decided IPv6 was optional. Fly's engineers are now playing detective with network packets while the rest of us watch the investigation updates roll in like a slow-motion car crash. (Auto-resolved: no updates in 24h)
🟢 FLY May 21, 2026
🟡 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)
🟢 FLY May 11, 2026
🟡 Your Redis is experiencing what we call 'selective amnesia'—it's still there, just not talking to anyone. Fly and Upstash are playing tech support ping-pong while your connections contemplate the void. (Auto-resolved: no updates in 24h)
🟢 FLY May 08, 2026
🟠 LetsEncrypt decided to take an unscheduled sabbatical, torching Fly's certificate creation. Your existing certs and preview domains are chilling just fine, but good luck adding new ones until the certificate overlords get their act together. (Auto-resolved: no updates in 24h)
🟢 FLY May 07, 2026
🟡 Some hosts in Fly's San Jose region decided to ghost their upstream network. Your apps are now experiencing what we call 'quantum computing' — simultaneously running and not running. Schrödinger would be proud. (Auto-resolved: no updates in 24h)
🟢 FLY May 05, 2026
🟡 Petsem went full ostrich mode and buried itself. Fly's investigation team is now playing detective with zero leads, which tracks for a service named after a tiny flying insect that keeps crashing into windows. (Auto-resolved: no updates in 24h)
🟢 FLY May 04, 2026
🟡 Grafana's log search is returning 502s like a vending machine that ate your quarters. The CLI and dashboard still work, so at least your app logs didn't completely ghost you—just the fancy search interface decided to play dead. (Auto-resolved: no updates in 24h)
🟢 FLY Apr 09, 2026
🟡 Some ORD region hosts went full Houdini, taking Managed Postgres clusters with them. Fly's provider relationship is being tested in real time. Your apps in Chicago are experiencing what we call 'an unexpected vacation'. (Auto-resolved: no updates in 24h)
🟢 FLY Apr 09, 2026
🟡 Fly's managed Postgres in SYD decided new clusters are too much responsibility right now. Existing DBs mostly chilling, but creates/restores/upgrades are getting the silent treatment. Some clusters did surprise failovers—the database equivalent of ghosting your primary. (Auto-resolved: no updates in 24h)
🟢 FLY Mar 03, 2026
🟡 Fly's billing dashboard went full ostrich—refuses to load cost data and pretend everything's fine. Engineers are investigating why the thing designed to show you money problems is now the money problem. (Auto-resolved: no updates in 24h)
🟢 FLY Mar 03, 2026
⚪ 🔐 Vault cluster went catatonic, turning certificate operations into an infinite timeout buffet. API requests decided to just hang out indefinitely while TLS connections waited for Godot. All better now, but that was 12 minutes of pure infrastructure theater. (Auto-resolved: no updates in 24h)
🟢 FLY Feb 27, 2026
🟠 Dallas and Ashburn data centers are tapped out—new machines refuse to materialize and Depot builders are playing hide-and-seek. Your deploys get to experience the joy of infinite waiting, which sounds meditative until you realize it's actually a capacity hostage situation. (Auto-resolved: no updates in 24h)
🟢 FLY Feb 26, 2026
🟠 Fly's having inventory problems in two regions—new machines are DOA and Depot builders are playing dead. Management suggests you beg your containers to move elsewhere or disable Depot entirely, because apparently 'scaling' is still a theoretical concept. (Auto-resolved: no updates in 24h)
🟢 FLY Feb 14, 2026
🟠 Managed Postgres in ORD decided replicas are optional and primaries are suggestions. Some clusters got the memo about failover, others are still checking their email. (Auto-resolved: no updates in 24h)
🟢 FLY Feb 09, 2026
🟠 Someone's upstream provider decided 7am was prime time for emergency maintenance. AMS apps are experiencing the networking equivalent of a hiccup—some are fine, others are definitely not. Welcome to the fun zone. (Auto-resolved: no updates in 24h)
🟢 FLY Feb 07, 2026
🟡 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)
🟢 FLY Feb 05, 2026
🟠 MPG clusters in Amsterdam, DC and Singapore are having an identity crisis thanks to a downstream Machines API meltdown. Most users just got slower replicas; unlucky few can't reach their primary at all. Fly's firefighters are on scene. (Auto-resolved: no updates in 24h)
🟢 FLY Feb 05, 2026
🟠 Turns out 'degraded' is Fly's polite way of saying their database replicas forgot how to do their job. MPG clusters in Amsterdam and DC are having an identity crisis—some can't even find their primary node. The Machines API decided to pull the fire alarm, and everyone's pretending this was intentional. (Auto-resolved: no updates in 24h)