BREAKING: Supabase Projects Stuck in Restarting State — Workarounds Available

Supabase experiencing widespread issues with projects stuck in restarting state. Immediate workarounds and status check methods inside.

Incident Summary

Supabase is currently experiencing a critical issue where projects become stuck in a "restarting" state, preventing access to databases and APIs. This affects users attempting to restart projects or access their instances during the restart cycle.

What Is Down

Project restart functionality: Projects initiated for restart hang indefinitely

Database connectivity: Affected projects show unavailable status

API access: Applications relying on stuck projects cannot connect

Management dashboard: Limited functionality for impacted projects

*Note: Not all Supabase projects are affected; this appears region or account-specific*

How to Check If You're Affected

1. Log into your Supabase dashboard at supabase.com 2. Check your project status indicator—look for "Restarting" state that doesn't resolve 3. Attempt a database query via SQL Editor—timeouts indicate impact 4. Monitor your project status page; affected projects show spinning restart indicator beyond 5+ minutes

Immediate Workarounds

Workaround 1: Wait and Retry

Supabase incidents of this type occasionally resolve automatically

Wait 10-15 minutes before attempting further action

Refresh dashboard periodically

Workaround 2: Force Project Reload (Unsure of Effectiveness)

Open browser developer console (F12)

Clear localStorage specific to Supabase session

Log out completely and log back in

*Note: This may or may not resolve the stuck restart state*

Workaround 3: Use Database Backup/Export

If you maintain database backups, restore to alternative infrastructure

Export data via Supabase backup features if accessible

Temporarily migrate to alternative PostgreSQL provider

Workaround 4: Contact Supabase Support (Priority)

Submit urgent support ticket at supabase.com/support

Include project ID and restart initiation timestamp

Request manual intervention to restart project backend

Enterprise customers should escalate via Slack channel

Immediate Alternatives (Temporary Migration)

Railway.app: Quick PostgreSQL deployment (minutes)

Render: Managed PostgreSQL with connection strings

DigitalOcean App Platform: Restore from Supabase export

AWS RDS: For larger applications requiring immediate continuity

Local PostgreSQL: For development-only recovery

Real-Time Status

Check Supabase status page: status.supabase.com

Monitor Twitter: @supabase for official updates

Join Supabase Discord for community reports

Recommendations

1. Immediately: Check if your project is affected using steps above 2. If affected: Contact Supabase support with project ID 3. Parallel action: Begin data export if accessible 4. Communication: Alert your team/users of potential service disruption 5. Future: Implement multi-database redundancy for critical applications

Known Limitations

I'm uncertain about:

Exact percentage of users affected

Root cause determination

ETA for full resolution

Whether manual restart bypass exists

These details should be confirmed via official Supabase channels.

Last Updated: Refer to status.supabase.com for latest incident information.