Hi everyone,
We have a production Next.js 16 (App Router) deployment on the Hobby plan that is fully built and marked Ready/Promoted, but every single request to it — on every hostname, including Vercel’s own *.vercel.app system domain — comes back with a platform-level 404:
X-Vercel-Error: NOT_FOUND
This happens on every path we’ve tried (/, /login, /api/auth/session, /favicon.ico), so it’s not a routing bug in our app — nothing is reaching the app at all.
Project: sativa.marketing
Project ID: prj_eZEi1DD8AeGZbKzoDvwUsw0cJsDj
Team: camilasophia62-6483s-projects (team_3wT8T5vjqtpaXUSDn4mZPoF9)
Custom domain: www.sativamarketing.com.br
System domain: sativamarketing.vercel.app
What we’ve confirmed is correct on our end: deployment readyState: READY, readySubstate: PROMOTED, target: production; alias array includes both domains with aliasError: null; domain verified: true with no redirect/branch/environment restriction; nameservers are Vercel’s own (confirmed ✓); build logs show a fully successful next build with all 33 routes present, ending in “Deployment completed”.
The most telling clue: a deliberately unclaimed subdomain under the same domain returns a different error — DEPLOYMENT_NOT_FOUND — instead of plain NOT_FOUND. So the edge network recognizes www.sativamarketing.com.br as belonging to this project, but fails to route the matched request to the deployment. And since even sativamarketing.vercel.app shows the identical NOT_FOUND, this rules out any DNS/domain misconfiguration on our side.
Tried over several hours, 5+ deployments, no change: multiple vercel deploy --prod (incl. --force), vercel alias set reassignment, vercel promote (confirmed already current production), and a dashboard-triggered Redeploy from the UI.
Deployment IDs affected: dpl_wviKgRmwQnDLrFhD83nHCncE483B, dpl_2pSjQmQwrwDaj2zKRDujfNb54QiH, sativamarketing-ayyihk5df-camilasophia62-6483s-projects.vercel.app
Recent request IDs: gru1::64k9k-1783433348430-7f6c323449d9 (custom domain), gru1::68wmd-1783433348882-bab45599cbb9 (system domain)
This is currently blocking our production launch for a real client. Would really appreciate it if someone from the Vercel team could take a look at project prj_eZEi1DD8AeGZbKzoDvwUsw0cJsDj.