## 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.