BREAKING: Supabase DNS Resolution Failures for .co Domain Users

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

Incident Overview

Supabase is currently experiencing DNS resolution failures specifically impacting users accessing services via .co domain extensions. This affects both API connectivity and dashboard access for affected users.

What's Down

Primary Impact: DNS resolution for Supabase services accessed through .co domains

Services Affected:

- Supabase API endpoints - Realtime connections - Dashboard access - Database connections via standard hostname resolution

Geographic/User Scope: Primarily .co TLD users; some DNS resolver inconsistencies reported

Immediate Workarounds

1. Use IP Address Direct Access

Instead of relying on DNS resolution, connect directly using resolved IP addresses: ```bash

Get your Supabase project IP

nslookup your-project.supabase.co

Use the returned IP in connection strings

```

2. Switch DNS Resolvers

Try alternative DNS providers temporarily:

- Google DNS: 8.8.8.8, 8.8.4.4 - Cloudflare DNS: 1.1.1.1, 1.0.0.1 - Quad9: 9.9.9.9, 149.112.112.112

3. Use VPN or Proxy

Route traffic through a VPN service or HTTP proxy to bypass local DNS resolution issues.

4. Temporary Hostname Mapping

Add manual entries to your /etc/hosts file (Linux/Mac) or C:\Windows\System32\drivers\etc\hosts (Windows): ``` 1.2.3.4 your-project.supabase.co ``` *(Replace 1.2.3.4 with the actual IP found via nslookup)*

How to Check If You're Affected

Test DNS Resolution

```bash

Linux/Mac/Windows (PowerShell)

nslookup your-project.supabase.co

Or use dig (Linux/Mac)

dig your-project.supabase.co

Windows command prompt

ipconfig /all ```

If Affected: No valid IP address returned, or timeout errors

Test Connectivity

```bash

Ping test

ping your-project.supabase.co

Connection test

curl -I https://your-project.supabase.co ```

Alternative Solutions

1. Use Regional Endpoints

I'm unsure if Supabase currently offers region-specific alternate endpoints—check your project settings or documentation.

2. Temporary Database Connection Alternative

If using PostgreSQL directly, some users report success connecting via:

SSH tunneling through a working server

Third-party database tools with proxy support

3. Contact Supabase Support

Status page: https://status.supabase.com

Email support with your project ID

Supabase Discord community for real-time updates

Next Steps

1. Verify your domain TLD - Confirm if you're using .co or another extension 2. Test with alternative DNS - Implement workaround #2 immediately 3. Monitor status page - Updates posted regularly 4. Document error messages - Share with Supabase support for faster resolution

Notes

This appears to be DNS-infrastructure specific; database/application data is likely unaffected

TTL (Time To Live) cache clearing may be necessary once resolved

Unknown: Expected resolution time and whether all .co registrars are equally affected

Last Updated: Monitor Supabase status page for latest information.