BREAKING: Supabase Project Status Change Failures Across Multiple Regions

Supabase experiencing widespread project status change failures. Check affected status and immediate workarounds inside.

Incident Summary

Supabase is currently experiencing project status change failures affecting multiple regions. This impacts users attempting to pause, resume, or modify project states through the dashboard and API.

What Is Down

Project status modification operations (pause/resume/delete operations via dashboard)

Project configuration changes in affected regions

Real-time status synchronization across the platform

Exact regions affected: We recommend checking Supabase status page for current region list

What IS working:

Database read/write operations for existing active projects

Authentication services

Real-time subscriptions (for active projects)

API endpoints for data operations

How to Check If You're Affected

1. Try the dashboard: Navigate to your project settings → attempt to pause/resume 2. Check status page: Visit https://status.supabase.com for real-time updates 3. Monitor logs: Check your project logs for ProjectStatusChange errors 4. API test: If using management API, test project status endpoints

Immediate Workarounds

For Pause/Resume Operations

Defer non-urgent changes until the incident resolves (typically 1-4 hours based on Supabase history)

Contact Supabase support directly via dashboard if you need emergency status changes

If you need to reduce costs immediately, consider pausing reads at the application level instead

For Development Teams

Continue using your database normally—this incident doesn't affect data operations

If you need to test project state changes, wait for the incident to clear or use a test project in an unaffected region (if available)

Document any critical changes needed for post-incident execution

For Production Applications

No action needed if your app only reads/writes data

Applications relying on project pause/resume logic should implement fallback mechanisms or queue status changes for retry

Monitor Supabase status page and set up webhook notifications

Alternatives & Workarounds

1. Use Supabase CLI locally: supabase link --project-ref XXX for local testing instead of dashboard modifications 2. Contact support directly: Email support@supabase.com with urgent status change needs 3. Implement exponential backoff: If using management API, add retry logic with exponential backoff 4. Check secondary regions: If your project is multi-region capable, verify status across all regions

Next Steps

Monitor: Watch status.supabase.com for updates

Subscribe to updates: Enable notifications on the status page

Document impact: Log any business impact for post-incident review

Prepare rollback: Have your last known-good configuration documented

Status Page

For live updates, blockers, and ETAs, visit: https://status.supabase.com

Last Updated: Check status page for most current information

*Note: This report covers known details. Supabase may provide additional context on their status page.*