Fix Supabase on Jio in 60 Seconds

The problem

Jio (along with Airtel and ACT Fibernet) DNS-blocks *.supabase.co. Your app's API calls fail with ERR_CONNECTION_TIMED_OUT for every user on these networks.

This affects all Supabase services -- database queries, auth, storage, edge functions, and realtime. Your code is fine. The network is blocking you.

The fix (3 steps)

Route your Supabase traffic through an unblocked domain. JioBase is a Cloudflare reverse proxy that does exactly this. Here is how to set it up:

The one-line change

Before (blocked on Jio):

import { createClient } from '@supabase/supabase-js'

const supabase = createClient(
  'https://abcdefgh.supabase.co',
  'your-anon-key'
)

After (works on every ISP):

import { createClient } from '@supabase/supabase-js'

const supabase = createClient(
  'https://myapp.jiobase.com',   // changed
  'your-anon-key'              // same key
)

If you use environment variables (recommended), just update the env:

# Before
SUPABASE_URL=https://abcdefgh.supabase.co

# After
SUPABASE_URL=https://myapp.jiobase.com

# Key stays the same
SUPABASE_ANON_KEY=your-anon-key

Verify it works

After deploying, run a quick check from a Jio connection:

# This should time out on Jio:
$ curl -I https://abcdefgh.supabase.co/rest/v1/
curl: (28) Connection timed out

# This should work instantly:
$ curl -I https://myapp.jiobase.com/rest/v1/
HTTP/2 200

If the proxy URL returns a 200, you are done. Your app now works on Jio, Airtel, ACT Fibernet, and every other ISP.

Why changing DNS will not help

Switching to 1.1.1.1 or 8.8.8.8 might fix things on your machine. But it does nothing for your users. You cannot ask 500 million Jio subscribers to change their DNS settings.

Some ISPs also use Deep Packet Inspection (DPI) that blocks connections to *.supabase.co even when DNS resolves correctly. A DNS change only helps you during local development -- it is not a production solution.

What about VPNs?

VPNs work but are not a real solution for production apps:

• Latency: VPNs add 50-200ms per request by routing through distant servers.
• Cost: Users need a paid VPN for reliability. Free VPNs are slow and may log traffic.
• UX friction: You cannot ask every visitor to install and enable a VPN before using your app.

A reverse proxy is transparent -- your users do not know it exists. They just use your app normally.

Frequently Asked Questions