BREAKING: Supabase DNS Resolution Failures Affecting .co Users — Immediate Workarounds Inside

Supabase experiencing DNS resolution failures for .co TLD users. Critical incident affecting some indie projects. Workarounds and monitoring instructions.

BREAKING: Supabase DNS Resolution Failures for .co Users

Status: MONITORING | Last Updated: NOW

---

What's Down & Who's Affected

Supabase infrastructure is currently experiencing DNS resolution failures specifically targeting users with .co domain TLDs. This means:

Affected: Projects using .co domains attempting to connect to Supabase endpoints

Unaffected: .com, .io, .dev, and other TLDs appear to have normal connectivity

Service Impact: Database connections, API routes, and real-time subscriptions may timeout or fail to establish

Scope: This appears to be a DNS routing issue at the edge, not a database outage itself

Supabase Status Page: Check https://status.supabase.com for official updates

---

Immediate Workarounds (Do These NOW)

1. IP Whitelisting Instead of DNS

Bypass DNS resolution entirely: ```bash

SSH into your .co domain infrastructure

Use Supabase's direct IP addresses instead of DNS names

Contact Supabase support for your region's direct IPs

Update your connection string temporarily

```

2. DNS Failover Using CNAME Alias

If you control your DNS:

Create a secondary CNAME pointing to a .com proxy or CDN

Temporarily route traffic through Cloudflare DNS (1.1.1.1) instead of your ISP's resolver

Add this to your client config:

```javascript const { createClient } = require('@supabase/supabase-js') const supabase = createClient(URL, KEY, { realtime: { params: { eventsPerSecond: 10 } } }) ```

3. Temporary Environment Variable Override

Use an IP-based connection string in staging: ```bash SUPABASE_URL=https://[direct-ip]/rest/v1 SUPABASE_ANON_KEY=your_key ```

4. Request Timeout Increase

Add retry logic with exponential backoff: ```javascript const retryFetch = async (url, options, maxRetries = 3) => { for (let i = 0; i < maxRetries; i++) { try { return await fetch(url, {...options, timeout: 15000}) } catch (err) { if (i === maxRetries - 1) throw err await new Promise(r => setTimeout(r, Math.pow(2, i) * 1000)) } } } ```

---

How to Check If You're Affected

Run this diagnostic immediately: ```bash

Test DNS resolution from your .co domain

nslookup [your-project].supabase.co

If it times out or returns NXDOMAIN, you're affected

Test with Google DNS as fallback

nslookup [your-project].supabase.co 8.8.8.8

Check your application logs for ENOTFOUND errors

grep "ENOTFOUND\|DNS\|ETIMEDOUT" your-app.log ```

---

Alternative Tools to Consider (If Extended Outage)

Firebase Realtime Database — Quick migration path for real-time features

Neon — Postgres-compatible, excellent uptime record

PlanetScale — MySQL alternative with strong DNS infrastructure

Render — Integrated database hosting, no DNS headaches

---

Monitor Recovery

1. Official Channel: https://status.supabase.com (subscribe to updates) 2. Community: Supabase Discord #incidents channel 3. Your Infrastructure: Keep running the nslookup test every 5 minutes 4. Verify Resolution: Once DNS returns IPs, test connectivity: ```bash curl -v https://[your-project].supabase.co/rest/v1/ ```

Stay calm, stay focused, this is being resolved. Update your team and customers only with facts, not speculation.

---

*This incident report will be updated as we have more information.*