BREAKING: Supabase Project Status Change Failures Across Multiple Regions

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

Incident Overview

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

What's Affected

Project dashboard controls - pause/resume functionality unavailable

Project status API endpoints - status change requests returning errors

Multiple regions - US-East, EU-West, and APAC regions reporting issues

Dashboard UI - status toggle buttons may be unresponsive or throw errors

Billing-related pauses - cannot pause projects for cost management

NOT affected: Database queries, authentication, real-time subscriptions, or data access (assuming project was already in correct state before incident)

How to Check If You're Affected

1. Navigate to your Supabase dashboard 2. Attempt to click pause/resume on any project 3. Check if you receive timeout or "status update failed" errors 4. Test via API: POST /v1/projects/{ref}/pause - watch for 5xx responses 5. Check [Supabase status page](https://status.supabase.com) for official confirmation

Immediate Workarounds

For Active Projects (No Immediate Action Needed)

If your projects are running normally, no action required. This outage only prevents status *changes*, not ongoing operations.

If You Need to Pause a Project

1. Contact Supabase Support directly - request manual pause via support ticket (priority given for production) 2. Reduce resource usage - limit active connections and queries if cost-cutting is urgent 3. Wait for resolution - check status page for ETA before spending engineering effort

If You Need to Resume a Project

Same as above: submit support ticket or wait for automatic recovery

Ensure team is aware of downtime before communicating to customers

Database Access Workarounds

If your project is paused and you need data access:

Connect directly via pgAdmin or psql using project credentials (if network permits)

Use Supabase direct connection string from project settings (may work independently of status)

Consider temporary read-replica or backup access

Mitigation Steps You Can Take

1. Document your project status - screenshot current state for records 2. Alert your team - ensure developers know status changes are unavailable 3. Avoid dependency on dashboard - use alternative tools for monitoring 4. Monitor status page - check [https://status.supabase.com](https://status.supabase.com) every 15 mins 5. Prepare communications - draft customer updates if applicable

Alternatives During Outage

Direct PostgreSQL tools - pgAdmin, DBeaver for database management

CLI operations - Supabase CLI (supabase commands) may bypass dashboard

Manual backups - export critical data via pg_dump if concerned

Temporary PostgreSQL instances - spin up RDS/Cloud SQL as fallback (not recommended for extended use)

Next Steps

Do NOT refresh obsessively - adds load to Supabase infrastructure

File support ticket - if time-sensitive (include timestamp and region)

Monitor Slack/Twitter - Supabase team posts updates regularly

Estimated resolution: Check status page; typically 30-60 mins for regional issues

Status: Ongoing as of report time. This is a monitoring issue - core data remains accessible.