β Back to the carnage
SUPABASE
π 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)
// The official story
Documents Search Unavailable
// Status page says
Jul 28 , 14:06 UTC Identified - We noticed the search function for our documentation was not available as it should be. We're making the necessary updates to fix that problem.
π Official status page (for the PR-approved version)
https://status.supabase.com/incidents/pg5mnvsyxl31Supabase'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
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)