engineering··5 min read·WoWSQL Team

Supabase Blocked in India? What Happened and Your Options

Was Supabase blocked in India? A Feb–Mar 2026 timeline, what was restored, and practical options including custom domains and Indian-hosted backends.

Supabase was disrupted in India in late February 2026, when a government blocking order under Section 69A of the IT Act led several ISPs — including Jio, Airtel and ACT Fibernet — to stop resolving supabase.co reliably. Access was later restored. It is not accurate, on 20 November 2026, to say that Supabase is still banned nationwide. If you are choosing a backend now, the useful question is how to reduce the impact of a future block, not whether the 2026 incident is still on.

WoWSQL is a managed PostgreSQL BaaS from an Indian company, WoWSQL Technologies Private Limited (Tamil Nadu), with a Mumbai region and an Apache 2.0 self-hosted edition. That is one option among several. It is not a promise that any vendor, including us, is immune to a blocking order.

Key facts

  • Timeline, from contemporaneous reporting: a Section 69A order was issued on 24 February 2026, according to TechCrunch (27 February 2026). AIM (2 March 2026) described the ongoing disruption. Supabase's status incident posted a "fully restored" update on 4 March 2026; AIM (4 March 2026) reported the same. A later write-up was published on the status page on 31 March 2026.
  • The government did not publish a detailed public reason. TechCrunch and AIM both noted the lack of an official explanation at the time.
  • WoWSQL: Indian company; NVIDIA Inception member; DPIIT-recognised startup. Regions: Mumbai (ap-south-1), US East (us-east-1), Frankfurt (eu-central-1). Plans: Free $0, Pro $25, Scale $99 (Scale includes custom domains). Yearly billing saves 7%.
  • No immunity claim: an Indian legal entity and a Mumbai region do not prevent a future Section 69A order against a domain you use.

What happened (February–March 2026)

On 24 February 2026, according to a source described in TechCrunch's 27 February report, a blocking order went out under Section 69A of the Information Technology Act, 2000, which allows the government to direct intermediaries to block access to online information. Users on JioFiber were among the first to report trouble; the problem then showed up on Airtel and ACT Fibernet as well. TechCrunch wrote that the main marketing site could still load for some people while developer infrastructure on supabase.co did not.

Supabase first described a DNS problem (ISP resolvers not returning the right answers) and suggested alternate public DNS or a VPN as a workaround. Those workarounds help a developer at a laptop. They are a poor answer for every end user of a production app.

AIM's 2 March piece captured the practical damage: dashboards, APIs and live apps that depended on the blocked domain stopped working for people on affected networks. India was described there as a large and growing Supabase market.

By 4 March 2026, Supabase said on its status page that access to supabase.co had been fully restored for users across India, and thanked MeitY for engagement. AIM published a matching restoration story the same day. DNS caches can lag, which is why Supabase asked people to flush DNS and wait up to 24 hours for provider-side changes.

If you still cannot reach Supabase from a particular ISP today, treat that as a current network issue and check status.supabase.com plus your resolver — do not assume the February order is still in force nationwide.

What this was, and what it was not

  • It was an access disruption at the ISP / DNS layer, tied in contemporaneous reporting to a Section 69A order.
  • It was not a court judgment that "Supabase is illegal in India." No public official reason was released in the stories cited above.
  • It was not a failure of Supabase's own servers. The company said infrastructure stayed up and that projects remained reachable from outside India.
  • Restoration does not mean a similar order cannot be issued again, against Supabase or against anyone else.

Practical options if you need resilience

None of these is a guarantee. They are standard ways teams reduce single-domain risk.

1. Custom domains and proxies. During the incident, Supabase told some customers that a custom domain, with DNS pointed at an alternative resolver and proxying enabled, might restore connectivity. On WoWSQL, custom domains are a Scale plan feature ($99/month, pricing). A custom domain only helps if the blocked name is the vendor hostname, not yours. If the order lists your domain too, it does not help.

2. Keep a way to export and move. Standard Postgres (pg_dump) and a documented schema make a change of host possible. A weekend spent on a documented restore drill is worth more than a logo change.

3. Self-host or multi-region thinking. Self-hosting Supabase, Appwrite or WoWSQL on infrastructure you control changes which domain your app calls. It also makes you the person who patches and backs it up.

4. An Indian company, and an India region. WoWSQL is incorporated in India and offers Mumbai ap-south-1. That can help with contracts, DPDP conversations and latency. It does not exempt a hostname from a future blocking order. See Best backend as a service in India, Indian Supabase alternative, and Indian startup backend stack 2026.

5. Do not tell your users to "just use a VPN." That is an emergency workaround for developers, not a product strategy.

FAQ

Is Supabase banned in India?

Not as of the 4 March 2026 restoration reported by Supabase and AIM. It was disrupted from about 24 February 2026 under a Section 69A order, with uneven ISP behaviour. Check current access and the Supabase status page rather than repeating old headlines.

Why was supabase.co blocked?

The government did not publish a detailed public explanation in the TechCrunch and AIM reporting from the time. Section 69A is the legal provision those articles cite. Treat any more specific "reason" you see on social media as unverified unless it comes from an official release.

What if Supabase is not working on Jio or Airtel today?

First check status.supabase.com, your DNS resolver, and whether the failure is the dashboard, a project URL, or both. A local ISP issue is possible. It is not automatically the same event as February 2026.

Does using an Indian BaaS prevent blocking?

No. An Indian legal entity and a Mumbai region do not make a product unblockable. They may help with support, contracts and data location. For WoWSQL, Scale's custom domains are one extra control, not a shield.

Should I migrate off Supabase because of 2026?

Only if you have a broader reason (data model, price, support, or a written resilience requirement). Many teams stayed after restoration. If you do want an Indian Postgres BaaS with a Mumbai region, you can try WoWSQL and keep a migration plan either way.

Create a free WoWSQL project · Pricing · Docs