Cmcom outage history

We are aware of an issue affecting wallboards in Mobile Service Cloud. Productivity wallboards may appear empty or not display up-to-date data. Instant and Native Voice wallboards are not affected. Our engineering team has identified a likely cause related to a recent release and is working on a fix.

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

This incident has been resolved.

Customers might experience trouble scanning or selling the Museumkaart, Vriendenloterij and potentially others. This issue is caused 3th party vendor. Intersolve. More information via: https://www.status.intersolve.com/

A fix has been implemented by Intersolve and are monitoring the results.

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

This incident has been resolved.

GB - O2 - 23410 is experiencing an issue on their platform which affects MT/MO SMS traffic and Status Reports. The operator is investigating the issue.

This incident has been resolved.

[France] - [Orange] - [20801] 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 investigate this issue.

This incident has been resolved.

We are currently investigating an issue that prevents users to create/update MO webhooks. Existing MO webhooks are not impacted.

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

A fix has been deployed and creating and updating MO webhooks should now work as expected. We are monitoring to confirm the issue is fully resolved. If you still experience problems, please contact our Support team.

This incident has been resolved.

Our engineering team is investigating the cause.

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

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

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

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

This incident has been resolved.

Due to delayed processing from an external source, a limited group of merchants may receive no payout or only a partial payout today. Other merchants are not affected. All missing amounts will be added to the payout of tomorrow

This incident has been resolved.

We are currently investigating this issue.

We have found the possible issue, performance is stabilizing.

Issue has been resolved. Open orders will be retried soon and tickets will be sent out for delayed orders. New orders experience no issues or delay.

Older orders are being processed and we are sending out tickets now.

An issue which caused processing delays on incoming conversations and emails has been identified and a fix has been applied. Processing is currently recovering. Our engineers are monitoring the results.

We are continuing to monitor for any further issues.

Update: Conversations and emails that could not be processed this afternoon are still being reprocessed. As the fix takes effect, queued messages will be released, so you may still see delays.

Resolved: Queues have been processed and the service is operating normally. We apologize for the inconvenience this may have caused. Kindly reach out to support in case you still experience any issues.

We’re currently experiencing degraded performance in Email Campaigns. Some users may be unable to open or duplicate campaigns, and campaign statistics and templates may fail to load or show error messages. Our team is actively investigating the issue.

We are continuing to investigate this issue.

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

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

We are continuing to monitor for any further issues.

This incident has been resolved.

We are currently experiencing delays in the synchronization of addressbook data between CDP and Addressbook. As a result, changes made in one system may take longer than usual to appear in the other. Our team is looking into the cause and we will share an update as soon as we know more.

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

This incident has been resolved.

We are currently experiencing delays in the synchronization of addressbook data between CDP and Addressbook. As a result, changes made in one system may take longer than usual to appear in the other. Our team is looking into the cause and we will share an update as soon as we know more.

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

This incident has been resolved.

We are currently investigating an issue where the payments portal seems to be unavailable.

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

This incident has been resolved.

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

This incident has been resolved.

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

This incident has been resolved.

We are investigating an issue with Mastercard transactions on CCV. Some Mastercard payments may be declined or fail to complete. The cause is an issuer issue on the CCV and Mastercard side. The CM.com platform is not affected.

The issue has been resolved. We see normal transaction authorizations.

Users are experiencing random 401 errors on authentication. We are working to resolve this issue. Refreshing the page (multiple times) can temporarily resolve the issue.

This incident has been resolved.

We are investigating an issue where part of the email campaign traffic to Microsoft-hosted mailboxes (Outlook, Hotmail, Live, Microsoft 365) and iCloud mailboxes is being rejected, resulting in an increased number of bounces. Delivery to other email providers is not affected.

We have made changes to our sending infrastructure and bounce rates have returned to normal levels. We apologize for the inconvenience.

We are experiencing an issue with the database cluster which is currently being investigated.

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

This incident has been resolved.