Historial de interrupciones de Callrail

1. 23 de octubre de 2026 a las 13:51 UTCinvestigating

   Un incidente en Unbounce ha dejado inoperable la integración entre CallRail y Unbounce desde aproximadamente las 18:00 el 22 de octubre. Nuestro equipo está trabajando activamente con ellos para restaurar la funcionalidad.

2. 23 de octubre de 2026 a las 14:51 UTCinvestigating

   Seguimos investigando esta situación.

3. 23 de octubre de 2026 a las 16:05 UTCidentified

   Identificaron el tema y trabajando en una solución.

4. 23 de octubre de 2026 a las 17:10 UTCidentified

   Continuamos trabajando en la solución.

5. 23 de octubre de 2026 a las 18:02 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

6. 23 de octubre de 2026 a las 19:57 UTCmonitoring

   Continuamos monitoreando la solución

7. 23 de octubre de 2026 a las 20:22 UTCresolved

   El incidente se ha resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 1 de septiembre de 2026 a las 17:01 UTCmonitoring

   Hemos identificado una cuestión con un proveedor de asistencia y estamos trabajando activamente con ellos para mitigar la situación. This issue is causing the following impacts: - Call Performance - Call Recording Disponibilidad Sinceramente nos disculpamos por cualquier perturbación que esto pueda causar.

2. 1 de septiembre de 2026 a las 17:29 UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

3. 1 de septiembre de 2026 a las 19:53 UTCmonitoring

   El vendedor de corriente arriba ha resuelto la salida y estamos viendo rendimiento para la mayoría de los productos regresan a la normalidad. Sin embargo, los clientes todavía pueden experimentar retrasos con la disponibilidad de Call Recording ya que nuestro sistema trabaja para procesar el atraso de las grabaciones que ocurrieron durante la salida del proveedor.

4. 1 de septiembre de 2026 a las 23:24 UTCmonitoring

   El proveedor de corriente ha resuelto el problema y estamos viendo rendimiento para todos los productos afectados regresan a la normalidad.

5. 1 de septiembre de 2026 a las 23:25 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 28 de agosto de 2026 a las 14:49 UTCidentified

   Somos conscientes de un problema en la aplicación CallRail iOS Mobile donde los Registros de Llamada y Forma no logran renderizar. Hemos identificado el tema y nuestro equipo está trabajando en una solución para resolver. El problema ocurre cuando la aplicación devuelve más de 1 página de datos a mostrar. Los clientes pueden trabajar en torno a este problema utilizando los filtros de fecha para reducir el rango de fechas de modo que se devuelva un pequeño conjunto de resultados.

2. 28 de agosto de 2026 a las 19:59 UTCresolved

   Este incidente ha sido resuelto. Para implementar la solución, actualice su aplicación CallRail Mobile a la versión 6.12.1 o posterior.

Traducido automáticamente desde la actualización oficial del incidente.

1. 20 de agosto de 2026 a las 15:34 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

2. 20 de agosto de 2026 a las 15:56 UTCidentified

   Seguimos trabajando en una solución para esta cuestión.

3. 20 de agosto de 2026 a las 15:59 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. 20 de agosto de 2026 a las 16:04 UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

5. 20 de agosto de 2026 a las 16:15 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 20 de agosto de 2026 a las 14:13 UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. 20 de agosto de 2026 a las 14:17 UTCinvestigating

   Seguimos investigando esta cuestión.

3. 20 de agosto de 2026 a las 14:20 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

4. 20 de agosto de 2026 a las 14:58 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

5. 20 de agosto de 2026 a las 15:25 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 17 de agosto de 2026 a las 17:10 UTCinvestigating

   Estamos investigando un problema que puede causar que algunas ideas de PCI sean retrasadas. Sinceramente nos disculpamos por cualquier inconveniente que estos retrasos puedan causar.

2. 17 de agosto de 2026 a las 17:32 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. 17 de agosto de 2026 a las 18:06 UTCresolved

   Este incidente se ha resuelto, y PCI Insights debe procesarse normalmente.

Traducido automáticamente desde la actualización oficial del incidente.

1. 8 de mayo de 2026 a las 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 de mayo de 2026 a las 11:15 UTCresolved

   This incident has been resolved.

1. 2 de marzo de 2026 a las 0: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 de marzo de 2026 a las 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. 2 de marzo de 2026 a las 13:47 UTCresolved

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

1. 3 de febrero de 2026 a las 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 de febrero de 2026 a las 21:21 UTCresolved

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

1. 29 de enero de 2026 a las 18:44 UTCinvestigating

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

2. 29 de enero de 2026 a las 19:18 UTCidentified

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

3. 29 de enero de 2026 a las 20:28 UTCresolved

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

1. 29 de enero de 2026 a las 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 de enero de 2026 a las 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 de enero de 2026 a las 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 de enero de 2026 a las 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 de enero de 2026 a las 15:04 UTCresolved

   The remaining areas of messaging impact have been resolved.

1. 23 de octubre de 2025 a las 13:40 UTCinvestigating

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

2. 23 de octubre de 2025 a las 13:49 UTCidentified

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

3. 23 de octubre de 2025 a las 14:01 UTCmonitoring

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

4. 23 de octubre de 2025 a las 14:39 UTCresolved

   This incident has been resolved.

1. 20 de octubre de 2025 a las 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. 20 de octubre de 2025 a las 8:02 UTCinvestigating

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

3. 20 de octubre de 2025 a las 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. 20 de octubre de 2025 a las 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. 20 de octubre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 13:00 UTCresolved

   This incident has been resolved.

1. 21 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 20:31 UTCresolved

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

1. 22 de julio de 2025 a las 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 de julio de 2025 a las 19:40 UTCresolved

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

1. 14 de julio de 2025 a las 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 de julio de 2025 a las 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 de julio de 2025 a las 18:51 UTCresolved

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

1. 2 de julio de 2025 a las 19:03 UTCinvestigating

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

2. 2 de julio de 2025 a las 19:16 UTCidentified

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

3. 2 de julio de 2025 a las 19:33 UTCmonitoring

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

4. 2 de julio de 2025 a las 20:48 UTCresolved

   The issue has been resolved.

1. 2 de julio de 2025 a las 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 de julio de 2025 a las 0:04 UTCmonitoring

   We are still closely monitoring the issue at this time.

3. 3 de julio de 2025 a las 12:23 UTCresolved

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

1. 12 de junio de 2025 a las 18:16 UTCidentified

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

2. 12 de junio de 2025 a las 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 de junio de 2025 a las 21:01 UTCmonitoring

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

4. 12 de junio de 2025 a las 21:23 UTCresolved

   This incident has been resolved.

1. 28 de mayo de 2025 a las 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 de mayo de 2025 a las 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 de mayo de 2025 a las 15:23 UTCresolved

   This incident has been resolved.