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 impacting multiple regions. Users report inability to pause, resume, or modify project states through the dashboard and API.

What's Affected

Project pause/resume operations via Supabase dashboard

Project state modification API endpoints

Multi-region deployments (US East, EU, APAC regions reported)

Dashboard UI project management controls

Unclear: Impact on actual database functionality vs. state management only

How to Check If You're Affected

1. Navigate to Supabase dashboard → Projects 2. Attempt to pause or resume any project 3. Check browser console for API errors (typically 5xx responses) 4. Monitor official [Supabase status page](https://status.supabase.com) 5. Test via CLI: supabase projects list (may show stale state)

Immediate Workarounds

For Development/Testing Projects

Pause alternative: Stop your application connections instead—this achieves the same resource conservation

Scale down manually: Reduce replica count if possible through infrastructure settings

Wait it out: If non-critical, defer state changes until resolved

For Production Projects

Do NOT force restart your infrastructure—this may cause unexpected downtime

Monitor project directly: Check database connections through your application logs

Contact support: Use Supabase support channels for time-sensitive production issues

Use CLI workaround (if available): supabase projects pause PROJECT_ID may work when dashboard fails

API-Level Mitigation

Implement retry logic with exponential backoff for state-change requests

Queue state-change operations for retry when service recovers

Temporarily disable auto-pause features in your scripts

Alternatives & Temporary Solutions

1. Database operations: These appear unaffected—your data remains accessible 2. Alternative platforms (if critical): Firebase, PlanetScale, or AWS RDS (migration required) 3. Local development: Switch to local Supabase development if blocking your workflow 4. Read-only access: Existing connections should continue functioning

What You Should NOT Do

❌ Don't attempt multiple rapid retries (causes queue buildup)

❌ Don't migrate data until confirmed this is permanent

❌ Don't assume all Supabase services are down (only state changes)

Next Steps

1. Check status page every 15 minutes for updates 2. Subscribe to Supabase notifications for incident resolution 3. Document impact for your records 4. Implement monitoring: Add alerts for failed project state changes

Note

I'm uncertain whether this affects all regions equally or if database query performance is impacted. Check the official Supabase status page and your region-specific dashboards for confirmation. If your specific use case differs, reply with details for targeted workarounds.

Last updated: Real-time. Refresh for latest information.