Supabase down on JIO ISP
Problem
Bug report - [x] I confirm this is a bug with Supabase, not with my own application. - [x] I confirm I have searched the Docs, GitHub Discussions, and Discord. Describe the bug All Supabase API requests (`.supabase.co`) are completely inaccessible for users on Jio (Reliance) — The ISP appears to be performing DNS poisoning on `.supabase.co` domains, resolving them to a Jio-owned sinkhole IP (`49.44.79.236`) instead of the actual AWS IPs. This results in `ERR_CONNECTION_TIMED_OUT` for all API calls, Edge Functions, and Auth endpoints. This is not a project-specific issue — all Supabase projects are affected. The Supabase marketing site (`supabase.com`) loads fine (different domain), but `supabase.co` (used for all API/project endpoints) is fully blocked. This affects a massive portion of Indian internet users and could silently break any production app using Supabase for users on Jio broadband or Jio mobile data. To Reproduce 1. Connect to any Jio network in India (broadband or mobile data) 2. Open any app that makes API calls to `.supabase.co` (e.g., a project using Supabase Auth, REST API, or Edge Functions) 3. API requests fail with `ERR_CONNECTION_TIMED_OUT` 4. The same app works perfectly on other ISPs (Airtel, Vi, BSNL) or through a VPN DNS resolution proof: [code block] The resolved IP `49.44.79.236` belongs to Jio/Reliance, not to AWS (where Supabase is hosted). This confirms DNS-level blocking/poisoning. curl output: [code block] Both `supabase.co` and p
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Mitigate DNS Poisoning for Supabase on Jio ISP
The issue arises from Jio ISP performing DNS poisoning on the `.supabase.co` domain, redirecting requests to a Jio-owned sinkhole IP (`49.44.79.236`) instead of the actual AWS IPs where Supabase is hosted. This results in a failure to connect to Supabase services for users on Jio networks.
Awaiting Verification
Be the first to verify this fix
- 1
Contact Jio Support
Reach out to Jio customer support to report the DNS poisoning issue. Provide them with evidence of the incorrect DNS resolution and request an investigation into the matter.
- 2
Implement DNS Workaround
Instruct users on Jio networks to change their DNS settings to a public DNS service (e.g., Google DNS `8.8.8.8` and `8.8.4.4` or Cloudflare DNS `1.1.1.1`). This can be done on their device or router settings.
bashecho 'nameserver 8.8.8.8 nameserver 8.8.4.4' | sudo tee /etc/resolv.conf - 3
Use a VPN as a Temporary Fix
Advise users to connect to a VPN service to bypass the DNS poisoning issue. This will route their traffic through a different DNS resolver, allowing access to Supabase services.
- 4
Monitor API Access
Set up monitoring on your application to track API access attempts and failures from Jio users. This will help gauge the impact of the issue and the effectiveness of the implemented workarounds.
javascriptconst apiMonitor = (response) => { if (response.status !== 200) { console.error('API access failed:', response); } }; - 5
Update Documentation
Update your application's documentation to include information about the DNS issue with Jio and the recommended workarounds for users experiencing connectivity problems.
Validation
Confirm that users on Jio networks can successfully make API calls to Supabase after implementing the DNS changes or using a VPN. Monitor the API access logs for successful connections.
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep