Custom domains removed but still held by Vercel CloudFront after 48+ hours

Hello,

I removed fundfocus.capital and www.fundfocus.capital from the Vercel project fundfocus more than 48 hours ago. The Vercel dashboard now shows only fundfocus.vercel.app. The authenticated Vercel API confirms that the custom domains are removed. GET /v9/projects/{projectId}/domains returns only fundfocus.vercel.app, while GET /v6/domains returns an empty domains array. Authoritative DNS no longer points either hostname to Vercel.

However, AWS CloudFront still reports both exact aliases assigned to the same external distribution:

fundfocus.capital: distribution *******UKJ1IDS, account ******200621 www.fundfocus.capital: distribution *******UKJ1IDS, account ******200621

We configured AWS’s required TXT verification records and attempted an AWS-verified cross-account alias move. CloudFront returns:

InvalidAssociation: You don't have permission to move this domain name for this AWS account. The domain name is already in use.

Our AWS distribution and certificate are valid. The remaining blocker is the stale exact-domain association on Vercel’s CloudFront distribution. DNS propagation or cache flushing cannot resolve this CloudFront control-plane conflict.

Could a Vercel team member please remove the stale CloudFront aliases for fundfocus.capital and www.fundfocus.capital?

I can provide the Vercel project and team IDs privately if needed.

Thank you.

The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points.

https://vercel.com/docs/domains/troubleshooting

vercel.com

Troubleshooting domains

Learn about common reasons for domain misconfigurations and how to troubleshoot your domain on Vercel.

I’ve run into a similar issue with custom domains. Sometimes the old configuration or CDN cache can take longer to clear even after removing the domain. Checking the DNS records and waiting for propagation usually helps.