BREAKING: Supabase Project Lifecycle Actions Down — Workarounds Available

Supabase experiencing elevated error rates on Project Lifecycle Actions across all regions. Immediate workarounds and status checks inside.

BREAKING: Supabase Project Lifecycle Actions Outage

What's Down

Supabase is currently experiencing increased error rates on Project Lifecycle Actions across all regions. This affects:

Project creation/deletion operations

Database provisioning and initialization

Project scaling and configuration changes

Environment setup tasks

Status: Identified and being investigated. Database queries and API endpoints appear largely unaffected; the issue is isolated to management/lifecycle operations.

How to Check If You're Affected

1. Attempting project operations? If your create/delete/scale actions are returning 500 errors or timeouts, you're affected. 2. Check Supabase Status Page: Visit [status.supabase.com](https://status.supabase.com) for real-time updates 3. Monitor your dashboard: Look for timeout messages in project settings or deployment panels

Immediate Workarounds

If Creating a New Project

Retry with exponential backoff (wait 2-5 minutes, then retry)

Use different region if available—error rates vary by region; try switching your selected region

Defer non-critical projects until status returns to normal

If Scaling/Modifying Existing Projects

Hold off on configuration changes until the incident resolves

Use CLI as alternative (if available): supabase CLI tools may bypass some UI-layer issues

Contact Supabase support if changes are urgent—they can escalate to engineering

For Database Operations

Your current projects should remain stable—this outage affects provisioning, not running databases

Direct database queries should work normally—connect via connection string as usual

API endpoints (postgREST/Auth/etc.) are not reported as affected

Alternative Actions

1. Use Supabase CLI locally for development—you can still build locally and deploy when lifecycle actions resume 2. Prepare infrastructure-as-code (if using it): Have your project definitions ready to deploy once services recover 3. Contact support: Open a ticket at [Supabase Support](https://supabase.com/support) if you have time-sensitive project needs

What We Don't Know (Need Confirmation)

Exact ETA for resolution: Not publicly announced yet

Root cause: Under investigation; specific technical details unavailable

If Auth/Storage management is affected: Likely separate from lifecycle actions but not confirmed

Regional variation details: Some regions may have better availability—experimentation recommended

Recommended Next Steps

1. Monitor status.supabase.com for updates every 15 minutes 2. Subscribe to incident notifications if not already 3. Avoid bulk project operations until resolved 4. If business-critical: Reach out to Supabase account team

Key Takeaway

Your existing Supabase projects and databases are likely fine. This incident primarily impacts new provisioning and lifecycle management. Defer administrative actions 1-2 hours and retry.

---

*Last updated: Issue identified and workarounds published. Check status.supabase.com for resolution timeline.*