BREAKING: Supabase Project Status Change Failures Across Multiple Regions

Supabase experiencing widespread project status change failures. Immediate workarounds and status checks inside.

Incident Overview

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's Affected

Primary Impact: Project status modification operations (pause/resume/restart)

Scope: Multiple geographic regions

Services: Supabase Dashboard, Management API

Severity: Monitoring - ongoing investigation

Note: Database connections and existing project functionality appear unaffected at this time. Only state-change operations are impacted.

How to Check If You're Affected

1. Dashboard Method: Try pausing or resuming a project in your Supabase dashboard 2. API Method: Attempt a project status change via Management API 3. Error Signs: Look for timeouts, 500 errors, or "Failed to update project status" messages 4. Check Status Page: Visit [status.supabase.com](https://status.supabase.com) for real-time incident updates

Immediate Workarounds

If You Need to Pause Projects

Workaround 1: Contact Supabase support directly for manual project pause/resume

Workaround 2: If not urgent, wait for service restoration before attempting again

Note: If your goal is cost-saving, existing projects in paused state remain unaffected

If You're Blocked by Status Changes

Alternative 1: Use the Supabase CLI (if available in your region) for project operations

Alternative 2: Delay non-critical project modifications until service is restored

Alternative 3: For urgent needs, open a support ticket with Supabase directly

For Development/Testing

Continue using existing active projects normally

Do not attempt status changes during the incident

Database read/write operations should proceed uninterrupted

Workaround Details I'm Uncertain About

CLI status: I cannot confirm with certainty whether the Supabase CLI experiences the same failures—verify this before relying on it

Specific error codes: The exact error responses may vary by region

API endpoints affected: While Management API is impacted, I'm not certain which specific endpoints are most affected

Recommended Actions

Immediate: 1. Check your Supabase status page for updates 2. If affected, avoid retry loops (they add unnecessary load) 3. Monitor your applications for any cascading issues

Short-term: 1. Subscribe to status.supabase.com for incident updates 2. Document any workarounds you implement 3. Contact support if you have time-critical needs

Post-Incident: 1. Review what project state changes are truly necessary 2. Consider automation tools for routine maintenance 3. Keep contact info for Supabase support handy

What You CAN Still Do

Read/write database operations

Deploy function changes

Access existing project data

Create new projects (verify this works first)

Use authentication services

Status Updates

This incident is ongoing. Check back for updates as Supabase works on a fix. Follow [@supabase](https://twitter.com/supabase) on Twitter for announcements.

Last Updated: Monitor status.supabase.com for latest information.