BREAKING: Supabase Project Status Change Failures Across Multiple Regions

Supabase experiencing widespread project status change failures. Critical workarounds and mitigation strategies inside.

Incident Summary

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

What's Affected

Project pause/resume functionality - Dashboard and API calls failing

Project deletion operations - Status transitions blocked

Region-specific impacts - Multiple geographic regions affected (US East, EU, APAC)

Control plane operations - Administrative project management compromised

Estimated impact scope - Unclear at this time; we're monitoring for complete assessment

How to Check If You're Affected

1. Try pausing/resuming a project in your Supabase dashboard 2. Check API responses - Look for 5xx errors or timeout responses when calling project status endpoints 3. Monitor your databases - Existing database operations may continue unaffected; only status management is impacted 4. Check Supabase status page - https://status.supabase.com for real-time updates

Immediate Workarounds

For Development/Testing Projects

Pause via billing hold (if available in your region) as temporary alternative

Use read-only mode - Configure projects to read-only instead of pausing

Contact support - Request manual project state changes if critical

For Production Databases

Continue operations normally - Data and existing connections unaffected

Avoid status changes - Don't attempt pause/resume operations; these will fail

Implement application-level throttling if needed instead of project-level pausing

Use direct PostgreSQL connections - Bypass dashboard management if possible

Application-Level Alternatives

Implement rate limiting in your application code rather than at project level

Use connection pooling (PgBouncer) configuration to manage load

Deploy read replicas manually if load distribution needed

Implement feature flags to disable functionality instead of pausing infrastructure

API Workaround Details

If you've automated project management via Supabase Management API:

Expected endpoint: PATCH /v1/projects/{ref}/pause

Current status: Returning errors (exact error codes TBD)

Temporary solution: Queue these requests and retry with exponential backoff once service recovers

Note: We're unsure if partial regions are unaffected - test your specific region independently

What You Should NOT Do

❌ Repeatedly retry status change requests (adds load) ❌ Assume database data is lost (it's not) ❌ Migrate to competitors without confirming incident scope ❌ Attempt workarounds involving direct Postgres manipulation unless experienced

Expected Resolution Timeline

Unfortunately, we cannot provide a specific ETA. Supabase engineering is investigating root cause across all affected regions.

Stay Updated

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

Twitter: @supabase

Discord: Supabase community channels

Email: Check your registered email for official communications

Last Updated: Monitor this page for updates. We'll revise with more specific mitigation details as we confirm root causes.

*This report contains information we can verify. For real-time status, always defer to official Supabase channels.*