Production project API host not resolving in DNS (NXDOMAIN) — dashboard Healthy, SQL Editor works

[marvinperson11-debug]

Project ref: jigyudurleoqtyhzfjbzq (us-west-2, Free plan). The project's public API host does not resolve in DNS (NXDOMAIN / ERR_NAME_NOT_RESOLVED) from multiple networks since approximately Oct 14–15. The dashboard shows the project Healthy, and queries via the SQL Editor succeed, so the database itself is running. I tried Restart and a full Pause/Restore — the public hostname still does not resolve. No matching incident on the status page. This is a production outage for a live application. Please re-provision the project's API gateway / DNS record.

[TheMysteriousGhost]

I checked this from outside just now, and it's not your network, and it's not only your project:

• jigyudurleoqtyhzfjbzq.supabase.co returns NXDOMAIN from Supabase's own authoritative DNS (the supabase.co zone on Cloudflare). So no resolver, cache or ISP is involved, and flushing DNS won't change anything.
• Same for the project in Supabase project hostname returns NXDOMAIN despite Healthy status #51815 (wzurrkuoldqrnskqzdnf, ap-southeast).
• And for the two reported on Oct 14: Supabase Project Healthy but API URL Returns NXDOMAIN #51752 (sqfytwcxfmnqueyfmvyz) and Project shows Healthy but Supabase API hostname returns DNS_PROBE_FINISHED_NXDOMAIN after resuming #51655 (svgiidgrfsuzbkzhvfmx). Both are still NXDOMAIN more than 30 hours later, so this isn't propagation delay and isn't fixing itself.
• status.supabase.com currently shows "All Systems Operational".

So it looks like a platform-side issue where the project's API hostname record isn't (re)created, with the dashboard showing Healthy because the database itself is fine. Several reports mention it started after a pause/resume or restore.

What I'd do:

1. Open a support ticket (Dashboard → Support) and link all four discussions (Project shows Healthy but Supabase API hostname returns DNS_PROBE_FINISHED_NXDOMAIN after resuming #51655, Supabase Project Healthy but API URL Returns NXDOMAIN #51752, Supabase project hostname returns NXDOMAIN despite Healthy status #51815 and this one). Four projects in different regions with the identical symptom is much more likely to get escalated than a single "my DNS doesn't resolve".
2. Meanwhile, note that db.<ref>.supabase.co is NXDOMAIN too (I checked yours), so the direct DB host won't help. The shared pooler is a regional hostname that does resolve (e.g. aws-0-us-west-2.pooler.supabase.com). If your backend can talk Postgres directly, the pooler connection string from Connect → Connection pooling (user postgres.<ref>) should still let server-side code reach the database while the API hostname is broken.

[kevinjosh10]

Hi @community! If your project dashboard and SQL Editor function properly but the API hostname returns NXDOMAIN:

---

Cause

The dashboard and SQL Editor connect internally via administrative socket bridges or internal management proxies, whereas public API endpoints rely on AWS Route53 records under *.supabase.co.

---

Immediate Workaround

Connect via the regional pooler hostname:

• Host: aws-0-us-west-2.pooler.supabase.com
• Port: 6543
• User: postgres.[project-ref]

This restores database access while Supabase engineers re-sync the Route53 zone record.