← Back to the carnage
SUPABASE
🟡 Supabase's instance operations went full Sleeping Beauty—new projects won't spin up, paused ones refuse to budge. The good news: your existing projects are still breathing. Bad news: they're watching the chaos unfold. (Auto-resolved: no updates in 24h)
// The official story
new project creation and project unpauses unavailable
// Status page says
Feb 4 , 17:55 UTC Investigating - We are investigating issues affecting instance operations globally. This may impact new project creation and project unpauses. Existing projects remain unaffected.
🔗 Official status page (for the PR-approved version)
https://status.supabase.com/incidents/7pq6klfzhd52Supabase'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)