SUPABASE

🟡 Supabase locked down subscription modifications while their billing provider ghosted them mid-investigation. Users stuck on their current plans like it's a bad relationship they can't escape. (Auto-resolved: no updates in 24h)

⏰ Mar 07, 2026 Fixed (for now) spotted via status_rss

// The official story

Subscription Plan changes currently unavailable

// Status page says

Mar 7 , 12:10 UTC Investigating - We are currently experiencing issues with subscription plan changes and have contacted our upstream billing provider to help investigate. Subscription Plan changes are temporarily disabled while we investigate.

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

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

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)