CM.com incident

Halo logging incident

Resolved on January 21, 2026.

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.

Started
Jan 21, 2026, 08:00 AM UTC
Resolved
Jan 21, 2026, 08:00 AM UTC
Duration
–
Detected by Pingoru
Jan 21, 2026, 08:00 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.

Your product runs on more than CM.com

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →