← Back to the carnage
SUPABASE
🟠 Supabase's European infrastructure briefly forgot basic project management—creating, restoring, and pausing databases all threw errors like they were having an existential crisis. The kill switch got hit, error rates dropped, but some projects are still receiving therapy. Monitoring continues. (Auto-resolved: no updates in 24h)
// The official story
Project lifecycle operation errors in the EU region
// Status page says
Status: Monitoring We identified increased error rates in project lifecycle operations (create, restore, pauses, etc.) in the EU region since 21 Oct 23:00 UTC. A mitigation has been put in place and error rates have reduced to normal levels. We are monitoring the situation and are working on fixing affected projects. Affected components eu-west-1 (Partial outage)
🔗 Official status page (for the PR-approved version)
https://status.supabase.com//incidents/01M5GVWF6HPD9H7PPKXA0JCBWNSupabase's Greatest Hits
🟢 SUPABASE
5d ago
🟡 Supabase's Management API is choking harder than a bootcamp student's first deployment. Project creation is gambling, logins are timing out, and the dashboard is having commitment issues. Multiple regions down means this isn't a hiccup, it's a full respiratory event. (Auto-resolved: no updates in 24h)
🟢 SUPABASE
5d ago
🟡 Supabase's project creation, pausing, and restoration features are currently playing dead across four regions. Engineers are 'investigating,' which is tech-speak for 'we're refreshing our beverages and hoping it fixes itself.' Your infrastructure changes are now in a quantum state—both deployed and not deployed simultaneously. (Auto-resolved: no updates in 24h)
🟢 SUPABASE
Oct 17, 2026
🟠 Someone's upstream provider decided to ghost them, and now Supabase can't spin up projects in ap-northeast-1. Traffic is being redirected to regions that remember how to function. Engineers are refreshing their monitoring dashboards and stress-eating. (Auto-resolved: no updates in 24h)
🟢 SUPABASE
Oct 12, 2026
🟡 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)