Every URL type 404s (NOT_FOUND) on a Ready/Production deployment

Project: iksana-ess (team iksana1)

Every URL I try for this project returns Vercel's platform-level 404 NOT_FOUND page, even though the deployment shows Ready and Production in the dashboard, and "Promote"/"Instant Rollback" are both disabled because "this deployment is already in Production."

I've tested every routing path Vercel offers, and all of them fail identically:

The project's original custom .vercel.app domain — iksana-ess.vercel.app A brand-new .vercel.app domain added fresh just to test — iksanaess.vercel.app The auto-generated git-branch alias — iksana-ess-git-main-iksana1.vercel.app The deployment's own raw generated URL — tested on two different deployments (including one created today from a fresh Redeploy), e.g. iksana-o8a7ppm39-iksana1.vercel.app A real custom domain on my own DNS (ess.iksana.tech), with a valid CNAME record and a successfully-issued Vercel SSL certificate — still returns the same 404

That last one rules out any explanation involving .vercel.app-specific routing quirks or ISP filtering, since it's not a .vercel.app domain at all.

Things I've already tried, none of which fixed it:

vercel alias set via CLI — reports "Success" for both domain aliases, but they still 404 Removing and re-adding the domain in Project Settings → Domains A full Redeploy (not just a new commit) — new deployment, same failure Toggling Vercel Authentication (Deployment Protection) off and back on — no change

Also worth noting: the project's own Logs tab shows zero request logs, despite dozens of real requests hitting these URLs (each returning a valid Vercel request ID). That suggests the requests are being rejected before they ever reach the deployment/function layer — a routing-table issue on Vercel's side, not something in my app code.

Sample request IDs from the 404 pages: bom1::k7phm-1790099305143-d43745b4fdd4 bom1::tpl4r-1790144129290-ee32f0545a0d bom1::5649x-1790145785904-718974aa6118 bom1::n4bgt-1790147937935-fa3f4919475e bom1::mr5lf-1790149521343-12a6bc73175e bom1::lgzbn-1790150891262-5db75f5cf6e9

This is a Hobby plan project, so I don't have access to a direct support case for this category (their AI support agent confirmed CDN/routing tickets aren't available on Hobby). Would appreciate a Vercel team member taking a look — happy to provide any further logs or details.

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

Vercel Community

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are...

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

Found it, thanks for the pointer. The issue was the Framework Preset in Project Settings → Build and Deployment — it was stuck on "Other" instead of "Next.js," because the project was first imported when the repo only had a README, before any Next.js code existed. That setting doesn't auto-correct once real code is pushed, so Vercel kept serving the app as a static/generic project instead of running Next.js routing — explaining the universal 404 across every URL type and the empty Logs tab.

Fix: switch Framework Preset to Next.js, save, redeploy. Resolved immediately.

Leaving this here in case others hit the same thing after importing a repo before its framework code was pushed.

Thanks for sharing the solution!