Imagine pushing a critical update to your application, only to wake up to a flood of support tickets from users in India claiming your app is dead. Your server logs look fine, your status dashboard is all green, but for millions of people, your backend simply doesn’t exist. That is the frustrating reality facing thousands of developers this week as Supabase, the popular open-source alternative to Google’s Firebase, has been suddenly blocked across major Indian networks.
Starting around February 24, 2026, developers began noticing patchy access to their projects. By February 27, Supabase confirmed what many feared: this wasn’t a technical glitch or a server outage. It was a government-mandated block. If you are building on Supabase and have users in India, you are likely navigating a chaotic few days of timeouts and broken APIs.
Why is Supabase blocked in India?
The disruption stems from an order issued by India’s Ministry of Electronics and Information Technology (MeitY). According to Supabase’s own investigation, the block is being enforced by major Internet Service Providers (ISPs), including Reliance Jio, Airtel, and ACT Fibernet. These providers have implemented the block via a method known as DNS poisoning.
While the government rarely comments on specific blocking orders immediately, industry context suggests this is likely a case of “collateral damage.” Under Section 69A of India’s IT Act, authorities frequently order the blocking of specific URLs deemed illegal—often related to betting apps, predatory loan schemes, or phishing operations. Because Supabase is a backend-as-a-service (BaaS) platform, it hosts thousands of different projects. It is highly probable that one bad actor hosted an illegal app on the platform, and rather than blocking that specific sub-page, the ISPs or the government order targeted the main supabase.co domain.
This isn’t the first time we’ve seen this happen. Platforms like Telegram, Medium, and SourceForge have faced similar temporary bans in India, where the “sledgehammer” approach of blocking a root domain is used instead of the “scalpel” approach of blocking a specific URL.
Is Supabase down for everyone?
Technically, Supabase is up and running perfectly. The servers are humming along. The problem is strictly regarding access for users on specific Indian networks. Because the block is implemented via DNS poisoning, it essentially means the ISPs’ phone books are lying to your computer. When a user’s device asks, “Where is supabase.co?”, the ISP returns an incorrect address or no address at all, leading to API timeouts.
The block specifically affects the supabase.co domain, which is crucial because that is where the APIs live. Interestingly, the marketing website might still load for some users if it is hosted on a different domain or cached differently, but the actual functionality of live applications—fetching user data, authentication, database calls—is hitting a brick wall.
How can developers bypass the block?
If you are a developer trying to work on your project, or if you need to advise technical users on a workaround, there is good news: the block is relatively easy to bypass because it is DNS-based, not IP-based.
You can restore access by changing your DNS settings to a public provider that ignores the local ISP’s censorship filters. The two most popular options are:
Cloudflare: Set your DNS to 1.1.1.1
Google: Set your DNS to 8.8.8.8
Alternatively, using a VPN will route your traffic outside of the affected Indian networks, allowing you to connect to Supabase without issues. However, these are developer-side fixes. You obviously cannot ask every end-user of your consumer app to change their network settings, which is why this incident is causing such a scramble for startups.
What is Supabase doing about it?
Supabase is treating this as a critical incident. The company’s CEO, Paul Copplestone, has publicly addressed the situation, stating that “millions of users in India are currently unable to access our platform due to these blocks.” The company has formally reached out to Union Minister Ashwini Vaishnaw to resolve the matter.
The team is actively investigating the scope of the block and communicating with the relevant authorities to clarify that they are a neutral infrastructure provider, not a publisher of illegal content. Given Supabase’s massive footprint in India—driven by a huge population of students and early-stage AI startups—the pressure is high to get this resolved quickly.
What This Really Means
While access will likely be restored once the specific offending URL is isolated, this incident highlights a massive “platform risk” for the Indian tech ecosystem. India is currently pushing hard to be a global AI hub, and Supabase has become a critical tool for that wave, especially with its recent expansion into vector storage and AI capabilities. When fundamental infrastructure can be severed without notice due to the actions of a single bad tenant, it spooks serious businesses. For Indian startups, this serves as a harsh reminder: relying on foreign-hosted domains that haven’t established a local legal entity or direct line to MeitY creates a single point of failure that no amount of code can fix.
![Illustration related to Supabase Blocked in India: Bypass DNS Poisoning [Fix]](https://bytewire.press/wp-content/uploads/bytewire-images/2026/02/supabase-blocked-india-dns-fix-8d3a17aaa0.webp)
![Diagram related to Supabase Blocked in India: Bypass DNS Poisoning [Fix]](https://bytewire.press/wp-content/uploads/bytewire-images/2026/02/supabase-blocked-india-dns-fix-4978f229b4.webp)
