BREAKING: Supabase Project Status Change Failures Across Regions

Supabase experiencing widespread project status update failures. Immediate workarounds and mitigation steps inside.

Supabase Project Status Change Failures - Incident Report

What's Down

Supabase is currently experiencing project status change failures across multiple regions. This impacts:

Project pause/resume operations

Project deletion workflows

Status transition requests in the dashboard

Potentially related API endpoints handling project state changes

Note: Database connectivity and query operations appear unaffected at this time. This is isolated to project management operations.

How to Check If You're Affected

1. Dashboard Access: Try to pause, resume, or delete a project in the Supabase dashboard 2. Error Message: Watch for timeout errors or "Project status change failed" messages 3. Regions Impact: Affects US, EU, and APAC regions (confirmation pending on specific regional breakdown) 4. API Calls: If using the management API, status change endpoints will return errors

Immediate Workarounds

For Project Pausing/Resuming:

Delay non-urgent operations: If pause/resume isn't critical, wait for resolution

Contact Supabase Support: For urgent project status changes, reach out directly via the dashboard support chat

Alternative: If you need to reduce costs, disable specific services within your project rather than pausing

For Project Deletion:

Hold deletions: Do not attempt to delete projects during this incident

Export data first: Ensure all critical data is backed up before attempting deletion once service restores

Support escalation: Contact support@supabase.io for urgent deletion requests

For Production Applications:

Database operations continue: Your applications should continue functioning normally

No query impact: Read/write operations are unaffected; only management operations are impacted

Monitor your apps: Verify that application functionality remains stable

Alternative Solutions

1. Use Supabase CLI: For programmatic project management, test if the CLI commands work during this incident: ```bash supabase projects list ``` (Success depends on whether CLI uses different endpoints)

2. Management API: Try direct API calls to the management API—status may differ from dashboard

3. PostgreSQL Direct Access: If you need to perform operations, connect directly via psql or your database client

4. Temporary Provider: If absolutely critical, consider temporary migration to Heroku Postgres or AWS RDS (not recommended for active applications)

Status & Updates

Last Updated: [Current time]

Incident Duration: Unknown—monitoring shows this is ongoing

Affected Customers: All regions and projects

Data Loss Risk: None identified

Next Steps

1. Check Supabase's official status page: https://status.supabase.com 2. Follow @supabase on Twitter for updates 3. Monitor your project dashboard for "Service Restored" notices 4. Contact support if you have time-sensitive requirements

We will update this report as more information becomes available.