CM.com incident

Messaging platform performance is degraded

Major Resolved View vendor source →

CM.com experienced a major incident on July 9, 2026 affecting Business Messaging API and SMS - High Priority and 1 more component, lasting 3h 54m. The incident has been resolved; the full update timeline is below.

Started
Jul 09, 2026, 12:08 PM UTC
Resolved
Jul 09, 2026, 04:03 PM UTC
Duration
3h 54m
Detected by Pingoru
Jul 09, 2026, 12:08 PM UTC

Affected components

Business Messaging APISMS - High PriorityWhatsApp Business

Update timeline

  1. investigating Jul 09, 2026, 12:08 PM UTC

    Currently the messaging platform performance is degraded. Messages are still accepted and will be processed with a delay. We are working to resolve the issue.

  2. investigating Jul 09, 2026, 12:26 PM UTC

    The cause if the issues has been identified. We are currently working on a solution to resolve the degraded performance.

  3. identified Jul 09, 2026, 01:20 PM UTC

    We are carefully deploying a fix to resolve the problem. Traffic processing performance can degrade and improve again during the rollout.

  4. monitoring Jul 09, 2026, 02:49 PM UTC

    Fixes have been implemented and traffic processing has resumed. Queued traffic is being processed at the moment. We are monitoring the situation.

  5. resolved Jul 09, 2026, 04:03 PM UTC

    This incident has been resolved.