BREAKING: Supabase MINOR 🚨 DNS Record Delays—Workarounds Inside [ms53dzxm1gtl]

Supabase experiencing delays in DNS record creation. Partial disruption affecting new project deployments. Immediate workarounds and monitoring steps for indie hackers.

BREAKING: Supabase DNS Record Creation Delays

Status: Investigating | Severity: MINOR | Impact: Partial Disruption

Last Updated: Now | ETA: TBD

---

What's Affected

Supabase is currently experiencing delays in DNS record propagation for newly created projects. This impacts:

New project deployments (primary impact)

Custom domain configuration for existing projects

Projects migrating to new instances

Teams creating multiple projects in rapid succession

Who's affected: Primarily indie hackers and small teams spinning up new Supabase instances in the last 2-4 hours. Existing projects and their data are safe—this is purely DNS infrastructure.

---

Immediate Workarounds (Do These Now)

1. Use Default Supabase URLs Temporarily

Don't wait for custom DNS. Your project's auto-generated Supabase URL (format: https://xxxxx.supabase.co) works immediately and doesn't require DNS propagation.

```bash

Use this instead of waiting for custom domain

const SUPABASE_URL = 'https://your-project.supabase.co' const SUPABASE_ANON_KEY = 'your-anon-key' ```

2. Delay Custom Domain Setup

If you haven't added custom domains yet, wait 30-60 minutes before attempting. The DNS pipeline should clear by then.

3. Check DNS Propagation Independently

If you already requested DNS records:

```bash

Check status without Supabase dashboard

nslookup your-domain.com dig your-domain.com

Or use online tools:

- whatsmydns.net

- mxtoolbox.com

```

4. Hard Refresh Your Supabase Dashboard

The UI might show stale status. Force refresh:

``` Cmd+Shift+R (Mac) or Ctrl+Shift+F5 (Windows) ```

---

How to Check If Your Project Is Affected

1. Go to your Supabase project dashboard 2. Navigate to Settings > API 3. Check if your custom domain shows "Pending" longer than 10 minutes 4. Try connecting to your default supabase.co URL—if that works, you're fine 5. Test connectivity:

```javascript const { createClient } = require('@supabase/supabase-js') const supabase = createClient(URL, KEY) const { data } = await supabase.from('your_table').select('count', { count: 'exact' }) console.log('Connected:', data ? 'YES' : 'NO') ```

---

Alternative Tools (If You Need Alternatives)

If you're blocked and need immediate action:

Firebase Realtime Database – quick setup, similar UX

PlanetScale (MySQL) – solid DNS, handles scaling

MongoDB Atlas – mature platform, excellent DNS

Neon (PostgreSQL) – Postgres alternative, simpler networking

Note: We don't recommend switching unless this extends beyond 2 hours.

---

How to Monitor Recovery

Official Channels:

Supabase Status Page: status.supabase.com

Twitter/X: @supabase

Discord Community: Check #incidents

Set a Reminder: Check back in 45 minutes. Supabase typically resolves DNS issues in 1-2 hours.

Subscribe to Updates: Enable notifications on your Supabase project settings for real-time status changes.

---

Bottom Line

Your data is safe. Your projects work. Custom domains are just slow right now. Use default Supabase URLs and carry on building. This will pass.

Stay calm. Keep shipping.