Escalations not progressing past first step during race conditions

Escalations

Operational

Resolved

Thanks for all your patience. We have now released a new fix on the escalation engine and we are monitoring the situation.

Please do reach out to us via live chat or support@spike.sh if you face any issues.

Jun 09, 2026 - 07:48AM (UTC)

Update

We have implemented a solution for the race condition and queuing issues. Currently in testing phase but it's looking promising.

Jun 09, 2026 - 07:00AM (UTC)

Update

We've identified the root cause, and we're trying out the best solution to fix this. Rest assured, we know that this is a one-off scenario but we want to continue to make sure that Spike is able to alert in all cases at all times.

Thanks for your patience.

Jun 08, 2026 - 06:14PM (UTC)

Identified

We've identified an issue where some escalation policies are not advancing beyond the first escalation step. The first responder is being notified correctly, but if they don't acknowledge, the alert is not moving on to the next person or step as configured.

We've traced this to a processing issue in our alert pipeline and are working on a fix now. Acknowledged and resolved alerts are unaffected. We'll post an update as soon as we have one.

Jun 08, 2026 - 02:52PM (UTC)

Components affected

Escalations

Reported on

Mon, Jun 8, 2026 2:52 PM (UTC)

Resolved at

Tue, Jun 9, 2026 7:48 AM (UTC)

Monday Jun 08, 2026