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
General Admission
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
Upcoming Deprecation of TLS 1.2 for Messaging Services (March 2026) Nov 19, 2025 16:00-17:00 CET
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, 2026 - 16:22 CET
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, 2026 - 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, 2025 - 15:34 CET
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, 2025 - 15:34 CET