Fix Supabase Realtime Blocked in India

What breaks

Supabase Realtime uses WebSocket connections to deliver live updates, presence tracking, and broadcast messages. When *.supabase.co is DNS-blocked, the WebSocket handshake fails because it starts as an HTTP upgrade request to the blocked domain. All real-time subscriptions, presence channels, and broadcast channels stop working. Your app falls silent - no live updates, no typing indicators, no online status, no collaborative features.

Impact on your users

Apps that depend on real-time features become static and unresponsive. Chat applications stop receiving new messages. Collaborative documents stop syncing. Live dashboards freeze. Notification systems go silent. The app appears "stuck" or "lagging" to users, who may think the app itself is broken rather than the connection.

Why Realtime is blocked

Indian ISPs (Jio, Airtel, BSNL, ACT Fibernet) are DNS-blocking all subdomains under *.supabase.co following a government order under Section 69A of the IT Act. This means every Supabase service endpoint is unreachable, including the /realtime/v1/ path that Realtime depends on.

The block is at the DNS level. Your ISP's DNS resolver returns incorrect IP addresses for Supabase domains, causing connections to time out or fail. Supabase itself is fully operational - the block is ISP-specific.

Technical details

Supabase Realtime makes HTTP requests (and WebSocket connections for Realtime) to your Supabase project's /realtime/v1/ endpoint. When DNS is poisoned:

Affected ISPs

The following ISPs are confirmed to block Supabase Realtime (along with all other Supabase services):

Fix Supabase Realtime

Route Supabase Realtime traffic through an unblocked domain. Your existing code stays almost identical — just swap the URL. Two options:

npx create-jiobase

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

// Proxied through JioBase - Realtime works including WebSockets:
const supabase = createClient('https://myapp.jiobase.com', 'your-anon-key')

// Subscribe to real-time changes (works through proxy)
const channel = supabase
  .channel('room-1')
  .on('postgres_changes',
    { event: '*', schema: 'public', table: 'messages' },
    (payload) => console.log('New message:', payload)
  )
  .subscribe()

// Presence tracking (works through proxy)
const presence = supabase.channel('online-users')
presence.on('presence', { event: 'sync' }, () => {
  console.log('Online:', presence.presenceState())
})

Deploy and verify

Deploy your updated code and test from a blocked ISP (Jio, Airtel) to confirm Realtime operations work through the proxy. Your anon key stays the same. Supabase Realtime works identically through the proxy.

What stays the same

When you switch to a JioBase proxy URL, everything except the URL stays identical:

Frequently asked questions