The issue was caused by an incomplete production deployment. Part of a related code change was deployed successfully, but another required part was not yet included in the production release. This caused the application startup process to fail during deployment, which prevented the latest update from completing normally.
The issue did not indicate a security breach, data loss, or unauthorized access. Our database remained healthy throughout the incident, and the failure occurred during application startup rather than during data processing or storage operations.
We resolved the issue by deploying the missing application changes and improving our deployment process so future releases are tied to the exact verified code revision, rather than any server-local branch state. We also added stronger deployment logging so startup failures will surface immediately with clearer diagnostics.
To reduce the chance of recurrence, we are tightening our release validation process, improving deployment consistency checks, and strengthening safeguards around multi-file production changes that must ship together.