Live / CM.com / Incident
CM.com: Message Insights + Transactions API - Interruption
CM.com · cm.comMinor incidentResolved2026-11-04 08:31 UTC
Public — what happened
Summary
CM.com reported an interruption affecting its Message Insights customer tooling and its Transactions API, which it classed as minor. The company said it began investigating at 07:00 UTC on 2026-11-04, and by 07:59 UTC it said the problem had been identified and a fix was being put in place. At 08:14 UTC CM.com said the fix was in place and it was monitoring results, and the incident was marked resolved at 08:31. The company did not describe what caused the interruption.
Affected
Messaging Apps
Timeline
- Started — 2026-11-04 07:00 UTC
- Investigating — 2026-11-04 07:00 UTC
- Identified — 2026-11-04 07:59 UTC
- Monitoring — 2026-11-04 08:14 UTC
- Resolved — 2026-11-04 08:31 UTC · 1h 31m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach CM.com against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for CM.com: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the CM.com report →
More from CM.com
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.