Following up with more context. I’ve found several other reports on this board describing the exact same fingerprint (control plane shows a correctly aliased, verified, Ready deployment; edge returns X-Vercel-Error: NOT_FOUND regardless):
- Ready/Promoted production deployment returns NOT_FOUND on all hostnames
- Custom domain 404 NOT_FOUND despite valid config and healthy deployment - CLI evidence
- [Bug] Custom domain returns 404 NOT_FOUND — edge routing entry missing
That last thread has some really solid diagnostic back-and-forth with @ryux1, who correctly identified it as a control-plane/edge-routing desync rather than anything client-side. Tagging you here in case you’re able to look at this one too, the pattern looks identical: alias/verify state is correct, deployment is Ready, but the edge won’t route to it.
To match the evidence format from that thread:
auto
vercel alias ls (relevant lines):
eopinion-jrt8pbdia-chris-h-projects.vercel.app eopinion.org (current)
eopinion-jrt8pbdia-chris-h-projects.vercel.app www.eopinion.org (current)
Expected deployment: dpl_8VCqzkQWGsSF4HRsLTDBNjXR5ZNK (readyState: READY, target: production)
Failing request:
curl -I https://eopinion.org/
HTTP/2 404
x-vercel-error: NOT_FOUND
x-vercel-id: iad1:iad1::kf2xn-1785654066067-ab55ffa034d5
Timestamp: 2026-08-02T07:01:06Z
I’ve stopped making further alias or domain changes to keep the state stable while this is looked at. Happy to provide anything else that’s useful, this is still down.