BREAKING: Supabase ca-central-1 Region Experiencing Project Creation Failures — Workarounds Inside

Supabase's ca-central-1 region reporting degraded project creation success rates. Immediate workarounds and alternatives available.

Supabase ca-central-1 Region Outage: Project Creation Failures

What's Down

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

New project provisioning requests in ca-central-1 are failing or experiencing extended delays

Existing projects in this region are reportedly unaffected

The issue is isolated to project creation workflows, not runtime database operations

API calls and database queries for established projects should continue normally

How to Check If You're Affected

1. Verify your region: Check your Supabase project settings → General → Region. If it shows ca-central-1, you're in the affected region. 2. Timing: If you attempted to create a new project in ca-central-1 in the last few hours and received errors or timeouts, you're likely affected. 3. Monitor status: Check [Supabase Status Page](https://status.supabase.com) for real-time updates on this incident. 4. Test endpoint connectivity: Existing projects can verify functionality by running test queries against their PostgreSQL instance.

Immediate Workarounds

Option 1: Switch Regions (Fastest)

Create new projects in us-east-1 or eu-west-1 regions instead

These regions are currently operating normally

For production use cases, us-east-1 offers similar latency for North American users

Trade-off: Slightly higher latency depending on your actual geographic location

Option 2: Retry with Exponential Backoff

If you need ca-central-1 specifically, attempt project creation again after 5 minutes

Supabase engineering typically identifies and mitigates such issues within 30-60 minutes

Wait for status page confirmation of resolution before retrying

Option 3: Temporary Alternative Hosts

AWS RDS PostgreSQL (ca-central-1): Full database hosting alternative

Azure Database for PostgreSQL: Similar managed service

Digital Ocean Managed Databases: Quick provisioning in Toronto region

These require manual setup and won't include Supabase's additional services (Auth, Realtime, Storage)

For Existing Projects

Good news: Projects already created in ca-central-1 should continue operating normally. This outage affects only the *creation workflow*, not running infrastructure.

Database connections should persist

Auth flows remain functional

Real-time subscriptions unaffected

API routes continue serving requests

Next Steps

1. Subscribe to updates: Check Supabase Status Page for incident resolution 2. Document impact: Note affected users and timing for post-incident review 3. Plan multi-region: For critical applications, consider distributed deployment across multiple Supabase regions 4. Contact support: For time-sensitive production migrations, reach out to Supabase support for priority handling

Additional Resources

[Supabase Status Page](https://status.supabase.com)

[Supabase Discord Community](https://discord.supabase.com) (real-time discussion)

[Region Selection Best Practices](https://supabase.com/docs/guides/platform/regional-deployments)

Last Updated: Monitor status page for latest information. This incident is being actively investigated.