56 Callrail incidents · 2024年2月 — official updates, affected components, duration and resolution details.
在Unbounce的一起事件中,CallRail和Unbunce的集成自10月22日大约下午6点起便无法运行. 我们的团队正在积极与他们合作,以恢复功能.
我们正在继续调查这一局势.
查明了问题,并着手解决问题.
我们正在继续努力解决该问题.
一项措施已经执行,我们正在监测结果.
我们继续监视修复工作
此事已决.
自动翻译自官方事件更新。
我们已经与一个上游供应商确定了一个问题,并正同他们积极合作来缓解局势。 这一问题造成以下影响: - 调用性能 - 调用记录可用性 我们对此可能造成的任何破坏表示诚挚的歉意.
我们正在继续监测任何其他问题.
上游供应商解决了停产问题,我们看到大多数产品的业绩恢复正常。 然而,由于我们的系统正在处理供应商停产期间所积压的录音,在提供呼叫记录方面,客户仍然可能遇到延误.
上游供应商已经解决了这一问题,我们看到所有受影响产品的业绩都恢复正常.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们知道CallRail iOS Mobile应用程序上的一个问题是Call和表格日志无法提供。 我们已经确定了这一问题,我们的团队正在设法解决问题。 当应用程序返回超过1页要显示的数据时,就会出现这个问题. 客户可以通过使用日期过滤器来缩小日期范围来围绕这一问题开展工作,这样就可以返回一套较小的结果.
这一事件已经得到解决。 为了执行固定,请更新您的 CallRail Mobile 应用程序到6.12.1 版本或稍后.
自动翻译自官方事件更新。
这一问题已经确定,一个解决办法正在实施之中.
我们正在继续努力解决这个问题。
一项措施已经执行,我们正在监测结果.
我们正在继续监测任何其他问题.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
我们正在继续调查这一问题.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查一个可能导致PCI一些见解被拖延的问题. 我们对这些拖延可能造成的任何不便表示诚挚的歉意.
一项措施已经执行,我们正在监测结果.
这一事件已经解决,PCI Insights应该正常处理.
自动翻译自官方事件更新。
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.
This incident has been resolved.
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.
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.
This incident has been resolved and the report backlog is now empty.
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.
This issue has been resolved with the vendor, and systems are now operating normally.
We are investigating increased latency in transcript delivery due to an issue with an upstream provider.
Transcript delivery latency is recovering. We are continuing to monitor performance and provide updates until fully resolved.
We are no longer seeing transcript latency. This issue has been resolved.
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.
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.
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.
We continued to see intermittent impact in outbound messages overnight. We will continue monitoring the situation and provide further updates until fully resolved.
The remaining areas of messaging impact have been resolved.
We are currently investigating the degraded performance for lead center outbound calling.
The issue has been identified and a fix is being implemented.
A fix has been deployed, and we will continue to monitor.
This incident has been resolved.
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.
We've identified an issue with our infrastructure provider. We are investigating possible solutions.
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.
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.
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.
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.
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.
Our infrastructure provider, AWS, is reporting all issues resolved on their end. We will continue to monitor for any residual issues.
This incident has been resolved.
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.
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.
This issue has been resolved. Caller details are again available.
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.
This incident has been resolved and call recordings are posting successfully to HubSpot.
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
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.
Our third party vendor will continue monitoring for a while, but our services are all functioning as expected.
There is currently an issue with text conversations not loading in the timeline. We are investigating the issue.
We have identified the issue and we are currently working on a fix.
Fix has been implemented for the issue and we are now monitoring.
The issue has been resolved.
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.
We are still closely monitoring the issue at this time.
The incident has been resolved and the Google Ads integration is functioning normally.
We are continuing to work on a fix for this issue.
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.
Google appears to have fixed the issue; we are continuing to monitor for any impacts.
This incident has been resolved.
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.
Our monitoring indicates that the previously reported errors are now clearing. We are continuing to observe the situation closely to confirm full resolution.
This incident has been resolved.
