BREAKING: Supabase Project Status Change Failures Across Regions

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

Supabase Project Status Change Failures - Incident Report

What's Down

Supabase is currently experiencing failures in project status change operations across multiple regions. This affects:

Project pause/resume functionality

Project deletion workflows

Project status management in the dashboard

Potentially related administrative operations

Core database services (PostgreSQL, Realtime, Auth, Storage) appear to be operational, but the control plane managing project lifecycle operations is impaired.

How to Check If You're Affected

1. Attempt project status change: Try pausing or resuming a non-production project in your Supabase dashboard 2. Check error messages: Look for "Project status change failed" or generic 500 errors 3. Test region-specific: The issue spans multiple regions—try different project regions 4. Monitor dashboard: Visit [status.supabase.com](https://status.supabase.com) for official updates 5. Check API logs: Review recent API calls for failed PATCH/POST requests to /project/{id}/status

Immediate Workarounds

If You Need to Pause Projects

Delay non-urgent pauses: If pausing is not time-critical, wait for resolution

Use API directly: Some users report success with direct REST API calls vs. dashboard—attempt curl requests to Supabase Management API

Contact support: For production projects requiring immediate pausing, open urgent support tickets

If You Need to Delete Projects

Document project details: Export any necessary metadata, backups, or configuration

Defer deletion: If not blocking, postpone until incident is resolved

Use support escalation: Contact Supabase support for manual project removal if critical

Alternatives & Contingencies

For Development/Testing:

Spin up temporary projects in unaffected regions if available

Use local development databases (PostgreSQL locally) to bypass cloud operations

Store project configuration externally for rapid redeployment

For Production:

This incident shouldn't affect running applications—only management operations

Continue serving traffic normally; your database connections remain stable

Prepare rollback plans if you cannot modify project status as needed

What Remains Operational

✅ Database read/write operations

✅ Authentication (Supabase Auth)

✅ Realtime subscriptions

✅ Storage operations

✅ Vector operations

⚠️ ❌ Project status management (pausing, resuming, deletion)

Next Steps

1. Monitor [status.supabase.com](https://status.supabase.com) for updates 2. Verify your applications continue functioning (they should) 3. Defer non-urgent project status changes 4. Document any failed operations with timestamps for support claims 5. Review incident post-mortem once published

Support

For urgent issues:

Open support ticket via Supabase dashboard

Mention: "Project status change failures" and affected region

Include timestamps of failed attempts

*Last updated: Monitor status page for latest information.*