BREAKING: Supabase DNS Resolution Failures for .co TLD Users
Supabase experiencing DNS resolution issues affecting .co domain users. Immediate workarounds and status inside.
BREAKING: Supabase DNS Resolution Failures for .co TLD Users
What's Down
Supabase is currently experiencing DNS resolution failures specifically affecting users accessing services through .co top-level domain (TLD) addresses. This impacts:
.co domain connections to Supabase projects.co domain clientsStatus: Monitoring - incident is active as of this report.
How to Check If You're Affected
1. Check your domain TLD: Does your application or connection endpoint use a .co domain?
2. Run DNS diagnostics:
```bash
nslookup your-project.supabase.co
dig your-project.supabase.co
```
3. Monitor connection errors: Look for DNS timeout or NXDOMAIN errors in application logs
4. Check Supabase status page: https://status.supabase.com for official updates
Immediate Workarounds
1. Use Alternative TLD Resolution
If available, temporarily route connections through alternative domain suffixes (e.g.,.app or regional alternatives if Supabase offers them).2. Direct IP Connection
Resolve the IP address manually and hardcode it temporarily: ```bash nslookup your-project.supabase.co @8.8.8.8 ``` Use the returned IP in your connection string if your client supports it.3. DNS Provider Override
Switch to alternative DNS resolvers:8.8.8.8, 8.8.4.41.1.1.1, 1.0.0.1208.67.222.222, 208.67.220.220Update your system/application DNS settings: ```bash
Linux/Mac
resolvectl query-statisticsWindows
ipconfig /all ```4. Connection String Modification
If your client library supports it, use IP-based connection strings instead of domain names, or temporarily use a VPN/proxy service to route around affected DNS.5. Regional Failover
Implement application logic to failover to backup database instances if available in your architecture.Alternatives to Consider
Status and Updates
This is a DNS infrastructure issue specific to .co TLD routing. Supabase infrastructure itself appears operational. Resolution typically requires either:
1. DNS provider infrastructure repair (Supabase's responsibility) 2. Propagation of corrected DNS records (24-48 hours typical)
Uncertain details: I cannot confirm the exact root cause (Supabase DNS, registrar, or global DNS propagation issue) or exact ETA for resolution. Monitor the official Supabase status page for authoritative updates.
Next Steps
1. Switch DNS resolvers immediately as temporary fix 2. Implement connection retry logic with exponential backoff 3. Subscribe to Supabase status updates 4. Test all workarounds before deploying to production 5. Document incident for post-mortem analysis
Last Updated: See Supabase status page for real-time incident details.