BREAKING: Supabase Projects Stuck in Restarting State — Immediate Workarounds [01M5DN6V02FJHZTE9390XJM9YY]

Supabase is experiencing a critical incident affecting project restarts. Immediate workarounds for indie hackers impacted by this outage.

BREAKING: Supabase Projects Stuck in Restarting State

Status: Identified | Severity: High | Updated: Now

---

What's Down & Who's Affected

Supabase is currently experiencing an issue where projects become stuck in a "restarting" state and fail to become available. This primarily affects:

Projects that recently triggered a restart (manual or automatic)

Users attempting to restart projects for updates or configuration changes

Teams with multiple projects—some may be affected while others remain operational

Scope: This is NOT a universal outage. If your project is running normally, you're likely unaffected. However, attempting to restart may trigger the issue.

---

Immediate Workarounds (Do This NOW)

1. Don't Restart Unless Critical

Avoid manual project restarts until Supabase confirms resolution

If your project is running, leave it alone

Do not chain multiple restart attempts

2. For Stuck Projects

Navigate to your project settings → "Infrastructure"

If stuck in restart, wait 15 minutes before attempting another restart

Check the Supabase status page—they may force-recover stuck projects automatically

Do NOT rapidly click restart; this can compound the issue

3. Database Access Fallback

If your project is stuck but you need data access:

- Use direct PostgreSQL connection string (Settings → Database → Connection String) - Connect via psql CLI or pgAdmin from your local machine - This bypasses Supabase UI and often works even during restarts - Export critical data immediately as a precaution

4. API Layer Failover

If using Supabase REST API, switch to direct PostgreSQL queries temporarily

For PostgREST, try accessing your database via raw SQL connections

Cache frequently-needed data locally if possible

---

How to Check If Your Project Is Affected

1. Log into Supabase Dashboard 2. View project status in the top-right corner (green = healthy, orange/red = issue) 3. Check project state: Settings → Infrastructure → look for "Restarting" status that persists beyond 5 minutes 4. Test connectivity: Run a simple query via the SQL Editor—if timeout, project is stuck 5. Verify with: SELECT NOW(); in the SQL Editor

---

Alternative Tools to Consider (Temporary Shift)

If your project remains stuck:

Neon — PostgreSQL-as-a-service, faster onboarding, similar feature set

Railway — Managed databases with quick provisioning

PlanetScale — If using MySQL instead of PostgreSQL

Render — Simple database hosting alternative

Self-hosted PostgreSQL on AWS RDS/DigitalOcean — More control, manual management required

*Note:* Migrating is last resort. Most stuck projects should recover within 30-60 minutes.

---

How to Monitor Recovery

Official Channels:

Supabase Status Page: status.supabase.com (real-time updates)

Twitter: @supabase (incident announcements)

Discord: Supabase community server (fastest updates)

What to Watch For:

"Projects stuck in restarting state" removed from status page

All user projects returning to healthy state

Dashboard confirming restart operations are working

Estimated Recovery: Supabase typically resolves infrastructure issues within 1-2 hours once identified.

---

Next Steps

1. ✅ Check if your project is affected right now 2. ✅ If affected, wait—do not panic-restart 3. ✅ Monitor status.supabase.com for updates 4. ✅ Export critical data if concerned 5. ✅ Contact Supabase support if stuck beyond 60 minutes

Stay calm. This is a known issue with a fix in progress. Your data is safe.

—Senior Dev Team