We are seeing what appears to be an account-level deployment finalisation fault across two separate production projects in the same Veazy Hobby team. In both cases the verified build artifact is ready, but the deployment remains indefinitely in INITIALIZING and the production domain correctly remains on the previous live deployment.

Affected deployment 1

• Project: salvomigration
• Deployment: dpl_Ga5ak56xgALeGGVpqVf27GrrC1qz
• URL: https://salvomigration-2245yfqw9-veazy.vercel.app

Troubleshooting completed:

1. A normal production deploy remained in INITIALIZING with no build failure.
2. We removed that non-live attempt and retried from a clean committed worktree; same result.
3. vercel pull --environment production and vercel build --prod completed successfully locally.
4. We removed the stalled retry and deployed the verified prebuilt output using --prebuilt --prod; the retained deployment above has the same state.
5. Each build object reported READY, while deployment finalisation and custom-domain assignment never completed.

The existing live domain https://salvomigration.com.au remains safely on its previous deployment.

Affected deployment 2

• Project: salvo-os
• Deployment: dpl_2c1qHwAwZeLd3Vpz82Z9Fe3VgQsX
• URL: https://salvo-mvh42rrmd-veazy.vercel.app

This is also a verified local prebuilt production artifact. It remains in INITIALIZING with no error or build logs. The production domain https://os.salvomigration.com.au remains safely on deployment dpl_GHAuLYLmzRBxcf6cEMejzmXsEbs5.

Vercel Status reports all systems operational. Because this reproduces across two projects using verified local prebuilt artifacts, it does not appear to be an application build failure.

Could Vercel investigate and repair the deployment finalisation state for this team/account? Please do not cancel, promote, or alter either existing live production deployment while investigating.