CallTrackingMetrics Outage History

CallTrackingMetrics is up right now

CallTrackingMetrics had 15 outages in the last 2 years totaling 48h 24m of downtime — averaging 0.6 incidents per month.

There were 15 CallTrackingMetrics outages since June 11, 2024 totaling 48h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://calltrackingmetrics.statuspage.io

Minor March 16, 2026

Investigating Potential Issue with Logins

Detected by Pingoru
Mar 16, 2026, 09:46 PM UTC
Resolved
Mar 16, 2026, 11:16 PM UTC
Duration
1h 29m
Affected: Application Availability
Timeline · 6 updates
  1. investigating Mar 16, 2026, 09:46 PM UTC

    We are aware of intermittent errors occurring on the service. Our incident response team is investigating.

  2. investigating Mar 16, 2026, 09:47 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 16, 2026, 09:48 PM UTC

    We are continuing to investigate this issue.

  4. identified Mar 16, 2026, 09:49 PM UTC

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

  5. monitoring Mar 16, 2026, 09:57 PM UTC

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

  6. resolved Mar 16, 2026, 11:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 19, 2026

Unable to access app.calltrackingmetrics.com

Detected by Pingoru
Jan 19, 2026, 10:22 PM UTC
Resolved
Jan 19, 2026, 11:47 PM UTC
Duration
1h 24m
Affected: Application Availability
Timeline · 4 updates
  1. investigating Jan 19, 2026, 10:22 PM UTC

    We are currently investigating this issue.

  2. identified Jan 19, 2026, 10:55 PM UTC

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

  3. monitoring Jan 19, 2026, 10:56 PM UTC

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

  4. resolved Jan 19, 2026, 11:47 PM UTC

    This incident is resolved. We will publish an RFO (reason for outage) after further investigation.

Read the full incident report →

Major October 20, 2025

Upstream vendor outage affecting calls, texts, and forms

Detected by Pingoru
Oct 20, 2025, 10:15 AM UTC
Resolved
Oct 20, 2025, 12:58 PM UTC
Duration
2h 42m
Affected: Incoming Text MessagesTwilio Outgoing SMSTwilio Outgoing MMSTwilio Incoming MMS
Timeline · 4 updates
  1. monitoring Oct 20, 2025, 10:15 AM UTC

    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.

  2. monitoring Oct 20, 2025, 10:37 AM UTC

    Our upstream provider has reported progress toward recovery, and we are seeing partial improvements in some CTM services.

  3. monitoring Oct 20, 2025, 11:32 AM UTC

    We are seeing recovery of services. We will continue to monitor and provide updates.

  4. resolved Oct 20, 2025, 12:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 13, 2025

Activities were not appearing or were disappearing from the activity log

Detected by Pingoru
Oct 13, 2025, 06:11 PM UTC
Resolved
Sep 23, 2025, 03:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 13, 2025, 06:11 PM UTC

    On September 22, 2025, between 20:00 UTC and 23:00 UTC, some customers experienced issues where activities were not appearing or were disappearing from the CTM activity log. The disruption was caused by server-side database index replication processes that did not perform as expected. Service was fully restored at 23:00 UTC, and the issue has been remediated.

Read the full incident report →

Minor October 13, 2025

Brief outage because job queues were backed up

Detected by Pingoru
Oct 13, 2025, 06:10 PM UTC
Resolved
Sep 15, 2025, 05:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 13, 2025, 06:10 PM UTC

    On September 15, 2025, between 12:31 PM EST and 12:45 PM EST, our systems experienced a brief outage where job queues were backed up. During this time, some customers reported calls showing as active even after the agent had ended the call. The issue was addressed by adjusting job server parameters to handle queues more efficiently. Service was fully restored at 12:45 PM EST, and the issue has been remediated.

Read the full incident report →

Major October 13, 2025

Intermittent outages preventing some customers making or receiving calls and text messages

Detected by Pingoru
Oct 13, 2025, 06:08 PM UTC
Resolved
Sep 11, 2025, 03:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 13, 2025, 06:08 PM UTC

    On September 11, 2025, between 2:14 AM and 10:49 AM UTC, our systems experienced intermittent outages that prevented some customers from making or receiving calls and text messages. The disruption was caused by multiple servers failing due to a memory-related issue. Service was fully restored at 10:49 AM UTC, and the issue has been remediated.

Read the full incident report →

Minor September 2, 2025

Investigating Slowness

Detected by Pingoru
Sep 02, 2025, 07:23 PM UTC
Resolved
Sep 02, 2025, 08:27 PM UTC
Duration
1h 3m
Affected: Application Availability
Timeline · 3 updates
  1. investigating Sep 02, 2025, 07:23 PM UTC

    We are aware of reports of slowness affecting some areas of our platform. Our incident response team is actively investigating the issue to identify and resolve the cause as quickly as possible. We will provide further updates as more information becomes available. Thank you for your patience.

  2. monitoring Sep 02, 2025, 07:58 PM UTC

    We have identified the issue and deployed a fix. Our team is closely monitoring the systems to ensure stability. Customers may continue to experience temporary slowness with transcriptions and other background jobs; however, all pending tasks will process and catch up shortly. Thank you for your patience while we confirm full resolution.

  3. resolved Sep 02, 2025, 08:27 PM UTC

    This issue is resolved.

Read the full incident report →

Minor August 6, 2025

Softphone agents are not being signaled of an inbound call

Detected by Pingoru
Aug 06, 2025, 02:00 PM UTC
Resolved
Aug 06, 2025, 03:00 PM UTC
Duration
1h
Timeline · 4 updates
  1. investigating Aug 06, 2025, 02:00 PM UTC

    We are currently investigating an issue where Softphone agents are not being signaled for an inbound call. All technical resources are dedicated to solving this issue.

  2. identified Aug 06, 2025, 02:02 PM UTC

    We have identified the cause of the issue and are working on a solution.

  3. monitoring Aug 06, 2025, 02:18 PM UTC

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

  4. resolved Aug 06, 2025, 03:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 28, 2025

Investigating issue with site availability and delayed jobs

Detected by Pingoru
Jul 28, 2025, 03:48 PM UTC
Resolved
Jul 29, 2025, 11:54 AM UTC
Duration
20h 5m
Affected: Incoming Text MessagesApplication AvailabilityTwilio Outgoing SMS
Timeline · 8 updates
  1. investigating Jul 28, 2025, 03:48 PM UTC

    We are currently investigating this issue.

  2. identified Jul 28, 2025, 03:55 PM UTC

    Issue identified and being mitigated.

  3. monitoring Jul 28, 2025, 04:25 PM UTC

    Mitigation in place. Delays in analytics and transcriptions are being addresssed.

  4. monitoring Jul 28, 2025, 05:35 PM UTC

    We are still monitoring the backlog of jobs including transcriptions.

  5. monitoring Jul 28, 2025, 07:03 PM UTC

    We’ve resolved the majority of the delays affecting service earlier today. While some residual disruptions may still occur, these are expected to taper off throughout the afternoon. Thank you for your patience and continued support.

  6. monitoring Jul 28, 2025, 08:37 PM UTC

    We are continuing to monitor delayed transcriptions.

  7. monitoring Jul 28, 2025, 09:46 PM UTC

    We are still working to clear delayed transcriptions.

  8. resolved Jul 29, 2025, 11:54 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 22, 2025

Transcriptions are delayed

Detected by Pingoru
Jul 22, 2025, 08:03 PM UTC
Resolved
Jul 22, 2025, 09:58 PM UTC
Duration
1h 54m
Timeline · 3 updates
  1. identified Jul 22, 2025, 08:03 PM UTC

    We are working to reduce the backlog

  2. monitoring Jul 22, 2025, 08:37 PM UTC

    We are continuing to make progress.

  3. resolved Jul 22, 2025, 09:58 PM UTC

    Transcriptions are no longer delayed.

Read the full incident report →

Minor June 17, 2025

Investigating Potential Issue of Slowness in the CTM Call Log

Detected by Pingoru
Jun 17, 2025, 07:30 PM UTC
Resolved
Jun 17, 2025, 10:56 PM UTC
Duration
3h 25m
Affected: Application Availability
Timeline · 5 updates
  1. investigating Jun 17, 2025, 07:30 PM UTC

    We are aware of errors occurring on the service. Our incident response team is investigating.

  2. investigating Jun 17, 2025, 07:41 PM UTC

    We continue to investigate the degraded performance in the CTM interface. All available technical and engineering resources are working on identifying the cause.

  3. investigating Jun 17, 2025, 08:13 PM UTC

    All available technical and engineering resources are working on identifying the cause of the degraded performance in the CTM interface.

  4. monitoring Jun 17, 2025, 09:52 PM UTC

    A resolution has put in place and we are monitoring performance. Please report any issues you encounter.

  5. resolved Jun 17, 2025, 10:56 PM UTC

    Services have been restored and operations are back to normal. Thank you for your patience.

Read the full incident report →

Major March 31, 2025

Intermittent issues with voice services.

Detected by Pingoru
Mar 31, 2025, 03:50 PM UTC
Resolved
Mar 31, 2025, 05:30 PM UTC
Duration
1h 40m
Affected: Application Availability
Timeline · 6 updates
  1. investigating Mar 31, 2025, 03:50 PM UTC

    We are aware of intermittent errors affecting your ability to answer calls. Our incident response team is investigating.

  2. investigating Mar 31, 2025, 04:04 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 31, 2025, 04:05 PM UTC

    Our technical partners are diligently working to identify and address the issue. Please visit https://status.twilio.com for more information. We will update you as we have more information.

  4. identified Mar 31, 2025, 04:21 PM UTC

    Our upstream service provider has identified the problem causing the issues with CTM. They are working on a solution. Visit https://status.twilio.com/incidents/5mbfvb8mzhcn for updates.

  5. monitoring Mar 31, 2025, 05:09 PM UTC

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

  6. resolved Mar 31, 2025, 05:30 PM UTC

    The incident has been resolved. We will continue to monitor performance. Please reach out if you continue to experience issues with receiving or placing voice calls.

Read the full incident report →

Major November 22, 2024

Investigating Potential Issue

Detected by Pingoru
Nov 22, 2024, 11:36 PM UTC
Resolved
Nov 23, 2024, 04:02 AM UTC
Duration
4h 26m
Affected: Application Availability
Timeline · 4 updates
  1. investigating Nov 22, 2024, 11:36 PM UTC

    We are aware of intermittent errors occurring on the service. Our incident response team is investigating.

  2. identified Nov 23, 2024, 12:09 AM UTC

    We've identified the cause, and have implemented a fix towards full recovery.

  3. monitoring Nov 23, 2024, 12:49 AM UTC

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

  4. resolved Nov 23, 2024, 04:02 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 4, 2024

Difficulty connecting to app.calltrackingmetrics.com

Detected by Pingoru
Nov 04, 2024, 06:32 PM UTC
Resolved
Nov 04, 2024, 06:32 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Nov 04, 2024, 06:32 PM UTC

    At approximately 1:19 pm EST on November 4, 2024 a brief period of very isolated issues connecting to https://app.calltrackingmetrics.com was experienced by a small subset of our users. Remediation actions were swift and the site recovered to normal operation at 1:26 pm EST.

Read the full incident report →