CM.com incident
Mobile Service Cloud - Issues answering native voice calls
Resolved after 1 hour 53 minutes, affecting Native Voice, on July 14, 2026.
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.
Affected components
Update timeline
- investigating Jul 14, 2026, 06:53 AM UTC
We are currently investigating this issue.
- identified Jul 14, 2026, 07:20 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 14, 2026, 07:39 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 14, 2026, 08:47 AM UTC
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.
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.
Amazon Web Services