Skip to content
← Back to activity

Immutable solution version

Supabase unreachable on Jio ISP: DNS poisoning and the reverse proxy fix

Version 1Sign in to save

Complete solution

ISP-level DNS poisoning, verified by multiple reporters. The community-settled fix: put a reverse proxy in front of your Supabase API so clients talk to your own domain instead of *.supabase.co. One reporter confirmed this resolved it and recommends it for any production app, since ISP disruptions like this recur.

The problem

All Supabase API requests to .supabase.co are completely unreachable for users on Jio (Reliance) in India. The ISP appears to be DNS-poisoning .supabase.co, resolving it to a Jio-owned sinkhole IP instead of the real address. Every Supabase-backed app breaks for those users at once, with no error on Supabase's side.

The fix

ISP-level DNS poisoning, verified by multiple reporters. The community-settled fix: put a reverse proxy in front of your Supabase API so clients talk to your own domain instead of *.supabase.co. One reporter confirmed this resolved it and recommends it for any production app, since ISP disruptions like this recur. Note the caveat from the thread: Supabase custom domains alone are not foolproof here, one user was already on a custom domain and still got hit, so the reverse proxy on infrastructure you control is the reliable layer.

Evidence

In gh:supabase/supabase#43142 (https://github.com/supabase/supabase/issues/43142), the reporter ran into this: All Supabase API requests to .supabase.co are completely unreachable for users on Jio (Reliance) in India. The ISP appears to be DNS-poisoning .supabase.co, resolving it to a Jio-owned sinkhole IP instead of the real address. Every Supabase-backed app breaks for those users at once, with no error on Supabase's side. The verified resolution: ISP-level DNS poisoning, verified by multiple reporters. The community-settled fix: put a reverse proxy in front of your Supabase API so clients talk to your own domain instead of *.supabase.co. One reporter confirmed this resolved it and recommends it for any production app, since ISP disruptions like this recur. Note the caveat from the thread: Supabase custom domains alone are not foolproof here, one user was already on a custom domain and still got hit, so the reverse proxy on infrastructure you control is the reliable layer.

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_atvOvo8Msz3Fg3bXFWmFVQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Supabase unreachable on Jio ISP: DNS poisoning and the reverse proxy fix <span>— Vectle</span></a>