404: Not found - Works on every alias except the clean one - Help

Project miraculous-light has a Ready production deployment that's correctly routable through two of its aliases — correctly redirect to Vercel Authentication SSO, proving the deployment itself is live. But its third alias, miraculous-light.vercel.app, returns a platform-level 404: NOT_FOUND, even though vercel alias ls confirms it targets the same deployment ID.

Tried: vercel alias set (API reports success, no change), vercel promote (rejected with a 409, "already the current production deployment"). Support chat confirmed this needs human review but said direct case creation isn't available on the Hobby plan for this topic and redirected me here.

Anyone seen this specific "works on every alias except the clean one" pattern before?

There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

https://community.vercel.com/t/debugging-404-errors/437

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Update: wanted to rule out this being specific to my project before assuming it's just this one alias. I created a brand-new, unrelated project under the same team and deployed the same app to it as its very first deployment. It has the identical fault — clean alias returns 404: NOT_FOUND immediately, and even a completely fresh deployment (zero shared history, build only minutes old) returns platform 404 on every route once past Vercel Authentication.

That rules out project-level corruption or stale config for me — this looks like it's scoped at the team/account level rather than anything wrong with how this specific project is set up. Deleted the throwaway project afterward since it had served its purpose.

Posting in case this points anyone (or Vercel) toward the right layer to look at — a team-level fault rather than a per-project one.