New production aliases in my team are not being routed at the edge, even though the alias record exists in the control plane and points to a READY production deployment.
**Affected project:** `minemate-app` (`prj_S7bdUWWLytHLqsvJQdUi26bliVOa`)
**Working (unaffected) project:** `minemate` (landing) — its older aliases work fine.
Symptom
- `https://app.minemate.com.au/login\` → **404**, `x-vercel-error: NOT_FOUND` (served at `syd1` edge)
- `https://minemate-app.vercel.app/login\` → **404** (this is the Vercel-managed `.vercel.app` alias, no custom DNS involved)
- The exact same deployment on its **hashed URL** works: `https://minemate-i9hl107l1-liocode-6335s-projects.vercel.app/login\` → **302** (expected redirect)
What I verified (it is NOT a config problem on my side)
- **Domain:** `app.minemate.com.au` → `verified: true`, `misconfigured: false`, assigned to the correct project. DNS A record `76.76.21.21`, request reaches the Vercel edge.
- **Alias record exists and is correct:** `GET /v4/aliases?domain=minemate.com.au` returns `app.minemate.com.au → <latest app deployment>`, which is READY, `target: production`, and serves on its direct hashed URL.
- **Deployment:** READY, `aliasAssigned: true`, `aliasError: null`.
- **Account:** `blocked: null`, `softBlock: null`, `featureBlocks: {}`, billing `status: active`.
Key differentiator
- **Old** aliases created 2026-06-15 (`minemate.com.au`, `www.minemate.com.au` → landing) are routed fine (HTTP 200).
- **All new** aliases created 2026-07-13 (`app.minemate.com.au` + `minemate-app.vercel.app`) return 404.
- Reproduced on a brand-new empty project in the same team → same 404. So it is **account-wide**, not project/code specific.
What I already tried (no effect)
- `vercel alias set <deployment> app.minemate.com.au` → CLI reports "Success", edge still 404.
- Removed and re-added the domain assignment to the project.
- Multiple clean `vercel --prod` redeploys.
This is NOT DNS propagation
Please note: the **`*.vercel.app` alias also returns 404**. Since `minemate-app.vercel.app` has no custom DNS, this cannot be a DNS propagation delay — it points to a control-plane ↔ edge routing issue. (In the community threads where only the custom domain 404s and `*.vercel.app` works, e.g. #32411/#38333, waiting for DNS fixed it — that is a different situation from mine.)
This looks identical to community thread **#45034** ("Custom domain 404 NOT_FOUND after moving to new project via API"), where both the custom domain and `*.vercel.app` returned 404 and redeploys + remove/re-add + 12h wait did not help.
Conclusion / ask
There appears to be a **control-plane ↔ edge inconsistency**: the alias record is correct and points to a healthy deployment, but the edge routing table has no route for the new aliases in this account. Please re-sync / re-provision edge routing for team `team_oZgM6VFzA8avVRBWLZbRRdfd` so newly created production aliases are served.
Thanks.
