Project API hostname returns DNS_PROBE_FINISHED_NXDOMAIN

[jurgenhila3]

Summary:
My Supabase project API hostname returns DNS_PROBE_FINISHED_NXDOMAIN and cannot be resolved publicly.

Impact:
My application cannot connect to Supabase Auth or the Data API. This has been blocking development for more than 80 hours.

Project:
Name: doctor-display-os-2
Project ref: rqekimzgituxajiywftd
Region: West EU (Ireland)

Expected behavior:
https://rqekimzgituxajiywftd.supabase.co should resolve and expose the project's API/Auth endpoints.

Actual behavior:
Opening the project URL directly in Google Chrome returns:

DNS_PROBE_FINISHED_NXDOMAIN

The Supabase Dashboard shows the project as healthy, and the SQL Editor works normally.

Troubleshooting completed:

• Tested the project URL directly in Chrome.
• Confirmed DNS_PROBE_FINISHED_NXDOMAIN.
• Tested the application from localhost.
• Updated the application to use the correct project URL and publishable key.
• A previous Supabase project also experienced the same DNS resolution problem.

Request:
Could someone from the Supabase community/team help determine why the public API hostname is not resolving and whether the project's DNS/API hostname needs to be provisioned or repaired?

I can provide screenshots and additional diagnostics if needed.

[GaryAustin1]

You need to contact support thru the dashboard. No one from Github can touch or see your project internals.
I can confirm the url you provide does not work from Texas.

[chukwuchikelu]

I'm experiencing the exact same issue.

Project ref: weeyptukyrezdynwldf

Project URL: https://weeyptukyrezdynwldf.supabase.co

My Supabase dashboard shows the project as Healthy, but the project hostname returns NXDOMAIN.

nslookup weeyptukyrezdynwldf.supabase.co 8.8.8.8 → Non-existent domain

nslookup weeyptukyrezdynwldf.supabase.co 1.1.1.1 → Non-existent domain

google.com resolves normally through 8.8.8.8.

My production Next.js application consequently gets Failed to fetch when calling /auth/v1/token?grant_type=password.

I also tested the Supabase Auth health endpoint with curl and the hostname cannot be resolved.

This is an existing project containing my database, Auth users and application data, so I need the existing project repaired rather than creating a new project.

Could someone confirm whether this is a Supabase DNS/API hostname provisioning issue?