Removed domain still attached to Vercel's CloudFront — DEPLOYMENT_NOT_FOUND (papyrustrade.xyz) - Help

Hi Vercel team,

I removed papyrustrade.xyz from our team (Hobby) and deleted the project, but the apex domain is still attached to a Vercel-managed CloudFront distribution, so all traffic still lands on Vercel's edge and returns 404 DEPLOYMENT_NOT_FOUND.

What I've verified:

Our team has 0 domains and 0 projects (/v5/domains → empty; /v5/domains/papyrustrade.xyz → not_found).
DNS is on Route 53 and points to our own CloudFront distribution (confirmed via public resolvers).
Responses for papyrustrade.xyz carry server: Vercel and x-vercel-error: DEPLOYMENT_NOT_FOUND, without the via / x-amz-cf-id headers our own distribution adds.
AWS list-conflicting-aliases shows papyrustrade.xyz is attached to a distribution in an external AWS account (******900156), not ours. AWS can't move an apex alias cross-account unless the source releases it.

Support case CSE_01acxsZlMUvANORT was closed as a Hobby technical request, but this isn't a configuration question: it's a removed domain that wasn't released on Vercel's side (same issue as thread 50143).

Could someone from the Vercel team release papyrustrade.xyz (and any associated certificate) from the edge network? Thanks!

There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

https://community.vercel.com/t/debugging-404-errors/437

Vercel Community

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are...

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Update: I tried re-adding and removing the domain to force a cleanup.

Created a new project on this team and added papyrustrade.xyz. It verified immediately (the domain config API reported configuredBy: http, i.e. requests for the domain are still reaching Vercel's edge).
Then removed it from the project, deleted the team domain, and deleted the project.
10+ minutes later, AWS list-conflicting-aliases still shows papyrustrade.xyz attached to the external distribution, and the domain still returns server: Vercel / DEPLOYMENT_NOT_FOUND.

There is also a system certificate for papyrustrade.xyz (cert_ssDTi5EdS0SiGdilsrDdLYr2, autoRenew: true) that can't be deleted (cert_deletion_denied).

Could someone on the Vercel team release the domain and this certificate from the edge network? Thanks.

Hi Vercel team,

What I've verified:

Our team has 0 domains and 0 projects (/v5/domains → empty; /v5/domains/papyrustrade.xyz → not_found).
DNS is on Route 53 and points to our own CloudFront distribution (confirmed via public resolvers).
Responses for papyrustrade.xyz carry server: Vercel and x-vercel-error: DEPLOYMENT_NOT_FOUND, without the via / x-amz-cf-id headers our own distribution adds.
AWS list-conflicting-aliases shows papyrustrade.xyz is attached to a distribution in an external AWS account (******900156), not ours. AWS can't move an apex alias cross-account unless the source releases it.

Could someone from the Vercel team release papyrustrade.xyz (and any associated certificate) from the edge network? Thanks!