CM.com incident

Halo logging incident

Notice Resolved View vendor source →

CM.com experienced a notice incident on January 21, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jan 21, 2026, 10:37 AM UTC
Resolved
Jan 21, 2026, 08:00 AM UTC
Duration
Detected by Pingoru
Jan 21, 2026, 10:37 AM UTC

Update timeline

  1. resolved Jan 21, 2026, 10:37 AM UTC

    We're missing conversation logs from multiple tenants between yesterday 16:42 and this morning 08:57. The root cause has been isolated and our engineers have deployed a fix this morning at 08:57. Conversation were logged, but in a corrupted state. Due to the fact that logging still took place our alerts were not triggered. We've updated our alerting to prevent similar issues from reoccurring in the future.