Next.js 16 deployment shows 404: NOT_FOUND despite successful Vercel build

My Next.js 16.2.10 project builds successfully both locally and on Vercel.

Build verification:

npm run build succeeds locally.
Vercel deployment status is Ready.
Next.js generates / and /login plus 100+ other routes.
Vercel Root Directory is frontend.
The production URL returns 404: NOT_FOUND.
The unique deployment URL also returns 404: NOT_FOUND.
I created a fresh Vercel project from the same GitHub repository and it has the same issue.
The Vercel runtime/request logs show no request reaching the application.

Please check whether the deployment/project is correctly registered in the Vercel edge routing layer.

Repository: RushdhiMR/London-Network Branch: main Root Directory: frontend

I can provide the exact deployment ID and 404 request ID if needed.

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.

Deployment URL: https://london-network-omsl-lbbcm357-rushdhimrs-projects.vercel.app

Production URL: https://london-network-omsl-zeta.vercel.app

Repository: RushdhiMR/London-Network

Branch: main

Root Directory: frontend

Next.js: 16.2.10

Issue: Both the production URL and the unique deployment URL return Vercel's 404: NOT_FOUND.

Build: npm run build succeeds locally and on Vercel.

Routes generated: / /login and 100+ other routes.

Runtime: No request logs appear when opening the URLs.

I found another recent Vercel Community case with the same behavior:

Next.js build succeeds
Deployment is Ready / Production
/ and other routes are generated successfully
A fresh Vercel project was created from the repository
Every URL still returns Vercel 404: NOT_FOUND
The request never appears in runtime logs

The other user mentioned that their issue appeared to be related to a team-level edge-routing state that required Vercel staff intervention.

Could someone please check whether there is a similar edge-routing or deployment registration issue affecting my team/project?

Repository: RushdhiMR/London-Network Root Directory: frontend Next.js: 16.2.10

I have now completed the troubleshooting steps in the Vercel 404 documentation:

The deployment exists and is marked Ready.
The production and unique deployment URLs both return 404: NOT_FOUND.
The build succeeds locally and on Vercel.
Next.js 16.2.10 generates /, /login, and 100+ routes.
Root Directory is frontend.
I tested a fresh Vercel project from the same GitHub repository and the same 404 occurs.
The request does not appear in the runtime logs.

This seems consistent with other recent reports where the deployment is Ready but the Vercel edge/routing layer returns NOT_FOUND before the application is reached.

Could you please check the deployment/project routing state on the Vercel side?

Repository: RushdhiMR/London-Network

Vercel Staff

It looks like the earlier deployments you linked to have been deleted

CleanShot 2026-08-21 at 09.59.06@2x

Hopefully you already found a solution. If you're still having trouble with this, can you share the latest production deployment URL?