BREAKING: Supabase MAJOR 🔴 DNS failures blocking project operations [72nly8q8062v]

Supabase experiencing DNS record creation failures impacting project creation, restore, and pause operations. Immediate workarounds for indie hackers inside.

⚠️ BREAKING: Supabase DNS Record Creation Failures

Status: Monitoring | Severity: MAJOR | Last Updated: Now

What's Down & Who's Affected

Supabase is experiencing DNS record creation failures that are blocking critical operations:

❌ New project creation - cannot spin up fresh projects

❌ Project restoration - restore from backup failing

❌ Project pause/unpause - state management broken

✅ Existing projects: Still operational (READ/WRITE working)

Who's affected: Anyone trying to create new projects, restore backups, or manage project states. Existing production projects remain functional.

Immediate Workarounds (Do This NOW)

If You Need a New Project

1. Wait for recovery (monitoring in progress) - ETA unknown 2. Use PostgreSQL directly - Spin up a Postgres instance on: - Railway.app (instant deploy) - Render (free tier available) - DigitalOcean App Platform - AWS RDS (t3.micro free tier) 3. Delay non-critical projects - If timeline allows, wait for Supabase recovery

If You Need to Restore a Backup

1. Export from backup - Download your backup SQL dump if available in Supabase dashboard 2. Restore to temporary Postgres - Use Railway/Render temporarily 3. Manual schema restoration - Apply SQL dump to alternate database 4. Avoid data loss - Do NOT attempt forced operations that might corrupt state

If Your Project is Paused

1. Contact Supabase support - Reference this incident 2. Use alternative DB temporarily - Don't let your app die waiting 3. Keep API keys safe - Store credentials securely if switching services

How to Check If You're Affected

``` ✅ Your project IS affected if:

You created project in last 24 hours

You attempted restore/pause in last 2 hours

Dashboard shows "DNS" or "record creation" errors

Project operations hang on loading state

✅ Your project is UNAFFECTED if:

Project already existed before incident

All database queries execute normally

API responses are standard latency

Auth + storage operations working

```

Check [status.supabase.com](https://status.supabase.com) for official updates.

Alternative Tools to Consider

If you're reconsidering your stack:

| Tool | Pros | Cons | |------|------|------| | Railway | Dead simple, instant deploys, great DX | Less features than Supabase | | Render | Free tier, reliable, good docs | Smaller ecosystem | | Neon | Serverless Postgres, auto-scaling | Still scaling infrastructure | | PlanetScale (MySQL) | MySQL alternative, generous free tier | Not Postgres | | AWS RDS | Enterprise grade, reliable | More complex setup |

Pro tip: Many indie hackers run Postgres on Railway for $5-7/month. Reliable. Simple. Works.

Monitor for Recovery

1. Watch official channels: - [status.supabase.com](https://status.supabase.com) - [@supabase on Twitter](https://twitter.com/supabase) - Discord #announcements

2. Test recovery yourself: ``` Try creating a test project every 15 min When it succeeds = incident resolved ```

3. Expected timeline: DNS issues typically resolve within 2-6 hours. Supabase infrastructure is solid—this is temporary.

Bottom Line

Existing projects are safe. Your data is safe. New projects/restores are blocked temporarily. Use alternatives above if time-critical. Check status.supabase.com every 30 minutes. We'll update when resolved.

Stay calm. Keep building. 🚀