Hi Vercel team,

I’m seeing what appears to be a provider-side production alias / routing association inconsistency on a Hobby project.

Team: cut8981-7925s-projects Team ID: team_ecJaWdHAkxV2Roa5oxYDC3Sn Project: investor-os-unified Project ID: prj_YQJ38L2wcCVPPLQHk1CIvic5ZLUg Production deployment ID: dpl_3MBpR2Y9csbRzYfpaLi6mHYooe3E

Unique deployment URL: https://investor-os-unified-brus7dr2y-cut8981-7925s-projects.vercel.app

Production alias: https://investor-os-unified.vercel.app

Verified state:

• Deployment is READY
• Production state is PROMOTED
• Project paused=false
• No usage/team throttle detected
• No abuse block detected
• Build succeeds and generates / and /api/health
• Explicit vercel promote returns 409 because this deployment is already the current Production deployment
• Explicit vercel alias set succeeds and reports that the production alias now points to this exact deployment
• Unique deployment URL resolves to Vercel authentication
• Production alias / still returns Vercel platform 404 NOT_FOUND
• Production alias /api/health also returns 404 NOT_FOUND
• No application runtime log entry is generated by these requests

Recent Vercel request IDs:

sin1:iad1::24nq9-1787494544982-bc7252591d0a

sin1:iad1::69k2q-1787494552245-e71728b2a2ff

Could you please inspect and repair the provider-side production alias / routing association for this project? The alias assignment control plane reports success, but traffic does not reach the current Production deployment.