← Back to the carnage
SUPABASE
🟠 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)
// The official story
Endpoints in Americas regions returning 500 Internal server error
// Status page says
Jul 6 , 15:10 UTC Update - The scope of the errors is across regions in the Americas. We are narrowing down the likely causal chains. Jul 6 , 14:47 UTC Update - The 500 errors are limited to us-east-1, we are actively exploring causes. Jul 6 , 14:45 UTC Investigating - Multiple endpoints are retur
🔗 Official status page (for the PR-approved version)
https://status.supabase.com/incidents/mkt5vw3qxh08Supabase'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)