Supabase project hostname returns NXDOMAIN although project is Healthy

[tarunkumarc1201-commits]

Hello Supabase community,

I have a Supabase project that shows Healthy in the dashboard, but the project hostname is not resolving.

Project ID: tzfqmhzbqxruyrzlqsz
Region: ap-southeast-1
Project URL: https://tzfqmhzbqxruyrzlqsz.supabase.co

When I open the project URL in the browser, I get:
DNS_PROBE_FINISHED_NXDOMAIN

I also tested with Windows DNS:
nslookup tzfqmhzbqxruyrzlqsz.supabase.co
Result: Non-existent domain

I tested with Cloudflare DNS (1.1.1.1) as well:
Result: Non-existent domain

The Supabase dashboard shows the project as Healthy, and the Data API is enabled.

Could someone please advise whether this looks like a DNS/API Gateway provisioning issue for the project hostname?

I have already submitted a Supabase support request.
Ticket ID: SU-466890

Thank you.

[ssmurfgg04-gif]

NXDOMAIN on your own resolver and on 1.1.1.1 means the record is gone on the Supabase side, it is not a local cache thing. From what I have seen that comes down to a few cases:

1. The project was paused for inactivity on a free plan. Restore brings DNS back within minutes.
2. The project entered the deletion grace period, then the hostname is pulled even while the dashboard still renders project info.
3. A gateway reprovision on Supabase's end where the DNS record for your ref did not come back. This one matches your situation best since the dashboard says Healthy.

Worth checking while you wait on the ticket: the org billing page for a failed payment or pause flag, and whether a custom domain was ever attached to the project, removing one can leave the hosted hostname in a weird state.

If the ticket has not moved after a day, reply to it with the exact NXDOMAIN output and ask specifically whether the API gateway DNS record still exists for ref tzfqmhzbqxruyrzlqsz. They can re-register it on their end pretty quickly once an engineer looks.

[russfranky]

NXDOMAIN from both your resolver and 1.1.1.1 means the record is gone at the authoritative end. Not propagation. Not your cache.

Check two things. Project paused? Free plans pause after inactivity and the hostname stops resolving. Billing clean? No failed payment or pause flag.

If both check out, the gateway DNS record for your project ref was never re-registered on Supabase's side. That matches your symptom: dashboard says Healthy, hostname dead.

Reply to ticket SU-466890 with the nslookup output and your project ref. Ask them to confirm the gateway DNS record still exists for that ref. They can re-register it.

One check while you wait: does another project's hostname in the same org resolve? Yes means project-specific. No means org-wide.