← Back to the carnage
SUPABASE
🟠 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)
// The official story
Database issues in us-east-2
// Status page says
Mar 3 , 04:08 UTC Monitoring - We've fixed majority of the affected projects. They are very few projects that need extra steps to resolve. We are working on them at the moment. Mar 3 , 03:14 UTC Update - We are currently continuing with remediation actions for affected projects. If you’re affected, you can also fix it manually by restarting your project by vi
🔗 Official status page (for the PR-approved version)
https://status.supabase.com/incidents/ktlmc2pqh6k7Supabase's Greatest Hits
🟢 SUPABASE
1d 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. (Auto-resolved: no updates in 24h)
🟢 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)