Hello Vercel Support,

I have a production custom-domain routing issue with my ViaFinds project.

My Next.js production deployment is READY and the application works correctly, but the production custom domain returns a Vercel platform-level 404.

Project: ViaFinds

Production deployment: dpl_Dkfzsq18gTwE2xH9zDqGDQqtJJAS

Production deployment URL: https://viafinds-ds5k160yv-noman-yousufs-projects.vercel.app

Affected domain: https://www.viafinds.com/

Observed response:

HTTP/1.1 404 Not Found Server: Vercel X-Vercel-Error: NOT_FOUND X-Vercel-Id: bom1::tnh6c-1787980223926-4bdafad70a20

The Vercel API confirms that www.viafinds.com is correctly aliased to the current production deployment.

viafinds.com correctly returns 308 and redirects to www.viafinds.com.

Deployment Protection is Standard Protection, and the dashboard explicitly shows www.viafinds.com as publicly accessible.

The generated deployment URL is protected by SSO as expected, but the custom production domain should be public.

I have already verified:

• Next.js framework detection
• Production deployment status
• Production target
• Domain verification
• Domain-to-deployment alias
• DNS
• Build logs
• Application homepage

Please investigate the Vercel Edge routing/data-plane state for www.viafinds.com and compare it with the control-plane alias.

Could you please refresh/re-provision the production edge routing entry if necessary?

Thank you.