SUPABASE

⚪ Supabase sweated through a hardware failure in us-east-2 that left projects wondering if they were dumped. The team resurrected all affected databases by 17:02 UTC. If your project's still not texting back, they want to hear from you. (Auto-resolved: no updates in 24h)

⏰ Jun 17, 2026 Fixed (for now) spotted via status_rss

// The official story

Hardware failure in us-east

// Status page says

Jun 17 , 17:02 UTC Resolved - We have now recovered all Projects affected by the outage in us-east-2. Jun 17 , 16:13 UTC Monitoring - All the identified affected projects in us-east-2 are now healthy. If your project is in us-east and not responsive, please open a ticket to let us know. Jun 17 , 15:44 UTC Ide

🔗 Official status page (for the PR-approved version)

https://status.supabase.com/incidents/dj3n11rv8q6h

Supabase'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)