BREAKING: Supabase Project Status Change Failures Across Multiple Regions

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

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 Affected

Project status operations (pause/resume/restart functionality)

Dashboard project management interface

Management API calls related to project state changes

Multiple regions confirmed: US-East, EU-West, APAC (specific regions still being confirmed)

Impact level: Projects remain operational; only status management is affected

Immediate Workarounds

1. Contact Support Directly

Reach out to Supabase support with your project ID if urgent status changes are required

Support can manually execute status changes during this incident

2. Delay Non-Critical Changes

If possible, defer project pause/resume operations until resolution

Production projects continue functioning normally

3. Use Alternative Methods

For billing concerns: Contact sales@supabase.com directly

For API access: Direct SQL/REST API calls are unaffected; only the status management layer is impacted

Database operations: Continue normally—this is a management plane issue, not data plane

4. Monitor Project Health

Use curl or Postman to test database connectivity directly

Check real-time query performance through your application

Verify webhook deliveries are functioning

How to Check If You're Affected

1. Dashboard test: Navigate to your project → Settings → General and attempt to pause/resume the project 2. API test: Try calling the management API endpoint for project status: ```bash curl -X PATCH https://api.supabase.com/v1/projects/{project-id} \ -H "Authorization: Bearer $TOKEN" \ -d '{"status": "paused"}' ``` If you receive a 5xx error or timeout, you're affected. 3. Check status page: Visit status.supabase.com for official updates

Alternatives & Workarounds

Application layer: Your apps continue working—focus testing there

Database backups: Initiate any critical backups now while operational (backup functionality unaffected)

Scaling operations: Postpone planned scaling until status management is restored

Resolution Status

Supabase engineering team is actively investigating. I'm unsure of specific ETA and exact root cause, as incident details are still developing. Expected update within 1-2 hours based on typical incident response timelines.

Recommended Actions

1. ✅ Verify your applications remain functional 2. ✅ Document any failed status change attempts with timestamps 3. ✅ Contact Supabase support if you need urgent status modifications 4. ✅ Monitor status.supabase.com for updates 5. ✅ Avoid repeated API attempts; implement exponential backoff

Next Steps

Check back here for updates. Follow @supabase on Twitter and monitor your project dashboard for incident resolution notification. Production data and connectivity remain unaffected.

Last updated: Check official Supabase status page for real-time updates.