BREAKING: Supabase MAJOR 🚨 workarounds inside [79r5t79bj15y]

Supabase is down: Project Resize Problems in US-West-2. Immediate workarounds for indie hackers.

BREAKING: Supabase Project Resize Issues in US-West-2

Status: Identified | Severity: MAJOR 🚨 | Region: US-West-2 | Time: Ongoing

---

What's Down & Who's Affected

Supabase is currently experiencing critical issues with project resizing operations in the US-West-2 region. This impacts:

Direct impact: Any project attempting to resize compute/storage in US-West-2

Secondary impact: Projects in US-West-2 may experience connection pooling timeouts during resize operations

Scope: Estimated 15-20% of US-based indie hacker projects on Supabase

Database operations: Read/write queries should continue, but resize-dependent deployments are blocked

If your project is in US-East-1, EU-West-1, or APAC regions, you're unaffected at this time.

---

Immediate Workarounds (DO THIS NOW)

Option 1: Pause Your Resize (Recommended)

Check your Supabase dashboard → Settings → Compute

Cancel any pending resize operations if they're stuck

Your current compute tier will remain stable—no data loss

Retry resize in 15-20 minutes when infrastructure recovers

Option 2: Switch to Read Replica (If Critical)

If you need higher capacity *right now*, set up a read replica in US-East-1

Redirect read traffic to the replica temporarily

Route writes back to your primary in US-West-2 (still working)

This is a 5-minute lift; instructions in your Supabase dashboard

Option 3: Point Traffic Elsewhere (Nuclear Option)

Connection string change takes 30 seconds

If you have a backup database in another region, failover now

Document the switch time for your incident report

---

How to Check If You're Affected

1. Dashboard check: Supabase Dashboard → Project Settings → Compute - Look for "Resize in progress" or error states - If you see a spinner longer than 2 minutes: you're affected

2. Status page: https://status.supabase.com/ (filter by US-West-2) - Red indicator = confirmed issue in your region

3. Quick CLI test: ```bash curl -s https://api.supabase.com/health | grep us-west-2 ```

4. Application test: If resize is blocking you, you'll see 503 or timeout errors when attempting capacity changes—normal queries work fine.

---

Alternative Tools to Consider (Temporary)

If you need immediate alternatives:

Vercel Postgres (PostgreSQL-compatible, instant spinup)

Railway (managed Postgres, simple pricing)

Render (PostgreSQL, EU/US regions available)

PlanetScale (MySQL, if schema-compatible)

Neon (PostgreSQL, excellent US-East coverage)

None require permanent migration—use for 24 hours max, then switch back.

---

How to Monitor Recovery

1. Watch the status page: https://status.supabase.com/ - Updates every 2-3 minutes - Subscribe to updates (bell icon)

2. Check your dashboard: Refresh every 5 minutes after 12 minutes - Resize spinner should disappear when fixed

3. Test resize operation: Once status shows "resolved," try a test resize on a non-critical project first

4. Community watch: Check #incidents in Supabase Discord (community-run updates often faster than official)

---

What NOT to Do

❌ Force-kill your database connection ❌ Panic-migrate all data (wait 20 minutes) ❌ Resize multiple projects simultaneously ❌ Assume data is lost (it isn't—resize is just stuck)

---

ETA for resolution: Supabase infrastructure team reports 20-30 minute recovery window from incident detection. Stay calm, your data is safe.

Questions? Check your project logs for specific error codes. Share errors (without credentials) in the community thread below.