β Back to the carnage
SUPABASE
π 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)
// The official story
Project Actions Failing Across Multiple Regions
// Status page says
Jul 17 , 20:21 UTC Monitoring - The mitigation has returned project activity to normal performance. Project actions that failed during the outage are being requeued to run. We will continue to monitor to ensure project functionality. Jul 17 , 19:45 UTC Identified - We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observ
π Official status page (for the PR-approved version)
https://status.supabase.com/incidents/xhs8d4l3wtscSupabase'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)