← Back to the carnage
SUPABASE

πŸ”΄ 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)

⏰ Sep 16, 2026 Fixed (for now) spotted via status_rss

// The official story

Auth Service Outage

// Status page says

Sep 16 , 07:17 UTC Identified - We have identified an issue related to the Auth service on some projects. We are actively working on a fix.

πŸ”— Official status page (for the PR-approved version)

https://status.supabase.com/incidents/frmk3zk2cwql

Supabase's Greatest Hits

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