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 URL returns a Vercel platform-level 404 NOT_FOUND.

Project: uniradar Custom domain: myuniradar.com

The Next.js build completes successfully and includes the / route:

Route (app) ┌ ○ / ├ ○ /_not-found ├ ○ /housing ├ ○ /housing/dorms ├ ƒ /housing/dorms/[slug] ├ ƒ /housing/dorms/[slug]/review └ ○ /login

The deployment status is:

status: Ready target: production

DNS verification is also successful:

Success! Valid Configuration: myuniradar.com is configured (A record) and verified for project uniradar

The domain currently resolves to the A records Vercel requested:

64.29.17.1 216.198.79.1

I also manually assigned the domain to the deployment:

Success! https://myuniradar.com now points to uniradar-4i89hjghn-june7417-6353s-projects.vercel.app

However, both the custom domain and the deployment URL return:

HTTP/2 404 server: Vercel x-vercel-error: NOT_FOUND

I also tested the deployment directly using vercel curl with a Deployment Protection bypass token, and it still returned the same Vercel platform-level 404:

HTTP/2 404 x-vercel-error: NOT_FOUND x-vercel-id: sfo1::csq8w-1787700801363-22a40f20e6c3

Deployment Protection / Vercel Authentication has also been disabled for testing.

Since the build is successful, the deployment is Ready, the / route exists, DNS is verified, and even the protected deployment URL returns a Vercel NOT_FOUND, this appears to be a deployment/edge-routing issue rather than an application-level 404.

Could someone from the Vercel team please check whether the deployment registration or edge routing for this project/team needs to be re-synced or re-provisioned?

Thank you!

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.

Based on the detailed debugging steps you've shared, your conclusion is spot on: this is almost certainly a platform-level edge routing or provisioning issue rather than an application-level bug. The presence of the x-vercel-error: NOT_FOUND header on both the custom domain and the direct .vercel.app URL—especially when bypassing Deployment Protection—confirms that Vercel's edge network is failing to map the URL to your specific deployment ID, despite the build succeeding and showing as "Ready".

While waiting for a Vercel team member to manually re-sync or check your edge routing on their end, here are the most effective steps to force a resolution or rule out the remaining edge cases:

Trigger a Redeploy Without Cache (Clean Build)
Double-Check the Root and Output Directory
Check for Account-Level Restrictions

For more context on how Vercel categorizes these errors, you can refer to their official documentation on the DEPLOYMENT_NOT_FOUND error - https://vercel.com/docs/errors/deployment_not_found.

vercel.com

DEPLOYMENT_NOT_FOUND

The deployment was not found. This is a deployment error.