New deployments return 404 X-Vercel-Error: NOT_FOUND despite Ready + aliases

Team: abdullah-abuzaids-projects Project: wajba-gaza Date issue started: Aug 23, 2026

Since Aug 23, every new deployment on this team reaches "Ready" status but is completely unreachable at the edge. Every request returns:

HTTP 404 with header: X-Vercel-Error: NOT_FOUND

Tested from 3 independent networks (home ISP, mobile data, and a cloud-based HTTP fetcher from a different region) — identical result everywhere.

Affected deployments (all show "Ready" in the dashboard):

https://wajba-gaza-fny4vw5fu-abdullah-abuzaids-projects.vercel.app
  id: dpl_3MgG66ivW5auCAh13zrxEpCpqh88 (production)
https://wajba-gaza-bwd3s80zu-abdullah-abuzaids-projects.vercel.app
https://wajba-gaza-ar7xfkzm7-abdullah-abuzaids-projects.vercel.app

All production domains are assigned and aliased correctly:

https://wajba-gaza.vercel.app

وجبة

وجبة | توصيل طعام فلسطيني في غزة

اطلب من أكثر من ١٢٠ مطعم في غزة. توصيل سريع، منيو حقيقي، وأسعار شفافة.

https://wajba-gaza-abdullah-abuzaids-projects.vercel.app

Evidence that this is a platform-side routing failure:

vercel inspect reports status: Ready, target: production, with both aliases attached to dpl_3MgG66ivW5auCAh13zrxEpCpqh88.

vercel alias ls confirms both aliases point to this exact deployment.
Yet the edge returns X-Vercel-Error: NOT_FOUND for every request.
Deployment Protection (Vercel Authentication / Password) is DISABLED for this project — verified in Settings → Deployment Protection.
Deployments triggered BOTH via GitHub integration AND via Vercel CLI (vercel deploy --prod, which reported "▲ Aliased") fail identically.
Older deployments on the same team (45+ days old, e.g. dawai-gaza, e-commerce-fullstack) still serve HTTP 200 normally — only NEW deployments since Aug 23 are affected.
The issue persisted across a project recreation: I deleted project "food-delivery-system" and created "wajba-gaza" fresh — same behavior.

My conclusion: deployment aliases exist in the API layer but the edge routing layer never picks them up for any new deployment on this team. Build logs are clean (Ready within ~30s). Please investigate the routing/ alias registration pipeline for team abdullah-abuzaids-projects.

I attempted to submit an official support case via the Vercel Agent, but the case form failed to submit. Could a staff member escalate this internally? Happy to provide any additional details needed.

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.

I’m seeing what appears to be the same issue across two separate projects under the same Vercel team.

Both deployments show Ready, vercel inspect confirms healthy deployments with complete Next.js route trees, and the aliases appear correctly assigned. However, requests return Vercel’s platform-level 404 NOT_FOUND before reaching the application.

Affected examples:

pinasbnb-pro.vercel.app
pinasbnb-pro-staging.vercel.app
pinasbnb.pro
haven-in-lipa.pinasbnb.pro

Interestingly, team-suffixed deployment URLs route correctly, and an older staging wildcard subdomain also works. We’ve made no DNS, alias, application, or database changes for 12+ hours, and the behavior remains unchanged.

I already opened a Vercel support ticket and provided deployment IDs, project IDs, timestamps, and x-vercel-id values. Posting here as another data point since this no longer appears consistent with normal propagation delay.

Happy to provide additional diagnostics if useful.

Additional data point: pinasbnb.pro is also fully delegated to Vercel DNS (ns1.vercel-dns.com / ns2.vercel-dns.com), so there is no third-party DNS provider in the path for the custom domains. Combined with the same NOT_FOUND occurring on the native .vercel.app aliases, this seems to further point toward Vercel's alias/edge-routing layer rather than external DNS.