Ready/Production deployment returns NOT_FOUND on all paths, zero runtime logs

Our most recent deployment shows status Ready/Production, and the custom domain shows "Valid Configuration" — but every request, both to the custom domain and to the exact deployment URL, returns Vercel's platform-level 404 (NOT_FOUND), with zero entries appearing in Runtime Logs. Build is clean, no TypeScript errors, all routes correctly listed in the build manifest (including a Proxy/Middleware entry). Tested with middleware/proxy.ts removed entirely — same result, which rules out application code as the cause.

This matches the pattern described in other recent threads on this forum about a control-plane ↔ edge-routing desync.

Project ID: prj_hoJoWa5RrppIh4VSqT15CdPR1GEt Deployment ID: 3JJXQJgw2 Custom domain: controle-dispositivos-utin.vercel.app Request ID from the error page: gru1::xcfzf-1790635031462-2c65f019621c Plan: Hobby Framework: Next.js 16.3.6 (App Router, Turbopack)

Would appreciate someone from the team taking a look at the edge routing registration for this project.

Captura de tela 2026-09-28 193722.png

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.