One of my Hobby projects has a Preview branch alias of the form
<project>-git-<branch>-<team>.vercel.app. (Happy to share the exact project, alias and
deployment IDs privately with Vercel staff.)
Since about 15:00 PST on 2026-11-20 the alias has served the previous Preview build. Three independent Ready deployments of the new HEAD exist, and the newest is marked "Latest" with this alias listed in its Domains.
What I observed (fresh cookieless browser profile, never-before-requested URLs):
- A static file that exists only in the new build: alias returns a platform 404 with a fresh x-vercel-id; the new deployment's own URL returns 200.
- A shared JS bundle: alias serves 100426 bytes; the new deployment's URL serves 100576 bytes.
- An API route with a never-used query string: the alias response lacks the new response fields the deployment URL returns, i.e. it appears to run the old code.
What I tried: 8 push-triggered deployments, one deploy-hook deployment, and one manual redeploy of the new HEAD with build cache disabled. The alias did not move after any of them. My app's sign-in flow is pinned to this alias, so switching hostnames is not a workaround for me.
This resembles https://community.vercel.com/t/canonical-alias-returns-not-found/45849, where redeploys didn't help either, though I don't know if the root cause is the same.
Is there anything left to try from my side, or can a Vercel engineer check the routing state for this alias? I can add fresh x-vercel-id request IDs with UTC timestamps when posting.