Deployment is Ready but all URLs return 404 NOT_FOUND

My Next.js deployment builds successfully and is marked Ready, but the production vercel.app URL and the unique deployment URL both return Vercel's 404: NOT_FOUND page.

The build log successfully generates the / route. The deployment is marked Ready. Runtime/function logs show the application functions are not being invoked correctly.

Latest request ID: bom1::qqchf-178755732492-8b5a104cb14

Can someone help me identify why a successful deployment is returning Vercel's platform-level 404?

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.

I have the same issue. My project builds without issues but the domain returns:

404: NOT_FOUND

Code: NOT_FOUND

ID: fra1::pcn4x-1787643776616-c742221a3b8a

v0 Ambassador

Hi guys,

This may help - https://community.vercel.com/t/deployment-is-ready-but-all-urls-return-vercel-404-not-found/48426#post_3

Vercel Community

Deployment is Ready but all URLs return Vercel 404 NOT_FOUND

Hi Vercel team, I’m having an issue where my Next.js deployment shows as Ready, the build completes successfully, and my custom domain is verified, but every...