CTM incident

Session Tracking Interruption

Minor Resolved View vendor source →

CTM experienced a minor incident on April 16, 2026 affecting CTM service, lasting 5m. The incident has been resolved; the full update timeline is below.

Started
Apr 16, 2026, 10:09 PM UTC
Resolved
Apr 16, 2026, 10:15 PM UTC
Duration
5m
Detected by Pingoru
Apr 16, 2026, 10:09 PM UTC

Affected components

CTM service

Update timeline

  1. resolved Apr 16, 2026, 10:15 PM UTC

    The backend application receiving CTM tracking script requests experienced extended downtime due to a denial of service attack. This resulted in gaps in tracking sessions records during the impacted period of time. During this outage, CTM was not tracking all sessions that may have observed a tracking number. While dynamic number rotation was operating normally the session tracking component of the service was experiencing a surge in traffic designed to impact the services ability to capture all sessions. An investigation found the root cause leading the team to implement patches to mitigate and block the bad traffic resulting in service being fully restored. Impacted: Tracking & DNI (US)