Deployment Details
- Deployment:
cambree-home-connect-5luw27102-cambreehomeconnects-projects.vercel.app - Domain:
cambreehomeconnect.com - x-vercel-id:
cle1::5f9h5-1774538994051-4596a8223850
Steps Taken
- CDN cache purge via CLI already attempted
cambree-home-connect-5luw27102-cambreehomeconnects-projects.vercel.appcambreehomeconnect.comcle1::5f9h5-1774538994051-4596a8223850Hi!
It doesn’t look like an edge cache issue. A Vercel NOT_FOUND response usually means there is no active deployment serving that domain, rather than stale cached content. Since the request is reaching Vercel (you have an x-vercel-id) and you already tried purging the CDN cache, it’s unlikely that caching is the problem.
This typically happens when there is no successful “Ready” deployment, the production alias is missing, or the domain is not pointing to an active deployment. In other words, Vercel isn’t finding anything to serve for that domain at the moment.
I’d recommend checking your deployments to make sure there is one in a “Ready” state, that it’s assigned to production, and that the domain is correctly connected to it. If everything looks off, try redeploying and promoting it to production.
Hope this helps