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.

Hi, this looks like orphaned deployments left behind after the project and repository were deleted.

Since they still appear as “Production” but return 404 and have no available actions in the UI, it suggests the deployments are no longer linked to a valid project context. In other words, they seem to be dangling records without a parent project.

This might indicate that the deletion flow didn’t fully clean up associated deployments, leaving them in an inconsistent state.

It could be worth checking whether these deployments still reference a projectId or teamId that no longer exists, and if so, cleaning them up from the backend.

Hope this helps point in the right direction

thank you - that’s exactly right - waiting now on someone from @vercel to correct at the backend :-)