CallRail Outage History

CallRail is up right now

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

There were 39 CallRail outages since August 27, 2024 totaling 149h 45m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.callrail.com

Critical August 20, 2026

Integrations Connection Error

Detected by Pingoru
Aug 20, 2026, 03:34 PM UTC
Resolved
Aug 20, 2026, 04:15 PM UTC
Duration
41m
Affected: Other Integrations
Timeline · 5 updates
  1. identified Aug 20, 2026, 03:34 PM UTC

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

  2. identified Aug 20, 2026, 03:56 PM UTC

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

  3. monitoring Aug 20, 2026, 03:59 PM UTC

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

  4. monitoring Aug 20, 2026, 04:04 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Aug 20, 2026, 04:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 20, 2026

Transcriptions API Timeout

Detected by Pingoru
Aug 20, 2026, 02:13 PM UTC
Resolved
Aug 20, 2026, 03:25 PM UTC
Duration
1h 12m
Affected: Call TranscriptionConversation Intelligence
Timeline · 5 updates
  1. investigating Aug 20, 2026, 02:13 PM UTC

    We are currently investigating this issue.

  2. investigating Aug 20, 2026, 02:17 PM UTC

    We are continuing to investigate this issue.

  3. identified Aug 20, 2026, 02:20 PM UTC

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

  4. monitoring Aug 20, 2026, 02:58 PM UTC

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

  5. resolved Aug 20, 2026, 03:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 17, 2026

PCI Insights Delay

Detected by Pingoru
Aug 17, 2026, 05:10 PM UTC
Resolved
Aug 17, 2026, 06:06 PM UTC
Duration
56m
Affected: Conversation Intelligence
Timeline · 3 updates
  1. investigating Aug 17, 2026, 05:10 PM UTC

    We are investigating an issue that may cause some PCI insights to be delayed. We sincerely apologize for any inconvenience these delays may cause.

  2. monitoring Aug 17, 2026, 05:32 PM UTC

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

  3. resolved Aug 17, 2026, 06:06 PM UTC

    This incident has been resolved, and PCI Insights should be processing normally.

Read the full incident report →

Minor May 8, 2026

Lead Center incoming call notification issue on iOS

Detected by Pingoru
May 08, 2026, 06:09 PM UTC
Resolved
May 09, 2026, 11:15 AM UTC
Duration
17h 5m
Affected: Lead Center Mobile App
Timeline · 2 updates
  1. identified May 08, 2026, 06:09 PM UTC

    We're currently experiencing issues with incoming call notifications for Lead Center on iOS devices. Android devices are not impacted. The team has identified the issue and a fix is being implemented.

  2. resolved May 09, 2026, 11:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 8, 2026

Scheduled maintenance for CallRail Applications

Detected by Pingoru
Apr 08, 2026, 02:30 AM UTC
Resolved
Apr 08, 2026, 02:30 AM UTC
Duration
—
Timeline · 1 update
  1. monitoring Apr 08, 2026, 02:30 AM UTC

    Apr 7, 22:30 EDT Completed - The scheduled maintenance has been completed. Apr 7, 22:00 EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr 3, 14:49 EDT Scheduled - CallRail will be performing routine scheduled maintenance on Tuesday, April 7th at 10:00pm EDT (02:00 UTC) for 30 minutes. No customer impact is anticipated. Phone calls will continue to route normally throughout the maintenance period.

Read the full incident report →

Minor March 2, 2026

Degraded Performance in Report Export Pipeline

Detected by Pingoru
Mar 02, 2026, 01:47 PM UTC
Resolved
Mar 02, 2026, 01:47 PM UTC
Duration
—
Timeline · 1 update
  1. monitoring Mar 02, 2026, 01:47 PM UTC

    Mar 2, 08:47 EST Resolved - This incident has been resolved and the report backlog is now empty. Mar 1, 21:32 EST Monitoring - A fix has been implemented. Our monitors are showing latency is drastically reduced and jobs are now working through the queue at a normal rate. We have added additional server capacity to work through these delayed jobs as quickly as possible. Mar 1, 19:55 EST Identified - We are currently experiencing delays in report exports due to degraded performance in our export pipeline. Our engineering team has identified the root cause and is implementing a fix. No reports have been lost. We will continue to provide updates and appreciate your patience.

Read the full incident report →

Minor February 3, 2026

Intermittent Call Failover to Voice Mail

Detected by Pingoru
Feb 03, 2026, 09:21 PM UTC
Resolved
Feb 03, 2026, 09:21 PM UTC
Duration
—
Timeline · 1 update
  1. monitoring Feb 03, 2026, 09:21 PM UTC

    Feb 3, 16:21 EST Resolved - This issue has been resolved with the vendor, and systems are now operating normally. Feb 3, 16:02 EST Monitoring - We are aware of an upstream vendor issue that is causing intermittent failure of calls to route properly to Voice Assist. These calls are instead falling over to voice mail, and the caller will hear a voice mail greeting. We are monitoring the problem and exploring potential workarounds.

Read the full incident report →

Minor January 29, 2026

Latency in transcript delivery

Detected by Pingoru
Jan 29, 2026, 08:28 PM UTC
Resolved
Jan 29, 2026, 08:28 PM UTC
Duration
—
Timeline · 1 update
  1. monitoring Jan 29, 2026, 08:28 PM UTC

    Jan 29, 15:28 EST Resolved - We are no longer seeing transcript latency. This issue has been resolved. Jan 29, 14:18 EST Identified - Transcript delivery latency is recovering. We are continuing to monitor performance and provide updates until fully resolved. Jan 29, 13:44 EST Investigating - We are investigating increased latency in transcript delivery due to an issue with an upstream provider.

Read the full incident report →

Minor October 23, 2025

Outbound calling for Lead Center customers

Detected by Pingoru
Oct 23, 2025, 02:39 PM UTC
Resolved
Oct 23, 2025, 02:39 PM UTC
Duration
—
Timeline · 1 update
  1. monitoring Oct 23, 2025, 02:39 PM UTC

    Oct 23, 10:39 EDT Resolved - This incident has been resolved. Oct 23, 10:01 EDT Monitoring - A fix has been deployed, and we will continue to monitor. Oct 23, 09:49 EDT Identified - The issue has been identified and a fix is being implemented. Oct 23, 09:40 EDT Investigating - We are currently investigating the degraded performance for lead center outbound calling.

Read the full incident report →

Minor August 21, 2025

Upstream provider failure

Detected by Pingoru
Aug 21, 2025, 08:31 PM UTC
Resolved
Aug 21, 2025, 08:31 PM UTC
Duration
—
Timeline · 1 update
  1. monitoring Aug 21, 2025, 08:31 PM UTC

    Aug 21, 16:31 EDT Resolved - This issue has been resolved. Caller details are again available. Aug 21, 15:52 EDT Update - We are continuing to monitor this issue. The vendor has deployed a mitigation and we are seeing improvement. Until fully resolved, this issue will continue causing the following impacts for a small percentage of calls: some caller details may be delayed and may show as "unknown" until the vendor issue is resolved We sincerely apologize for any disruption this may cause. Aug 21, 14:52 EDT Investigating - We have identified an issue with an upstream vendor and are actively working with them to mitigate the situation. This issue is causing the following impacts: - some caller details may be delayed and may show as "unknown" until the vendor issue is resolved We sincerely apologize for any disruption this may cause.

Read the full incident report →

Minor July 22, 2025

HubSpot integration not sending call recordings

Detected by Pingoru
Jul 22, 2025, 05:24 PM UTC
Resolved
Jul 22, 2025, 07:40 PM UTC
Duration
2h 16m
Affected: Hubspot
Timeline · 2 updates
  1. investigating Jul 22, 2025, 05:24 PM UTC

    Our HubSpot integration is experiencing an issue with call recordings. Contact data as well as call, text, and form activities are flowing, but recordings are not sending for calls.

  2. resolved Jul 22, 2025, 07:40 PM UTC

    This incident has been resolved and call recordings are posting successfully to HubSpot.

Read the full incident report →

Minor July 14, 2025

Call routing issues for Lead Center

Detected by Pingoru
Jul 14, 2025, 04:59 PM UTC
Resolved
Jul 14, 2025, 06:51 PM UTC
Duration
1h 52m
Affected: Softphone
Timeline · 3 updates
  1. investigating Jul 14, 2025, 04:59 PM UTC

    We are hearing reports that an upstream carrier may be having trouble resulting in some call routing failures for our Lead Center customers. We are investigating

  2. monitoring Jul 14, 2025, 06:09 PM UTC

    The third party provider has resolved their issue and is in monitoring. Our own error rate seems to have recovered, so we believe the issue is resolved, but will continue monitoring for a short time.

  3. resolved Jul 14, 2025, 06:51 PM UTC

    Our third party vendor will continue monitoring for a while, but our services are all functioning as expected.

Read the full incident report →

Notice July 2, 2025

Text messages not appearing in the timeline

Detected by Pingoru
Jul 02, 2025, 07:03 PM UTC
Resolved
Jul 02, 2025, 08:48 PM UTC
Duration
1h 44m
Timeline · 4 updates
  1. investigating Jul 02, 2025, 07:03 PM UTC

    There is currently an issue with text conversations not loading in the timeline. We are investigating the issue.

  2. identified Jul 02, 2025, 07:16 PM UTC

    We have identified the issue and we are currently working on a fix.

  3. monitoring Jul 02, 2025, 07:33 PM UTC

    Fix has been implemented for the issue and we are now monitoring.

  4. resolved Jul 02, 2025, 08:48 PM UTC

    The issue has been resolved.

Read the full incident report →

Minor July 2, 2025

Google Ads disruption of service

Detected by Pingoru
Jul 02, 2025, 05:23 PM UTC
Resolved
Jul 03, 2025, 12:23 PM UTC
Duration
19h
Affected: Google Ads
Timeline · 5 updates
  1. investigating Jul 02, 2025, 05:23 PM UTC

    Google Ads is reporting disruptions to its Ads Manager service, which includes the APIs used by our integration. https://ads.google.com/status/publisher/incidents/xF9wKox7evao5WupR7mu Customers using CallRail's Google Ads Integration may experience degraded service or intermittent failures due to issues with the upstream provider, including delayed conversion reporting data and missing or incorrect CPL, keyword, and campaign data. Customers may also experience issues configuring or authorizing the Google Ads Integration on CallRail's platform. We are closely monitoring the fix and will report when service is restored for all customers.

  2. monitoring Jul 02, 2025, 06:32 PM UTC

    We are still closely monitoring the issue at this time.

  3. monitoring Jul 02, 2025, 07:46 PM UTC

    We are still closely monitoring the issue at this time.

  4. monitoring Jul 03, 2025, 12:04 AM UTC

    We are still closely monitoring the issue at this time.

  5. resolved Jul 03, 2025, 12:23 PM UTC

    The incident has been resolved and the Google Ads integration is functioning normally.

Read the full incident report →

Major May 28, 2025

Facebook Integration disruption of service

Detected by Pingoru
May 28, 2025, 01:45 PM UTC
Resolved
May 28, 2025, 03:23 PM UTC
Duration
1h 37m
Affected: Other Integrations
Timeline · 3 updates
  1. identified May 28, 2025, 01:45 PM UTC

    Our monitoring indicates disruption to the APIs used by our Facebook Integration. Customers using CallRail's Facebook Integration may experience degraded service or intermittent failures due to issues with the upstream provider, including delayed conversion reporting data and missing or incorrect CPL, keyword, and campaign data. Customers may also experience issues configuring or authorizing the Facebook Integration on CallRail's platform. We are closely monitoring the fix and will report when service is restored for all customers.

  2. monitoring May 28, 2025, 03:05 PM UTC

    Our monitoring indicates that the previously reported errors are now clearing. We are continuing to observe the situation closely to confirm full resolution.

  3. resolved May 28, 2025, 03:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 13, 2025

Events passed in Google Analytics integration are missing attribution data

Detected by Pingoru
May 13, 2025, 05:59 PM UTC
Resolved
May 13, 2025, 08:12 PM UTC
Duration
2h 12m
Affected: Google Analytics
Timeline · 2 updates
  1. identified May 13, 2025, 05:59 PM UTC

    We have been made aware of a change in format for the session cookie issued by Google Analytics (GA4) that is causing events to be passed without standard GA4 attribution data. This impacts calls and texts to website pools as well as form submissions that are sent to GA4 via our integration. These events will show in report with attribution data of "not set" and default channel grouping of "undefined". In-app reporting and other integrations are not impacted.

  2. resolved May 13, 2025, 08:12 PM UTC

    The issue is now resolved. Note that due to GA processing times, you may need to wait until tomorrow (5/14) to see this reflected in your reports.

Read the full incident report →

Minor May 12, 2025

Investigating reports of API users recieving 500 Internal Server errors

Detected by Pingoru
May 12, 2025, 04:53 PM UTC
Resolved
May 12, 2025, 05:06 PM UTC
Duration
12m
Timeline · 2 updates
  1. investigating May 12, 2025, 04:53 PM UTC

    We are investigating reports of API users recieving 500 Internal Server errors. No other functionality should be impacted. Calls are continuing to route.

  2. resolved May 12, 2025, 05:06 PM UTC

    This incident has been resolved. All functionality has been restored.

Read the full incident report →

Minor May 1, 2025

Ongoing report exporting delays

Detected by Pingoru
May 01, 2025, 02:06 PM UTC
Resolved
May 01, 2025, 06:39 PM UTC
Duration
4h 32m
Affected: Reports
Timeline · 3 updates
  1. investigating May 01, 2025, 02:06 PM UTC

    We are investigating delays with report exports completing. The reports are loading and are viewable in the application.

  2. monitoring May 01, 2025, 03:59 PM UTC

    Our engineering team identified the cause of the slow report exports and have added additional capacity to mitigate the export issues. We are monitoring the system and will continue to make updates as they become available.

  3. resolved May 01, 2025, 06:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 26, 2025

iOS CallRail app loading delays

Detected by Pingoru
Apr 26, 2025, 05:52 PM UTC
Resolved
Apr 30, 2025, 02:55 PM UTC
Duration
3d 21h
Timeline · 2 updates
  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

Detected by Pingoru
Apr 19, 2025, 05:04 PM UTC
Resolved
Apr 19, 2025, 07:02 PM UTC
Duration
1h 57m
Affected: Lead Center General
Timeline · 3 updates
  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 →