Callrail 장애 기록

1. 2026년 9월 1일 PM 5:01 UTCmonitoring

   우리는 업스트림 공급 업체와 문제점을 확인하고 상황을 완화하기 위해 그들과 적극적으로 협력하고 있습니다. 이 문제는 다음과 같은 영향을 미칩니다. - 전화 성능 - 통화 녹음 가능 우리는 진심으로 모든 혼란에 대한 사과가 발생 할 수 있습니다.

2. 2026년 9월 1일 PM 5:29 UTCmonitoring

   우리는 더 많은 문제를 모니터링하고 있습니다.

3. 2026년 9월 1일 PM 7:53 UTCmonitoring

   상류 납품업자는 outage를 해결하고 우리는 정상에 대부분의 제품 반환을 위한 성과를 보고하고 있습니다. 그러나, 고객은 여전히 우리의 시스템으로 통화 녹음 가용성과 지연을 경험할 수 있습니다.

4. 2026년 9월 1일 PM 11:24 UTCmonitoring

   업스트림 공급 업체는 문제를 해결하고 우리는 모든 영향을받는 제품에 대한 성능이 정상으로 돌아 왔습니다.

5. 2026년 9월 1일 PM 11:25 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 28일 PM 2:49 UTCidentified

   CallRail iOS Mobile 애플리케이션에 문제가 있습니다. 통화 및 양식 로그가 렌더링되지 않습니다. 우리는 문제점을 확인하고 우리의 팀은 해결하기 위하여 고침에 일하고 있습니다. 이 문제는 응용 프로그램이 표시 될 데이터의 1 페이지 이상을 반환 할 때 발생합니다. 고객은 날짜 필터를 사용하여 날짜 범위를 축소하여이 문제를 해결할 수 있으므로 더 작은 결과를 반환합니다.

2. 2026년 8월 28일 PM 7:59 UTCresolved

   이 사건은 해결되었습니다. 수정을 구현하려면 CallRail Mobile 응용 프로그램을 버전 6.12.1 이상으로 업데이트하십시오.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 20일 PM 3:34 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

2. 2026년 8월 20일 PM 3:56 UTCidentified

   이 문제를 해결하기 위해 계속 노력하고 있습니다.

3. 2026년 8월 20일 PM 3:59 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

4. 2026년 8월 20일 PM 4:04 UTCmonitoring

   우리는 더 많은 문제를 모니터링하고 있습니다.

5. 2026년 8월 20일 PM 4:15 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 20일 PM 2:13 UTCinvestigating

   우리는 현재이 문제를 조사하고 있습니다.

2. 2026년 8월 20일 PM 2:17 UTCinvestigating

   이 문제를 조사하고 있습니다.

3. 2026년 8월 20일 PM 2:20 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

4. 2026년 8월 20일 PM 2:58 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

5. 2026년 8월 20일 PM 3:25 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 17일 PM 5:10 UTCinvestigating

   PCI 통찰력을 지연시킬 수 있는 문제점을 조사하고 있습니다. 우리는 진심으로이 지연이 발생할 수 있는 불편에 대해 사과합니다.

2. 2026년 8월 17일 PM 5:32 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 8월 17일 PM 6:06 UTCresolved

   이 사건은 해결되고 PCI Insights는 일반적으로 처리해야합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 5월 8일 PM 6: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. 2026년 5월 9일 AM 11:15 UTCresolved

   This incident has been resolved.

1. 2026년 3월 2일 AM 12: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. 2026년 3월 2일 AM 2: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. 2026년 3월 2일 PM 1:47 UTCresolved

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

1. 2026년 2월 3일 PM 9: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. 2026년 2월 3일 PM 9:21 UTCresolved

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

1. 2026년 1월 29일 PM 6:44 UTCinvestigating

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

2. 2026년 1월 29일 PM 7:18 UTCidentified

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

3. 2026년 1월 29일 PM 8:28 UTCresolved

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

1. 2026년 1월 29일 PM 3: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. 2026년 1월 29일 PM 8: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. 2026년 1월 29일 PM 10: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. 2026년 1월 30일 PM 2: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. 2026년 1월 30일 PM 3:04 UTCresolved

   The remaining areas of messaging impact have been resolved.

1. 2025년 10월 23일 PM 1:40 UTCinvestigating

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

2. 2025년 10월 23일 PM 1:49 UTCidentified

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

3. 2025년 10월 23일 PM 2:01 UTCmonitoring

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

4. 2025년 10월 23일 PM 2:39 UTCresolved

   This incident has been resolved.

1. 2025년 10월 20일 AM 7: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. 2025년 10월 20일 AM 8:02 UTCinvestigating

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

3. 2025년 10월 20일 AM 8: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. 2025년 10월 20일 AM 9: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. 2025년 10월 20일 AM 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. 2025년 10월 20일 PM 2: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. 2025년 10월 20일 PM 9: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. 2025년 10월 20일 PM 11:16 UTCmonitoring

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

9. 2025년 10월 21일 PM 1:00 UTCresolved

   This incident has been resolved.

1. 2025년 8월 21일 PM 6: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. 2025년 8월 21일 PM 7: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. 2025년 8월 21일 PM 8:31 UTCresolved

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

1. 2025년 7월 22일 PM 5: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. 2025년 7월 22일 PM 7:40 UTCresolved

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

1. 2025년 7월 14일 PM 4: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. 2025년 7월 14일 PM 6: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. 2025년 7월 14일 PM 6:51 UTCresolved

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

1. 2025년 7월 2일 PM 7:03 UTCinvestigating

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

2. 2025년 7월 2일 PM 7:16 UTCidentified

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

3. 2025년 7월 2일 PM 7:33 UTCmonitoring

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

4. 2025년 7월 2일 PM 8:48 UTCresolved

   The issue has been resolved.

1. 2025년 7월 2일 PM 5: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. 2025년 7월 3일 AM 12:04 UTCmonitoring

   We are still closely monitoring the issue at this time.

3. 2025년 7월 3일 PM 12:23 UTCresolved

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

1. 2025년 6월 12일 PM 6:16 UTCidentified

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

2. 2025년 6월 12일 PM 6: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. 2025년 6월 12일 PM 9:01 UTCmonitoring

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

4. 2025년 6월 12일 PM 9:23 UTCresolved

   This incident has been resolved.

1. 2025년 5월 28일 PM 1: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. 2025년 5월 28일 PM 3: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. 2025년 5월 28일 PM 3:23 UTCresolved

   This incident has been resolved.

1. 2025년 5월 15일 PM 1: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. 2025년 5월 15일 PM 2:12 UTCresolved

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