BREAKING: Supabase DNS Resolution Failures for .co Domain Users

Supabase experiencing DNS resolution issues affecting .co TLD users. Immediate workarounds and status checks inside.

BREAKING: Supabase DNS Resolution Failures for .co TLD Users

What's Down

Supabase is currently experiencing DNS resolution failures specifically impacting users attempting to connect via .co domain extensions. This affects:

Database connections through .co endpoint URLs

API calls routed through affected regional DNS resolvers

Authentication services for affected TLD users

Real-time subscriptions using .co domain infrastructure

Note: We're monitoring reports and some details are still emerging. Regional scope and full impact assessment ongoing.

Who's Affected

Primarily users whose Supabase project endpoints resolve through .co TLD infrastructure or those connecting from regions using affected DNS servers. Not all Supabase users are impacted—standard .com endpoints may function normally.

Immediate Workarounds

1. Switch Connection Methods

If using direct endpoint URLs, try accessing via IP address instead of domain name

Use hardcoded IP addresses in your connection strings temporarily (contact Supabase support for IP whitelist approval)

Route connections through VPN or proxy services that bypass affected DNS resolvers

2. Change DNS Resolvers

Switch your system DNS from your ISP's resolver to:

- Cloudflare: 1.1.1.1 and 1.0.0.1 - Google: 8.8.8.8 and 8.8.4.4 - Quad9: 9.9.9.9

This bypasses potentially compromised .co TLD resolution paths

3. Use Alternative Endpoints

If available, request IPv6 endpoints from Supabase support

Try accessing through mirror/failover endpoints if provided

Implement connection pooling with fallback logic in your application

4. Temporary Application-Level Fixes

```javascript // Add retry logic with exponential backoff const connectWithRetry = async (maxRetries = 5) => { for (let i = 0; i < maxRetries; i++) { try { return await supabase.connect(); } catch (error) { await new Promise(r => setTimeout(r, Math.pow(2, i) * 1000)); } } }; ```

How to Check If You're Affected

1. Test DNS Resolution: ```bash nslookup your-project.supabase.co # or dig your-project.supabase.co ``` If no results or timeout errors appear, you're likely affected.

2. Check Supabase Status Page: Visit status.supabase.com for real-time updates

3. Test Connectivity: ```bash curl -v https://your-project.supabase.co/rest/v1/ ``` Connection timeouts indicate DNS issues.

4. Review Application Logs: Look for DNS resolution errors or NXDOMAIN responses

Recommended Alternatives (Temporary)

Firebase Realtime Database - immediate migration path

PlanetScale - MySQL compatibility layer

Neon - PostgreSQL alternative with similar feature set

Railway - PostgreSQL hosting with DNS redundancy

Ongoing Monitoring

Supabase engineering is investigating root cause and DNS propagation delays. Updates expected within 2-4 hours. Do not switch providers permanently without confirmation this isn't a temporary regional issue.

Next Steps

1. Contact Supabase support with your project ID 2. Implement one of the workarounds above 3. Monitor status.supabase.com continuously 4. Keep application team informed of ETA

Last Updated: Monitoring (details subject to change as situation develops)

Status: Investigating