BREAKING: Supabase Project Status Change Failures Across Multiple Regions

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

Incident Summary

Subabase 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 pause/resume functionality - Dashboard and Management API

Project status modifications - All region deployments

Affected regions - Multiple (exact regions unconfirmed; check status page)

Services still operational - Database queries, authentication, real-time subscriptions appear unaffected

Immediate Workarounds

1. Bypass Dashboard (Temporary)

If you need to pause/resume projects:

Use direct PostgreSQL connections to manage workloads

Scale compute resources via native PostgreSQL configuration if available

Contact Supabase support for manual project state changes

2. API Alternative

If dashboard is unavailable, the Management API may still work: ```bash curl -X PATCH https://api.supabase.com/v1/projects/{project-id} \ -H "Authorization: Bearer $SUPABASE_TOKEN" \ -H "Content-Type: application/json" \ -d '{"status": "paused"}' ``` Note: This may also fail if backend services are affected.

3. Application-Level Mitigation

Implement connection pooling to reduce database load

Cache frequently accessed data where possible

Reduce real-time subscription frequency if needed

Monitor database connections in your application logs

How to Check If You're Affected

1. Dashboard Test: Attempt to pause/resume any non-production project 2. Status Page: Visit [status.supabase.com](https://status.supabase.com) for official incident updates 3. API Test: Try the Management API call above; watch for 5xx responses 4. Check your region: Confirm your project's region in Supabase dashboard settings 5. Monitor logs: Check application error logs for authentication/connection failures

Alternatives & Next Steps

Short-term

Continue using database and authentication services normally

Contact support@supabase.com for urgent project modifications

Monitor status.supabase.com for updates (typically updated every 30 minutes)

Escalation

Enterprise customers: Use dedicated support channel

Open source deployments: Self-hosted Supabase instances unaffected

Consider multi-region redundancy: For critical applications

What We Don't Know (Unconfirmed)

Exact affected region list

Root cause details

ETA for full resolution

Whether all project types are equally affected

If the API backend is fully operational

Recommendation: Monitor official Supabase status page and avoid attempting repeated status changes, which may increase queue strain.

Resources

[Supabase Status Page](https://status.supabase.com)

[Management API Docs](https://supabase.com/docs/reference/api/management-api)

Support: support@supabase.com

Last Updated: Check status page for latest incident timeline.