On June 4, AlertOps experienced a system-wide issue causing alert escalations to persist even after alerts were assigned or closed. As a result, users continued to receive escalation notifications despite taking action on those alerts.
This issue was caused by a code regression that disrupted the logic responsible for halting escalation threads when alerts are updated with a resolved or assigned state.