Service instability and outage.
Timeline · 1 update
- resolved Jul 30, 2024, 04:31 PM UTC
A package upgrade was necessary due to a vulnerability, requiring additional updates to other packages. During deployment, some services did not restart appropriately due to a usage change in a newer container version, which requires a restart after upgrades. This was the root cause: the container service was not restarted, and all containers were stopped. Our operating procedures have been updated to reflect the proper usage pattern for newer versions.