DNS Resolution Failures for TLD .co users

Updates timeline

1. Identified Jun 8, 03:39 AM UTC

   We are investigating reports of DNS resolution failures affecting a subset of customers connecting to Supabase project endpoints. This appears to be related to a third-party issue with .co TLD resolution impacting multiple DNS providers. Customers may be able to bypass this issue by using a VPN while we work towards resolution. We will update the statuspage when we have more information to share.

2. Monitoring Jun 8, 06:37 AM UTC

   The third-party has confirmed a fix has been implemented and we are validating the results with our impacted users.

3. Monitoring Jun 8, 12:38 PM UTC

   Our testing has observed that the issue is related to selected ISP resolvers to .co domains. The clients impacted are mainly located in us-east-1, us-east-2 region. We continue to review this issue for resolution with our third party network partner.

4. Monitoring Jun 8, 05:32 PM UTC

   We have opened a follow-up issue with our provider to address the continued problems a subset of our customers in the Americas are experiencing with top-level ".co" domain resolution. We will continue to pursue this issue until it is resolved and customers who have reported the issue are able to correctly resolve the domain name.

5. Monitoring Jun 10, 11:24 PM UTC

   Our upstream TLD provider believes they have identified the underlying issue, and we are continuing to coordinate with them to review their findings and potential remediation options. In parallel, we are investigating other factors that may be contributing to the ongoing resolution problems affecting a subset of customers. VPNs continue to provide a workaround for impacted end users while our investigation remains ongoing.

6. Monitoring Jun 12, 11:09 AM UTC

   Our upstream TLD provider is continuing to make changes to its network routing policies to address this issue. These changes are intended to improve regional traffic routing and reduce DNS resolution failures. We have already begun to see improvements as these changes take effect, but the issue has not yet been fully resolved. We are continuing to monitor the situation closely and work with the provider toward a complete resolution. We will provide another update as soon as more information becomes available.

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

8. Resolved Jun 16, 08:16 AM UTC

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