How to Fix Vercel: 404 NOT_FOUND / DEPLOYMENT_NOT_FOUND after deploy
Error message
404: NOT_FOUND. Code: DEPLOYMENT_NOT_FOUND. The requested deployment could not be found.
If you're seeing "Vercel: 404 NOT_FOUND / DEPLOYMENT_NOT_FOUND after deploy", you're not alone. Here's what it means, why it happens, and the steps to resolve it.
What this error means
Vercel routed your request, but no deployment matches the URL. Either the deployment was deleted, rolled back, or the alias points at a deployment that no longer exists.
Why this happens
Common: deleted preview deployment, alias still points at an old build, project deleted, or the URL has a typo.
Step-by-step fix
Open the Vercel dashboard → your project → Deployments. Confirm the latest production deployment exists and is marked Ready.
Check the Domains tab — confirm your domain is aliased to a current deployment, not a deleted one.
If the alias is wrong, set it from the CLI.
commandvercel alias set <deployment-url> <your-domain>Trigger a fresh production deploy.
commandgit commit --allow-empty -m 'redeploy' && git push
Affected products
Vercel
Still broken? Try these
- Visit the canonical deployment URL directly (vercel.com → Deployments → click one) to bypass aliases.
- If using a Git Integration branch alias, confirm the branch is still active and has a successful build.
- Check whether someone deleted the project or transferred it to another team.
Related errors
Frequently asked questions
What does "Vercel: 404 NOT_FOUND / DEPLOYMENT_NOT_FOUND after deploy" mean?
Vercel routed your request, but no deployment matches the URL. Either the deployment was deleted, rolled back, or the alias points at a deployment that no longer exists.
What causes "Vercel: 404 NOT_FOUND / DEPLOYMENT_NOT_FOUND after deploy"?
Common: deleted preview deployment, alias still points at an old build, project deleted, or the URL has a typo.
How do I fix "Vercel: 404 NOT_FOUND / DEPLOYMENT_NOT_FOUND after deploy"?
1. Open the Vercel dashboard → your project → Deployments. Confirm the latest production deployment exists and is marked Ready. 2. Check the Domains tab — confirm your domain is aliased to a current deployment, not a deleted one. 3. If the alias is wrong, set it from the CLI. 4. Trigger a fresh production deploy. Always test changes in a non-production environment first.
Browse more errors in Vercel: Fix Vercel deployment errors. Build failures, missing output directories, exceeded build duration, missing env vars, and module resolution issues. Or paste your own error into the error decoder tool to find a match. You can also go back to the homepage to browse common errors by topic.