Supabase India: Complete Timeline of the Block (Feb 2026)
A complete timeline of the Supabase block in India - from the first reports to the global news coverage. Here is every key event, day by day.
The timeline
The Supabase block in India did not happen with a single announcement. It unfolded over five days, starting with a quiet government order and escalating into a full-blown crisis for thousands of Indian developers. Here is how it played out.
Monday, February 24
The order drops
A government order is issued under Section 69A of the Information Technology Act. The order directs Indian ISPs to block access to all subdomains under *.supabase.co. As with all 69A orders, the directive is confidential. No public announcement is made.
ISPs begin DNS-blocking. Jio, Airtel, and ACT Fibernet start poisoning DNS responses for *.supabase.co, returning sinkhole IP addresses instead of Supabase's real servers. Apps that depend on Supabase begin failing silently. Users see ERR_CONNECTION_TIMED_OUT errors without any explanation.
Scattered reports appear on developer Slack channels and Discord servers. Most developers initially assume the issue is on Supabase's end or a local network problem. Few suspect an ISP-level block at this point.
Tuesday, February 25
Reports flood social media
Developer reports flood social media. X (formerly Twitter) sees dozens of posts from Indian developers reporting broken apps. The Supabase community forums light up with threads from India-based developers asking why their projects have stopped working.
Pattern recognition kicks in. Developers start comparing notes across ISPs. When reports come in from Jio, Airtel, and ACT Fibernet users simultaneously, the community begins to suspect a coordinated DNS block rather than a Supabase outage. Developers run nslookup and confirm sinkhole IPs.
Early workaround discussions begin. Some developers try switching to public DNS resolvers like 1.1.1.1 or 8.8.8.8. Results are inconsistent. The fix works for some ISPs but not others, likely due to Deep Packet Inspection (DPI) blocking at the SNI level.
Wednesday, February 26
Supabase responds
Supabase officially acknowledges the block. The Supabase team confirms on their community channels that Indian ISPs are blocking *.supabase.co and that they are investigating the situation.
Supabase posts on X tagging India's IT Minister Ashwini Vaishnaw, asking for clarification on the block. The post gains significant traction in the Indian developer community. Shortly after, the post is deleted. No official explanation is given for why it was removed.
Supabase recommends reverse proxying as a workaround. Developers begin experimenting with Cloudflare Workers and Nginx reverse proxies to route traffic through unblocked domains.
Thursday, February 27
Global coverage
TechCrunch, MediaNama, and other outlets publish coverage. The story goes global. Articles detail the impact on Indian developers and the broader implications of blocking developer infrastructure.
Key data points emerge: India represents approximately 9% of Supabase's global traffic, making it the 4th largest market for the platform. Supabase's valuation is reported at roughly $5 billion. The block affects thousands of production applications serving millions of Indian end users.
Developer advocacy organizations including the Internet Freedom Foundation (IFF) begin tracking the block. Comparisons are drawn to previous blocks on GitHub, Medium, Pastebin, and other developer tools.
Friday, February 28
Block persists, workarounds solidify
The block remains fully active. No sign of the government order being reversed. ISPs continue to enforce DNS poisoning on all *.supabase.co subdomains.
Community workarounds mature. Reverse proxy solutions become the accepted approach. Developers share Cloudflare Worker configurations, DNS switching guides, and VPN recommendations. Managed proxy services like JioBase emerge to provide ready-to-use solutions.
Indian startup founders voice concerns about the reliability of cloud infrastructure in India. The block has prompted discussions about building resilient architecture that does not depend on any single domain remaining accessible.
What is blocked vs what is not
The block is targeted at a specific domain. Understanding the distinction is important for diagnosing and fixing the problem.
*.supabase.co
All project API endpoints. This includes REST API (PostgREST), Authentication, Storage, Edge Functions, GraphQL, and Realtime WebSockets. Every production app that calls Supabase is affected.
supabase.com
The marketing website, documentation, and dashboard. You can still log in to Supabase, view your projects, manage settings, and read docs. You just cannot reach the API from within India.
This creates a confusing situation. Developers can access the Supabase dashboard and see their project running normally. But their production app cannot reach the API. If you are not aware of the block, this looks like a bug in your code or a Supabase outage, when it is neither.
ISPs enforcing the block
The block has been confirmed across the largest Indian ISPs. Together, these providers cover the vast majority of internet users in the country.
Reliance Jio
Approximately 500 million subscribers. India's largest ISP. Block confirmed on both 4G/5G mobile networks and JioFiber broadband connections.
Bharti Airtel
Over 380 million subscribers. Block confirmed on Airtel broadband and mobile data. Both prepaid and postpaid connections are affected.
ACT Fibernet
Regional broadband provider popular among developers. Block confirmed across multiple cities including Bangalore, Hyderabad, and Chennai.
BSNL
Government-owned ISP. Already blocking Firebase since August 2025. Supabase block status on BSNL is being confirmed. BSNL users may face blocks on both Firebase and Supabase simultaneously.
Reports from Vi (Vodafone Idea) and smaller regional ISPs are still emerging. If you are experiencing Supabase connectivity issues on any Indian ISP, you can run a quick diagnostic test to confirm whether it is an ISP block.
Why this matters
The Supabase block is not just a technical inconvenience. It has significant implications for India's developer ecosystem and the startups built on Supabase.
India is Supabase's 4th largest market worldwide. That translates to tens of thousands of active projects and an unknown number of production applications serving Indian end users.
Every app that uses Supabase for its backend broke overnight. SaaS products, mobile apps, internal tools, MVPs, hackathon projects, student applications, and freelance client work all went dark on Indian networks.
Early-stage startups that chose Supabase as their backend found their products completely non-functional for Indian users. For companies with paying customers, every hour of downtime means lost revenue and damaged trust. Some founders discovered the issue only when customers reported the app was not working.
The block raises a fundamental question: can Indian developers rely on international cloud services? If Supabase can be blocked today, other platforms could follow. This uncertainty makes it harder for developers to commit to any single backend provider.
How to verify the block on your network
If you suspect your network is affected, run this quick DNS lookup from your terminal:
If the returned IP address starts with 49.44.x.x instead of a legitimate Supabase server IP, your ISP is DNS-poisoning the domain. For a more thorough diagnostic, check our complete ISP block testing guide.
You can also compare results by querying a public DNS directly:
The fix: reverse proxy through Cloudflare
The most reliable solution is to route your Supabase traffic through a domain that is not blocked. A reverse proxy sits between your app and Supabase, forwarding requests through an unblocked domain on Cloudflare's global edge network.
JioBase is a managed reverse proxy that does this for you. Instead of setting up your own Cloudflare Worker, configuring DNS, handling CORS, and managing WebSocket upgrades, you get a ready-to-use proxy endpoint.
The setup takes less than five minutes:
Sign up at JioBase
Create a free account at jiobase.com/register. No credit card required.
Create a proxy app
Enter your Supabase project URL and choose a slug. You will get a proxy URL like myapp.jiobase.com.
Swap the URL in your code
Replace yourproject.supabase.co with your JioBase proxy URL. Your API keys stay the same.
For a detailed walkthrough with code examples, read our complete fix guide. If you prefer to self-host, use our Worker Generator to create a ready-to-deploy Cloudflare Worker.
Frequently Asked Questions
When exactly did the Supabase block start?
Is Supabase still blocked in India as of today?
Why did Supabase delete the post tagging India's IT Minister?
Do not wait for the block to be lifted
History shows that ISP blocks in India can persist for months or years. Get your Supabase-powered app working again in under five minutes with JioBase.
Free tier includes 1 proxy app and 50,000 requests/month. No credit card required.
Suggested reading
More guides on Supabase, DNS blocks, and building resilient apps in India.
Supabase Blocked in India: What Happened and How to Fix It
Indian ISPs are DNS-blocking *.supabase.co. Here is everything you need to know and how to fix it.
Firebase AND Supabase Blocked in India: The Double Backend Crisis
Firebase blocked on BSNL. Supabase blocked on Jio, Airtel, and ACT. Here is what happened.
Why Is Supabase Banned in India? Section 69A Explained
Understanding Section 69A of the IT Act and how blocking orders work.