CallRail Outage History

CallRail is up right now

CallRail had 39 outages in the last 2 years totaling 64h 9m of downtime — averaging 1.6 incidents per month.

There were 39 CallRail outages since June 21, 2024 totaling 64h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.callrail.com

Minor March 18, 2025

SMS Messaging May be Delayed

Detected by Pingoru
Mar 18, 2025, 06:26 PM UTC
Resolved
Mar 18, 2025, 07:55 PM UTC
Duration
1h 29m
Affected: SMSWebhooksMMS
Timeline · 5 updates
  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

Detected by Pingoru
Mar 03, 2025, 02:45 PM UTC
Resolved
Mar 04, 2025, 12:28 PM UTC
Duration
21h 42m
Affected: CallRail Web ApplicationLead Center General
Timeline · 5 updates
  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

Detected by Pingoru
Jan 07, 2025, 05:48 PM UTC
Resolved
Jan 07, 2025, 06:32 PM UTC
Duration
43m
Affected: CallRail Web ApplicationLead Center Web Application
Timeline · 3 updates
  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

Detected by Pingoru
Nov 25, 2024, 08:49 PM UTC
Resolved
Nov 26, 2024, 01:09 PM UTC
Duration
16h 20m
Affected: Google AdsEmail Notifications
Timeline · 2 updates
  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

Detected by Pingoru
Nov 12, 2024, 03:34 PM UTC
Resolved
Nov 12, 2024, 05:29 PM UTC
Duration
1h 55m
Affected: CallRail Web Application
Timeline · 4 updates
  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

Detected by Pingoru
Nov 11, 2024, 04:44 PM UTC
Resolved
Nov 11, 2024, 05:12 PM UTC
Duration
28m
Timeline · 3 updates
  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 →

Minor October 24, 2024

Google Call Context data missing

Detected by Pingoru
Oct 24, 2024, 12:39 PM UTC
Resolved
Oct 24, 2024, 03:02 PM UTC
Duration
2h 23m
Affected: Google Call Details Forwarding
Timeline · 3 updates
  1. investigating Oct 24, 2024, 12:39 PM UTC

    We are currently investigating an issue with our Google Call Details Forwarding integration. You may be missing keywords, campaign, and gclid information in your reports for Google Ad Extension calls as early as October 15th. This issue does not affect call routing or conversion uploads to Google Ads.

  2. monitoring Oct 24, 2024, 02:06 PM UTC

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

  3. resolved Oct 24, 2024, 03:02 PM UTC

    The issue has been resolved. Calls from Google Ad Extensions that are configured for Call Details Forwarding are now receiving additional details like gclid and Campaign ID.

Read the full incident report →

Minor October 21, 2024

Convert assist insights may be slow to generate

Detected by Pingoru
Oct 21, 2024, 03:54 PM UTC
Resolved
Oct 21, 2024, 05:31 PM UTC
Duration
1h 37m
Timeline · 4 updates
  1. investigating Oct 21, 2024, 03:54 PM UTC

    We are currently investigating this issue.

  2. identified Oct 21, 2024, 04:04 PM UTC

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

  3. monitoring Oct 21, 2024, 05:04 PM UTC

    A fix has been deployed, and we are now monitoring.

  4. resolved Oct 21, 2024, 05:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 26, 2024

CallRail and Lead Center Intermittent Access Delays

Detected by Pingoru
Sep 26, 2024, 04:13 PM UTC
Resolved
Sep 26, 2024, 07:32 PM UTC
Duration
3h 19m
Affected: CallRail Web ApplicationLead Center Web ApplicationLead Center Mobile App
Timeline · 6 updates
  1. investigating Sep 26, 2024, 04:13 PM UTC

    Some customers are continuing to experience issues accessing the CallRail web app and mobile app. Using the web app incurs several requests each time you navigate, we are seeing a small percentage of these failing. We are aware of these issues and are taking rapid action to resolve the situation. Calls and Dynamic Number Insertion are working normally, though Lead Center may not be accessible for some.

  2. identified Sep 26, 2024, 05:32 PM UTC

    We've identified an issue at our infrastructure provider that appears related to this incident. We're watching that incident, and working to expedite a full resolution for our affected systems.

  3. monitoring Sep 26, 2024, 05:43 PM UTC

    We identified an incident at our infrastructure provider that caused some traffic to fail to route properly through our load balancers. We took steps to reinitialize our load balancers there and our monitoring tools are indicating performance has been restored. We'll continue to watch performance closely to ensure no further action is necessary.

  4. monitoring Sep 26, 2024, 05:56 PM UTC

    We are seeing additional reports of errors when accessing the application. We are investigating and will continue to provide updates.

  5. monitoring Sep 26, 2024, 06:17 PM UTC

    We are seeing systems begin to recover and performance has been restored. We will continue to watch performance closely to ensure no further action is necessary.

  6. resolved Sep 26, 2024, 07:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 4, 2024

Service Provider Performance Issues Impacting Plan Changes & Invoice Viewing

Detected by Pingoru
Sep 04, 2024, 06:58 PM UTC
Resolved
Sep 04, 2024, 11:45 PM UTC
Duration
4h 47m
Timeline · 4 updates
  1. monitoring Sep 04, 2024, 06:58 PM UTC

    Due to performance issues with one of our service providers, we have temporarily disabled the following: - Plan changes - Invoice viewing - New trial sign up with credit card

  2. monitoring Sep 04, 2024, 08:33 PM UTC

    We are continuing to monitor.

  3. monitoring Sep 04, 2024, 10:32 PM UTC

    We are continuing to monitor. As a reminder, the following actions are unavailable during this time: - Plan changes - Invoice viewing - New trial sign up with credit card - Adding/updating credit card to existing accounts

  4. resolved Sep 04, 2024, 11:45 PM UTC

    Performance issues have been resolved and functionality has been restored.

Read the full incident report →

Minor August 27, 2024

HubSpot outage impacting integration setup and data flow

Detected by Pingoru
Aug 27, 2024, 03:00 PM UTC
Resolved
Aug 27, 2024, 05:10 PM UTC
Duration
2h 10m
Affected: Hubspot
Timeline · 4 updates
  1. investigating Aug 27, 2024, 03:00 PM UTC

    HubSpot is currently experiencing an outage: https://status.hubspot.com/ Until it is resolved, it may impact receipt of data in integrated HubSpot accounts and customers may be unable to set up new HubSpot integrations. We are closely monitoring the HubSpot status page.

  2. investigating Aug 27, 2024, 04:01 PM UTC

    Per HubSpot status page, HubSpot has addressed the initial outage issue and are still in monitoring mode of all their systems.

  3. investigating Aug 27, 2024, 05:10 PM UTC

    HubSpot is fully operational. Quick check done to confirm.

  4. resolved Aug 27, 2024, 05:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 7, 2024

Degraded Application Performance

Detected by Pingoru
Aug 07, 2024, 07:01 PM UTC
Resolved
Aug 07, 2024, 08:40 PM UTC
Duration
1h 38m
Affected: CallRail Web ApplicationLead Center General
Timeline · 4 updates
  1. investigating Aug 07, 2024, 07:07 PM UTC

    We are investigating delays with reports and dashboards loading. This may result in notifications and data flowing via webhooks being delayed as well. We are actively working to resolve this issue. We apologize for any inconvenience this may cause.

  2. investigating Aug 07, 2024, 07:12 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Aug 07, 2024, 07:47 PM UTC

    We have identified a product update that was negatively impacting performance, and have reverted that change. Performance is recovering back to expected levels.

  4. resolved Aug 07, 2024, 08:40 PM UTC

    This incident has been resolved

Read the full incident report →

Notice June 26, 2024

Delayed event updates

Detected by Pingoru
Jun 26, 2024, 02:15 PM UTC
Resolved
Jun 26, 2024, 06:40 PM UTC
Duration
4h 24m
Affected: CallRail Web Application
Timeline · 6 updates
  1. investigating Jun 26, 2024, 02:15 PM UTC

    Due to some processing queue backups, we are experiencing delays to some events, especially events triggered post-call. Some actions such as user management may take additional time to process.

  2. investigating Jun 26, 2024, 02:16 PM UTC

    We are continuing to investigate this issue.

  3. identified Jun 26, 2024, 02:57 PM UTC

    We've identified the issue and are working on a fix.

  4. monitoring Jun 26, 2024, 03:59 PM UTC

    We've identified a delay 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. Users may be unable to activate new Google Ads integrations. Overall CallRail event queue health is improving and we will continue to monitor Google's metrics. We'll re-enable all processes and post any delayed conversions as soon as the APIs have recovered.

  5. monitoring Jun 26, 2024, 05:59 PM UTC

    Delays in Google Ads APIs continue, so conversion reporting remains disabled. All other post-call events are processing normally. We'll continue to monitor Google Ads API health and restore conversion reporting when it recovers.

  6. resolved Jun 26, 2024, 06:40 PM UTC

    Delays in Google Ads APIs have cleared, and we've re-enabled conversion reporting.

Read the full incident report →

Notice June 21, 2024

Sign-on issues

Detected by Pingoru
Jun 21, 2024, 05:06 PM UTC
Resolved
Jun 21, 2024, 06:16 PM UTC
Duration
1h 10m
Affected: CallRail Web Application
Timeline · 3 updates
  1. investigating Jun 21, 2024, 05:06 PM UTC

    We are receiving reports of errors when logging in from a small subset of users. We are actively working on a resolution and apologize for any disruptions you are experiencing related to this issue.

  2. identified Jun 21, 2024, 05:38 PM UTC

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

  3. resolved Jun 21, 2024, 06:16 PM UTC

    This incident has been resolved.

Read the full incident report →