CallTrackingMetrics incident

Issues with connecting to CTM

Major Resolved View vendor source →

CallTrackingMetrics experienced a major incident on February 2, 2023 affecting Application Availability, lasting 5h 32m. The incident has been resolved; the full update timeline is below.

Started
Feb 02, 2023, 07:08 PM UTC
Resolved
Feb 03, 2023, 12:41 AM UTC
Duration
5h 32m
Detected by Pingoru
Feb 02, 2023, 07:08 PM UTC

Affected components

Application Availability

Update timeline

  1. investigating Feb 02, 2023, 06:27 PM UTC

    We are currently investigating the issue.

  2. investigating Feb 02, 2023, 06:36 PM UTC

    We are continuing to investigate the issue.

  3. investigating Feb 02, 2023, 07:08 PM UTC

    We appreciate your patience as we continue to investigate the cause of the issue. We will update again at 2:30 pm EST.

  4. monitoring Feb 02, 2023, 07:25 PM UTC

    Site availability has been restored. Our team continues to monitor as a regional outage in AWS infrastructure caused a database failure.

  5. monitoring Feb 02, 2023, 07:29 PM UTC

    We are seeing recovery and continue to monitor performance. We will update again at 3:00 pm EST.

  6. monitoring Feb 02, 2023, 08:04 PM UTC

    We continue to monitor site performance. Thank you for your patience. Our next update will be at 3:30 pm EST.

  7. monitoring Feb 02, 2023, 08:34 PM UTC

    Site performance has improved, we continue to monitor. Our next update will be at 4:30 pm EST.

  8. identified Feb 02, 2023, 09:03 PM UTC

    At the moment, our issues have returned. Our team is working on the resolution. The next scheduled update is at 4:30 pm EST.

  9. identified Feb 02, 2023, 09:36 PM UTC

    We are continuing to work on a fix for this issue.

  10. monitoring Feb 02, 2023, 09:36 PM UTC

    We are seeing recovery and are monitoring performance. We will update again at 5:00 pm EST.

  11. monitoring Feb 02, 2023, 10:24 PM UTC

    Our system is currently stable. Activities that were received during the incident will eventually appear in the log. New activities will appear in real time. We will continue to monitor performance.

  12. resolved Feb 03, 2023, 12:41 AM UTC

    This incident has been resolved.