Breaking February 28, 2026 · 7 min read

Firebase and Supabase Both Blocked in India: The Double Backend Crisis

Q: Is Firebase completely blocked in India?

Not on all ISPs. The Firebase block primarily affects BSNL and some regional ISPs since August 2025. Users on Jio and Airtel can still access Firebase in most cases, but the block is inconsistent.

Q: Can I use JioBase to proxy Firebase too?

JioBase is currently optimized for Supabase. For Firebase, you can build a similar proxy using a Cloudflare Worker. The same architectural principle applies.

Q: Should I switch from Firebase to Supabase or vice versa?

No. Both platforms face blocks on different ISPs, and other providers could be next. Add a proxy layer in front of whatever backend you are already using instead of migrating.

Q: What is the safest backend setup for Indian users?

All client-side traffic goes through a domain you own, and the backend provider is abstracted behind a proxy. Use any BaaS you prefer but route traffic through a Cloudflare Worker or managed proxy.

Q: How quickly can I fix my blocked app?

With JioBase, you can set up in under five minutes. For a DIY proxy with Cloudflare Workers, the tutorial takes about 30 minutes. Either way, the fix is deployable same-day.

Indian developers are facing an unprecedented situation. Two of the most widely used Backend-as-a-Service platforms -- Firebase and Supabase -- are now blocked by different ISPs across India. Developers who migrated from one to the other to escape the first block are now discovering that the problem was never about the provider. It is about depending on third-party domains for critical infrastructure.

What happened

Starting in August 2025, BSNL and a handful of regional ISPs began blocking Firebase endpoints. Developers on those networks found that Firestore queries, Firebase Auth calls, Cloud Functions invocations, and Storage uploads were failing silently or timing out. The block was inconsistent -- some Firebase services worked intermittently, others were completely unreachable.

Many developers responded by migrating to Supabase. It was the obvious choice: open-source, PostgreSQL-based, growing rapidly, and critically, not blocked. Migration guides flooded dev Twitter and Reddit. Hundreds of Indian startups and indie projects made the switch.

Then on February 24, 2026, Supabase was DNS-blocked on Jio, Airtel, and ACT Fibernet. The entire *.supabase.co domain started resolving to sinkhole IPs. Every app that had just finished migrating to Supabase was broken again -- this time on networks covering over 900 million subscribers.

The worst-case scenario is here. If your app used Firebase, it was broken on BSNL. If you migrated to Supabase, it is now broken on Jio and Airtel. If you somehow used both, your app is broken on nearly every major Indian ISP.

The timeline of blocks

The pattern of ISP-level blocks on developer tools has been accelerating. Here is the timeline:

AUG

August 2025

BSNL blocks raw.githubusercontent.com and certain Firebase endpoints including Firestore and Cloud Functions. Developers on BSNL lose access to Firebase-dependent apps and GitHub raw content.

OCT

October 2025

Medium.com blocked across major ISPs including Jio, Airtel, and BSNL. Millions of developers lose access to technical blogs, documentation, and engineering postmortems hosted on Medium.

FEB

February 24, 2026

*.supabase.co DNS-blocked on Jio, Airtel, and ACT Fibernet. REST API, Auth, Storage, Realtime, and Edge Functions all inaccessible. Apps that migrated from Firebase to Supabase are broken again.

The pattern is accelerating. The gap between major developer tool blocks has shortened from years to months. These are not isolated incidents -- they are a systemic trend in how Indian ISPs handle government blocking orders.

Which services are affected

Both Firebase and Supabase offer a full suite of backend services. The blocks affect different services on different ISPs, creating a patchwork of failures across the country.

Firebase

BSNL / some regional ISPs

Firestore (document reads and writes)
Firebase Auth (sign-in, sign-up, OAuth)
Cloud Functions (HTTPS triggers)
Firebase Hosting (custom domains unaffected)
Cloud Storage (uploads and downloads)

Supabase

Jio / Airtel / ACT Fibernet

REST API / PostgREST (all queries)
Supabase Auth (all auth flows)
Storage (file uploads, signed URLs)
Realtime (WebSocket subscriptions)
Edge Functions (serverless invocations)

The result is that there is no single BaaS platform that works reliably across all Indian ISPs right now. Firebase fails on BSNL. Supabase fails on Jio, Airtel, and ACT. A developer whose users span multiple ISPs has no safe choice -- unless they add a proxy layer.

The migration trap

When Firebase was blocked on BSNL, the developer community's instinct was to migrate. Hundreds of projects switched from Firebase to Supabase, rewriting auth flows, migrating databases, and updating client SDKs. It was weeks of engineering effort for many teams.

That migration was built on a flawed assumption: that the block was Firebase-specific. That if you moved to a different provider on a different domain, you would be safe. The Supabase block proved that assumption wrong.

The cycle looks like this:

ISP blocks Provider A. Your app breaks.

You spend weeks migrating to Provider B. Your app works again.

A different ISP blocks Provider B. Your app breaks again.

Migrate again? To where? Every provider is one government order away from being blocked.

The problem is not Firebase. The problem is not Supabase. The problem is that your production app makes requests to a domain you do not control, and that domain can be made unreachable at any time by any ISP. Switching providers does not fix this. You need to eliminate the dependency on third-party domains in your critical path.

What about other BaaS platforms?

If Firebase and Supabase are both blocked, some developers are considering Appwrite, Nhost, PocketBase, or other alternatives. While these platforms are excellent tools, migrating to them does not solve the underlying problem.

Appwrite Cloud uses *.appwrite.io -- a .io domain that is just as susceptible to DNS blocking as .co domains.

Nhost uses *.nhost.run -- another foreign SaaS domain with no special protection from ISP blocks.

PocketBase is self-hosted, which avoids the domain problem -- but it requires managing your own server infrastructure, scaling, backups, and security. It is a fundamentally different operational model.

The pattern shows that Indian ISPs will comply with government orders to block any domain. The TLD does not matter. The provider does not matter. Any foreign SaaS domain used in your client-side code is a potential single point of failure. The only domains that are safe are the ones you own and control.

The real solution: domain independence

The fix is not to find a backend provider whose domain is not currently blocked. The fix is to stop exposing third-party domains to your end users entirely. Route all backend traffic through a domain you own, using a reverse proxy.

This is not a new concept. CDNs, API gateways, and load balancers have always worked this way. Your users hit your domain. Your infrastructure handles the routing. The backend provider is an implementation detail that your users never see.

Architecture principle

Your users should never make requests to a domain you do not control.

Whether you use Firebase, Supabase, Appwrite, or any other BaaS, the traffic from your client should flow through api.yourapp.com, not xyz.provider.co. A reverse proxy on Cloudflare's edge network gives you this decoupling with negligible latency overhead.

Block-proof

If your backend domain gets blocked, change the proxy target without updating any client code. Zero downtime for your users.

Provider-agnostic

Switch from Supabase to Firebase to Appwrite without touching your frontend. The proxy abstracts the backend.

Minimal latency

Cloudflare Workers execute at the edge in 300+ locations. The proxy adds 1-5ms, far less than a VPN or DNS workaround.

Transparent to users

Your users do not need to install a VPN, change DNS, or do anything. The proxy works silently at the infrastructure level.

How JioBase helps

JioBase is a managed Supabase reverse proxy built on Cloudflare's edge network. It gives you a proxy endpoint that routes all Supabase traffic through an unblocked domain -- with full support for REST, Auth, Storage, Realtime WebSockets, and Edge Functions.

For Supabase users, the setup is a one-line code change:

lib/supabase.ts
import { createClient } from '@supabase/supabase-js'
export const supabase = createClient(
//'https://xyz.supabase.co'
'https://myapp.jiobase.com', // proxied through Cloudflare edge
'your-anon-key' // same key, same RLS policies
)

For Firebase users, the concept is identical -- you need a proxy layer between your client and Firebase's servers. While JioBase is purpose-built for Supabase, you can use the same approach with a custom Cloudflare Worker for Firebase. Our free Worker Generator Tool can help you get started with a DIY proxy, and we have a step-by-step tutorial that covers the full implementation.

What JioBase handles for Supabase users

Complete REST API proxying (PostgREST, Auth, Storage, Edge Functions)
WebSocket proxying for Supabase Realtime (subscriptions, presence, broadcast)
Automatic CORS header management with per-app configuration
Custom subdomains and custom domain support
Request analytics and monitoring dashboard
Minimal latency (1-5ms overhead) via Cloudflare's 300+ edge locations

Frequently Asked Questions

Is Firebase completely blocked in India?

Not on all ISPs. The Firebase block is primarily affecting BSNL and some regional ISPs since August 2025. Users on Jio and Airtel can still access Firebase in most cases. However, the block is inconsistent -- some Firebase services may work while others do not, and the situation can change without warning. If your app serves users on BSNL, you should assume Firebase endpoints are unreliable.

Can I use JioBase to proxy Firebase too?

JioBase is currently optimized for Supabase, handling its specific API patterns including PostgREST, Auth, Storage, and Realtime WebSockets. For Firebase, you can build a similar proxy using a Cloudflare Worker. The same architectural principle applies -- route traffic through a domain you control. Check out our Worker Generator Tool to get started with a DIY solution, and stay tuned for potential Firebase support in the future.

Should I switch from Firebase to Supabase or vice versa?

Switching providers to avoid a block is a short-term fix at best. Both Firebase and Supabase are blocked on different ISPs, and other providers could be next. Instead of migrating, add a proxy layer in front of whatever backend you are already using. This protects you regardless of which provider is blocked and avoids the cost and risk of a full backend migration.

What is the safest backend setup for Indian users?

The safest setup has two properties: (1) all client-side traffic goes through a domain you own, and (2) the backend provider is abstracted behind a proxy. Use any BaaS you prefer -- Firebase, Supabase, Appwrite -- but route traffic through a Cloudflare Worker or a managed proxy like JioBase on your own domain. This way, if a provider domain gets blocked, you change the proxy target on your server -- not the client code on every user's device.

How quickly can I fix my blocked app?

If you are using Supabase, you can set up JioBase in under five minutes -- create an account at jiobase.com/register, create a proxy app, and swap the URL in your code. For Firebase or a DIY proxy, the Cloudflare Worker tutorial takes about 30 minutes. Either way, the fix is deployable same-day.

Stop losing users to ISP blocks

Firebase blocked on BSNL. Supabase blocked on Jio and Airtel. The next block could be any provider. Add a proxy layer today and make your app resilient to ISP-level disruptions -- permanently.

Start for free Learn more

Free tier includes 1 proxy app and 50,000 requests/month. No credit card required.

Written and verified by

Sunith VS

Building tools that help Indian developers ship without ISP interference. Creator of JioBase.