CM.com Incident History

This incident has been resolved.

A fix has been implemented and tasks are currently being processed without delays. We continue to monitor the results.

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

We are currently investigating an issue causing delay in processing tasks for the Agent Inbox

Over the past weekend, Visa reported an incident affecting one of their services, which has caused a delay in the payout of Visa transactions processed during this period. Current status: We expect to process the affected Visa payouts with a one-day delay, starting Tuesday. We are in continuous contact with Visa to have this incident resolved as quickly as possible, and will update this page as soon as new information becomes available. We apologize for any inconvenience this may cause.

This incident has been resolved.

DE - 1&1 - 26223 is experiencing an issue on their platform which affects MT/MO SMS traffic and Status Reports. The operator is investigating the issue. Traffic is queueing and will be delivered when it is resolved.

This incident has been resolved.

Due to import failures, the Mobile Service Cloud data has not been refreshed today, meaning it will only show data up to the day before yesterday. The problem should be resolved around 07:00 UTC tomorrow

What happened Today, some of our services experienced disruption following a release in which credentials for our Realtime service could not be read correctly during task processing. This had the potential to impact various parts of the platform, with the most significant effect on Native Voice Calls, which remained stuck in the queue and were not offered to available agents. Additionally, AI suggestions were not plotted in real time. By 09:39, the issue had been fully resolved and all services were restored to normal. What we are doing to prevent this in the future This issue was introduced by a hotfix that bypassed our standard test pipeline. Going forward, we will run core regression tests before any hotfix is released to production, ensuring issues like this are caught early. In addition, we are adding monitoring and alerting to detect this type of disruption earlier and respond more quickly. Closing Our apologies for the inconvenience caused. We will work diligently to prevent this from happening again.

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

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

We are currently investigating this issue.

This incident has been resolved.

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

We are currently investigating unresponsive or slow loading Agent Inbox.