Custom domain returns platform NOT_FOUND despite verified alias and Ready deployment

Hello Vercel team,

My custom domains tea-chose.com and www.tea-chose.com return a Vercel platform-level 404 NOT_FOUND.

I have confirmed the following:

Production deployment status is Ready
Both domains are verified and configured correctly
SSL certificate has been issued
Both aliases point to the latest production deployment
Deployment Protection has been disabled
Domains were removed and re-added
A fresh production deployment was completed without build cache
Requests do not reach the application runtime and no runtime logs are created

The issue still persists.

Latest X-Vercel-Ids:

sin1::wzszf-1788363159038-dc547057636d sin1::49fc6-1788363160592-1453dc2c0434

This appears to be a control-plane / edge-routing synchronization issue. Could a Vercel team member please check and refresh the edge routing entries for these domains?

There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

https://community.vercel.com/t/debugging-404-errors/437

Vercel Community

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are...

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Just tested it and saw it's returning a 404 with code NOT_FOUND rather than DEPLOYMENT_NOT_FOUND. That means the deployment exists, but the page you expected doesn't. Please use the debugging steps linked above to figure out why that's happening