BREAKING: Supabase Project Status Change Failures Across Multiple Regions

Supabase experiencing widespread project status change failures. Immediate workarounds and status checks inside.

Incident Summary

Supabase is currently experiencing project status change failures affecting multiple regions. Users report inability to pause, resume, or modify project states through the dashboard and API.

What's Down

Project status management: Cannot pause/resume projects

Dashboard controls: Status change buttons unresponsive

Management API: Project state modification endpoints returning errors

Affected regions: Multiple (specific regions unclear at this time)

Scope: Database projects, authentication status toggles potentially affected

How to Check If You're Affected

1. Attempt to pause/resume a project in your Supabase dashboard 2. Check for error messages like "Failed to update project status" or similar 3. Monitor your application logs for 400/500 errors from api.supabase.co 4. Check [Supabase Status Page](https://status.supabase.com) for official updates 5. Test the Management API directly if you use it programmatically

Immediate Workarounds

For Production Projects:

Keep projects in their current state during this incident

Do not attempt repeated status changes (may cause additional errors)

If you need to pause for cost reasons, contact Supabase support directly

Monitor your project's database metrics to ensure it remains operational

For Development/Testing:

Create new projects with desired initial states if needed

Use CLI for project management: supabase projects list (if available)

Consider using environment variables to switch between projects rather than toggling states

For API Integration:

Implement retry logic with exponential backoff if you have automated status management

Queue status change requests and retry after incident resolution

Check status page before executing status change operations

Alternative Solutions

1. Contact Support: File an urgent ticket with Supabase support for manual status changes 2. Use Supabase CLI: Some project management operations may work via CLI even if dashboard fails 3. Temporary Workarounds: If cost is a concern, document what you'd like to change for manual execution post-incident 4. Infrastructure as Code: Consider storing project configurations to quickly recreate if needed

What You Should NOT Do

Do not repeatedly attempt status changes (may queue errors)

Do not create workarounds that bypass official APIs

Do not assume your data is lost (databases themselves appear operational)

Monitoring Status

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

Twitter: @supabase

Discord Community: Supabase Discord for real-time updates

Check back every 15 minutes for updates

Data Safety

This appears to be a control plane issue, not a data plane issue. Your databases, data, and active projects should remain accessible. Only status management is affected.

Note: Specific region details and ETAs are not currently available. This report will be updated as more information emerges.