India ISP Status
Real-time tracking of Supabase and Firebase DNS blocking across major Indian ISPs. Last checked: February 28, 2026
Affecting 980M+ combined subscribers across Jio, Airtel, BSNL, and ACT Fibernet
| ISP | Subscribers | Supabase | Firebase | Notes | Fix |
|---|---|---|---|---|---|
| Reliance Jio | 500M+ | Blocked | Working | DNS poisoning confirmed. All supabase.co subdomains affected. | Fix guide → |
| Bharti Airtel | 380M+ | Blocked | Working | DNS poisoning confirmed. Mobile and broadband affected. | Fix guide → |
| BSNL | 100M+ | Blocked | Blocked | Both platforms blocked. Most restrictive ISP. | Fix guide → |
| ACT Fibernet | 2M+ | Blocked | Working | DNS blocking confirmed in some cities. Inconsistent rollout. | Fix guide → |
| Vodafone Idea (Vi) | 230M+ | Unconfirmed | Working | Not yet confirmed. May implement block per ministry order. | Fix guide → |
Supabase
Firebase
DNS poisoning confirmed. All supabase.co subdomains affected.
View fix guide →Supabase
Firebase
DNS poisoning confirmed. Mobile and broadband affected.
View fix guide →Supabase
Firebase
Both platforms blocked. Most restrictive ISP.
View fix guide →Supabase
Firebase
DNS blocking confirmed in some cities. Inconsistent rollout.
View fix guide →Supabase
Firebase
Not yet confirmed. May implement block per ministry order.
View fix guide →Our status data comes from multiple verification methods to ensure accuracy:
We perform DNS resolution tests from connections on each major ISP, comparing results against known Supabase IP ranges.
Direct HTTP and HTTPS requests to Supabase API endpoints, measuring response codes and timeout behavior.
Reports from developers across India are cross-verified against our automated checks to confirm ISP-specific status.
If your app uses Supabase and serves Indian users, the affected ISPs represent over 1 billion combined subscribers. That is the vast majority of India's internet population unable to reach your backend.
Even partial blocks on a single ISP affect tens of millions of users. For example, ACT Fibernet's block only covers certain cities, but those cities include Bangalore - India's tech capital and home to a large portion of the developer community.
Firebase blocking on BSNL adds another layer of concern. If you were considering Firebase as a fallback, that option is already compromised on India's government-operated ISP.
The only reliable fix is routing your API traffic through a domain that is not blocked. A reverse proxy on Cloudflare Workers is the most proven approach because Cloudflare's domains are not on any ISP block list.
Managed proxy service. Change one URL and your app works across all Indian ISPs. Free tier available.
Get started →
Generate a ready-to-deploy Worker script. Full control, no third-party dependency. Uses Cloudflare free tier.
Generate code →
Detailed technical breakdown of the block, why it happened, and every available fix option compared.
Read article →
Do not wait for ISPs to unblock Supabase. Deploy your own proxy and make your app accessible to every user in India.
npx create-jiobase — self-host on Cloudflare Workers for free