SUPABASE

🔴 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)

⏰ Aug 28, 2026 Fixed (for now) spotted via status_rss

// The official story

Projects failing to load Supautils in multiple regions

// Status page says

Aug 28 , 16:18 UTC Resolved - PostgreSQL 15 projects were failing to load /usr/lib/postgresql/15/lib/supautils.so because GLIBC_2.33 is unavailable on affected hosts. This disrupted database access in multiple regions. Rollback is now complete and we are seeing access restored to projects in the affected regions.

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

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

Supabase's Greatest Hits

🔴 SUPABASE 23h 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.

🟢 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 Jul 28, 2026

🟠 Supabase's documentation search decided to play hide-and-seek with your queries. Turns out even databases need to learn how to find things. Engineers are frantically flipping through code trying to locate their own locate function. (Auto-resolved: no updates in 24h)