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
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.
On Januari 20th at 13:00 CET, we will perform maintenance on our Singapore Platform. This will impact all connections to SMPP 208 and all HTTP traffic towards gateway-sgp.cmtelecom.com. Active binds will be disconnected, and SMPP and HTTP will be unavailable until maintenance is completed.
Traffic towards http gateway sgp-gw.messaging.cm.com will be routed to our NL platform. We estimate this maintenance will take around five hours. Posted on
Nov 10, 2025 - 16:55 CET
Resolved -
We experienced issues with our Triggered Campaign functionality between approximately 16:00 - 18:40 CET. During this time, triggered campaigns (campaigns triggered from CDP workflows and Triggered Campaigns API) failed to send.
Impact: All email triggers initiated during this timeframe were not delivered.
Current Status: We are actively investigating whether it is possible to recover the failed triggers and retroactively send the affected emails. We will provide an update as soon as we have more information. We sincerely apologize for any inconvenience this may have caused.
Jan 8, 19:40 CET
Resolved -
Summary: We experienced an issue with our campaign statistics processing system that affected the accuracy of delivery rate metrics in Campaign Insights. Timeframe: 10:00 CET January 7th - 10:00 CET January 8th Impact: Campaign statistics were not processed correctly during this period. Delivery rate statistics displayed in Campaign Insights were inaccurate All emails were sent out successfully and delivered as expected. No impact to actual email delivery or customer communications Root Cause: Events were processed through our queue system, but a misconfiguration caused messages to be processed incorrectly, resulting in inaccurate statistics. Resolution: The issue was resolved through a rollback and implementation of fixes to prevent similar misconfigurations in the future. Key Takeaway: While statistics reporting was affected, all triggered campaigns functioned normally and emails were delivered to recipients without interruption.
Jan 7, 10:00 CET