Our Next.js 16 (App Router) project deploys successfully — build completes, dashboard marks the deployment "Ready" — but the deployment serves no content at all. Every URL for it returns 404 NOT_FOUND, including the production custom domain, the project's default *.vercel.app domain, and the deployment-specific URL.
What the build log actually shows (last lines):
Build Completed in /vercel/output [23s]Deploying outputs...
Nothing is logged after "Deploying outputs...". No error, no confirmation — the log simply ends there. The build itself is clean: all routes compiled correctly (static and dynamic pages, middleware/proxy included), no build errors, no warnings besides an unrelated npm warn allow-scripts notice.
Despite this, the deployment is marked "Ready" in the dashboard, and Vercel's own deployment-preview screenshot shows a 404 page.
Evidence this is not a config issue on our end:
- Reproduced across two separate Vercel accounts/teams (
agencia-f4andconectasaudepe) with the same codebase. - Reproduced via both a CLI-triggered deploy (
vercel --prod) and a Git-integration-triggered deploy (push tomain). - Reproduced across two Vercel CLI versions (59.1.4 and 59.3.0).
- Explicitly set
"framework": "nextjs"invercel.jsonto rule out framework-detection issues — no change. - Verified environment variables were present and correctly set before the deploy — no change.
- Domain DNS is correctly configured and verified (
vercel domains verifyreportsconfigured_correctly).
Deployment IDs for reference:
dpl_66ZLUohN6RTpvr4f3Rg2iTxJLV9o(agencia-f4, stuck at status UNKNOWN,Builds: . [0ms])dpl_Eifwg1RbCGDD99xNht13Cm3vvmQc(conectasaudepe, same UNKNOWN/0ms pattern)61Qabu2zhYX2M4M3iJkDUnbXn2V2(agencia-f4, Git-triggered, marked "Ready" in 25s, build log ends at "Deploying outputs...", live URL returns 404)
Could someone from the platform/infra team take a look at why builds that complete successfully aren't actually being registered/served at the edge? Happy to share full log exports or grant temporary access if useful.
