Millions of Indian developers and users woke up on February 24 to broken apps — not because of a bug in their code, but because Reliance Jio, India's largest telecom network with roughly 500 million subscribers, appears to have blocked access to Supabase's backend infrastructure.
Supabase, a popular open-source backend platform (think: the database, authentication, and API layer that powers thousands of apps), confirmed the disruption on its status page. Its investigation found that a service provider in India is not serving correct DNS responses for Supabase projects from their internal DNS resolvers.
In plain terms: when Jio users try to reach any app built on Supabase, Jio's internal "phonebook" — the DNS system — is handing back the wrong address, making the service unreachable.
Developers digging into the issue found that Jio appears to be DNS-poisoning *.supabase.co domains, resolving them to a Jio-owned sinkhole IP instead of the actual AWS IPs, resulting in connection timeouts for all API calls, Edge Functions, and authentication endpoints.
GitHub The Supabase marketing website loads fine — it's a different domain — but every live app running on the platform breaks silently for Jio users.
 |
| Supabase Statement |
In October 2025, Medium.com faced a nearly identical ISP-level block on Jio and Airtel networks, and in August 2025, state-owned BSNL blocked access to several legitimate platforms, including Dailymotion and Telegram shortened links, citing no clear public reason.
The pattern is raising uncomfortable questions about transparency, net neutrality, and whether India's telecom giants are acting within regulatory bounds set by the Telecom Regulatory Authority of India (TRAI).
If your app or workflow is affected, here's what to do right now:
Switch your DNS provider away from Jio's default. Cloudflare's 1.1.1.1, Google's Public DNS (8.8.8.8), or Quad9 (9.9.9.9) may restore access. If DNS switching alone doesn't work, some developers suspect Jio may also be using deep packet inspection alongside DNS poisoning — a VPN such as Cloudflare WARP is the most reliable workaround. Report the issue to Jio directly as well; Supabase says user reports help escalate resolution pressure on the ISP's end.
For developers building apps targeting Indian users, the bigger lesson is structural: routing API calls directly through third-party vendor URLs like *.supabase.co leaves zero room to maneuver when an ISP decides — for whatever reason — to cut off access. Proxying backend traffic through your own custom domain gives you the control to reroute on the fly.
Supabase says it will post an update once the issue is resolved. Given India's track record with unexplained ISP-level blocks, don't hold your breath waiting for Jio to explain itself.