BREAKING: Supabase DNS Resolution Failures for .co Domain Users

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

Supabase DNS Resolution Failures – .co TLD Users Affected

What's Down

Supabase is currently experiencing DNS resolution failures specifically impacting users accessing services through .co domain extensions. This affects:

API endpoint connectivity for .co based applications

Database connections initiated from .co domains

Real-time subscriptions and WebSocket connections

Authentication services for affected domain users

Status: Under active monitoring. Root cause investigation ongoing.

How to Check If You're Affected

1. Domain Check: Is your application domain a .co TLD? 2. DNS Lookup Test: Run the following in terminal: ```bash nslookup api.supabase.co dig api.supabase.co ``` 3. Connection Test: Attempt to connect to your Supabase project endpoint 4. Monitor Status: Check [Supabase Status Page](https://status.supabase.com) for official updates

Immediate Workarounds

Workaround 1: Use IP Address Directly

If you have your Supabase project's IP address, bypass DNS by connecting directly to the IP: ```javascript // Instead of: api.supabase.co // Use direct IP (contact Supabase support for your IP) ``` *Note: This is a temporary measure only.*

Workaround 2: DNS Over HTTPS (DoH)

Configure your application to use alternative DNS resolvers: ```bash

Linux/Mac

echo "nameserver 8.8.8.8" | sudo tee /etc/resolv.conf echo "nameserver 1.1.1.1" | sudo tee -a /etc/resolv.conf

Or use Cloudflare's DoH in your app configuration

```

Workaround 3: Local Hosts File

Temporarily map the domain locally (while fix is deployed): ```bash

Add to /etc/hosts (Linux/Mac) or C:\Windows\System32\drivers\etc\hosts (Windows)

[SUPABASE_IP] api.supabase.co ``` *Request the IP from Supabase support.*

Workaround 4: Use VPN/Proxy

Route traffic through a VPN with reliable DNS to bypass regional resolution issues.

Workaround 5: Temporary Domain Redirect

If possible, temporarily point your application to use a different domain extension (.com, .io) while maintaining backend infrastructure.

Alternative Solutions

Firebase: Consider temporary data syncing to Firebase Realtime Database

PlanetScale: MySQL-compatible alternative for database needs

MongoDB Atlas: NoSQL alternative with reliable infrastructure

AWS RDS + API Gateway: Direct cloud infrastructure alternative

What Supabase Is Doing

I'm unsure of specific details regarding:

Exact root cause of the DNS resolution failure

Estimated time to resolution

Geographic scope beyond .co TLD users

Whether other TLDs are affected

Recommendation: Contact Supabase support directly at support@supabase.com or check their status page for authoritative updates.

Next Steps

1. Verify if your domain is affected (.co users) 2. Implement recommended workaround immediately 3. Monitor Supabase status page for resolution updates 4. Have alternative service credentials ready 5. Document the incident for post-mortem analysis

This is a developing situation. We'll update as more information becomes available.