CM.com Outage History

Orange Belgium experienced a platform issue that disrupted MT SMS traffic for 34 hours. CM.com's Belgium mobile network operator services were affected during this period. The issue was resolved after the operator implemented a fix and monitored the results.

CM.com experienced a major service incident where Omnipay payment transactions could not be processed due to connection issues with the Omnipay service. The incident lasted 37 minutes, during which all payment processing through the Omnipay integration was unavailable. The connection issue was resolved and normal transaction processing was restored.

CM.com's Agent Inbox experienced slow loading and response issues for 7.2 hours due to a failed database index update during a release that caused database disruptions and task processing backlogs. The root cause was identified and resolved, with infrastructure scaled out to process the backlogged tasks and restore normal performance. The incident was fully resolved with Agent Inbox loading speeds and conversation processing returned to normal.

CM.com experienced failed transactions on payment terminals that affected their Mobile Order component for 1.7 hours. The company investigated the issue and successfully resolved it. The incident was classified as minor in severity.

CM.com experienced an 8.6-hour incident where Texter's test nodes were unavailable, preventing users from conducting testing activities. The company investigated the issue, implemented a fix, and monitored the results before confirming full resolution. The incident was classified as minor severity and has been fully resolved.

CM.com's Email gateway API experienced delivery issues for 34 minutes on April 18th, 2026. The incident affected email delivery functionality through their API service. The issue was resolved after investigation and monitoring.

CM.com experienced a database outage affecting their Seated Ticketing platform for 52 minutes. The outage prevented users from purchasing seated tickets and accessing ticketing dashboards, while ticket scanning functionality remained operational. The issue was resolved after implementing a fix and monitoring the results.

CM.com experienced a major service interruption with their Texter component that lasted 9.1 hours. The issue was identified and a fix was implemented, with the service being monitored before full resolution. The incident was successfully resolved after engineers worked through the investigation and repair process.

CM.com experienced a service interruption affecting their Payment Service Provider API for 1.1 hours. The issue impacted PSP services, preventing normal payment processing functionality. The incident was resolved after implementing a fix and monitoring the results.

Two Belgian mobile network operators (Base Belgium and Telenet Belgium) began rejecting most messages containing URLs in the message body, affecting CM.com's messaging service in Belgium. The service interruption lasted 2.7 hours while CM.com worked with the operators to resolve the issue. The incident was fully resolved after the operators stopped blocking URL-containing messages.