Project: reveries-campaign Domain: campaign.reveries.kr
The custom domain is attached to the correct Vercel project and shows Valid Configuration in the dashboard.
DNS verification succeeds:
vercel domains verify campaign.reveries.kr --project reveries-campaign
returns:
Success! Valid Configuration: campaign.reveries.kr is configured and verified for project reveries-campaign
The latest production deployment is Ready and is already the current Production deployment.
I have already tried all of the following:
- Verified DNS successfully
- Deployed again with vercel --prod --force
- Confirmed the deployment is the current Production deployment
- Removed and recreated the alias
- Removed campaign.reveries.kr completely from Project Domains
- Waited more than 2 minutes
- Added campaign.reveries.kr back to the Production environment
- Confirmed the dashboard again shows Valid Configuration
However:
curl -I https://campaign.reveries.kr/
still returns:
HTTP/1.1 404 Not Found X-Vercel-Error: NOT_FOUND
The generated Vercel deployment URL exists and redirects to Vercel SSO because Deployment Protection is enabled.
Vercel Agent also indicated that this may be a desynchronized edge routing entry.
At this point all standard self-service troubleshooting steps have been exhausted.
Could a Vercel team member please inspect and rebuild or repair the edge routing entry for campaign.reveries.kr?
This appears to be a platform-level routing issue rather than an application or DNS configuration issue.
edit
Additional diagnostic information:
I tested the current Production deployment directly with authenticated vercel curl, which generated a Deployment Protection bypass token successfully.
Current Production deployment:
reveries-campaign-b4wkpa1e9-seongsu0306-1361s-projects.vercel.app
vercel ls reports:
Status: Ready Environment: Production
vercel inspect reports:
Deployment ID: dpl_BmybYWXNn3XrNYR9caS1zc6nHQaN
Target: production
Status: Ready
Aliases:
- campaign.reveries.kr
- reveries-campaign.vercel.app
- reveries-campaign-seongsu0306-1361s-projects.vercel.app
However, authenticated:
vercel curl https://reveries-campaign-b4wkpa1e9-seongsu0306-1361s-projects.vercel.app/ -I
still returns:
HTTP/1.1 404 Not Found X-Vercel-Error: NOT_FOUND
The build logs also confirm that the application built successfully:
- Next.js 16.3.4 compiled successfully
- TypeScript completed successfully
/route exists- all application routes were generated
- Build Completed in /vercel/output
- Deploying outputs...
- Deployment completed
- final status: Ready
So the generated Deployment URL itself returns a platform-level NOT_FOUND even though the deployment is Ready and the build output contains /.
This now appears to be a deployment serving / edge routing registration issue rather than a DNS or application routing problem.
Could a Vercel engineer inspect the deployment-to-edge routing registration for:
Project: reveries-campaign Deployment: dpl_BmybYWXNn3XrNYR9caS1zc6nHQaN Domain: campaign.reveries.kr
