Custom domain returns Vercel 404 despite Valid Configuration

Hi,

I have a Next.js production deployment that is Ready and healthy.

The custom domain:

shows Valid Configuration
passes vercel domains verify
is assigned to the correct project
appears in vercel alias ls
points to the latest Ready Production deployment

I also tried:

vercel alias set
removing and re-adding the custom domain
waiting almost 24 hours

But the domain still returns:

HTTP 404 X-Vercel-Error: NOT_FOUND

The direct deployment URL is recognized by Vercel and reaches Vercel Authentication, so the deployment itself exists.

This looks like a control-plane / edge-routing mismatch.

Has anyone found a working fix for this recently?

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.