Hi Vercel team,
I’m seeing what appears to be a control-plane / edge-routing inconsistency on a Hobby project.
Project: toronto-quartz-rc Team: elite-countertop Deployment: dpl_CFyN1y31xmddf3FuapNgPmKF5cWM Environment: Preview State: READY Source commit: 36a0dc8c5920a44eb5f5b27bf6231f4b55ecd8ad
Exact generated deployment URL:
https://toronto-quartz-f1htwlm5l-elite-countertop.vercel.app
The build completed successfully, and the deployment output contains the expected routes:
- /
- /api/rc/status
- /get-estimate
- /admin
Deployment Protection is also working:
- Unauthenticated requests return HTTP 302 to Vercel Authentication.
- After authentication, the exact generated deployment URL returns Vercel platform 404: NOT_FOUND.
Example requests:
2026-08-22T13:21:56.650Z Path: / Vercel response ID: yul1::w5tfx-1787404916716-113d28709362
2026-08-22T13:22:13.063Z Path: /api/rc/status Vercel response ID: yul1::hhxx2-1787404933091-ddb23102d53c
We also checked deployment/runtime logs for the matching time window:
- Serverless invocations: 0
- Edge function invocations: 0
- Middleware invocations: 0
- Static/runtime request entries: 0
This indicates that the 404: NOT_FOUND is being returned by Vercel before the application runtime is reached.
No custom domain is attached, and the requests are being made directly against the exact generated deployment URL.
Could you please investigate whether this READY Preview deployment is correctly registered in Vercel’s edge routing layer, or whether there may be a control-plane / edge-routing inconsistency for this deployment?
We are intentionally retaining the affected deployment and are not redeploying or deleting it so the failing state remains available for investigation.
Thank you.