Fix DNS_PROBE_FINISHED_NXDOMAIN with Supabase in India
Getting DNS_PROBE_FINISHED_NXDOMAIN 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
DNS_PROBE_FINISHED_NXDOMAIN means your browser asked the DNS server to look up a domain name and the DNS server responded that the domain does not exist (NXDOMAIN = Non-Existent Domain). This is an immediate failure - your browser does not even attempt to connect because the DNS lookup failed entirely.
Why it happens in India
Some Indian ISPs implement the Supabase block by returning NXDOMAIN instead of a sinkhole IP. When the ISP's DNS resolver receives a query for *.supabase.co, it responds with "this domain does not exist" rather than forwarding the query to upstream DNS servers. This causes your browser to show DNS_PROBE_FINISHED_NXDOMAIN immediately, without the long timeout you would see with connection-based 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.
DNS_PROBE_FINISHED_NXDOMAIN
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:
Verify the domain exists
nslookup your-project.supabase.co 8.8.8.8Expected: If the domain exists (it should), you will get a valid IP. This confirms the domain is real and your ISP is lying.
Check your ISP DNS
nslookup your-project.supabase.coExpected: If your ISP is blocking: "** server can not find your-project.supabase.co: NXDOMAIN" or similar error.
Try Cloudflare DNS
nslookup your-project.supabase.co 1.1.1.1Expected: Should return a valid IP, confirming the block is ISP-specific.
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
Does DNS_PROBE_FINISHED_NXDOMAIN mean Supabase is down?
No. Supabase is fully operational. The NXDOMAIN error means your ISP's DNS is falsely reporting that the domain does not exist. You can verify this by using Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1) - the domain resolves correctly on public DNS.
Why do I see this error instead of ERR_CONNECTION_TIMED_OUT?
Different ISPs implement the block differently. Some return a sinkhole IP (causing timeout), while others return NXDOMAIN (causing this error). Both are DNS-level blocks. The fix is the same - use a reverse proxy to route traffic through an unblocked domain.
Can clearing browser cache fix this?
No. The error comes from your ISP's DNS resolver, not your browser cache. Clearing cache, cookies, or restarting your browser will not help. You need to either change your DNS for development or use a proxy for production.
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