CM.com Outage History

CM.com is up right now

Pingoru has recorded 169 incidents for CM.com: 169 in the last 12 months and 42 in the last 90 days.

Source: status.cm.com

169incidents recorded
169last 12 months
42last 90 days
4 hourstypical duration
Incidents per month
02040AprMayJunJulAugSepOct19
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct15%
Pingoru began tracking CM.com in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202630117 of 720 (16%)
May 20261344 of 744 (6%)
June 20261950 of 720 (7%)
July 20261791 of 744 (12%)
August 2026834 of 744 (5%)
September 20261554 of 720 (7%)
October 20261988 of 591 (15%)

Incidents, newest first

Minor January 26, 2026 onload, Halo - not responding. 1h 18m Studio, HALO Voice, Inference, Analytics API

Started Jan 26, 2026, 09:02 AM UTC· resolved Jan 26, 2026, 10:20 AM UTC

  1. investigating Jan 26, 2026, 09:02 AM UTC

    We are currently investigating an issue where onload and Halo are not responding.

  2. monitoring Jan 26, 2026, 09:26 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 26, 2026, 10:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 24, 2026 HALO - Issues with Inference 3h 18m Inference

Started Jan 24, 2026, 01:48 PM UTC· resolved Jan 24, 2026, 05:07 PM UTC

  1. investigating Jan 24, 2026, 01:48 PM UTC

    We are currently experiencing issues with inference and are actively investigating. This impacts all agents across customer environments.

  2. monitoring Jan 24, 2026, 01:55 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 24, 2026, 05:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 22, 2026 Operator Service Interruption - BE- Telenet- 20605 2h 12m Mobile network operators: Belgium

Started Jan 22, 2026, 02:17 PM UTC· resolved Jan 22, 2026, 04:30 PM UTC

  1. investigating Jan 22, 2026, 02:17 PM UTC

    Belgium operator Telenet is experiencing an issue on their platform which affects MT SMS traffic. The operator is investigating the issue.

  2. monitoring Jan 22, 2026, 02:49 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 22, 2026, 04:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 21, 2026 Halo logging incident –

Started Jan 21, 2026, 08:00 AM UTC· resolved Jan 21, 2026, 08:00 AM UTC

  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.

Read the full incident report →

Minor January 20, 2026 Issue with inbound media on WhatsApp 1h 7m WhatsApp Business

Started Jan 20, 2026, 03:32 PM UTC· resolved Jan 20, 2026, 04:40 PM UTC

  1. investigating Jan 20, 2026, 03:32 PM UTC

    We are investigating an issue with incoming media (images/video) messages on WhatsApp.

  2. resolved Jan 20, 2026, 04:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 17, 2026 Mobile Service Cloud - Duplicate messages 3h 14m Scripted Chatbot

Started Jan 17, 2026, 12:10 PM UTC· resolved Jan 17, 2026, 03:25 PM UTC

  1. investigating Jan 17, 2026, 12:10 PM UTC

    We are currently investigating an issue where messages may appear to be duplicated and snoozed chats could reappear.

  2. monitoring Jan 17, 2026, 12:29 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. identified Jan 17, 2026, 01:50 PM UTC

    The previous fix did not work, we are working on a new fix.

  4. monitoring Jan 17, 2026, 02:20 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jan 17, 2026, 03:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 14, 2026 Email Processing Service Interruption 3h 36m Email Campaigns

Started Jan 14, 2026, 06:09 AM UTC· resolved Jan 14, 2026, 09:45 AM UTC

  1. investigating Jan 14, 2026, 06:09 AM UTC

    We are investigating a service interruption on email processing.

  2. monitoring Jan 14, 2026, 07:04 AM UTC

    A fix has been implemented and we are now processing the backlog. We expect to be completely done with this around 8.30 CET.

  3. monitoring Jan 14, 2026, 08:12 AM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Jan 14, 2026, 08:27 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jan 14, 2026, 09:45 AM UTC

    This incident has been resolved.

  6. postmortem Jan 14, 2026, 01:06 PM UTC

    **Mobile Marketing Cloud – Delay in Email Delivery** We experienced issues with email delivery between January 13, 2026, at 17:37 CET and January 14, 2026, at 07:35 CET. During this timeframe, both triggered and newsletter email campaigns were delayed in their send-out process. **Root Cause:** This issue was introduced as an unintended effect of a recent maintenance project. A specific service responsible for email delivery stopped functioning, which prevented all emails from completing the sending process. As a result, these requests were queued in our background service, causing delays in both email sends and status reports. Current Status: As of 07:35 CET on January 14, 2026, the issue has been resolved. All queued emails have been successfully delivered, and the email routing service is fully operational. Key Takeaways: We’ve detected a gap in our alerting system, which we will investigate and resolve to ensure quicker detection of similar issues in the future. Additionally, our development team has already created a permanent code fix to address the root cause of this issue and will be rolled out soon to prevent this issue from recurring. We acknowledge that such incidents have occurred more frequently in these past few days. We'll be taking additional measures to intensify the monitoring efforts on our side. We sincerely apologize for any inconvenience this may have caused.

Read the full incident report →

Minor January 13, 2026 MSC - Performance Degradation 1h 12m Agent Inbox, SMS - Regular, E-Mail, WhatsApp Business and 5 more

Started Jan 13, 2026, 02:20 PM UTC· resolved Jan 13, 2026, 03:32 PM UTC

  1. investigating Jan 13, 2026, 02:20 PM UTC

    There is currently delayed delivery of incoming and outgoing messages and performance degradation in the app. We are investigating this issue.

  2. investigating Jan 13, 2026, 02:23 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jan 13, 2026, 02:25 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jan 13, 2026, 03:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 13, 2026 Operator Service Interruption - FR - SFR - 20810 4h 53m Mobile network operators: France

Started Jan 13, 2026, 12:39 AM UTC· resolved Jan 13, 2026, 05:32 AM UTC

  1. investigating Jan 13, 2026, 12:39 AM UTC

    FR - SFR - 20810 is experiencing an issue on their platform which affects MT/MO SMS traffic and Status Reports. The operator is investigating the issue. Traffic is being queued on our end until the issue is resolved.

  2. resolved Jan 13, 2026, 05:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 8, 2026 Mobile Marketing Cloud - Triggered Campaign Functionality – Email Campaigns

Started Jan 08, 2026, 06:40 PM UTC· resolved Jan 08, 2026, 06:40 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →