Fix “Supabase Down on Jio and JioFiber” by Hiding Supabase Behind Your Own Domain (Free-Tier Friendly)

If you are using supabase in your application and everything works on Airtel, Wi‑Fi and VPN — but Jio and JioFiber users in India keep saying “Supabase is down” or “Google login isn’t working”. In reality, Jio is silently blocking *.supabase.co from the browser. In this guide, we’ll show exactly how to put Supabase behind your own api.yourapp.com domain with a Cloudflare Worker proxy, switch Google auth to an ID‑token flow, and stop Jio’s ISP‑level block from breaking your Supabase app. The common pattern: every call that hit *.supabase.co from the browser either hung or failed with network errors. This guide explains: What’s actually broken (it’s not Supabase itself, it’s ISP‑level blocking of *.supabase.co). Who is affected (any app that calls Supabase directly from the browser, especially with Google OAuth). How we fixed it by putting Supabase behind our own domain via a Cloudflare Worker proxy and switching Google auth to an ID‑token flow so the browser never has to talk to supabas