Cmcom の障害履歴

We are currently investigating unresponsive or slow loading Agent Inbox.

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

This incident has been resolved.

Currently the messaging platform performance is degraded. Messages are still accepted and will be processed with a delay. We are working to resolve the issue.

The cause if the issues has been identified. We are currently working on a solution to resolve the degraded performance.

We are carefully deploying a fix to resolve the problem. Traffic processing performance can degrade and improve again during the rollout.

Fixes have been implemented and traffic processing has resumed. Queued traffic is being processed at the moment. We are monitoring the situation.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We experienced some delays in the processing of tasks. The cause has been identified and fixed. All queued tasks have been processed and traffic is up to date again. We continue to monitor the traffic.

This incident has been resolved.

Email Gateway is currently experiencing a service disruption. Our team is aware of the issue and actively working on a fix. As a result, emails sent by Sign are not being delivered at this time. All affected emails will be sent automatically once the service disruption is resolved.

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

Open and Click tracking has been temporarily disabled.

This incident has been resolved.

Email Gateway is currently experiencing a service disruption. Our team is aware of the issue and actively working on a fix. As a result, emails sent by Sign are not being delivered at this time. All affected emails will be sent automatically once the service disruption is resolved.

The issue has been identified and a fix is being implemented.

The Email Gateway service disruption has been resolved. All Sign emails have been sent.

On Tuesday, June 30th, 2026 between 18:15 and 21:13 CEST, some API calls to api.cm.com were affected by intermittent 500 Internal Server errors. The majority of traffic was unaffected, with the impact limited to specific endpoints and certain servers. Timeline: • 18:15 CEST — Incident began • 21:13 CEST — Incident fully resolved • Total duration: ~2 hours 58 minutes Root cause: A server issue caused a portion of API calls to fail intermittently. The affected functionality was limited to Triggered Campaigns/Emails. We apologize for any inconvenience this may have caused.

We are currently investigating this issue.

This incident has been resolved.

On July 1st, 2026 between 10:00 AM and 23:59 CEST, and continuing into July 2nd, 2026 between 00:01 and 10:00 AM CEST, a total of approximately 40,000 emails were not delivered due to an incident affecting our email sending infrastructure, impacting some accounts. Timeline: • July 1st, 10:00 AM – 23:59 CEST: ~33,000 emails affected • July 2nd, 00:01 – 10:00 AM CEST: ~7,000 emails affected Unfortunately, the affected emails were not recoverable and will not be delivered. We sincerely apologize for the impact this has caused.

Messaging Insights is currently experiencing a service interruption. We are looking into this issue.

This incident has been resolved.

Dutch operator Vodafone (20404) is experiencing an issue on their platform which affects MT/MO SMS traffic and Status Reports. The operator is investigating the issue.

We are continuing to work on a fix for this issue.

This incident has been resolved.

Customers might experience trouble scanning or selling the Museumkaart, Rotterdampas, VIP kaart, e.o. This issue is caused 3th party verdor Intersolve. More information via: https://www.status.intersolve.com/

This incident has been resolved.

France - SFR France - 20810 is experiencing an issue on their platform which affects MT/MO SMS traffic and Status Reports. The operator is investigating the issue.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

We are currently investigating an issue that causes a delay in handovers and the processing of tasks for Agent Inbox. All in and outgoing traffic is delayed. Our product team is continuing to investigate this issue.

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

This incident has been resolved.

We have confirmed reports of issues with our Voice APIs, apps and downstream services: Service Cloud Native Voice and HALO Voice (upon transfers to human agents) Engineers are investigating the issue. We will provide updates in 30 minutes or as events warrant.

Our Voice and Network Engineers are continuing to investigate this issue.

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

This incident has been resolved.

On Jun 25 between 05:30 and 09:20 CEST, some customers experienced an issue where emails were unable to be delivered. The root cause was identified as a misconfigured product recommendations integration that had lost its connection to the database. The connection has since been restored and email delivery is back to normal. We apologize for the inconvenience.

This incident has been resolved.

The Belgium operator Base and Telenet has scheduled a planned maintenance on their SMSC on 25 June between 00:00 – 09:00 AM (UTC+2). All MT/MO traffic will be queued on our platform and will be processed when the maintenance has been finished.

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

This incident has been resolved.

We are currently investigating an issue concerning NXTGN Ticketing

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

This incident has been resolved.

We are currently investigating an incident concerning the delayed delivery of OTP emails for logging in into the online portal.

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

This incident has been resolved.

We are currently experiencing delays in triggers and direct mail send via API. These delays are the result of queueing that happened due to an incident earlier today (https://status.cm.com/incidents/scwkch28t8jy). We expect these delays to be resolved within an hour. We apologize for the inconvenience.

This incident has been resolved.