Fix ERR_NAME_NOT_RESOLVED with Supabase in India
Getting ERR_NAME_NOT_RESOLVED when your app tries to connect to Supabase? Indian ISPs are DNS-blocking supabase.co. Here is what the error means, how to diagnose it, and how to fix it.
What this error means
ERR_NAME_NOT_RESOLVED means your device could not translate the domain name (e.g., your-project.supabase.co) into an IP address. This is similar to DNS_PROBE_FINISHED_NXDOMAIN but may appear on different browsers or operating systems. The underlying cause is the same - the DNS lookup failed.
Why it happens in India
Indian ISPs blocking *.supabase.co can cause this error when their DNS resolvers either return NXDOMAIN, fail to respond, or return SERVFAIL for Supabase domains. The exact error message varies by browser (Chrome shows ERR_NAME_NOT_RESOLVED, Firefox shows "Hmm. We are having trouble finding that site.") but the root cause is identical - ISP-level DNS blocking.
What you see in the browser
When your ISP blocks Supabase, your browser shows this error because the DNS lookup or connection to *.supabase.co fails. The error appears in the browser console and sometimes as a visible page error if your app does not handle network failures gracefully.
ERR_NAME_NOT_RESOLVED
Chrome / Edge browser error
Which ISPs trigger this error
This error can appear on any Indian ISP that blocks *.supabase.co. The confirmed ISPs include:
Diagnostic steps
Follow these steps to confirm whether the error is caused by ISP DNS blocking:
Test DNS with nslookup
nslookup your-project.supabase.coExpected: If blocked: error message or incorrect IP. If working: valid AWS IP.
Test with alternative DNS
nslookup your-project.supabase.co 1.1.1.1Expected: Should return valid IP, confirming ISP block.
Flush DNS cache and retry
# Windows
ipconfig /flushdns
# macOS
sudo dscacheutil -flushcache
# Linux
sudo systemd-resolve --flush-cachesExpected: If the error persists after flushing, it confirms the ISP is actively blocking (not a stale cache).
Understanding the root cause
The Indian government issued a blocking order under Section 69A of the IT Act that requires ISPs to block access to *.supabase.co. ISPs implement this by poisoning their DNS resolvers. When you query a blocked domain, instead of returning the real IP address, the ISP returns either a sinkhole IP (causing timeout) or NXDOMAIN (causing name resolution failure).
This is not a Supabase outage. Supabase's infrastructure is fully operational. The block exists only at the ISP level in India. Users outside India, or users on VPNs, can access Supabase normally.
Fix it with a reverse proxy
The permanent fix is to route your Supabase traffic through a domain that is not blocked. Two options:
Self-host your own proxy
Deploy a full-featured proxy on your own Cloudflare Workers account. Free, open-source, under 60 seconds.
npx create-jiobaseGuided setup: enter your Supabase URL, configure CORS, deploy. WebSocket + all 6 services included.
Learn more →Or use JioBase managed
Dashboard with analytics, rate limiting, and automatic updates. Sign up free, add your Supabase project, and swap one URL.
import { createClient } from '@supabase/supabase-js'
// Replace your Supabase URL with your proxy URL:
const supabase = createClient(
'https://your-proxy.workers.dev', // was: https://xyz.supabase.co
'your-anon-key' // stays the same
)Temporary workarounds (development only)
These workarounds can restore access on your own device for development, but they do not fix the issue for your end users:
Change DNS to 1.1.1.1 or 8.8.8.8
Works for your device only. Your users still use their ISP's DNS.
Use Cloudflare WARP or a VPN
Encrypts DNS queries and bypasses the block. Not a production solution - you cannot ask all users to install a VPN.
Frequently asked questions
Is ERR_NAME_NOT_RESOLVED the same as DNS_PROBE_FINISHED_NXDOMAIN?
Essentially yes. Both mean your device cannot resolve the domain name to an IP address. Different browsers and operating systems display different error messages for the same underlying DNS failure. The fix is identical.
I see this error on my phone but not on my laptop. Why?
Your phone and laptop may be using different DNS servers. If your laptop has been configured to use Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1), it bypasses the ISP block. Your phone on mobile data uses the ISP's default DNS, which is blocking supabase.co.
Fix your Supabase app in under 60 seconds
JioBase routes your Supabase traffic through Cloudflare's edge network. No VPN, no DNS hacks, no code rewrites. One command or one line change.
npx create-jiobase — deploy your own proxy on Cloudflare Workers