Account-wide platform NOT_FOUND — no deployment served on any URL (custom domain, .vercel.app alias, or exact deployment hash), across two independently created projects

Team: academydigitalagency (team_UlsOOpUB0MzrvbACK4FPqwhQ) Plan: Hobby

Summary

Every deployment under this account returns Vercel's own platform 404: NOT_FOUND — not an application-level 404, not a Next.js route miss. This happens on:

• The custom production domain (academydigitalagency.com, www.academydigitalagency.com)
• The project's own auto-generated .vercel.app alias
• The exact hashed deployment URL, accessed directly with a valid Deployment Protection bypass token

The last one is the key data point: hitting the literal deployment URL with x-vercel-protection-bypass set bypasses DNS, the custom domain, and all alias resolution entirely — yet still returns platform NOT_FOUND. This rules out DNS, nameservers, domain config, and project-level alias assignment as the cause. Every control-plane API response reports the deployment as READY and correctly configured.

What I tried, in order

1. Original project academy-digital-agency-website (prj_cgW98cANXXiLnRgClyoEi6qNebXX) — custom domain returns NOT_FOUND.
2. Confirmed via GET /v9/projects/{id}: aliasError: null, deployment READY, alias array correctly includes the custom domain, domain verified: true, no redirect/branch/environment restriction, Firewall config empty.
3. Confirmed DNS: nameservers fully delegated (ns1/ns2.vercel-dns.com), dig A resolves to genuine Vercel edge IPs, direct-IP curl --resolve bypass still returns the same error (rules out any caching layer).
4. Removed and re-added both domains from the project via the dashboard — no change.
5. vercel alias set <deployment> <domain> — CLI reports success, still NOT_FOUND.
6. vercel promote toggled to an older Ready deployment and back — no change.
7. Noticed project.live: false in the API response (a project-level flag distinct from deployment readyState) — matches the pattern in several other recent reports of this exact symptom.
8. Created a brand-new project from scratch (academy-digital-agency-website-v2, prj_mv1n2APqfCbbXustMTH4XHOKFJqS), reconnected the same GitHub repo, re-added all env vars, deployed fresh, moved the custom domain to it. Same NOT_FOUND. project.live: false on the new project too.
9. Retrieved each project's protectionBypass secret via the API and curl'd the exact deployment hash URLs directly with x-vercel-protection-bypass set (bypassing all alias/domain/DNS layers):
   • https://academy-digital-agency-website-8cp3wvhic-academydigitalagency.vercel.app/ (old project, dpl_Lw4rxCmqYeNBcz2sufJVwP342o4P) → 404 NOT_FOUND
   • https://academy-digital-agency-website-v2-6hrz8dii5.vercel.app/ (new project, dpl_5sjzpF4mJ2yDWgv9khUnip48wt6D) → 404 NOT_FOUND

Both return the identical x-vercel-error: NOT_FOUND with a valid server: Vercel header and real x-vercel-id trace — the request is reaching Vercel's edge, but nothing is being served, regardless of project.

Sample evidence

$ curl -sI https://academy-digital-agency-website-v2-6hrz8dii5.vercel.app/ -H "x-vercel-protection-bypass: "

HTTP/2 404 cache-control: public, max-age=0, must-revalidate content-type: text/plain; charset=utf-8 server: Vercel x-vercel-error: NOT_FOUND x-vercel-id: iad1::hz6nh-1787530204744-eed7bb26f98c

Request

Since this reproduces identically across two independently created projects — including on their exact deployment hash URLs, bypassing domains/DNS/aliases entirely — this looks like an account-level issue rather than anything project- or domain-specific. Could someone from Vercel take a look at team academydigitalagency (team_UlsOOpUB0MzrvbACK4FPqwhQ)? Happy to provide any further deployment IDs, timestamps, or trace IDs needed.