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
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.
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.
We will be performing maintenance to our General Admission / Ticketing NXTGN platform. This maintenance will improve the ticketing platform experience and finalize the migration from the old ticketing app towards the new NXTGN platform. Our services will be fully unreachable during this time. Impacted services are:
- NXTGN dashboard
- NXTGN shop (sales.ticketing.cm.com)
- Ticket download and personalization
- CM Ticket scan app (Entrance Management is not impacted) Posted on
Mar 17, 2026 - 21:50 CET
Resolved -
This incident has been resolved.
Mar 18, 16:53 CET
Update -
Issue has been identified, and a fix is implemented. New incoming in/outbound traffic is processed without delay, Product will continue monitoring the situation.
Mar 18, 15:16 CET
Update -
We are continuing to monitor for any further issues.
Mar 18, 15:13 CET
Monitoring -
Issue has been identified, and a fix is implemented. Delayed in/outbound traffic is being processed at the moment. Product will continue monitoring the situation.
Mar 18, 15:13 CET
Update -
Issue remains ongoing, product is investigating. All in/outbound traffic will be processed with a delay.
Mar 18, 14:38 CET
Investigating -
There is a queue at Agent Inbox. this results in delayed processing of tasks.
This impacts the processing of all inbound and outbound work.
Product is investigating this issue at the moment.
Mar 18, 13:50 CET
Resolved -
This incident has been resolved.
Mar 18, 11:47 CET
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 18, 10:17 CET
Investigating -
We are currently experiencing some external network issues, which might have an impact on the quality of voice calls. We are working with our external partner to have this problem resolved as soon as possible.
Mar 18, 10:07 CET