SUPABASE

🟠 Supabase's 'Restore to New Project' beta decided to YOLO into the void. Turns out 'beta' is corporate speak for 'we haven't tested this part yet.' Feature going dark while engineers frantically Google 'how restore actually works.'. (Auto-resolved: no updates in 24h)

⏰ Jul 01, 2026 Fixed (for now) spotted via status_rss

// The official story

Issues with Restore to New Project

// Status page says

Jul 1 , 15:16 UTC Identified - We have identified an issue with the Restore to New Project beta feature and we are implementing a fix. The Restore to New Project beta feature will be temporarily unavailable while we fix this issue. We will update this page when the fix has been rolled out.

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

https://status.supabase.com/incidents/0fmgxxth7wd2

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)