← Back to the carnage
SUPABASE
🔴 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)
// The official story
Outage in US-East-2 (Ohio)
// Status page says
Feb 13 , 01:53 UTC Resolved - Service has been fully restored. All impacted jobs have been requeued and are currently processing normally. We will be publishing a public post-mortem with additional details about this incident. Feb 13 , 01:26 UTC Monitoring - The revert of the change helped and most of the metrics are back to the pre incident levels. We are requeuing failed
🔗 Official status page (for the PR-approved version)
https://status.supabase.com/incidents/pqrf96m6fzxkSupabase'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)