BREAKING: Supabase MINOR 🟡 workarounds inside [xlf9g62wsgnw]

Supabase is down: Degraded project creation success rates in the ca-central-1 region. Immediate workarounds for indie hackers.

BREAKING: Supabase ca-central-1 Project Creation Degraded

Status: Identified | Severity: Minor | Impact: Partial | Updated: Now

---

What's Down & Who's Affected

Supabase is experiencing degraded project creation success rates in the ca-central-1 (Canada Central) region. This means:

✋ New projects in ca-central-1 are failing or timing out during creation

✋ Existing projects in ca-central-1 remain operational (no data loss)

✋ Other regions (us-east-1, eu-west-1, etc.) are unaffected

✅ Auth, Database, Realtime, and Storage for *existing* projects continue normally

Who's impacted: Indie hackers trying to spin up new projects specifically in Canada Central region.

---

Immediate Workarounds (Do This Now)

Option 1: Switch Regions (Fastest)

If your project doesn't have regional requirements:

1. Go to Supabase Dashboard → New Project 2. Select a different region: us-east-1 or eu-west-1 (both fully operational) 3. Complete project creation normally 4. Your project spins up in <2 minutes

Best for: 90% of indie projects that don't need Canada-specific latency.

Option 2: Wait & Retry (If You Need ca-central-1)

1. Wait 15-30 minutes for Supabase engineering to resolve the issue 2. Retry project creation 3. Monitor their status page for "Resolved" confirmation

Best for: Projects with Canadian compliance or latency requirements.

Option 3: Temporary Alternative Database

If you're blocked and need to launch today:

PlanetScale (MySQL) - instant provisioning, US/EU/Asia regions

Neon (PostgreSQL) - similar to Supabase, fully operational

Railway.app - PostgreSQL with one-click deployment

Render - managed PostgreSQL, no regional issues

You can migrate to ca-central-1 Supabase later once resolved (data export tools available).

---

How to Check if YOU're Affected

``` Your project is affected IF: ✓ You tried creating a new project in last 2 hours ✓ You selected ca-central-1 region ✓ Creation timed out or returned "Error: Project creation failed"

Your project is NOT affected IF: ✓ You're in us-east-1, eu-west-1, ap-southeast-1, or other regions ✓ Your existing ca-central-1 project is already running ✓ You created your project >2 hours ago ```

Test your existing project: Try accessing your Supabase dashboard. If it loads, you're fine.

---

Alternative Tools to Consider

If you want to diversify away from single-region risk:

| Tool | Type | Regions | Best For | |------|------|---------|----------| | Neon | PostgreSQL | US/EU/Asia | Drop-in Supabase alternative | | Railway | PostgreSQL | Global | Simplicity + 1-click deploys | | PlanetScale | MySQL | 50+ regions | Scale-first architecture | | Firebase | NoSQL | Global | Real-time, serverless |

---

Monitor Recovery

Real-time status: https://status.supabase.com

What to watch for:

Check "ca-central-1" component status

Look for "All Systems Operational" confirmation

Estimated resolution: 1-4 hours from incident start

Subscribe to updates: 1. Visit status.supabase.com 2. Click "Subscribe" (top right) 3. Select "ca-central-1 Region" component 4. Get Slack/email alerts when resolved

---

Bottom Line

This is a partial, contained issue. Most of you are unaffected. If you're creating a new project in Canada, switch regions for 5 minutes and you're back in business. No data loss, no emergency.

Stay calm. Switch regions. Keep shipping. 🚀

—Your StillNotAThing.com devops team