RAP Sheet home
Install the bug reporting skill
22 people reported

All time, since Aug 2.

Ready deployment returns 404

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

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/vercel/issues/9075/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports in the last two weeks, down from 5 a week at the mid-August peak.

Ready production deployment returns 404 NOT_FOUND on every URL. Aliases, custom domains with Valid Configuration, and raw deployment URLs all 404 with no runtime invocation in logs.

Is this your bug?

File my report
Where
Edge routing
Error text
X-Vercel-Error: NOT_FOUNDPasted in 5 reports
HTTP/1.1 404 Not FoundPasted in 3 reports
404 NOT_FOUNDPasted in 2 reports
Versions
16.2.10 to 59.1.4
How bad
Stops work: a core feature can't be used. Some reports say it blocks them completely.

Not quite your bug?

  1. Domain serves stale deployment4 people
  2. Deploying outputs step fails5 people
  3. Custom domain response stalls9 people

Original reports23, newest first

  1. Ready/Production deployment returns NOT_FOUND on all paths, zero runtime logs#49875
  2. Every URL type 404s (NOT_FOUND) on a Ready/Production deployment#49606
  3. Production deployment returns 404 NOT_FOUND despite READY build#49534
  4. Custom domain returns Vercel 404 NOT_FOUND despite Valid Configuration and correct production alias#49499
  5. Project production alias routing broken — all aliases 404 despite Ready deployment#49250
  6. Vercel deployment is Ready but returns 404 NOT_FOUND#49192
  7. Custom domain returns platform-level 404 NOT_FOUND despite Valid Configuration#49125
  8. Custom domain returns Vercel 404 despite Valid Configuration#49090
  9. READY production deployment returns Vercel 404 at every URL#49045
  10. Custom domain returns platform NOT_FOUND despite verified alias and Ready deployment#48741
Show all 23Show only the newest 10
  1. Vercel Deployment Redirects to SSO Instead of Opening My Project#48571
  2. Account-wide platform NOT_FOUND - No deployment served on any URL#48321
  3. Deployment is Ready but all URLs return 404 NOT_FOUND#48299
  4. New deployments return 404 X-Vercel-Error: NOT_FOUND despite Ready + aliases#48255
  5. Production alias returns NOT_FOUND despite READY + PROMOTED deployment#48251
  6. READY production deployment aliases return platform NOT_FOUND#48199
  7. Deployment marked Ready but returns 404 — build log stops after 'Deploying outputs...'#48195
  8. Deployment#48174
  9. Production alias returns 404 NOT_FOUND#48126
  10. Next.js 16 deployment shows 404: NOT_FOUND despite successful Vercel build#48106
  11. Production deployment READY but all URLs return 404 NOT_FOUND before runtime#47664
  12. Sitewide NOT_FOUND on every path despite successful build — persists after re-import#47039
  13. starklab.design 404s at edge despite READY deploy (live:false)#47001

Do you work on Vercel?

Claim its RAP Sheet to see what your users report and answer them in one place.

Claim a tool