CallRail Outage History

CallRail is up right now

Pingoru has recorded 61 incidents for CallRail: 19 in the last 12 months and 6 in the last 90 days.

Source: status.callrail.com

61incidents recorded
19last 12 months
6last 90 days
4 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking CallRail in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202621 of 720 (0%)
May 2026117 of 744 (2%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202648 of 744 (1%)
September 202616 of 720 (1%)
October 202617 of 591 (1%)

Incidents, newest first

Notice April 26, 2025 iOS CallRail app loading delays 3d 21h

Started Apr 26, 2025, 05:52 PM UTC· resolved Apr 30, 2025, 02:55 PM UTC

  1. monitoring Apr 26, 2025, 05:52 PM UTC

    We are aware of an issue causing the iOS app to remain in a loading state for some users. Reinstalling the app has been effective in resolving these cases. Our team is actively monitoring the situation to ensure a complete resolution.

  2. resolved Apr 30, 2025, 02:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 19, 2025 Caller ID not available with call 1h 57m Lead Center General

Started Apr 19, 2025, 05:04 PM UTC· resolved Apr 19, 2025, 07:02 PM UTC

  1. investigating Apr 19, 2025, 05:04 PM UTC

    We are currently investigating an issue that is causing the receipt of caller ID information to be delayed. Caller names may display as "Unavailable" in Lead Center, the call and text activity logs, and in reports. Call routing is not impacted.

  2. identified Apr 19, 2025, 05:44 PM UTC

    We have identified that this issue is caused by a downstream provider and we are working with them to resolve this issue. In the meantime, all calls are routing correctly although caller identification data may be missing. We will continue to monitor and work with our provider to fix this issue as quickly as possible.

  3. resolved Apr 19, 2025, 07:02 PM UTC

    The issue with our downstream provider has been resolved and caller ID information is no longer delayed. Current/in-progress calls will display the expected information. Prior calls that were received while the incident may still show as "Unavailable", but we will backfill any missing data.

Read the full incident report →

Minor April 12, 2025 Google Ads Call Details Forwarding Issue 1h 8m Google Ads Call Details Forwarding

Started Apr 12, 2025, 03:44 PM UTC· resolved Apr 12, 2025, 04:53 PM UTC

  1. investigating Apr 12, 2025, 03:44 PM UTC

    We are investigating reports of some dropped calls for Google Ads Call Details Forwarding to CallRail trackers. Other calls are routing correctly and reporting and access to CallRail are unaffected.

  2. identified Apr 12, 2025, 04:05 PM UTC

    We have identified the root cause of this issue and are working to resolve it.

  3. monitoring Apr 12, 2025, 04:41 PM UTC

    Google Ads Call Details Forwarding calls should now be returning to normal. Though we will continue to monitor this to ensure the issue has been fully resolved.

  4. resolved Apr 12, 2025, 04:53 PM UTC

    This issue has been resolved.

Read the full incident report →

Minor April 1, 2025 Call Log Export Issue 5h 36m Reports

Started Apr 01, 2025, 01:41 PM UTC· resolved Apr 01, 2025, 07:17 PM UTC

  1. investigating Apr 01, 2025, 01:41 PM UTC

    We're aware of an issue with exporting the Call Log. Our engineers are working diligently to identify the issue. We will make updates as they become available. Thank you for your patience.

  2. identified Apr 01, 2025, 02:01 PM UTC

    We've identified the cause of the Call Log export and our engineers are working on a resolution. We will continue to make updates as they become available.

  3. identified Apr 01, 2025, 03:45 PM UTC

    Our team is diligently pursuing solutions for the reported issue. We will continue to provide regular updates on our progress.

  4. monitoring Apr 01, 2025, 05:03 PM UTC

    A fix has been implemented and we are monitoring the results. We appreciate your continued patience.

  5. resolved Apr 01, 2025, 07:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 31, 2025 Investigating Isolated Call Routing Issues 1h 56m Call Routing

Started Mar 31, 2025, 03:45 PM UTC· resolved Mar 31, 2025, 05:41 PM UTC

  1. investigating Mar 31, 2025, 03:45 PM UTC

    We're currently investigating call routing failures affecting a small portion of calls. Our team is actively working to identify the root cause and restore full functionality. We will provide updates as we learn more.

  2. identified Mar 31, 2025, 04:27 PM UTC

    We have identified an issue with an upstream vendor that is impacting call routing for some customers. We are actively working with them to mitigate the situation. We sincerely apologize for any disruption this may cause.

  3. monitoring Mar 31, 2025, 05:39 PM UTC

    A fix has been implemented and we're observing normal call routing performance.

  4. resolved Mar 31, 2025, 05:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 18, 2025 SMS Messaging May be Delayed 1h 29m SMS, Webhooks, MMS

Started Mar 18, 2025, 06:26 PM UTC· resolved Mar 18, 2025, 07:55 PM UTC

  1. identified Mar 18, 2025, 06:26 PM UTC

    We've identified an issue with SMS, causing some messaging to be delayed. Integration processing for SMS events, including Webhook events, is also delayed. We are currently implementing a resolution.

  2. identified Mar 18, 2025, 06:26 PM UTC

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

  3. identified Mar 18, 2025, 06:28 PM UTC

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

  4. identified Mar 18, 2025, 07:12 PM UTC

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

  5. resolved Mar 18, 2025, 07:55 PM UTC

    Issues with messaging and webhooks have now been resolved. All delayed messages should have been delivered and new messages are being delivered without delay.

Read the full incident report →

Major March 3, 2025 Caller ID information is delayed 21h 42m CallRail Web Application, Lead Center General

Started Mar 03, 2025, 02:45 PM UTC· resolved Mar 04, 2025, 12:28 PM UTC

  1. investigating Mar 03, 2025, 02:45 PM UTC

    We are currently investigating an issue that is causing the receipt of caller ID information to be delayed. Caller names may display as "Unavailable" in Lead Center, the call and text activity logs, and in reports. Call routing is not impacted.

  2. investigating Mar 03, 2025, 03:39 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 03, 2025, 04:30 PM UTC

    The issue is resolved and caller ID information is no longer delayed. Current/in-progress calls will display the expected information. Prior calls that were received while the incident may still show as "Unavailable", but we expect to backfill missing data shortly.

  4. monitoring Mar 03, 2025, 08:48 PM UTC

    We are still working to recover caller name information for calls received between approximately 9:12am ET and 11:02am ET. Calls received since 11:02am are processing normally and have the expected caller ID information.

  5. resolved Mar 04, 2025, 12:28 PM UTC

    All missing caller ID information has been backfilled.

Read the full incident report →

Major January 7, 2025 Dashboard Unavailable 43m CallRail Web Application, Lead Center Web Application

Started Jan 07, 2025, 05:48 PM UTC· resolved Jan 07, 2025, 06:32 PM UTC

  1. identified Jan 07, 2025, 05:48 PM UTC

    We are currently investigating a problem with application dashboard availability, and believe to have identified the source of the issue. More details will be posted as soon as possible.

  2. monitoring Jan 07, 2025, 05:51 PM UTC

    We have reverted a recent deployment, and are currently monitoring to ensure full performance has been restored.

  3. resolved Jan 07, 2025, 06:32 PM UTC

    Full operational performance has been restored.

Read the full incident report →

Minor November 25, 2024 Google Ads disruption + delayed event updates 16h 20m Google Ads, Email Notifications

Started Nov 25, 2024, 08:49 PM UTC· resolved Nov 26, 2024, 01:09 PM UTC

  1. identified Nov 25, 2024, 08:49 PM UTC

    We've identified a disruption in service in the APIs used by our Google Ads integration. We have temporarily disabled conversion reporting to Google Ads as well as data retrieval of keywords and campaign data while we wait for the Google team to resolve the issue. Users may be unable to activate new Google Ads integrations. This issue is causing delays to some events, especially events triggered post-call. Some actions such as user management and email notifications may take additional time to process. Call routing is not impacted.

  2. resolved Nov 26, 2024, 01:09 PM UTC

    Google Ads has resolved their incident. We've re-enabled the integration and data should be flowing as normal.

Read the full incident report →

Minor November 12, 2024 "Call back" option not displaying in the Analytics section 1h 55m CallRail Web Application

Started Nov 12, 2024, 03:34 PM UTC· resolved Nov 12, 2024, 05:29 PM UTC

  1. investigating Nov 12, 2024, 03:34 PM UTC

    We are currently investigating an issue that is causing the "call back" button to not display in various pages of the Analytics section, including the Activity logs and the Lead timeline page. Call routing and reporting are not impacted.

  2. identified Nov 12, 2024, 03:55 PM UTC

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

  3. monitoring Nov 12, 2024, 04:56 PM UTC

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

  4. resolved Nov 12, 2024, 05:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 11, 2024 Call summaries not accessible to some users 28m

Started Nov 11, 2024, 04:44 PM UTC· resolved Nov 11, 2024, 05:12 PM UTC

  1. identified Nov 11, 2024, 04:44 PM UTC

    Call summaries are not accessible in the report view. They appear to be working fine in the Timeline view.

  2. monitoring Nov 11, 2024, 05:02 PM UTC

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

  3. resolved Nov 11, 2024, 05:12 PM UTC

    This incident has been resolved.

Read the full incident report →