← Back to the carnage
SUPABASE
🟠 Someone forgot to pay the AWS electricity bill in Europe. Supabase projects in eu-west-3 are currently playing hide-and-seek with their infrastructure, courtesy of an upstream EC2 meltdown. Team is desperately calling AWS support. (Auto-resolved: no updates in 24h)
// The official story
Some projects unavailable in eu-west-3
// Status page says
Apr 27 , 12:39 UTC Identified - Posting this. “We are seeing an increase in projects unavailable in eu-west-3 following an upstream issue with EC2 instances in the region. The team is working on restoring access to these projects”
🔗 Official status page (for the PR-approved version)
https://status.supabase.com/incidents/m8fzj42277s1Supabase'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)