История сбоев Callrail

1. 1 сентября 2026 г. в 17:01 UTCmonitoring

   Мы определили проблему с поставщиком и активно работаем с ними, чтобы смягчить ситуацию. Эта проблема вызывает следующие последствия: Вызов производительности - Доступность записи звонков Мы искренне извиняемся за любые нарушения, которые это может вызвать.

2. 1 сентября 2026 г. в 17:29 UTCmonitoring

   Мы продолжаем отслеживать любые дополнительные проблемы.

3. 1 сентября 2026 г. в 19:53 UTCmonitoring

   Продавец, работающий на рынке, решил проблему сбоя, и мы видим, что производительность большинства продуктов возвращается к норме. Тем не менее, клиенты могут по-прежнему испытывать задержки с доступностью записи звонков, поскольку наша система работает для обработки отставания записей, которые произошли во время отключения поставщика.

4. 1 сентября 2026 г. в 23:24 UTCmonitoring

   Поставщик решений решил проблему, и мы видим, что производительность всех затронутых продуктов возвращается к норме.

5. 1 сентября 2026 г. в 23:25 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 28 августа 2026 г. в 14:49 UTCidentified

   Мы знаем о проблеме в мобильном приложении CallRail iOS, где журналы вызовов и форм не отображаются. Мы определили проблему, и наша команда работает над решением. Проблема возникает, когда приложение возвращает более 1 страницы данных для отображения. Клиенты могут обойти эту проблему, используя фильтры дат, чтобы сузить диапазон дат, чтобы вернуть меньший набор результатов.

2. 28 августа 2026 г. в 19:59 UTCresolved

   Этот инцидент был урегулирован. Чтобы выполнить исправление, пожалуйста, обновите мобильное приложение CallRail до версии 6.12.1 или более поздней.

Автоматический перевод официального обновления инцидента.

1. 20 августа 2026 г. в 15:34 UTCidentified

   Этот вопрос был определен, и в настоящее время осуществляется исправление.

2. 20 августа 2026 г. в 15:56 UTCidentified

   Мы продолжаем работать над решением этой проблемы.

3. 20 августа 2026 г. в 15:59 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

4. 20 августа 2026 г. в 16:04 UTCmonitoring

   Мы продолжаем отслеживать любые дополнительные проблемы.

5. 20 августа 2026 г. в 16:15 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 20 августа 2026 г. в 14:13 UTCinvestigating

   В настоящее время мы расследуем этот вопрос.

2. 20 августа 2026 г. в 14:17 UTCinvestigating

   Мы продолжаем расследование этого вопроса.

3. 20 августа 2026 г. в 14:20 UTCidentified

   Этот вопрос был определен, и в настоящее время осуществляется исправление.

4. 20 августа 2026 г. в 14:58 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

5. 20 августа 2026 г. в 15:25 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 17 августа 2026 г. в 17:10 UTCinvestigating

   Мы расследуем проблему, которая может привести к задержке некоторых выводов PCI. Мы искренне извиняемся за любые неудобства, которые могут вызвать эти задержки.

2. 17 августа 2026 г. в 17:32 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

3. 17 августа 2026 г. в 18:06 UTCresolved

   Этот инцидент был устранен, и PCI Insights должна обрабатываться нормально.

Автоматический перевод официального обновления инцидента.

1. 8 мая 2026 г. в 18:09 UTCidentified

   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. 9 мая 2026 г. в 11:15 UTCresolved

   This incident has been resolved.

1. 2 марта 2026 г. в 00:55 UTCidentified

   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.

2. 2 марта 2026 г. в 02:32 UTCmonitoring

   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.

3. 2 марта 2026 г. в 13:47 UTCresolved

   This incident has been resolved and the report backlog is now empty.

1. 3 февраля 2026 г. в 21:02 UTCmonitoring

   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.

2. 3 февраля 2026 г. в 21:21 UTCresolved

   This issue has been resolved with the vendor, and systems are now operating normally.

1. 29 января 2026 г. в 18:44 UTCinvestigating

   We are investigating increased latency in transcript delivery due to an issue with an upstream provider.

2. 29 января 2026 г. в 19:18 UTCidentified

   Transcript delivery latency is recovering. We are continuing to monitor performance and provide updates until fully resolved.

3. 29 января 2026 г. в 20:28 UTCresolved

   We are no longer seeing transcript latency. This issue has been resolved.

1. 29 января 2026 г. в 15:45 UTCinvestigating

   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.

2. 29 января 2026 г. в 20:49 UTCidentified

   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.

3. 29 января 2026 г. в 22:55 UTCmonitoring

   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.

4. 30 января 2026 г. в 14:25 UTCmonitoring

   We continued to see intermittent impact in outbound messages overnight. We will continue monitoring the situation and provide further updates until fully resolved.

5. 30 января 2026 г. в 15:04 UTCresolved

   The remaining areas of messaging impact have been resolved.

1. 23 октября 2025 г. в 13:40 UTCinvestigating

   We are currently investigating the degraded performance for lead center outbound calling.

2. 23 октября 2025 г. в 13:49 UTCidentified

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

3. 23 октября 2025 г. в 14:01 UTCmonitoring

   A fix has been deployed, and we will continue to monitor.

4. 23 октября 2025 г. в 14:39 UTCresolved

   This incident has been resolved.

1. 20 октября 2025 г. в 07:47 UTCinvestigating

   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: Calls forwarded to a non-CallRail number will continue to route, but softphone availability is impacted. 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. Form data may not be captured by CallRail during this issue, but will still be collected by any external form providers. 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.

2. 20 октября 2025 г. в 08:02 UTCinvestigating

   We've identified an issue with our infrastructure provider. We are investigating possible solutions.

3. 20 октября 2025 г. в 08:53 UTCidentified

   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.

4. 20 октября 2025 г. в 09:45 UTCidentified

   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.

5. 20 октября 2025 г. в 11:45 UTCmonitoring

   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.

6. 20 октября 2025 г. в 14:23 UTCmonitoring

   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.

7. 20 октября 2025 г. в 21:29 UTCmonitoring

   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.

8. 20 октября 2025 г. в 23:16 UTCmonitoring

   Our infrastructure provider, AWS, is reporting all issues resolved on their end. We will continue to monitor for any residual issues.

9. 21 октября 2025 г. в 13:00 UTCresolved

   This incident has been resolved.

1. 21 августа 2025 г. в 18:52 UTCinvestigating

   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.

2. 21 августа 2025 г. в 19:52 UTCinvestigating

   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.

3. 21 августа 2025 г. в 20:31 UTCresolved

   This issue has been resolved. Caller details are again available.

1. 22 июля 2025 г. в 17:24 UTCinvestigating

   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. 22 июля 2025 г. в 19:40 UTCresolved

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

1. 14 июля 2025 г. в 16:59 UTCinvestigating

   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. 14 июля 2025 г. в 18:09 UTCmonitoring

   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. 14 июля 2025 г. в 18:51 UTCresolved

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

1. 2 июля 2025 г. в 19:03 UTCinvestigating

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

2. 2 июля 2025 г. в 19:16 UTCidentified

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

3. 2 июля 2025 г. в 19:33 UTCmonitoring

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

4. 2 июля 2025 г. в 20:48 UTCresolved

   The issue has been resolved.

1. 2 июля 2025 г. в 17:23 UTCinvestigating

   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. 3 июля 2025 г. в 00:04 UTCmonitoring

   We are still closely monitoring the issue at this time.

3. 3 июля 2025 г. в 12:23 UTCresolved

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

1. 12 июня 2025 г. в 18:16 UTCidentified

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

2. 12 июня 2025 г. в 18:17 UTCidentified

   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.

3. 12 июня 2025 г. в 21:01 UTCmonitoring

   Google appears to have fixed the issue; we are continuing to monitor for any impacts.

4. 12 июня 2025 г. в 21:23 UTCresolved

   This incident has been resolved.

1. 28 мая 2025 г. в 13:45 UTCidentified

   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. 28 мая 2025 г. в 15:05 UTCmonitoring

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

3. 28 мая 2025 г. в 15:23 UTCresolved

   This incident has been resolved.

1. 15 мая 2025 г. в 13:59 UTCidentified

   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.

2. 15 мая 2025 г. в 14:12 UTCresolved

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