4 people reported
All time, since Aug 12.
Domain serves stale deployment
“I have a custom-domain routing issue that appears to be serving a stale internal 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/9944/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
Production domain serves stale deployment despite Ready status. Dashboard shows the new deployment as current Production, but the vercel.app or custom domain returns an older bundle or build.
Is this your bug?
File my report- Where
- Production domains
- How bad
- Breaks a normal workflow. Some reports say it blocks them completely.
Not quite your bug?
- Ready deployment returns 40422 people
- Deploying outputs step fails5 people
Original reports4, newest first
- Production domain stuck serving 12+ day old deployment — confirmed not a cache issue#51122
- Deployments succeed but assets never change (CDN purge does not fix)#49223
- Production domain not serving latest Ready/Current deployment (Hobby plan)#47827
- Custom domain routes to a stale deployment despite valid Vercel configuration#47657