Is CM.com down?

Last checked 7m ago
Current status
CM.com is up

No incidents right now.

Official status page: https://status.cm.com · Polled every 5 minutes · 103 components tracked

CM.com is operational right now. Last checked 7m ago; the most recent incident resolved 3d ago.

Real-time CM.com status, recent outages, and incident history — pulled directly from CM.com's official status page at https://status.cm.com every 5 minutes. Pingoru tracks 103 CM.com services and has captured 62 incidents in the last 90 days (99.30% uptime). Get email, Slack, Discord, or webhook alerts the moment CM.com reports a new incident — free for 5 monitors, no credit card.

Users who monitor CM.com also follow these Telephony services: Twilio Aircall Dialpad Loom Plivo Nextiva Mitel OneSignal Attentive Grasshopper View all 6,000+ providers
CM.com uptime 99.30% uptime · past 90 days
Mon Wed Fri
AprMayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2h 10m
    Started Jul 27, 2026, 12:04 PM UTC · Resolved Jul 27, 2026, 02:14 PM UTC
    Agent Inbox
    Timeline · 4 updates
    • investigating · Jul 27, 2026, 12:04 PM UTC

      We are currently investigating an issue causing delay in processing tasks for the Agent Inbox

    • identified · Jul 27, 2026, 12:45 PM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Jul 27, 2026, 01:27 PM UTC

      A fix has been implemented and tasks are currently being processed without delays. We continue to monitor the results.

    • resolved · Jul 27, 2026, 02:14 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 1d 2h
    Started Jul 27, 2026, 07:11 AM UTC · Resolved Jul 28, 2026, 10:10 AM UTC
    Payment method: Visa
    Timeline · 2 updates
    • identified · Jul 27, 2026, 07:11 AM UTC

      Over the past weekend, Visa reported an incident affecting one of their services, which has caused a delay in the payout of Visa transactions processed during this period. Current status: We expect to process the affected Visa payouts with a one-day delay, starting Tuesday. We are in continuous contact with Visa to have this incident resolved as quickly as possible, and will update this page as soon as new information becomes available. We apologize for any inconvenience this may cause.

    • resolved · Jul 28, 2026, 10:10 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 28m
    Started Jul 17, 2026, 08:49 AM UTC · Resolved Jul 17, 2026, 09:18 AM UTC
    Mobile network operators: Germany
    Timeline · 2 updates
    • investigating · Jul 17, 2026, 08:49 AM UTC

      DE - 1&1 - 26223 is experiencing an issue on their platform which affects MT/MO SMS traffic and Status Reports. The operator is investigating the issue. Traffic is queueing and will be delivered when it is resolved.

    • resolved · Jul 17, 2026, 09:18 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved 1d 18h
    Started Jul 14, 2026, 11:18 AM UTC · Resolved Jul 16, 2026, 06:04 AM UTC
    Reporting
    Timeline · 2 updates
    • identified · Jul 14, 2026, 11:18 AM UTC

      Due to import failures, the Mobile Service Cloud data has not been refreshed today, meaning it will only show data up to the day before yesterday. The problem should be resolved around 07:00 UTC tomorrow

    • resolved · Jul 16, 2026, 06:04 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 1h 53m
    Started Jul 14, 2026, 06:53 AM UTC · Resolved Jul 14, 2026, 08:47 AM UTC
    Native Voice
    Timeline · 4 updates
    • investigating · Jul 14, 2026, 06:53 AM UTC

      We are currently investigating this issue.

    • identified · Jul 14, 2026, 07:20 AM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Jul 14, 2026, 07:39 AM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Jul 14, 2026, 08:47 AM UTC

      What happened Today, some of our services experienced disruption following a release in which credentials for our Realtime service could not be read correctly during task processing. This had the potential to impact various parts of the platform, with the most significant effect on Native Voice Calls, which remained stuck in the queue and were not offered to available agents. Additionally, AI suggestions were not plotted in real time. By 09:39, the issue had been fully resolved and all services were restored to normal. What we are doing to prevent this in the future This issue was introduced by a hotfix that bypassed our standard test pipeline. Going forward, we will run core regression tests before any hotfix is released to production, ensuring issues like this are caught early. In addition, we are adding monitoring and alerting to detect this type of disruption earlier and respond more quickly. Closing Our apologies for the inconvenience caused. We will work diligently to prevent this from happening again.

    Latest: What happened Today, some of our services experienced disruption following a release in which credentials for our Realtime service could not be read correctly during task processin…

See the full CM.com outage history

44 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse CM.com outage history →

Or sign up free to get alerts when CM.com breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 49 incidents View full outage history →