Sitewide NOT_FOUND on every path despite successful build — persists after re-import - Help

Sitewide NOT_FOUND on every path (including static assets) despite successful Ready/Production build — persists after deleting and re-importing the project fresh

Summary

Every request to my production deployment returns Vercel's platform-level 404 (Code: NOT_FOUND), including static assets like /favicon.ico that never reach the application layer. The build itself completes successfully and the deployment is marked "Ready" / "Production", but nothing is served.

Details

Framework: Next.js 16.2.12 (App Router, Turbopack), using proxy.ts (the new Next 16 middleware convention)
Repo: https://github.com/VegassZ17/finango (branch main)
Deployment URLs tried:
- finango-gamma.vercel.app (original project) — 404 on every path
- finango-three.vercel.app (deleted the project and re-imported the repo fresh) — identical 404 on every path
Example error ID: iad1::8wptq-1785713822006-f76445125475
Local next build completes cleanly with the expected route manifest (static /, dynamic routes, and a Proxy/Middleware entry all listed).
Deleting and re-importing the project as a brand new Vercel project did NOT resolve the issue — same symptom on the fresh project with a different auto-generated domain.

This matches other reports of the same symptom on this forum:

"Next.js 16 middleware returns 404 sitewide on Vercel" (topic 39029)
"Every deployment in two projects returns NOT_FOUND on all paths, incl. previously-working ones" (topic 46037), where the conclusion pointed to team-level edge-routing state that required Vercel staff to repair.

Since a fresh project reimport didn't fix it, this looks like an infrastructure-side issue rather than something fixable from my repo/config. Could someone take a look at my account/team and deployments?

Project ID: prj_GOKyIxrHipCIYOX4A9YxuH2zEJ08

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.

Thanks for the link — I went through the debugging guide and confirmed all of it checks out on my end:

Framework Preset: Next.js (detected correctly)
Root Directory: empty/default (repo root, where package.json lives)
Output Directory: automatic, no override
Domain: finango-three.vercel.app shows no warnings, "Valid Configuration"
Deployment status: Ready / Production

This is a completely fresh project (deleted the old one and re-imported from scratch), and the symptom is identical: every path, including static assets like /favicon.ico, returns the platform NOT_FOUND before reaching the app.

Since the standard checklist doesn't turn up anything, could a human take a look at the account? This matches the pattern described in topic 46037 (team-level edge-routing state that needed staff to repair).

Project ID: prj_GOKyIxrHipCIYOX4A9YxuH2zEJ08

Sitewide NOT_FOUND on every path (including static assets) despite successful Ready/Production build — persists after deleting and re-importing the project fresh

Summary

Details

Framework: Next.js 16.2.12 (App Router, Turbopack), using proxy.ts (the new Next 16 middleware convention)
Repo: https://github.com/VegassZ17/finango (branch main)
Deployment URLs tried:
- finango-gamma.vercel.app (original project) — 404 on every path
- finango-three.vercel.app (deleted the project and re-imported the repo fresh) — identical 404 on every path
Example error ID: iad1::8wptq-1785713822006-f76445125475
Local next build completes cleanly with the expected route manifest (static /, dynamic routes, and a Proxy/Middleware entry all listed).
Deleting and re-importing the project as a brand new Vercel project did NOT resolve the issue — same symptom on the fresh project with a different auto-generated domain.

This matches other reports of the same symptom on this forum:

"Next.js 16 middleware returns 404 sitewide on Vercel" (topic 39029)
"Every deployment in two projects returns NOT_FOUND on all paths, incl. previously-working ones" (topic 46037), where the conclusion pointed to team-level edge-routing state that required Vercel staff to repair.

Project ID: prj_GOKyIxrHipCIYOX4A9YxuH2zEJ08

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.

Thanks for the link — I went through the debugging guide and confirmed all of it checks out on my end:

Framework Preset: Next.js (detected correctly)
Root Directory: empty/default (repo root, where package.json lives)
Output Directory: automatic, no override
Domain: finango-three.vercel.app shows no warnings, "Valid Configuration"
Deployment status: Ready / Production

Project ID: prj_GOKyIxrHipCIYOX4A9YxuH2zEJ08