Fix Supabase on Reliance Jio
Supabase is blocked on Reliance Jio in India. Here is exactly what is happening, how to diagnose it, and how to fix it for your users in under 60 seconds.
Block Type
DNS poisoning with possible DPI
Block Confirmed
Yes - confirmed
Services Blocked
*.supabase.co (all Supabase services)
Affected network types
The block on Reliance Jio affects the following connection types. All users on these networks will experience Supabase connectivity failures unless a proxy is used.
What happened on Reliance Jio
Reliance Jio, India's largest telecom operator with over 500 million subscribers, began DNS-blocking all *.supabase.co domains in February 2026. The block was issued under Section 69A of the IT Act through a government ministry order. Jio's DNS resolvers return a sinkhole IP (49.44.79.236) instead of the actual Supabase AWS servers, making all Supabase API calls fail silently. This affects every Jio user - both mobile data and JioFiber broadband customers.
How Jio blocks Supabase
Jio uses DNS poisoning as the primary blocking mechanism. When a Jio user's device queries *.supabase.co, Jio's internal DNS resolvers return a Jio-owned IP address instead of the real Supabase server IP. This causes all HTTP and WebSocket connections to time out. Some users report that changing DNS to 1.1.1.1 or 8.8.8.8 restores access for development, but this does not fix the issue for your end users who are on Jio's default DNS. There are also reports of deep packet inspection (DPI) being used alongside DNS poisoning on some Jio networks.
Does changing DNS help?
Partial fix - development only
Switching to a public DNS like Google (8.8.8.8) or Cloudflare (1.1.1.1) can restore access on your own device for development. However, this does not fix the issue for your end users. They are on Jio's default DNS and cannot change it. For a production fix, you need a reverse proxy.
Diagnose the block
Run these commands from a device connected to Reliance Jio to confirm whether the block is active on your network:
# Check if Jio is blocking Supabase DNS
nslookup your-project.supabase.co
# If blocked: returns 49.44.79.236 (Jio sinkhole)
# If working: returns an AWS IP like 13.233.x.x
# Compare with Google DNS
nslookup your-project.supabase.co 8.8.8.8
# Should return the real AWS IP
# Test HTTP connectivity
curl -I https://your-project.supabase.co/rest/v1/ \
-H "apikey: YOUR_ANON_KEY"Fix it with JioBase
Route your Supabase traffic through an unblocked domain. Your Jio users connect to your proxy URL (which is not blocked), and the proxy forwards the request to Supabase. 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
If you prefer a dashboard with analytics, rate limiting, and automatic updates:
Sign up at jiobase.com/register (free, no credit card)
Add your Supabase project and get a proxy URL like myapp.jiobase.com
Swap your Supabase URL — one line change:
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
)What JioBase proxies
JioBase is not a simple URL redirect. It is a full reverse proxy running on Cloudflare Workers at the edge. Every Supabase service works through the proxy:
REST API
Database queries, inserts, updates, deletes via PostgREST
Auth
Sign up, sign in, OAuth, magic links, session refresh
Storage
File uploads, downloads, signed URLs, image transformations
Realtime (WebSockets)
Postgres changes, presence, broadcast channels
Edge Functions
Server-side Deno functions with custom logic
Additional notes
Jio is the most impactful block because it serves the largest subscriber base in India. If your app serves Indian users, there is a very high probability that a significant portion of your users are on Jio. The block affects both JioFiber broadband and Jio mobile data connections.
Frequently asked questions
Is Supabase blocked on all Jio connections?
Yes. The block affects Jio 4G/5G mobile data and JioFiber broadband connections across India. Some regions may experience the block at different times due to how Jio rolls out DNS changes, but as of February 2026, the block is confirmed nationwide.
Will changing DNS to 1.1.1.1 fix it for my users?
No. Changing DNS only fixes it on your own device for development purposes. Your end users on Jio will still be using Jio's default DNS resolvers and will not be able to reach *.supabase.co. You need a reverse proxy that routes traffic through an unblocked domain.
Does the Jio block affect Supabase Realtime/WebSockets?
Yes. The DNS block affects all traffic to *.supabase.co, including REST API, Auth, Storage, Realtime WebSocket connections, and Edge Functions. Everything that connects to the supabase.co domain is blocked.
How quickly can I fix my Jio-blocked app?
With JioBase, you can fix it in under 60 seconds. Run npx create-jiobase to self-host a free proxy on Cloudflare Workers, or sign up at jiobase.com/register for the managed option. Swap your Supabase URL — one line of code. Your Jio users will be able to access your app immediately.
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