Supabase Blocked in India? Here's How to Fix It in 60 Seconds

What Happened?

On February 24, 2026, the Indian government issued a blocking order under Section 69A of the Information Technology Act. Major ISPs — Jio, Airtel, ACT Fibernet — blocked access to *.supabase.co domains.

This means:

• All Supabase REST API calls from India → broken
• Supabase Auth (login, signup) → broken
• Supabase Storage (file uploads/downloads) → broken
• Supabase Realtime subscriptions → broken
• The supabase.com marketing site → still works
• The Supabase dashboard → still works

The government hasn't given a clear reason. An official stated "information was being shared that should not have been shared." Supabase has appealed to MeitY for clarification.

Some ISPs have partially restored access in March 2026, but there's no official unblock order. It can be blocked again at any time.

Who's Affected?

India accounted for ~9% of Supabase's global traffic in January 2026. Thousands of apps went down overnight:

• Startup MVPs and production apps
• Student projects and hackathon builds
• Indie developer SaaS products
• Any app with Indian users that uses Supabase as a backend

The 60-Second Fix: Use a Proxy

The fastest way to get your app working again — without migrating off Supabase — is to route your API traffic through a proxy that isn't blocked.

Option A: SupaRoute (managed proxy)

SupaRoute is a managed Supabase proxy built specifically for the India block. Change one URL:

// Before (broken in India)
const supabase = createClient(
  'https://yourproject.supabase.co',
  'your-anon-key'
);

// After (works everywhere)
const supabase = createClient(
  'https://matrixclawai.com/v1/yourproject',
  'your-anon-key'
);

That's it. Same SDK, same anon key, same everything. All Supabase features work through the proxy.

Option B: Self-hosted Cloudflare Worker proxy

If you want to run your own proxy, deploy a Cloudflare Worker:

// Cloudflare Worker - Supabase Proxy
export default {
  async fetch(request) {
    const url = new URL(request.url);
    const project = url.searchParams.get('project');
    const target = `https://${project}.supabase.co${url.pathname}`;
    
    const headers = new Headers(request.headers);
    headers.delete('host');
    
    return fetch(target, {
      method: request.method,
      headers,
      body: request.body,
    });
  }
};

Alternative: Change DNS Settings

Some ISPs block Supabase via DNS poisoning. Switching to a public DNS resolver may work:

# Try Google DNS
DNS: 8.8.8.8 / 8.8.4.4

# Or Cloudflare DNS
DNS: 1.1.1.1 / 1.0.0.1

⚠️ This only works if your ISP uses DNS-based blocking. Some ISPs (like Jio) use deep packet inspection, which DNS changes won't bypass. And you can't ask your users to change their DNS settings.

Alternative: VPN

A VPN will bypass the block, but it's not viable for production apps. You can't ask your users to install a VPN to use your product.

VPNs are fine for development — so you can access the Supabase dashboard from India. But for your app's API calls, you need a server-side solution.

Full Migration Options

If you want to leave Supabase entirely, here are your options:

Migration takes days to weeks. The proxy fix takes 60 seconds. Start with the proxy, then migrate at your own pace if you decide to leave Supabase.

FAQ

Is the proxy secure?

Yes. It's a stateless pass-through. No data is stored or logged. Your anon key is already public (it's in your frontend code). For backend operations, use your service_role key server-side as you normally would — it never touches the browser.

Will Supabase get unblocked?

Maybe. Some ISPs have partially restored access in March 2026. But there's no official government order lifting the block. It could be re-blocked at any time. The proxy is insurance.

Can I use Supabase custom domains instead?

Yes — if you're on a Supabase paid plan. Custom domains bypass the *.supabase.co block. But it costs $10/month on top of your Supabase plan and requires DNS configuration.

Does this affect apps hosted outside India?

Only if your app has Indian users. The block is on Indian ISPs, so API calls originating from India fail. Server-side calls from non-Indian servers still work fine.