Sifflet - Notice history

This incident has been resolved.

As previously stated, the current incident was an aftermath of the incident that occurred on the 17th of February (and that was resolved on that day). The detection of this residual impact was delayed by the low volume of impacted monitors compared with the total volume of monitors orchestrated by our platform. We've implemented corrective measures on our alerting systems to improve our detection of such events.

We deployed a fix of the issue, and are monitoring that the 7 monitors are now running according to their schedules.

We identified the cause of the issue, caused by a failure in the behavior of our orchestration framework that happens in some very specific situations, created by the incident that occurred on the 17th of February: https://siffletdata-status.com/cmlqprxwm01clmg0v51e5vj9h.

The fix for this issue will be deployed in production on Thursday 26th of February.

We've also clarified the impact of the incident: only one of the tenants of the cell is impacted, and only 7 scheduled monitors of this tenant are impacted (meaning they are no longer running according to their schedules). The customer associated with this tenant has already been contacted by our team.