Users Experiencing Network Connectivity Problems (India Region)

Update timeline

1. investigating Feb 24, 2026, 02:46 PM UTC

   We have reports of customers having difficulties connecting to Supabase from locations accessing AP-south-1, including a number of reports from India. We are actively investigating the issue.

2. identified Feb 24, 2026, 03:13 PM UTC

   A DNS resolution issue is affecting customers in AP-South-1 and AP-Southeast-2. Certain ISP DNS servers appear to be unavailable, preventing connections to Supabase endpoints. Some users reported that switching to Cloudflare DNS (1.1.1.1) may restore connectivity. We advise affected customers to also report the issue to their ISP. Supabase infrastructure remains fully operational.

3. identified Feb 24, 2026, 03:42 PM UTC

   We continue to work with customers to address their connectivity issues. We are also contacting the relevant network providers to work with them to resolve the issue.

4. identified Feb 24, 2026, 04:00 PM UTC

   We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation is currently focused on a potential ISP-level block affecting users within India.

5. identified Feb 24, 2026, 04:08 PM UTC

   We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation is currently focused on an ISP-level block affecting users within India. We advise affected customers to also report the issue to their ISP. Supabase infrastructure remains fully operational. The best workaround we have currently is for affected users to use an alternative DNS providers such as: Cloudflare: https://1.1.1.1 Google https://developers.google.com/speed/public-dns Quad9: https://quad9.net/

6. identified Feb 24, 2026, 04:39 PM UTC

   We are currently aware of an issue affecting reachability of Supabase projects for a subset of users based in India. Supabase infrastructure remains fully operational. We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation has confirmed that a service provider in the region is not serving the correct DNS responses for Supabase projects from their internal DNS resolvers. We are following up through all available channels to work with the ISP to resolve this issue. We also advise affected customers to also report the issue to their ISP. The best workaround we have currently is for affected users to use an alternative DNS providers such as: Cloudflare: https://1.1.1.1 Google https://developers.google.com/speed/public-dns Quad9: https://quad9.net/ Alternatively users can use a VPN to avoid this issue We will post a further update once the ISP has confirmed that the issue is resolved or additional information becomes available.

7. identified Feb 25, 2026, 06:27 PM UTC

   We continue to follow up through all available channels to work with the ISP to resolve this issue. We advise affected customers to also report the issue to their ISP and to use an alternative DNS provider as a workaround. We will post an updated once the ISP has confirmed that the issue is resolved or additional information becomes available.

8. identified Feb 26, 2026, 02:56 PM UTC

   We have received some reports that other ISPs in India may be impacted by access limitations. We continue to follow up through all available channels to resolve this issue. We have engaged multiple teams at Supabase communicating with multiple entities in India in an effort to do all we can to resolve the access issues our users in India are experiencing. We advise affected customers to continue to report the issue to their ISP and to use an alternative DNS provider or a VPN as a workaround in the interim. We will post an update once the issue is resolved or additional information becomes available.

9. identified Feb 26, 2026, 11:36 PM UTC

   Affected customers who are using the Custom Domain feature may be able to restore connectivity by switching their Custom Domain's DNS to an alternative DNS and enabling proxying. We advise affected customers to continue to report the issue to their ISP.

10. identified Feb 27, 2026, 05:39 PM UTC

    We understand many users in India continue to be blocked from accessing Supabase. We acknowledge the difficulties this is causing for our users there. Supabase continues to follow up through all available channels to resolve this issue. We continue to advise affected customers to use an alternative DNS provider or a VPN as a workaround in the interim. For some customers, custom domains may also be a viable solution. If you have any questions regarding these options, please contact Supabase support. We will post an update once the issue is resolved or additional information becomes available.

11. identified Feb 28, 2026, 04:02 PM UTC

    We acknowledge the ongoing impact this issue is having on our users in India. We have made important progress in our contact with the relevant authorities and continue to actively work towards a resolution. We continue to advise affected customers to use an alternative DNS provider or a VPN as a workaround in the interim. For some customers, custom domains may also be a viable solution. If you have any questions regarding these options, please contact Supabase support. We will post an update once the issue is resolved or additional information becomes available.

12. identified Mar 02, 2026, 02:22 PM UTC

    We continue to work closely with the relevant authorities to address the connectivity issues impacting some users in India. Our discussions are progressing, and we’re seeing constructive engagement as we work towards a resolution. While we don’t have a confirmed timeline to share just yet, this is top priority for our team. We will post an update once the issue is resolved or additional information becomes available.

13. identified Mar 03, 2026, 02:42 PM UTC

    We have continuing contact with the relevant authorities to address the connectivity issues impacting some users in India. Decision makers are involved on all sides. While we don’t have a confirmed timeline to share just yet, this is top priority for our team and leadership. We will post an update once the issue is resolved or additional information becomes available.

14. monitoring Mar 03, 2026, 07:12 PM UTC

    We are pleased to inform our community that access to Supabase’s website supabase.co has now been fully restored for all users across India. We sincerely thank the Ministry of Electronics and Information Technology (MeitY) for their prompt action and constructive engagement in resolving this matter. Access to our services has been fully restored, and we deeply appreciate the continued patience and support of builders, developers, and businesses across India. If you were previously affected, you should now be able to access your Supabase projects without any interruptions. Please clear your DNS cache or restart your network connection if you still encounter issues. Additionally, please allow up to 24 hours for the provider-side changes to propagate. If you continue to see access problems after 24 hours, let us know! Thank you for your patience while we worked through this incident.

15. resolved Mar 04, 2026, 09:02 PM UTC

    We are pleased to inform our community that access to Supabase’s website supabase.co has now been fully restored for all users across India. We sincerely thank the Ministry of Electronics and Information Technology (MeitY) for their prompt action and constructive engagement in resolving this matter. Access to our services has been fully restored, and we deeply appreciate the continued patience and support of builders, developers, and businesses across India.

16. postmortem Mar 31, 2026, 10:05 PM UTC

    Read more about incident and similar incidents in our new blog post about [Navigating Regional Network Blocks](https://supabase.com/blog/navigating-regional-network-blocks).