Customer Service

CM.com Status Page

We continuously monitor the status of our platform as well as external services we are using. If there are any interruptions in service, a note will be posted here.

For more information or any questions, please contact our Customer Service

Current information on Service Availability

All Systems Operational

About This Site

Subscribe to get real-time updates. Having trouble? Troubleshoot common issues in our Help Center.

Messaging Operational
Business Messaging API Operational
Smpp Operational
SMS - High Priority Operational
SMS - Regular Operational
WhatsApp Business Operational
Apple Messages for Business Operational
RCS Business Messaging Operational
Facebook Messenger Operational
Viber Operational
MMS Operational
Messaging Apps Operational
Texter Operational
LINE Notifications Operational
Mobile Push Operational
Instagram Messenger Operational
Voice Operational
Voice Platform - The Netherlands Operational
Voice API's Operational
Voice Apps Operational
Ticketing Operational
Seated Ticketing Operational
Ticketing NXTGN Operational
Your Ticket Provider Operational
Global Ticket / Ticketing Museum & Parks Operational
Scan app Operational
Conversational AI Cloud Operational
Production Gateway Operational
Admin Portal Operational
CMS Operational
Staging Gateway Operational
Reporting API Operational
Web Conversations Operational
Mobile Marketing Cloud Operational
Customer Data Platform Operational
Campaigns Operational
Pages Operational
Email Campaigns Operational
Voice Campaigns Operational
Address Book Operational
Tracedock Operational
Inspire Operational
Web Personalization Operational
Mobile Service Cloud Operational
Agent Inbox Operational
E-Mail Operational
Webchat Operational
Scripted Chatbot Operational
Customer Data Platform / CDP Operational
Native Voice Operational
Reporting Operational
Central Services Operational
Analytics Portal Operational
Conversational Router Operational
Online Payments Operational
Checkout Operational
CM Payments API Operational
iDEAL QR Operational
DocData PSP Operational
AutoCollect Operational
High Speed iDeal Gateway Operational
Payments Portal Operational
HALO Operational
Studio Operational
HALO Voice Operational
Inference Operational
Analytics API Operational
Electronic Cash Register Operational
Management Portal Operational
Electronic Cash Register Operational
In Person Payments Operational
Gateway Operational
Merchant Portal Operational
Processor Connections Operational
Verification & Sign Operational
Sign Operational
Seal Operational
iDIN Operational
IBAN Verification Operational
ID Scan Operational
OTP as a Service Operational
Mobile Identity Operational
Email Gateway Operational
Email Gateway API's Operational
Email Gateway App Operational
Platform Operational
Platform Apps Operational
Website Operational
Appmiral Operational
API Operational
Platform CMS Operational
External Services Operational
Mobile network operators: Netherlands Operational
Mobile network operators: Belgium Operational
Mobile network operators: France Operational
Mobile network operators: Spain Operational
Mobile network operators: Germany Operational
Mobile network operators: Sweden Operational
Mobile network operators: Norway Operational
Mobile network operators: Denmark Operational
Mobile network operators: Finland Operational
Mobile network operators: United States of America Operational
Mobile network operators: Japan Operational
Mobile network operators: Singapore Operational
Mobile network operators: United Arab Emirates Operational
Mobile network operators: United Kingdom Operational
Mobile network operators: South Africa Operational
Payment method: iDEAL Operational
Payment method: PayPal Operational
Payment method: Mastercard Operational
Payment method: Visa Operational
Payment method: Sofort banking Operational
Payment method: Bancontact Operational
Payments Processor connections: CCV Operational
Payments Processor connections: Omnipay Operational
Payments Processor connections: Six Operational
Payments Processor connections: Equens Operational
Payments Processor connections: Amex Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Scheduled Maintenance – Analytics Portal Service Cloud | June 18, 2026 Jun 18, 2026 00:00 - Jun 19, 2026 00:00 CEST

We will be performing scheduled maintenance on June 18, 2026. The Analytics Portal Service Cloud will remain fully available. In the unlikely event that data is affected, it may be up to one day behind.
Posted on Jun 12, 2026 - 18:11 CEST
System Metrics Month Week Day
cm.com Uptime
Fetching
cm.com Response time
Fetching
gw.cmtelecom.com Uptime
Fetching
gw.messaging.cm.com uptime
Fetching
secure.docdatapayments.com Uptime
Fetching
secure.docdatapayments.com Response time
Fetching
api.cmpayments.com Uptime
Fetching
api.cmpayments.com Response time
Fetching
Jun 14, 2026

No incidents reported today.

Jun 13, 2026

No incidents reported.

Jun 12, 2026
WhatsApp Business is currently experiencing an outage
Resolved - This incident has been resolved.
Jun 12, 19:07 CEST
Monitoring - Update 18:40 CEST – WhatsApp Business Messaging service is currently restored. We are continuing to monitor the situation.
Jun 12, 18:44 CEST
Update - Update 16:30 CEST - Meta has acknowledged the issue on their WhatsApp Business Platform. We will continue to monitor the situation and update this page once resolved.
Jun 12, 16:39 CEST
Update - We are continuing to investigate this issue.
Jun 12, 16:06 CEST
Investigating - Since 15:30 CEST, we are experiencing issues affecting WhatsApp Business.

We are monitoring the situation closely and will provide updates as more information becomes available. We apologize for any inconvenience.
Jun 12, 16:06 CEST
Operator Processing Delay - Belgium - Mobistar / Orange
Resolved - This incident has been resolved.
Jun 12, 16:08 CEST
Identified - We are currently experiencing processing delays to BE - Mobistar / Orange affecting MT traffic. We are working on resolving the incident.
Jun 12, 11:13 CEST
Jun 11, 2026

No incidents reported.

Jun 10, 2026

No incidents reported.

Jun 9, 2026
Operator Service Interuption - ODIDO NL (20416)
Resolved - This incident has been resolved.
Jun 9, 13:38 CEST
Update - We are continuing to monitor for any further issues.
Jun 9, 08:22 CEST
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 9, 08:22 CEST
Identified - The issue has been identified and a fix is being implemented.
Jun 9, 08:10 CEST
Investigating - We are currently investigating this issue.
Jun 9, 08:03 CEST
Jun 8, 2026
Degraded performance - Message processing degraded
Resolved - This incident has been resolved.
Jun 8, 18:28 CEST
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 8, 17:22 CEST
Investigating - Message processing performance is currently degraded. High-priority traffic is not affected. We are currently investigating the issue.
Jun 8, 17:03 CEST
HALO - degraded performance
Resolved - This incident has been resolved.
Jun 8, 12:53 CEST
Investigating - We are currently investigating degraded performance affecting HALO.
Response times have increased significantly, resulting in reduced service availability.

Our team is actively investigating the root cause. Further updates will follow.
Jun 8, 12:05 CEST
Jun 7, 2026

No incidents reported.

Jun 6, 2026

No incidents reported.

Jun 5, 2026
KPN NL (20408) Delayed Delivery - Planned Maintenance
Completed - The scheduled maintenance has been completed.
Jun 5, 02:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 5, 00:35 CEST
Scheduled - Delayed message delivery · 00:00–02:00 CEST
KPN scheduled maintenance may cause delivery delays during this window. Normal service expected to resume at 02:00 CEST.
Jun 5, 00:33 CEST
Jun 4, 2026
Delayed logging of 'regular' non-priority traffic.
Resolved - This incident has been resolved.
Jun 4, 22:44 CEST
Investigating - We are currently investigating delays concerning the logging of 'regular' non-priority traffic. Traffic delivery itself is not affected. Only logging and the return of delivery receipts.
Jun 4, 17:04 CEST
Jun 3, 2026

No incidents reported.

Jun 2, 2026
Upcoming Deprecation of TLS 1.2 for Messaging Services (March 2026)
Completed - The scheduled maintenance has been completed.
Jun 2, 16:47 CEST
Update - We previously announced a March 1, 2026 deadline to discontinue support for Transport Layer Security (TLS) 1.2 across all messaging-related services. We’d like to clarify that this deadline no longer applies.

While there is no longer a fixed timeline for the transition to TLS 1.3, we strongly encourage you to update your integrations to support TLS 1.3 as soon as possible. This applies to all connections to our messaging services and helps ensure secure and reliable communication.

Please be aware that while unencrypted connections or connections using TLS 1.2 are generally supported, traffic to specific destinations may still be blocked or cancelled due to security or compliance requirements.

Why TLS 1.3?
TLS 1.3 is a major step forward in both security and performance. It removes outdated cryptographic functions and simplifies the connection process, providing stronger protection for your data and more efficient communication. Moving to TLS 1.3 helps keep your services secure and running smoothly.

What you need to do
We recommend reviewing your systems and updating any clients that still use TLS 1.2. Although there is no longer a set deadline, testing and ensuring full compatibility with TLS 1.3 as soon as possible can help prevent potential disruptions, particularly when connecting to destinations that require TLS 1.3.

For more details about this update and guidance on how to prepare, please visit our release notes here:
https://releasenotes.cm.com/release-notes/connectivity-platform/messaging-platform
Jan 15, 16:22 CET
Scheduled - At CM.com, we are committed to providing secure and reliable services while adhering to the highest industry standards. As part of this commitment, we will be discontinuing support for Transport Layer Security (TLS) 1.2 on March 1, 2026, for all messaging-related services.

This change will impact all connections to our Business Messaging Gateway API and SMPP servers. After this date, any connection attempts made using TLS 1.2 will no longer be supported. To ensure uninterrupted service, we kindly request that you update your integrations to support TLS 1.3 before the deadline.
Why TLS 1.3?

TLS 1.3 represents a significant advancement in security and performance. By removing outdated cryptographic functions and streamlining the connection handshake process, TLS 1.3 offers enhanced protection for your data and improved efficiency. This upgrade is essential to safeguard your communications and maintain the stability of your services.

What You Need to Do
We strongly encourage all customers to review their systems and update any clients still using TLS 1.2. Please ensure your integrations are tested and fully compatible with TLS 1.3 well ahead of March 1, 2026, to avoid any disruptions.

For more details about this update and guidance on how to prepare, please visit our release notes here:
https://releasenotes.cm.com/release-notes/connectivity-platform/messaging-platform
Nov 19, 15:34 CET
Jun 1, 2026
CM Platform - Login Email Delivery Issues.
Resolved - We have reverted our internal maintenance changes made last week. Emails are sending and delivering as normal once again.
Jun 1, 14:30 CEST
Update - We are continuing to investigate this issue.
Jun 1, 11:59 CEST
Investigating - We are currently experiencing an issue affecting email delivery in the Email Campaigns application. Some emails are being delayed or failing to send. This issue was introduced by a maintenance release last week Thursday. We have identified the cause and are actively working on a fix. We apologize for the inconvenience.
Jun 1, 11:56 CEST
May 31, 2026
Email Campaign - Email Delivery Issue
Resolved - This incident has been resolved.
May 31, 11:55 CEST
Investigating - We are experiencing an issue in the Email Campaigns application that is causing email messages to not be sent.
May 31, 11:28 CEST
← Incident History Powered by Atlassian Statuspage