ISP Fix 2M+ subscribers

Fix Supabase on ACT Fibernet

Supabase is blocked on ACT Fibernet 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

Block Confirmed

Yes - confirmed

Services Blocked

*.supabase.co (all Supabase services)

Affected network types

The block on ACT Fibernet affects the following connection types. All users on these networks will experience Supabase connectivity failures unless a proxy is used.

Fiber broadband

What happened on ACT Fibernet

ACT Fibernet, a popular broadband provider in major Indian cities like Bengaluru, Hyderabad, Chennai, and Delhi, confirmed the Supabase block following the ministry order. However, the block has been inconsistent - TechCrunch verified that supabase.co was inaccessible on ACT in Delhi but some users in Bengaluru reported it still worked. This inconsistency is typical of how Indian ISPs implement blocking orders.

How ACT blocks Supabase

ACT Fibernet uses DNS-level blocking. Their DNS resolvers intercept queries for *.supabase.co and return incorrect results. The implementation appears to be region-dependent, with some ACT networks implementing the block before others.

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 ACT'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 ACT Fibernet to confirm whether the block is active on your network:

terminal

# Check ACT Fibernet DNS
nslookup your-project.supabase.co

# Compare with Cloudflare DNS
nslookup your-project.supabase.co 1.1.1.1

# Quick HTTP test
curl -m 5 -s -o /dev/null -w "%{http_code}" \
  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 ACT users connect to your proxy URL (which is not blocked), and the proxy forwards the request to Supabase. Two options:

Recommended

Self-host your own proxy

Deploy a full-featured proxy on your own Cloudflare Workers account. Free, open-source, under 60 seconds.

terminal

npx create-jiobase

Guided 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:

Add your Supabase project and get a proxy URL like myapp.jiobase.com

Swap your Supabase URL — one line change:

supabase.ts

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

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

ACT Fibernet is popular among tech professionals and developers in Tier-1 cities. The inconsistent blocking means your app may work for some ACT users but not others, making it especially frustrating to debug.

Frequently asked questions

Is Supabase blocked on all ACT Fibernet connections?

The block is inconsistent across ACT regions. Users in Delhi and some other cities have confirmed the block, while some users in Bengaluru reported intermittent access. If your app serves ACT users, you should assume the block can appear at any time in any region.

Does ACT Fibernet block Firebase too?

No. As of February 2026, Firebase works on ACT Fibernet. The Firebase block is primarily on BSNL. However, given ACT's compliance with the Supabase ministry order, future blocking of other services is possible.

My Supabase app works on ACT but my users say it does not. Why?

ACT's block rollout is region-dependent. Your ACT connection may not be affected yet while your users in a different city are blocked. Always test from multiple networks and consider adding a proxy proactively.

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.

Self-host free Try managed

npx create-jiobase — deploy your own proxy on Cloudflare Workers

ISP Fix