Supabase project hostname does not resolve in Canada Central

[jmcdona5]

Hi everyone. I'm setting up a Trip Planner app with Supabase and have run into a connection problem.

Project reference: krxeroksfwyrizrgygg
Region: Canada Central
Project URL: https://krxeroksfwyrizrgygg.supabase.co

The project dashboard shows the primary database running, and the Data API is enabled. However, Safari says the server cannot be found when I open the project URL or /auth/v1/health.

I've tested on my Mac and on my iPhone using cellular data with Wi-Fi turned off. The main Supabase website opens normally.

I've also submitted support ticket SU-502247.

Could someone help me determine whether this is a project DNS/hostname issue or another configuration problem? I'd prefer to fix the existing project rather than recreate it.

Thanks!

[lisarconnect-admin]

Could you copy the Project URL directly from the dashboard, then share the DNS result for that exact hostname from your Mac—an address, NXDOMAIN, SERVFAIL, or a timeout—along with the UTC test time? The Safari message alone does not identify that layer. You have already tested a second network, so attaching the exact hostname and timestamped DNS result to SU-502247 would give support a more useful comparison than another browser retry. Please omit API keys, passwords, and connection strings.

AI-assisted reply; I work on Lisar Connect.

[Bri4real]

Hi! Since you've already tested both Wi-Fi and cellular, I'd focus on DNS resolution before changing anything in your project.

Could you try these commands on your Mac?

dig krxeroksfwyrizrgygg.supabase.co
dig @1.1.1.1 krxeroksfwyrizrgygg.supabase.co

If both return NXDOMAIN, that would point more toward a hostname or DNS provisioning issue than a Safari problem.

If the hostname resolves correctly, the next step would be testing the HTTPS endpoint separately.

I'd include the DNS results and the exact UTC time in your existing support ticket. No need to recreate the project yet.

[0x496C6B696E]

Hey, since you're getting the same issue on both your Mac and iPhone using different networks, this sounds more like a DNS problem than something wrong with your app.

Also, the database showing as healthy in the dashboard doesn't necessarily mean the API hostname is working. They're separate things.

I'd start by checking whether the domain actually resolves through public DNS:

dig @1.1.1.1 krxeroksfwyrizrgygg.supabase.co A
dig @8.8.8.8 krxeroksfwyrizrgygg.supabase.co A

Might also be worth checking the AAAA records for IPv6.

If both return NXDOMAIN, double-check that the project URL matches the one in your Supabase dashboard and that the project hasn't been paused.

If everything looks correct there, it could be a DNS provisioning issue on Supabase's side.

If the domain does resolve, try:

curl -v https://krxeroksfwyrizrgygg.supabase.co/auth/v1/health

That should give you a better idea of whether it's a DNS, TLS, or API connectivity issue.

I wouldn't bother changing your database connection settings or trying the IPv4 pooler workaround for now. Those are more relevant to direct PostgreSQL connections, not the public API hostname.

Since you've already opened a support ticket (SU-502247), I'd send them the DNS lookup results as well. That should give them something concrete to investigate.

And I wouldn't recreate the project yet either. If the DNS records really are missing, that's something Supabase needs to look into.

Hope this helps! Let us know what the dig commands return.

[jmcdona5]

Thanks for the suggestions. I've now run the DNS and HTTPS tests.

dig @1.1.1.1 krxeroksfwyrizrgygg.supabase.co A returns NXDOMAIN.

dig @8.8.8.8 krxeroksfwyrizrgygg.supabase.co A returns NOERROR and 103.224.212.213.

curl -v https://krxeroksfwyrizrgygg.supabase.co/auth/v1/health fails with curl: (6) Could not resolve host.

I've also confirmed that the project URL shown in my Supabase dashboard matches the hostname above, and the project database appears healthy.

The results seem to indicate inconsistent DNS resolution. I've opened support ticket SU-502247 and will send these findings to Supabase Support as well.

Thanks again for your help!