> cat /var/log/failures.log

A comprehensive record of when things went wrong.

All the chaos openai (63) snyk (58) webflow (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 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)
🟢 MUX Mar 03, 2026
🟡 Mux's data collection pipeline decided to ghost its users starting 05:14 UTC. Your metrics are now in a quantum state—simultaneously delayed and missing. Schrödinger's analytics. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Mar 03, 2026
🟠 Supabase's us-east-2 region had a database meltdown, but they've resurrected most projects. A few holdouts are still playing dead and need manual revival via the restart button. Engineering is basically doing CPR on the last ones. (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)
🟢 SNYK Mar 03, 2026
⚪ Snyk's open source testing got the yips in US-02, but they've already fixed it and are now nervously watching it like a new parent checking on a sleeping baby. The CLI monitor command briefly decided snapshots were optional. (Auto-resolved: no updates in 24h)
🟢 AWS Mar 03, 2026
🔴 Drone strikes turned two UAE data centers into modern art installations and gave Bahrain's infrastructure a proximity haircut. AWS Middle East is discovering that 'act of God' clauses don't cover 'act of war.' Connectivity is what you might call 'collateral damage.'. (Auto-resolved: no updates in 24h)
🟢 VERCEL Mar 02, 2026
🔴 VERCEL - Dubai region (dxb1) is unavailable and traffic is being re-routed. (Auto-resolved: no updates in 24h)
🟢 COCKROACHDB Mar 02, 2026
🔴 Two availability zones collapsed in AWS me-central-1, leaving clusters completely offline. me-south-1 got the degraded experience special with single AZ failure. GCP and Azure laughing from the sidelines while customers frantically dust off disaster recovery plans written in 2019. (Auto-resolved: no updates in 24h)
🟢 LINEAR Mar 02, 2026
🟠 Linear's bug put agent apps in timeout jail—Cursor, Copilot, and Codex all got mysteriously banned. Fix is rolling out now, which is great news for the robots you've trained to write your code for you. (Auto-resolved: no updates in 24h)
🟢 VERCEL Mar 02, 2026
🔴 Vercel's dxb1 region decided to go offline, forcing your traffic into the Mumbai region like an overbooked flight. New deployments to Dubai are now accepting applications in the spring. Your ops team is definitely not fine. (Auto-resolved: no updates in 24h)
⚪ WEBFLOW Mar 02, 2026
⚪ 🛒 Webflow's upstream payment provider decided to take a siesta between 07:20-12:40 UTC, leaving customers unable to buy or upgrade plans. The provider eventually woke up, found the bug, and fixed it. Everyone's pretending this was totally fine and not a screaming nightmare.
⚪ WEBFLOW Mar 02, 2026
🟠 Webflow's upstream payment provider decided to ghost transactions for a bit, but apparently got their act together. If your upgrade finally went through, congratulations—you've been provisionally forgiven by the credit card gods.
🟢 MONGODB Mar 02, 2026
🔴 MongoDB's Middle Eastern clusters decided to play hide-and-seek across UAE and Bahrain. AWS is blaming 'infrastructure incidents' which translates to 'we also don't know what happened.' Your data's not lost, just spiritually unavailable. (Auto-resolved: no updates in 24h)
🟢 COCKROACHDB Mar 02, 2026
🔴 Two availability zones decided to ghost me-central-1 entirely while me-south-1 is limping along on life support. AWS infrastructure apparently scheduled unplanned maintenance with all the grace of a cockroach under a shoe. (Auto-resolved: no updates in 24h)
🟢 GRAFANA Mar 02, 2026
🟠 Grafana's prod-eu-west-3 logs decided to become read-only exhibits in a museum. Write operations hit a wall faster than a Brexit negotiation, and the engineering team is now playing archaeological dig with their own infrastructure. (Auto-resolved: no updates in 24h)
🟢 SNOWFLAKE Mar 02, 2026
🔴 Snowflake's Middle East region got unplugged by a power outage. AWS is doing that thing where they say 'multiple hours' which in corporate time means 'we genuinely have no idea.' Recovery happening but slower than your ex returning texts. (Auto-resolved: no updates in 24h)
🟢 COCKROACHDB Mar 01, 2026
🔴 Real actual fire took out an AWS data center. Not a metaphor. Not a typo. CockroachDB customers in the region are experiencing cluster operation failures while AWS plays firefighter. Next update allegedly by 4PM PST, assuming the sprinklers work. (Auto-resolved: no updates in 24h)
🟢 AWS Mar 01, 2026
🔴 Apparently someone threw objects at the data center hard enough to create sparks and fire in ME-CENTRAL-1. Fire department cut power and generators, AWS is now playing the waiting game for clearance to restore service. Your resilient multi-AZ architecture just became a single-AZ situation. (Auto-resolved: no updates in 24h)
🟢 COCKROACHDB Mar 01, 2026
🔴 AWS me-central-1 lost power, and CockroachDB's clusters are discovering they can't actually survive in the dark. AWS is playing electrician while your cluster operations contemplate the fragility of cloud infrastructure. Check back when the lights come back on. (Auto-resolved: no updates in 24h)
🟢 MONGODB Mar 01, 2026
🟠 MongoDB's Middle East clusters decided to go dark after AWS's power grid got a little too creative with the outage lottery. One availability zone in me-central-1 discovered that electricity is apparently optional. Delayed operations, increased errors, and the usual chorus of engineers refreshing status pages like slot machines. (Auto-resolved: no updates in 24h)