Aug <var data-var='date'>20</var>, <var data-var='time'>12:15</var> EDT Resolved - This incident has been resolved. Aug <var data-var='date'>20</var>, <var data-var='time'>12:04</var> EDT Update - We are continuing to monitor for any further issues. Aug <var data-var='date'>20</var>, <var data-var='time'>11:59</var> EDT Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'>20</var>, <var data-var='time'>11:56</var> EDT Update - We are continuing to work on a fix for this issue. Aug <var data-var='date'>20</var>, <var data-var='time'>11:34</var> EDT Identified - The issue has been identified and a fix is being implemented.

Integrations Connection Error

Aug <var data-var='date'>20</var>, <var data-var='time'>11:25</var> EDT Resolved - This incident has been resolved. Aug <var data-var='date'>20</var>, <var data-var='time'>10:58</var> EDT Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'>20</var>, <var data-var='time'>10:20</var> EDT Identified - The issue has been identified and a fix is being implemented. Aug <var data-var='date'>20</var>, <var data-var='time'>10:17</var> EDT Update - We are continuing to investigate this issue. Aug <var data-var='date'>20</var>, <var data-var='time'>10:13</var> EDT Investigating - We are currently investigating this issue.

Transcriptions API Timeout

Aug <var data-var='date'>17</var>, <var data-var='time'>14:06</var> EDT Resolved - This incident has been resolved, and PCI Insights should be processing normally. Aug <var data-var='date'>17</var>, <var data-var='time'>13:32</var> EDT Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'>17</var>, <var data-var='time'>13:10</var> EDT Investigating - We are investigating an issue that may cause some PCI insights to be delayed. We sincerely apologize for any inconvenience these delays may cause.

PCI Insights Delay

Jun <var data-var='date'>22</var>, <var data-var='time'>23:34</var> EDT Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>22</var>, <var data-var='time'>22:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>17</var>, <var data-var='time'>16:17</var> EDT Scheduled - CallRail will be performing routine scheduled maintenance on Monday, June 22nd at 10:00pm EDT (02:00 UTC) for two hours. No customer impact is anticipated. Phone calls will continue to route normally throughout the maintenance period.

Scheduled maintenance for CallRail Applications

May <var data-var='date'> 9</var>, <var data-var='time'>07:15</var> EDT Resolved - This incident has been resolved. May <var data-var='date'> 8</var>, <var data-var='time'>14:09</var> EDT Identified - 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.

Lead Center incoming call notification issue on iOS

Apr <var data-var='date'> 7</var>, <var data-var='time'>22:30</var> EDT Completed - The scheduled maintenance has been completed. Apr <var data-var='date'> 7</var>, <var data-var='time'>22:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr <var data-var='date'> 3</var>, <var data-var='time'>14:49</var> 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.

Mar <var data-var='date'> 2</var>, <var data-var='time'>08:47</var> EST Resolved - This incident has been resolved and the report backlog is now empty. Mar <var data-var='date'> 1</var>, <var data-var='time'>21:32</var> 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 <var data-var='date'> 1</var>, <var data-var='time'>19:55</var> 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.

Degraded Performance in Report Export Pipeline

Feb <var data-var='date'>24</var>, <var data-var='time'>00:00</var> EST Completed - The scheduled maintenance has been completed. Feb <var data-var='date'>23</var>, <var data-var='time'>22:47</var> EST Verifying - Verification is currently underway for the maintenance items. Feb <var data-var='date'>23</var>, <var data-var='time'>22:45</var> EST Update - Scheduled maintenance is still in progress. We will provide updates as necessary. Feb <var data-var='date'>23</var>, <var data-var='time'>22:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'>18</var>, <var data-var='time'>13:12</var> EST Scheduled - CallRail will be performing system-wide maintenance, beginning Monday, February 23, at 10 pm ET and ending Tuesday, February 24, at 1 am ET (3:00 - 6:00 UTC). During the scheduled 3-hour outage: - Access to CallRail reporting, messaging, API, and Lead Center will be disabled during this time. - Calls forwarded to a non-CallRail number will continue to route, but softphone availability will be impacted. This means if you usually receive or make calls in Lead Center, you will be unable to do so during the scheduled maintenance window. If you will need to receive calls during the scheduled maintenance window, we recommend that your Call Flows forward unanswered calls to voicemail or an outside phone number. - Calls to Voice Assist will continue to route successfully. - Notifications, call recordings, and transcriptions (including missed inbound calls) will be delayed but will be available shortly after maintenance is completed. - If you are attempting to sign up for a new account or a free trial of CallRail during the scheduled maintenance window, you will receive an error message. CallRail is committed to providing stable and reliable service as your business continues to grow, and this system-wide maintenance is a part of that commitment. The maintenance window was chosen to reduce downtime during normal operating hours. We apologize for any inconvenience this maintenance may cause.

Systemwide Scheduled Maintenance

Feb <var data-var='date'> 3</var>, <var data-var='time'>16:21</var> EST Resolved - This issue has been resolved with the vendor, and systems are now operating normally. Feb <var data-var='date'> 3</var>, <var data-var='time'>16:02</var> 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.

Intermittent Call Failover to Voice Mail

Jan <var data-var='date'>30</var>, <var data-var='time'>10:04</var> EST Resolved - The remaining areas of messaging impact have been resolved. Jan <var data-var='date'>30</var>, <var data-var='time'>09:25</var> EST Update - We continued to see intermittent impact in outbound messages overnight. We will continue monitoring the situation and provide further updates until fully resolved. Jan <var data-var='date'>29</var>, <var data-var='time'>17:55</var> EST Monitoring - There has been significant improvement in inbound and outbound text messaging. We will continue monitoring the situation and will provide another update tomorrow morning at 9a ET. Jan <var data-var='date'>29</var>, <var data-var='time'>15:49</var> EST Update - We are continuing to see intermittent impact in inbound and outbound messages. We are monitoring the situation and will continue to provide further updates until resolved. Jan <var data-var='date'>29</var>, <var data-var='time'>14:34</var> EST Update - We are continuing to see intermittent impact in inbound and outbound messages. We are monitoring the situation and will continue to provide further updates until resolved. Jan <var data-var='date'>29</var>, <var data-var='time'>12:28</var> EST Identified - We are continuing to see intermittent impact in inbound and outbound messages. We are monitoring the situation and will continue to provide further updates until resolved. Jan <var data-var='date'>29</var>, <var data-var='time'>10:45</var> EST Investigating - One of our providers is reporting delays in both SMS and MMS delivery. We are seeing intermittent impact in both inbound and outbound messages. We will continue monitoring and providing updates.

SMS and MMS Provider Delays

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

Latency in transcript delivery

Dec <var data-var='date'> 4</var>, <var data-var='time'>01:28</var> EST Completed - The scheduled maintenance has been completed. Dec <var data-var='date'> 4</var>, <var data-var='time'>00:24</var> EST Verifying - Verification is currently underway for the maintenance items. Dec <var data-var='date'> 3</var>, <var data-var='time'>22:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Dec <var data-var='date'> 1</var>, <var data-var='time'>11:04</var> EST Scheduled - CallRail will be performing system-wide maintenance, beginning Wednesday, December 3, at 10 pm ET and ending Thursday, December 4, at 2 am ET (5:00 - 9:00 UTC). During the scheduled 4-hour outage: - Access to CallRail reporting, messaging, API, and Lead Center will be disabled during this time. - Calls forwarded to a non-CallRail number will continue to route, but softphone availability will be impacted. This means if you usually receive or make calls in Lead Center, you will be unable to do so during the scheduled maintenance window. If you will need to receive calls during the scheduled maintenance window, we recommend that your Call Flows forward unanswered calls to voicemail or an outside phone number. - Calls to Voice Assist will continue to route successfully. - Notifications, call recordings, and transcriptions (including missed inbound calls) will be delayed but will be available shortly after maintenance is completed. - If you are attempting to sign up for a new account or a free trial of CallRail during the scheduled maintenance window, you will receive an error message. CallRail is committed to providing stable and reliable service as your business continues to grow, and this system-wide maintenance is a part of that commitment. The maintenance window was chosen to reduce downtime during normal operating hours. We apologize for any inconvenience this maintenance may cause.

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

Outbound calling for Lead Center customers

Oct <var data-var='date'>21</var>, <var data-var='time'>09:00</var> EDT Resolved - This incident has been resolved. Oct <var data-var='date'>20</var>, <var data-var='time'>19:16</var> EDT Update - Our infrastructure provider, AWS, is reporting all issues resolved on their end. We will continue to monitor for any residual issues. Oct <var data-var='date'>20</var>, <var data-var='time'>17:29</var> EDT Update - We continue to monitor for intermittent issues as our upstream infrastructure provider, AWS, works toward full stability. We are actively working to mitigate residual effects wherever possible. While active calls are routing and tracking data is being captured, some customers are currently experiencing latency across services. Oct <var data-var='date'>20</var>, <var data-var='time'>15:00</var> EDT Update - We continue to monitor for intermittent issues as our upstream infrastructure provider, AWS, works toward full stability. We are actively working to mitigate residual effects wherever possible. While active calls are routing and tracking data is being captured, some customers are currently experiencing latency across services. Oct <var data-var='date'>20</var>, <var data-var='time'>10:23</var> EDT Update - All CallRail services are currently performing as intended. We continue to monitor closely due to ongoing challenges in scaling additional infrastructure, but there is no known customer-facing impact at this time. Oct <var data-var='date'>20</var>, <var data-var='time'>07:45</var> EDT Monitoring - CallRail's infrastructure has recovered and our primary systems are back online. Some of our upstream providers are still recovering. At this time most calls are routing as expected, although with minor audio degradation effects. We continue to monitor closely to ensure no lingering issues remain. Oct <var data-var='date'>20</var>, <var data-var='time'>05:45</var> EDT Update - The infrastructure provider is working on a resolution and expecting gradual recovery of services. We are continuing to monitor the infrastructure provider's status page. Disruptions to CallRail app may persist during this time. We will continue to provide updates as we have more information to share. Oct <var data-var='date'>20</var>, <var data-var='time'>04:53</var> EDT Identified - We have identified the issue- the infrastructure provider has reported errors and is currently working on resolving these. We are closely monitoring their status page for updates. Several CallRail services, including, but not limited to call tracking, API, and DNI, are affected. We sincerely apologize for the disruption. Oct <var data-var='date'>20</var>, <var data-var='time'>04:02</var> EDT Update - We've identified an issue with our infrastructure provider. We are investigating possible solutions. Oct <var data-var='date'>20</var>, <var data-var='time'>03:47</var> EDT Investigating - There are likely issues logging in to the CallRail web app and mobile app. We are aware of these issues and are taking rapid action to resolve the situation. Aside from being able to log in, here are additional impacts you may be experiencing: <ul> <li>Calls forwarded to a non-CallRail number will continue to route, but softphone availability is impacted. <li>The web dashboard is currently unavailable. However, calls, texts, and chats will continue to be tracked. Similarly, call recordings and notifications will be delayed, but will be available once the issue is resolved. <li>Form data may not be captured by CallRail during this issue, but will still be collected by any external form providers. </ul> Your ability to track and receive calls and other transactions is of critical importance to us at CallRail. We are actively working on a resolution and apologize for any disruptions you are experiencing related to this issue.

Infrastructure outage impacts CallRail services

Aug <var data-var='date'>26</var>, <var data-var='time'>00:07</var> EDT Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>25</var>, <var data-var='time'>22:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>20</var>, <var data-var='time'>14:44</var> EDT Scheduled - CallRail is performing system-wide maintenance, resulting in a scheduled outage of up to 4 hours on Monday, August 25 2025 from 22:00 EST to 02:00 EST on Tuesday, August 26 (02:00-06:00 UTC). During the scheduled maintenance: - Access to CallRail reporting, messaging, API, and Lead Center will be disabled during this time. - Calls forwarded to a non-CallRail number will continue to route, but softphone availability will be impacted. This means if you usually receive or make calls in Lead Center, you will be unable to do so during the scheduled maintenance window. If you anticipate needing to receive calls during the maintenance window, we urge you to ensure that your Call Flows forward unanswered calls to voicemail or an outside phone number. - Calls to Voice Assist will continue to route successfully. - Notifications, call recordings, and transcriptions (including missed inbound calls) will be delayed, but available shortly after maintenance is completed.

Scheduled System Maintenance

Aug <var data-var='date'>21</var>, <var data-var='time'>16:31</var> EDT Resolved - This issue has been resolved. Caller details are again available. Aug <var data-var='date'>21</var>, <var data-var='time'>15:52</var> 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 <var data-var='date'>21</var>, <var data-var='time'>14:52</var> 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.

Upstream provider failure

Jul <var data-var='date'>22</var>, <var data-var='time'>15:40</var> EDT Resolved - This incident has been resolved and call recordings are posting successfully to HubSpot. Jul <var data-var='date'>22</var>, <var data-var='time'>13:24</var> EDT Investigating - 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.

HubSpot integration not sending call recordings

Jul <var data-var='date'>14</var>, <var data-var='time'>14:51</var> EDT Resolved - Our third party vendor will continue monitoring for a while, but our services are all functioning as expected. Jul <var data-var='date'>14</var>, <var data-var='time'>14:09</var> EDT Monitoring - 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. Jul <var data-var='date'>14</var>, <var data-var='time'>12:59</var> EDT Investigating - 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

Call routing issues for Lead Center

Jul <var data-var='date'> 3</var>, <var data-var='time'>08:23</var> EDT Resolved - The incident has been resolved and the Google Ads integration is functioning normally. Jul <var data-var='date'> 2</var>, <var data-var='time'>20:04</var> EDT Update - We are still closely monitoring the issue at this time. Jul <var data-var='date'> 2</var>, <var data-var='time'>15:46</var> EDT Update - We are still closely monitoring the issue at this time. Jul <var data-var='date'> 2</var>, <var data-var='time'>14:32</var> EDT Monitoring - We are still closely monitoring the issue at this time. Jul <var data-var='date'> 2</var>, <var data-var='time'>13:23</var> EDT Investigating - 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.

Google Ads disruption of service

Jul <var data-var='date'> 2</var>, <var data-var='time'>16:48</var> EDT Resolved - The issue has been resolved. Jul <var data-var='date'> 2</var>, <var data-var='time'>15:33</var> EDT Monitoring - Fix has been implemented for the issue and we are now monitoring. Jul <var data-var='date'> 2</var>, <var data-var='time'>15:16</var> EDT Identified - We have identified the issue and we are currently working on a fix. Jul <var data-var='date'> 2</var>, <var data-var='time'>15:03</var> EDT Investigating - There is currently an issue with text conversations not loading in the timeline. We are investigating the issue.

Text messages not appearing in the timeline

Jun <var data-var='date'>12</var>, <var data-var='time'>17:23</var> EDT Resolved - This incident has been resolved. Jun <var data-var='date'>12</var>, <var data-var='time'>17:01</var> EDT Update - Google appears to have fixed the issue; we are continuing to monitor for any impacts. Jun <var data-var='date'>12</var>, <var data-var='time'>16:55</var> EDT Monitoring - Google appears to have fixed the issue; we are continuing to monitor for any impacts. Jun <var data-var='date'>12</var>, <var data-var='time'>14:17</var> EDT Update - Google Ads is reporting disruptions to its Ads Manager service, which includes the APIs used by our integration. 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. Jun <var data-var='date'>12</var>, <var data-var='time'>14:16</var> EDT Update - We are continuing to work on a fix for this issue. Jun <var data-var='date'>12</var>, <var data-var='time'>14:12</var> EDT Identified - Google Ads is reporting disruptions to its Ads Manager service, which includes the APIs used by our integration. 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.

May <var data-var='date'>28</var>, <var data-var='time'>11:23</var> EDT Resolved - This incident has been resolved. May <var data-var='date'>28</var>, <var data-var='time'>11:05</var> EDT Monitoring - Our monitoring indicates that the previously reported errors are now clearing. We are continuing to observe the situation closely to confirm full resolution. May <var data-var='date'>28</var>, <var data-var='time'>09:45</var> EDT Identified - 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.

Facebook Integration disruption of service

May <var data-var='date'>15</var>, <var data-var='time'>10:12</var> EDT Resolved - The incident has been resolved and the Google Ads integration is functioning normally. May <var data-var='date'>15</var>, <var data-var='time'>09:59</var> EDT Identified - 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/kUAodsf3fRfrx2Gu7wLs 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.

May <var data-var='date'>13</var>, <var data-var='time'>16:12</var> EDT Resolved - 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. May <var data-var='date'>13</var>, <var data-var='time'>13:59</var> EDT Identified - 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.

Events passed in Google Analytics integration are missing attribution data

May <var data-var='date'>12</var>, <var data-var='time'>13:06</var> EDT Resolved - This incident has been resolved. All functionality has been restored. May <var data-var='date'>12</var>, <var data-var='time'>12:53</var> EDT Investigating - We are investigating reports of API users recieving 500 Internal Server errors. No other functionality should be impacted. Calls are continuing to route.

Is CallRail down?

CallRail status is UP

Lastest published events

Integrations Connection Error

Transcriptions API Timeout

PCI Insights Delay

CallRail Services, Components and Regions

Recent CallRail events

Integrations Connection Error

Transcriptions API Timeout

PCI Insights Delay

Scheduled maintenance for CallRail Applications

Lead Center incoming call notification issue on iOS

Scheduled maintenance for CallRail Applications