pingoru pingoru CallTrackingMetrics had 15 outages in the last 2 years totaling 214h 53m of downtime, averaging 0.6 incidents per month.
There were 15 CallTrackingMetrics outages since October 20, 2025 totaling 214h 53m of downtime. Each is summarised below. Incident details, duration, and resolution information.
Services have been restored and operations are back to normal. Thank you for your patience. Impacted: Core Application (EU), Inbound Calling (EU), Outbound Calling & Dialer (EU), +11 more
CTM API and mobile app access has been fully restored. Impacted: Core Application (US), Core Application (EU)
Service is restored and the app is working normally. The problem came from scheduled database maintenance. We are sorry for the disruption and are reviewing how we run this maintenance so it does not happen again. Impacted: Core Application (US), Inbound Calling (US), Outbound Calling & Dialer (US), +12 more
Services have been restored and operations are back to normal. Thank you for your patience. Impacted: Messaging (US)
The upstream provider has resolved the incident following a certificate configuration rollback. Functionality has returned to normal. Impacted: Softphone & Agents (US)
We mitigated an issue triggered by a recent Google Chrome update that affected users as the update was rolled out. Impacted: Core Application (US), Softphone & Agents (US)
The issue affecting embedded communication experiences has been mitigated, and affected workflows have returned to expected operation. We are continuing to monitor for stability. Impacted: Outbound Calling & Dialer (US)
Performance for hosted DNI script requests has returned to expected levels. We are continuing to monitor for stability. Impacted: Tracking & DNI (US)
The central .de registry has confirmed a fix for the DNS issue that impacted website access overnight. All calltrackingmetrics.de services are performing normally. Impacted: Core Application (EU)
Recovery is complete and all backlogs have been cleared. Impacted: Recording & Playback (US), Transcription & AI (US)
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)
We are aware of intermittent errors occurring on the service. Our incident response team is investigating.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident is resolved. We will publish an RFO (reason for outage) after further investigation.
Our investigation confirms that several CTM services are affected due to an outage with an upstream vendor. This includes failed inbound and outbound calls, text messages, and form submissions. There is no ETA for full resolution at this time. We will continue to monitor the situation closely and provide updates as new information becomes available.
Our upstream provider has reported progress toward recovery, and we are seeing partial improvements in some CTM services.
We are seeing recovery of services. We will continue to monitor and provide updates.
This incident has been resolved.