BREAKING: Supabase Project Upgrade Delays Identified – Workarounds Inside

Supabase experiencing project upgrade delays affecting deployments. Here are immediate workarounds and status checks.

Supabase Project Upgrade Delays - Incident Report

What's Down

Supabase is currently experiencing Project Upgrade Delays that may affect:

Project provisioning and upgrades

Potential delays in plan tier changes

Dashboard responsiveness during upgrade operations

New project creation timelines

*Note: Core database functionality (queries, auth, storage) appears operational for existing projects.*

How to Check If You're Affected

1. Visit the Supabase Dashboard at app.supabase.com 2. Look for these indicators: - Spinning loader on project upgrade/creation screens - "Upgrading..." status stuck for >30 minutes - Unable to access project settings or billing tabs - Dashboard timeout errors 3. Check Status Page: https://status.supabase.com 4. Monitor: Supabase Twitter/X (@supabase) and Discord #announcements

Immediate Workarounds

For Existing Projects:

Continue using your current project tier without upgrading

Database, API, and Auth services should function normally

Avoid triggering upgrades until incident resolves

Use direct database connections if dashboard access fails

For New Project Creation:

If creation is stuck, wait 30-60 minutes before retrying

Alternatively, contact Supabase Support for manual provisioning

Consider temporarily using development/free tier projects

For Upgrade/Downgrade Operations:

Defer plan changes until status normalizes

If urgent, contact support@supabase.com with project details

Request manual tier adjustment if time-sensitive

Database Access Workaround:

Use direct PostgreSQL connection strings (from project settings)

Connect via psql CLI: psql "postgresql://user:password@host/database"

Use database clients (pgAdmin, DBeaver) bypassing the dashboard

API endpoints should remain accessible

Alternative Services (Temporary)

If you need immediate alternatives:

Firebase (auth + database)

AWS RDS + Cognito (more complex setup)

PlanetScale (if MySQL-compatible)

Neon (PostgreSQL alternative)

Railway/Render (managed databases)

*Note: Migration takes time; use only for critical new projects.*

What We Don't Know

Exact scope of affected regions/projects

ETA for full resolution

Root cause (infrastructure/code deployment)

Whether upgrades will process retroactively

Impact on Supabase hosting vs. self-hosted instances

Recommended Actions

1. Notify your team if deployments are blocked 2. Do not retry upgrades excessively (causes queue buildup) 3. Monitor status.supabase.com for updates 4. Document the delay for billing/timeline adjustments 5. Contact support if mission-critical

Timeline

Identified: Project Upgrade Delays confirmed

Status: Ongoing investigation

Updates: Check Supabase status page every 15-30 minutes

---

Last Updated: Check status.supabase.com for real-time updates

Need Help? Email support@supabase.com with your project ID and affected operation.