BREAKING: Supabase Project Status Change Failures Across Multiple Regions

Supabase experiencing project status change failures in multiple regions. Immediate workarounds and mitigation steps inside.

Current Incident Status

Supabase is currently experiencing project status change failures impacting multiple geographic regions. This affects the ability to pause, resume, or modify project states through the dashboard and API.

What's Down

Project status change operations (pause/resume/restart) via Supabase Dashboard

Related project state modification endpoints

Estimated impact: Projects across multiple regions unable to toggle operational states

Database connectivity and query operations appear unaffected based on current monitoring

How to Check If You're Affected

1. Try accessing your project dashboard at app.supabase.com 2. Attempt any project state change: Look for pause/resume buttons in Project Settings 3. Watch for error messages like "Failed to update project status" or timeout errors 4. Check Supabase Status Page: https://status.supabase.com for official updates 5. Verify your region: Note which region your project operates in—not all regions may be equally impacted

Immediate Workarounds

If You Need to Pause Your Project:

Workaround: Stop application traffic at your application layer rather than pausing the Supabase project

Implement rate limiting or disable API endpoints temporarily

Use environment variables to disable feature flags connecting to your database

If You Need to Access Your Data:

Direct database connection: Use your database connection string directly (if you have it configured)

pgAdmin or database clients: Connect via psql or other PostgreSQL clients directly

Continue normal read/write operations—only *status changes* are affected

If You're Blocked on Project Operations:

Contact Supabase Support: Submit an urgent ticket at supabase.com/support if business-critical

Temporary solution: Document the state change you need and apply it once the service recovers

Monitor status page for updates on resolution timeline

Technical Details (Uncertain Aspects)

I'm unable to confirm with certainty:

Exact regions affected (all or subset)

Root cause of the status change failures

Whether this impacts the REST/GraphQL APIs for status queries or only dashboard operations

Estimated time to resolution

For authoritative details, consult the official Supabase status page and your support ticket.

Recommended Next Steps

1. Don't retry aggressively—exponential backoff recommended 2. Communicate with your team—ensure everyone knows database operations are still functional 3. Verify data access works normally to confirm scope is limited to status changes 4. Stay updated—monitor Supabase status page and their Twitter/Discord for resolution announcements 5. Plan alternatives—if you have time-sensitive scaling needs, consider manual workarounds

Alternative Services (If Extended Outage)

If this extends significantly:

AWS RDS or AWS Aurora for database needs

Hasura or PostgREST for API layer alternatives

Firebase/Firestore for complete backend replacement (requires migration)

Status: Actively monitoring. This report will be updated as more information becomes available.