Project: parentchime-website (team: ridhisardas-projects, Hobby plan). Custom domains parentchime.com and www.parentchime.com show “Valid Configuration” in the dashboard. This started right after a WHOIS ownership verification process via our registrar (Namecheap), which they’ve confirmed is complete.
What I’ve ruled out via Vercel CLI:
1. Stale/duplicate alias records - vercel alias ls --limit 100 shows exactly one alias entry each for parentchime.com and www.parentchime.com, no duplicates.
2. Broken/corrupted deployment - ran vercel redeploy to create a fresh deployment (parentchime-website-4raq5hv8s-ridhisardas-projects.vercel.app) and re-aliased both domains to it via vercel alias set. Curling that new deployment’s own unique URL directly returns a normal, healthy 302 redirect to vercel.com/sso-api (expected Deployment Protection behavior) - so the deployment itself is registered correctly at the edge.
3. Wrong alias target - confirmed via CLI output that both domains point to this exact healthy deployment.
Yet curling the custom domains directly still returns platform 404: NOT_FOUND:
curl -I https://parentchime.com
curl -I https://www.parentchime.com
Both: HTTP/2 404, x-vercel-error: NOT_FOUND, IDs bom1::nrtv8-1785480187574-065f0071ef0a and bom1::n66t4-1785480187762-ff4096449843 (2026-07-31T06:43:07Z).
Since the exact same deployment serves correctly on its own hashed URL but not on the aliased custom domains, this isolates the fault to the edge routing table entry for these two specific hostnames - not the deployment, not the alias record, not the domain-to-project link. This looks identical to the pattern reported in several other recent threads here (edge routing desync after domain/alias state changes). Could a Vercel team member inspect or reset the edge routing entry for these hostnames specifically? Happy to provide any additional diagnostics.