> 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)
🔴 SUPABASE 23h ago
🟡 Supabase's logging service decided to ghost its own data. Logs are either fashionably late or taking an indefinite sabbatical. The irony of your observability tool becoming unobservable is not lost on anyone.
🟢 SUPABASE Sep 16, 2026
🔴 Supabase's auth service decided selective amnesia was a personality trait. Some projects can't log in because apparently credentials are just vibes now. Engineers are frantically searching the couch cushions for the fix. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Sep 10, 2026
🟡 Supabase projects decided to ghost their users, but engineers found the off switch and flipped it back. Global rollout underway—turns out the fix was just turning it off and on again. Your database's 'contemplation phase' is now optional. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Aug 28, 2026
🔴 PostgreSQL 15 threw a tantrum because some ancient GLIBC version went missing. Database access got ghosted across multiple regions. Engineers performed emergency archaeology and rolled back the chaos. We're all friends again now. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Jul 28, 2026
🟠 Supabase's documentation search decided to play hide-and-seek with your queries. Turns out even databases need to learn how to find things. Engineers are frantically flipping through code trying to locate their own locate function. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Jul 17, 2026
🟠 A job in us-east-1 decided to ghost everyone's project actions across multiple regions. Supabase killed it with fire, requeued the failed tasks, and is now playing nurse. The good news: your deploys are unstuck. The bad news: they're all queued up like they're waiting for concert tickets. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Jul 16, 2026
🟠 EU-CENTRAL-1 projects went catatonic this morning—most are blinking again, but stragglers are still contemplating the void. Supabase engineers working through the survivors like archaeologists at a tech disaster site. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Jul 09, 2026
🟡 Supabase's log ingestion decided to ghost everyone across all regions. Your logs are either fashionably late or taking a permanent vacation—either way, good luck debugging production at 2 AM. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Jul 06, 2026
🟠 Supabase decided to make the entire Americas region a vending machine that only dispenses errors. Started in us-east-1, then decided to go continental. Engineers are playing geographic roulette trying to figure out which region will spontaneously combust next. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Jul 01, 2026
🟠 Supabase's 'Restore to New Project' beta decided to YOLO into the void. Turns out 'beta' is corporate speak for 'we haven't tested this part yet.' Feature going dark while engineers frantically Google 'how restore actually works.'. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Jun 30, 2026
🟠 Supabase's infrastructure pulled a Goldilocks across multiple regions—some zones got the porridge treatment while ap-northeast-2, ap-south-1, and eu-north-1 are still waiting for breakfast. Project operations are basically playing musical chairs with servers. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Jun 18, 2026
🔴 DNS record creation decided to return 500 errors like a petulant teenager, tanking project creation, pausing, and unpausing. Supabase hit the emergency brake and disabled new projects while engineers pray to the DNS gods. Impact still cascading through their infrastructure like a game of Jenga played by a toddler. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Jun 18, 2026
🟡 Supabase's DNS API decided to ghost new project creation attempts. Engineers are frantically checking if they unplugged the right cable this time. The irony of a backend service making backends inaccessible is not lost. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Jun 17, 2026
⚪ Supabase sweated through a hardware failure in us-east-2 that left projects wondering if they were dumped. The team resurrected all affected databases by 17:02 UTC. If your project's still not texting back, they want to hear from you. (Auto-resolved: no updates in 24h)
🟢 SUPABASE May 18, 2026
🔴 SUPABASE - Upgrade Shared Pooler V1 to V2 for eu-west-1 region. (Auto-resolved: no updates in 24h)
🟢 SUPABASE May 13, 2026
🟠 Supabase APIs are ghosting connections from Mullvad VPN users and possibly others, serving up timeouts and rejections like a bouncer at an exclusive club. Engineers are investigating whether this is a Mullvad-only problem or if other VPNs caught the same plague. (Auto-resolved: no updates in 24h)
🟢 SUPABASE May 08, 2026
🟠 Supabase's upgrade feature decided to commit sudoku mid-transaction. Most projects limped back to their old PostgreSQL version like a rejected lover, but some are still wedged in the upgrade machinery while engineers play database archaeologist. (Auto-resolved: no updates in 24h)
🟢 SUPABASE May 08, 2026
🟠 Supavisor connection times went full sloth mode in a single AZ after an upstream provider decided to take an unscheduled nap. Only projects living in us-east-1a got the privilege of experiencing this upstream provider's existential crisis. (Auto-resolved: no updates in 24h)
🟢 SUPABASE May 08, 2026
🔴 Supavisor decided to ghost projects in us-east-1a after an upstream provider had a complete meltdown. Turns out when your vendor's infrastructure goes dark, your availability zone follows like a sad puppy. Root cause identified, but the damage was already done. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Apr 27, 2026
🟠 Supabase discovered their multi-region deployment strategy works great—at hiding databases from users. The good news: turning it off and on again actually fixes it this time. The bad news: they had to learn about the outage the hard way. Regional whack-a-mole in full effect. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Apr 27, 2026
🟠 Someone forgot to pay the AWS electricity bill in Europe. Supabase projects in eu-west-3 are currently playing hide-and-seek with their infrastructure, courtesy of an upstream EC2 meltdown. Team is desperately calling AWS support. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Mar 26, 2026
🔴 SUPABASE - Realtime services unavailable. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Mar 07, 2026
🟡 Uploads and downloads in EU-Central-2 decided to move at continental drift speeds. Supabase is investigating why their storage suddenly developed commitment issues. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Mar 07, 2026
🟡 Supabase locked down subscription modifications while their billing provider ghosted them mid-investigation. Users stuck on their current plans like it's a bad relationship they can't escape. (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)
🟢 SUPABASE Feb 24, 2026
🟠 DNS servers in AP-South-1/Southeast-2 decided to ghost users while Supabase infrastructure plays innocent. ISP's fault apparently, but switching to Cloudflare DNS (1.1.1.1) might resurrect your connections if you're feeling charitable toward troubleshooting. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Feb 24, 2026
🟠 DNS servers in AP-South-1 and AP-Southeast-2 decided to forget how to resolve Supabase endpoints. Supabase infrastructure is fine—turns out the problem was your ISP's DNS having an existential crisis. Switching to Cloudflare DNS apparently works if you enjoy playing tech support roulette. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Feb 13, 2026
🔴 Ohio's finest backend service went full amnesiac for 27 minutes, ate all the jobs, then remembered how to work. Revert button earned its paycheck today. Post-mortem incoming for those who enjoy reading engineering apology notes. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Feb 05, 2026
🔴 Someone shipped a landmine in [email protected] and Edge Functions walked right into it. The fix? Pretend v2.95.0 never existed and rollback to v2.94.1 like it's a bad relationship. If you manually pinned the cursed version, congrats, you're the QA team now. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Feb 05, 2026
🟡 Some US customers can't resolve Supabase domains, but their actual databases are running fine. It's like having a working car with a broken GPS—the engine's great, you just can't find it. Only specific DNS providers affected, because consistency is overrated. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Feb 04, 2026
🟡 Supabase's instance operations went full Sleeping Beauty—new projects won't spin up, paused ones refuse to budge. The good news: your existing projects are still breathing. Bad news: they're watching the chaos unfold. (Auto-resolved: no updates in 24h)
🟢 SUPABASE Jan 28, 2026
🟠 New instances refusing to exist in eu-west-1 thanks to the provider's infrastructure having a very public identity crisis. Read replicas, unpauses, and upgrades all ghosted—but hey, your existing projects are safe (the ones that actually made it). Error rates trending down means someone finally found the off switch. (Auto-resolved: no updates in 24h)