Access Issues From Some Providers in Brazil

Updates timeline

1. Investigating May 14, 03:34 PM UTC

   We are investigating reports of some access issues to Supabase IP addresses from a network provider in Brazil.

2. Investigating May 14, 03:54 PM UTC

   We have isolated the issue to a specific Internet provider in Brazil and are working to contact that provider to resolve the issue. We will update the statuspage when we have more information to share.

3. Investigating May 14, 04:37 PM UTC

   We have made contact with the ISP in Brazil and are working through their support process for this issue. Customers may be able to bypass the problem by using a VPN or alternative network while we work towards resolution.

4. Identified May 14, 10:23 PM UTC

   We are continuing to contact the ISP in Brazil to work through this issue. Customers may be able to bypass this issue by using a VPN or alternative network while we work towards resolution. Thank you for your patience. We will provide an update when we have more information to share.

5. Identified May 19, 10:30 PM UTC

   We are continuing to contact the ISP in Brazil to work through this issue: however they have remained unresponsive to outreach. We are exploring other options to get in touch with them. Customers may be able to bypass this issue by using a VPN or alternative network while we work towards resolution. Thank you for your patience. We will provide an update when we have more information to share.

6. Identified Jun 3, 09:32 PM UTC

   We continue to work with the service provider to resolve the residual access issues. We have scheduled direct consultations with the provider to attempt to resolve the issue.

7. Identified Jun 9, 01:26 PM UTC

   We are engaged with senior networking team members at the impacted provider. They are actively investigating the domain name resolution issues we have reported. If you are continuing to experience .co name resolution issues in Brazil, please update your ticket or open a new ticket to let us know so we can add that information to the investigation.

8. Monitoring Jun 12, 02:42 PM UTC

   We continue to work with the relevant provider and have seen improvements. We are monitoring the progress that has been made to ensure it continues.

9. Monitoring Jun 15, 04:52 PM UTC

   The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal. We will monitor this for continued functionality.

10. Resolved Jun 16, 08:15 AM UTC

    The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal.