The Anatomy of the Block
In mid-February 2026, tech teams across India encountered unexpected database resolution timeouts when fetching data from endpoints like https://xyz.supabase.co. Major Indian telecom operators (Jio, Airtel, Vi) executed nationwide DNS filter blocks.
The directive was issued by the Ministry of Electronics and Information Technology (MeitY) under Section 69A of the Information Technology Act. The cause was not a flaw in Postgres, but rather abusive phishing content created by malicious free-tier users on sibling subdomains under the shared supabase.co domain.
Why Shared Subdomains Pose a Structural Risk
Global BaaS architectures host thousands of independent tenant backends on subdomains of a single root domain:
https://[project-id].supabase.co <-- Shared parent domain
When a government regulator orders ISPs to block a specific illegal URL on a shared domain, ISPs frequently apply wildcard blocklists on the entire root domain (*.supabase.co). As a result, legitimate production applications suffer collateral downtime through no fault of their own.
How IndBase Cloud Eliminates Domain Block Risks
1. Default Custom Domain Bindings
Every production project on IndBase Cloud (indbase.cloud) can be attached to your own company domain (e.g., api.yourcompany.com), completely isolating your DNS records from other platform users.
2. Bring Your Own Cloud (BYOC) Private VPC
For enterprise compliance, IndBase Cloud provisions isolated VPC clusters inside your private AWS/GCP account. Your database never touches shared public BaaS routing.
3. Automated Local Abuse Heuristics
Active local monitoring detects phishing and malicious tenant patterns prior to regulatory flags, maintaining a 100% clean platform reputation.