BREAKING: Supabase Project Status Change Failures Across Multiple Regions

Supabase experiencing project status change failures in multiple regions. Immediate workarounds and status check methods inside.

Incident Summary

Supabase is currently experiencing project status change failures affecting multiple geographic regions. This impacts users attempting to pause, resume, or modify project states through the dashboard and API.

What's Affected

Primary Impact: Project status modification operations (pause/resume/restart)

Scope: Multiple regions (exact regions not confirmed in this report)

Services: Dashboard UI and potentially related management APIs

Status: Monitoring/ongoing investigation

How to Check If You're Affected

1. Dashboard Test: Log into your Supabase dashboard and attempt to pause/resume any project 2. Error Response: You'll likely see timeout errors or "status update failed" messages 3. Check Status Page: Visit [status.supabase.com](https://status.supabase.com) for official updates 4. API Test: If using management API, POST requests to project status endpoints may fail or timeout

Immediate Workarounds

If You Need to Pause/Resume Projects

Defer Non-Critical Changes: If pausing for cost reasons, consider waiting for resolution unless urgent

Contact Support: Reach out to Supabase support for manual intervention if time-sensitive

Temporary Alternative: If you need to reduce costs immediately, consider scaling down database resources instead (if this functionality is available)

For Production Continuity

Database Operations: Regular database queries and data operations should continue unaffected

Authentication: Auth services remain operational

Realtime Features: Realtime subscriptions should function normally

Only Blocked: Project-level administration changes

Workaround for Automated Workflows

If you have scripts that modify project status, implement retry logic with exponential backoff

Set up alerting to notify when the incident is resolved

Queue status change requests for later execution

What Remains Operational

✅ Database connections and queries

✅ Authentication (Supabase Auth)

✅ Realtime subscriptions

✅ Storage operations

✅ Vector/pgvector functionality

✅ API endpoints (your application data layer)

Next Steps

1. Monitor Status: Check [status.supabase.com](https://status.supabase.com) regularly 2. Review Dashboard: Verify which of your projects are affected 3. Assess Impact: Determine if this blocks any critical workflows 4. Contact Support: If this is time-critical, open a support ticket 5. Plan Contingencies: Consider manual intervention strategies if needed

Important Note

This report is based on limited incident information. Specific details about:

Exact affected regions

Root cause

ETA for resolution

Percentage of users impacted

...are not confirmed in this report. Refer to [status.supabase.com](https://status.supabase.com) and your Supabase dashboard notifications for authoritative information.

Support Resources

Status Page: https://status.supabase.com

Discord Community: https://discord.supabase.com

GitHub Issues: https://github.com/supabase/supabase/issues

Support Portal: https://supabase.com/support

Last Updated: Monitor this incident for ongoing updates.