Is CM.com Down Right Now? Check if there is a current outage ongoing.

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

Several of our products are affected by the ongoing major Google outage.

We are currently investigating an issue where Global Ticketing shops are unreachable.

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

This incident has been resolved.

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

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

We are investigating elevated error rates for Conversational AI Cloud. Sessions may impacted.

This incident has been resolved.

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

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

We are investigating elevated error rates for Conversational AI Cloud. Sessions may impacted.

This incident has been resolved.

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

Due to this issue we are also noticing incoming and outgoing Traffic are not being processed to and from Mobile Service Cloud. E-mail is unaffected.

We are continuing to investigate this issue.

We are continuing to investigate the Issue

We're noticing that messages from the Conversational Router to the Scripted Chatbot are being deadlettered, meaning the Scripted Chatbot is not receiving these messages. We're currently investigating.

This incident has been resolved.

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

Due to this issue we are also noticing incoming and outgoing Traffic are not being processed to and from Mobile Service Cloud. E-mail is unaffected.

We are continuing to investigate this issue.

We are continuing to investigate the Issue

We're noticing that messages from the Conversational Router to the Scripted Chatbot are being deadlettered, meaning the Scripted Chatbot is not receiving these messages. We're currently investigating.

This incident has been resolved.

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

We are experiencing issues with our delivery reports for SMS in South Africa. Messages are delivering, but the status reports are not updating correctly.

This incident has been resolved.

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

We are experiencing issues with our delivery reports for SMS in South Africa. Messages are delivering, but the status reports are not updating correctly.

This incident has been resolved.

The Mobile Network Operator - Orange - 20801 - is currently witnessing a partial outage.

This incident has been resolved.

The Mobile Network Operator - Orange - 20801 - is currently witnessing a partial outage.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be performing maintenance on our platform's Login Service to enhance performance and stability. This scheduled maintenance will take place on the 27th of May, 2025, between 08:30 AM and 09:00 AM CEST.This will break current sessions, causing users to be logged out. A re-login and a page refresh should resolve any issues.

This incident has been resolved.

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

We are investigating some reports of a partial inbound mail failure, where mail is not delivered in Agent Inbox.

This incident has been resolved.

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

We are investigating some reports of a partial inbound mail failure, where mail is not delivered in Agent Inbox.

This incident has been resolved.

We are currently experiencing packetloss for both Inbound 10 and Inbound 20.Our engineers are looking into this.

This incident has been resolved.

We are currently experiencing packetloss for both Inbound 10 and Inbound 20. Our engineers are looking into this.

This incident has been resolved.

We are currently investigating an issue where users loading into the Agent Inbox might see a blank page.

This incident has been resolved.

We are currently investigating an issue where users loading into the Agent Inbox might see a blank page.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Dear partners, On Thursday morning, 22 May 2025, cm.com/IPP will perform extensive database maintenance.The maintenance will take place between 05:00 AM and 06:00 AM CEST (Central European Summer Time) to minimize the impact on our customers.Please be aware that there will be a brief period during this maintenance window when our gateway will be inaccessible. We apologize for any inconvenience this may cause and appreciate your patience.

This incident has been resolved.

The issue has been resolved, and we are continuing to monitor the situation closely. Should the issue persist, please refresh the application and try again.

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

We are investigating an issue where customers are not able to receive inbound calls or place outbound calls.

This incident has been resolved.

The issue has been resolved, and we are continuing to monitor the situation closely. Should the issue persist, please refresh the application and try again.

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

We are investigating an issue where customers are not able to receive inbound calls or place outbound calls.

This incident has been resolved.

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

Network has recovered and is fully reachable again. Our network was unreachable for about 4 minutes We are still identifying the cause.

We are currently investigating this issue.

This incident has been resolved.

Network has recovered and is fully reachable again. Our network was unreachable for about 6 minutes We are still identifying the cause.

We are continuing to investigate this issue.

We are currently investigating the issue and will update on scope at a later time.

This incident has been resolved.

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

We are observing degraded performance for Address Book. We're working on a fix that we expect to be live shortly.

This incident has been resolved.

Network has recovered and are fully reachable again. Our network were unreachable for about 6 minutes We are still determining the cause.

We are currently investigating the issue and will update on scope at a later time.

This incident has been resolved.

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

There is still some intermittent delay in the delivery of MT traffic. The operator is continuing their investigation.

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

Dutch operator Odido (20416) 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.

Regulations in Belgium to prevent phone number spoofing require operators and aggregators to block any local Belgian traffic for entities that do not have a registration in Belgium. This means that you can only use a +32 local number if your company has a registration and business address in Belgium. Via this message we inform you that we will reject and block any Voice calls using +32 numbers if the company profile is missing from our records. This automated blocking will become effective April 1st. Information about how to fill on a company profile can be found here: https://knowledgecenter.cm.com/kc/anti-spoofing-belgium

A fix is implemented and performance is stable.

The performance is stable and we are actively monitoring the application while working on a structural fix.

We possibly identified the root cause and are currently preparing a hotfix. The next update will be around 12:30.

The issue is being actively investigated.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results

we are currently investigating an issue leading to different behaviours such as the app not loading, loading slowly or customer profiles that will not load.

This incident has been resolved.

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

HALO processing issues incoming traffic. Our engineers have identified the issue and a fix is being implemented

The issue has been resolved and all trx have been restored.

we are experiencing payment processing issues with the webECR integration, we are investigating.

This incident has been resolved.

The issue has been fixed and we are currently monitoring the solution.

We are continuing to investigate this issue.

We are currently experiencing problems with incoming media messages from WhatsApp. We are engaging with META to try and pinpoint the issue.

This incident has been resolved.

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

We are experiencing degraded performance which is currently being investigated.

This incident has been resolved.

We have resolved the rendering issue, and buttons now display as intended. Please note that click tracking in Outlook is currently unavailable. Our team is actively working on a solution to restore full tracking functionality as soon as possible.

For all email campaign templates created or amended since 08:00 CEST this morning the buttons will not show text when sending out a campaign. This issue is under investigation and we are in contact with our external partner.

This incident has been resolved.

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

The issue has been identified and our engineers are working on a fix.

We've identified an issue within the Admin portal that impacts the user administration functionality. Actions such as inviting, deleting, or re-inviting users to Conversational AI Cloud are temporarily unavailable. Our team is investigating the issue and working on a resolution. We appreciate your patience and will provide updates as soon as more information is available.

This incident has been resolved.

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

We have implemented a temporary fix that resolved the issue. In the meantime, we are working on a permanent fix to prevent the issue from recurring.

Unfortunately the solution to the identified root cause has not yet been found and the implemented fix has not solved the entire issue. Together with our suppliers, we are looking at multiple solutions.

We have identified the root cause of the issue and are implementing a fix. Multiple test calls made show no further issues.

We are continuing analyzing the possible root cause of the issue. Regular updates will be shared during the day.

We are isolating the problem and making necessary measures to contain the impact. We will continue to work on solving the issue.

We are working together with our Voice Engineering en Infra team to pinpoint the exact cause of the issue. At this moment we are excluding possible systems in the call flow as multiple domains are involved.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating quality issues on our voice trunks. This is affecting both inbound and outbound.

This incident has been resolved.

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

We are currently investigating this issue.

Sign by CM.com experienced an interruption, causing some documents to not be signed properly. The issue has been resolved, and the service is back to normal as of 2025-04-11 16:05 CEST. We are working on next steps to digitally sign the impacted documents and will send out further communication next week. Thank you for your patience!

This incident has been resolved.

Transactions processing to Omnipay are restored. Monitoring results.

We are unable to process transactions to Omnipay at the moment. We are investigating the issue.

This incident has been resolved.

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

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

We are experiencing degraded performance which is currently being investigated.

This incident has been resolved.

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

We are currently experiencing downtime concerning HALO Studio. We are investigating the issue.

KPN has resolved the issue since 13:00.

We have been informed by KPN that the issue was resolved. We can confirm that we see significantly reduced packet loss since ~12.15 KPN indicates the solution was found outside their domain but did not specify further. We will continue to monitor for a few hours.

KPN continues investigating this issue. We are expecting an update from KPN around 12:00 CET.

KPN continues investigating this issue.

Please be aware that we are still experiencing packet loss and quality issues on inbound KPN Calls originating on some parts of the NL telephony network and we are waiting on the involved party to solve the issue. This is currently under investigation by KPN.

This incident has been resolved.

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

We're currently experiencing issues with the Conversational AI Cloud dashboards. This unfortunately causes these dashboards to be unavailable. Our developers are currently investigating. Thank you for your patience.

This incident has been resolved.

FR - Orange - 20801 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.

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

We are experiencing degraded performance with some of our supplier connections. This is being investigated.

This incident has been resolved.

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

We're currently experiencing issues with the Conversational AI Cloud dashboards. This unfortunately causes these dashboards to be unavailable. Our developers are currently investigating. Thank you for your patience.

This incident has been resolved.

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

We're currently experiencing issues with the Conversational AI Cloud dashboards. This unfortunately causes these dashboards to be unavailable. Our developers are currently investigating. Thank you for your patience

This incident has been resolved.

Queue processing is progressing well without any issues. We will continue to monitor the situation closely to ensure optimal performance before closing the issue.

Queues are emptying as anticipated, and events are being processed with workflows being triggered accordingly. Please note that the duration of this process may vary based on the queue size specific to your tenant.

The queued data is currently being processed in a stable way, it will need time to catch up the past 24h.

We have implemented fixes to restore the system and are closely monitoring the progress. The queued data is being processed. We will provide updates as we move forward.

We have identified the culprit causing the issue and are working on restoring our services with our service partner. For the past 16 hours, our customers have been able to log in to CDP and use the system, but without access to recent data from the past 24 hours.

The primary cause of the outage lies with our cloud service provider. We are actively coordinating with them to expedite resolution and are closely monitoring their progress, as our recovery depends on their actions.

We are persistently working, alongside our cloud provider, to address the issue impacting our primary database. Once we have more information, we will provide more updates.

We are diligently continuing our efforts and have identified some promising leads in collaboration with our cloud provider.

We are actively working with multiple teams together with our cloud provider to identify and resolve the issue affecting our primary database. Our priority is to restore full functionality as quickly and efficiently as possible.

We are experiencing an outage for our primary database. All incoming events are being fail overed to our secondary database however due to this events and workflows are not being processed. We are investigating this issue.

This incident has been resolved.

Based on our efforts from yesterday, the system has stabilized overnight and the system is now operating as expected. Our team is actively monitoring the system to ensure continued stability and is focused on retrying any failed event data to keep all processes up-to-date and accurate.

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

Following the latest update, we have decided to proceed with another system maintenance window. Although errors are decreasing, we aim to fine-tune and expedite this improvement further to enhance performance. Please note that during this maintenance window, no events will be processed, and workflows will not be triggered. We will perform this maintenance between 19:00 and 20:00 CET time.

We observe a positive decrease in errors and queues following our recent maintenance window. Our team will closely monitor these encouraging trends over the next hour to assess whether further emergency maintenance would be beneficial. We will provide our next update in 60 minutes or sooner if significant developments occur.

Our ongoing database maintenance is progressing successfully. However, to ensure we achieve the best possible outcome, we require an additional hour beyond our original schedule. We now anticipate concluding the maintenance around 16:00.

As mentioned in the previous update, we will perform maintenance between 14:00 and 14:30 CET time. During this timeframe no events and workflows will be processed, after the maintenance window this will be picked up again and continue.

We are going to perform maintenance on our systems to help mitigate the ongoing issues. During this timeframe no events and workflows will be processed, after the maintenance window this will be picked up again and continue. Please understand we are doing everything we can to mitigate the ongoing issues with the help of several partners. As soon as we know the timeframe we will post another update, but please be aware this is upcoming.

Update: We are actively working together with our third-party providers to resolve the ongoing issues. Our team is fully committed to restoring normal operations as quickly as possible, we are sorry for the inconvenience.

We are working on implementing the solution to resolve these issues.

We have identified the issue causing delays, as well as failures in processing events and syncing segments to the address book. We are working on implementing a solution to resolve these issues. No events have been lost during this issue, and failed events will be reprocessed once the fix is implemented.

We are continuing our investigation into this issue.

We are experiencing delays in data processing and loading times. Our team is actively investigating the issue.

This incident has been resolved.

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

We are currently investigating a potential issue with the WhatsApp integration regarding dialog options.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

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

Degraded performance resulting in delayed messages. Being investigated.

This incident has been resolved.

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

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently facing network traffic load issues. There is degraded performance for a small part of out traffic. We shall revert with an update in 30 mins.

This incident has been resolved.

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

There is currently degraded performance resulting in delayed messages. The issue is being investigated.

The issue at our supplier is solved. Sign is fully operational again. All queued dossiers were successfully processed.

We are currently experiencing delays in the delivery of signed documents, due to our certificate supplier experiencing an outage. Sign is available, but completed dossiers are queued. The signing of queued documents will automatically resume when the outage is resolved.

This incident has been resolved.

We are experiencing performance issues with our MSC agent inbox. We are investigating the issue.

This incident has been resolved.

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

We are currently investigating an issue with the Agent Inbox.

This incident has been resolved.

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

We are currently investigating reports about inbound calls being disconnected and not arriving in Agent Inbox.

This incident has been resolved.

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

We are currently investigating this issue.

This incident has been resolved.

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

We are investigating an issue that impacts in and outbound native voice traffic.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

Bouygues Telecom has confirmed there is an ongoing incident which is being investigated.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented, users need to refresh the application.

The issue has been identified and we expect everything will be working correctly again in 20 minutes.

we are continuing to investigate the issue, we expect the issue to be fixed in approximately 30 minutes

We have also received complaints regarding Native Voice, we have added this to the investigation.

We are currently investigating an issue regarding connection issues with the Agent Inbox, The realtime connection bar is displayed. Messages within conversation might not be delivered instantly.

This incident has been resolved.

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

Serialisation of the mentioned channel names (converting the channel names to text) within the Conversational Router is broken because of specific library updates that were done. We are working on fix for this regression.

It seems most likely the impacted channels are limited to Apple Business Chat, Telegram Messenger and Facebook Messenger.

Caused by a change put on production the 5th of February messages sent out over specific channels are not reaching their destination. What channels exactly are impacted is currently being investigated and the resolution of this impediment has our priority.