← Back to the carnage
SUPABASE
🔴 Someone shipped a landmine in [email protected] and Edge Functions walked right into it. The fix? Pretend v2.95.0 never existed and rollback to v2.94.1 like it's a bad relationship. If you manually pinned the cursed version, congrats, you're the QA team now. (Auto-resolved: no updates in 24h)
// The official story
Edge Function issues when using [email protected]
// Status page says
Feb 5 , 20:11 UTC Identified - We are removing v2.95.0 release, so the @2 tag will resolve to v2.94.1. This should resolve majority of issues. If you have previously switched to using v2.95.0 directly, please switch to v2.94.1 Feb 5 , 19:08 UTC Update - We recommend importing via `npm:` or `jsr:` specifiers instead of CDN imports: `import { createC
🔗 Official status page (for the PR-approved version)
https://status.supabase.com/incidents/v35nwyvkg84lSupabase'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)