Production deployment READY but all URLs return 404 NOT_FOUND before runtime

Help
1

Hello,

I’m experiencing what appears to be a Vercel edge/routing issue with a production deployment.

Project: alavi-producao
Team: ALAVI DESTINOS
Deployment ID: dpl_Cvy1VcCmoKQKx657UkLbkPe2o88d
Production alias: alavi-producao.vercel.app

The deployment is shown as READY and promoted to Production. The build completes successfully and generates 39 routes, including /.

However, every request to the production alias returns:

404 NOT_FOUND

Latest reproduction:

X-Vercel-Id: gru1::sbh54-1786591641981-389eb42fe486

We have already verified:

  • vercel inspect reports the deployment as Ready with target Production
  • Production aliases are correctly assigned with no aliasError
  • The / route is generated successfully during the build
  • /login and /favicon.ico also return the same platform-level 404 NOT_FOUND
  • The direct deployment URL also fails
  • Authenticated vercel curl reproduces the issue
  • vercel logs shows no runtime invocation when the 404 occurs
  • A fresh deployment without cache was already attempted
  • The production alias was reassigned
  • Waiting and retesting did not resolve the issue

Since there are no runtime logs for these requests, it appears that the request is being rejected before reaching the application runtime.

Could someone from Vercel please check whether this deployment/project is correctly registered in the edge routing layer, and whether there is a mismatch between the control-plane deployment/alias state and edge routing registration?

Thank you.

2

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.

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.