On March 18th, 2026, an internal misconfiguration caused some environments to re-attempt the latest deployment. This resulted in two outcomes:

1. For most environments this extra deployment failed early. This means your latest deployment status in the dashboard now says “failed” even though it previously had succeeded. Your live environment was not affected.

2. For a few environments that have public Github repositories, the deployment went through and your latest commit was built and deployed again. Usually this results in the exact same code being deployed, but if you had made changes over SSH/SFTP, those changes might have been overwritten. The state shown in the dashboard reflects this, your latest deployment will show “succeeded” with a new timing from today.

This issue only affects the most recent deployment, it does not affect any older or future new deployments, they work as expected.

This happened because we are working on improving deployment stability and this improvement was not tested properly with existing environments. We are very sorry for the inconvenience and we assure you that there are now several new automated tests in place to ensure this never happens again.