Historial de interrupciones de Livechat

1. 14 de octubre de 2026 a las 2:08 UTCidentified

   Actualmente estamos investigando el tema con los flujos de trabajo. Nos disculpamos por cualquier inconveniente que esto pueda causar, y nuestro equipo está trabajando diligentemente para resolver el problema lo antes posible.

2. 14 de octubre de 2026 a las 3:07 UTCidentified

   Hemos identificado la causa raíz de la cuestión y estamos trabajando en una solución. El servicio puede permanecer degradado mientras implementamos la solución. Proporcionaremos una actualización tan pronto como tengamos más detalles o un tiempo estimado para la resolución.

3. 14 de octubre de 2026 a las 3:36 UTCmonitoring

   Las correcciones necesarias se han aplicado con éxito al sistema. En este momento, estamos monitoreando activamente los resultados para evaluar la eficacia de estos cambios y asegurar que todo esté funcionando según lo previsto.

4. 14 de octubre de 2026 a las 3:59 UTCresolved

   Se ha resuelto la cuestión de los flujos de trabajo y los servicios funcionan normalmente. Nos disculpamos por cualquier perturbación que esto pueda haber causado y apreciar su paciencia y comprensión.

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

1. 12 de octubre de 2026 a las 17:21 UTCidentified

   Hemos identificado la causa raíz de la cuestión y estamos trabajando en una solución. El servicio puede permanecer degradado mientras implementamos la solución. Proporcionaremos una actualización tan pronto como tengamos más detalles o un tiempo estimado para la resolución.

2. 12 de octubre de 2026 a las 17:45 UTCidentified

   Nuestro equipo sigue trabajando activamente en la solución. Los flujos de trabajo pueden permanecer degradados mientras tanto. Apreciamos su paciencia y compartiremos otra actualización tan pronto como tengamos más detalles o un tiempo estimado para resolver.

3. 12 de octubre de 2026 a las 18:12 UTCidentified

   Nuestro equipo sigue trabajando en la solución. Los flujos de trabajo siguen degradados. Siguiente actualización para seguir.

4. 12 de octubre de 2026 a las 18:40 UTCidentified

   Todavía estamos trabajando para resolver este problema, y los flujos de trabajo siguen siendo degradados. Nuestros ingenieros siguen enfocados en implementar la solución, y estamos monitoreando la situación de cerca. Compartiremos más información en cuanto esté disponible.

5. 12 de octubre de 2026 a las 19:01 UTCidentified

   Todavía estamos trabajando activamente en la solución. El servicio sigue impactado, y nuestros ingenieros están enfocados en volver a la normalidad. Gracias por su paciencia. Compartiremos más información tan pronto como esté disponible.

6. 12 de octubre de 2026 a las 19:25 UTCidentified

   El tema aún no está resuelto, y nuestro equipo sigue trabajando en la solución. Lo actualizaremos de nuevo tan pronto tengamos más información.

7. 12 de octubre de 2026 a las 19:55 UTCidentified

   Todavía estamos trabajando para restaurar el servicio, que sigue siendo degradado. Nuestros ingenieros están totalmente comprometidos, y lamentamos la continua perturbación. Compartiremos otra actualización tan pronto como tengamos progresos para informar.

8. 12 de octubre de 2026 a las 20:26 UTCidentified

   Todavía estamos trabajando para restaurar el servicio. Lo sentimos por la continua perturbación y apreciamos su paciencia. Compartiremos otra actualización tan pronto como tengamos más que informar.

9. 12 de octubre de 2026 a las 21:04 UTCidentified

   Todavía estamos trabajando para restaurar el servicio. Estamos progresando y acercándonos a resolver el problema. Gracias por su paciencia.

10. 12 de octubre de 2026 a las 22:02 UTCidentified

    El servicio sigue degradado, y sabemos que esto ha estado en curso durante varias horas. Nuestro equipo sigue trabajando en restaurarlo. Lo sentimos por la interrupción prolongada.

11. 12 de octubre de 2026 a las 23:12 UTCidentified

    El uso de los flujos de trabajo sigue siendo degradado. Nuestro equipo está trabajando activamente para restaurar la funcionalidad completa. Nos disculpamos por la interrupción prolongada y cualquier inconveniente que esto pueda causar.

12. 13 de octubre de 2026 a las 0:14 UTCidentified

    La funcionalidad de los flujos de trabajo sigue experimentando degradación. Nuestro equipo está trabajando diligentemente para restaurarlo a plena capacidad. Nos disculpamos por la interrupción prolongada y cualquier inconveniente que esto pueda crear.

13. 13 de octubre de 2026 a las 0:23 UTCmonitoring

    Las correcciones necesarias se han aplicado con éxito al sistema. En este momento, estamos monitoreando activamente los resultados para evaluar la eficacia de estos cambios y asegurar que todo esté funcionando según lo previsto.

14. 13 de octubre de 2026 a las 1:00 UTCresolved

    Se ha resuelto la cuestión de los flujos de trabajo y los servicios funcionan normalmente. Nos disculpamos por cualquier perturbación que esto pueda haber causado y apreciar su paciencia y comprensión.

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

1. 26 de septiembre de 2026 a las 13:00 UTCinvestigating

   Actualmente estamos experimentando problemas con iniciar sesión en LiveChat. Nuestro equipo es consciente del problema y está trabajando en resolverlo lo antes posible

2. 26 de septiembre de 2026 a las 13:18 UTCinvestigating

   Estamos investigando un problema que afecta a algunos clientes. Nuestro equipo está trabajando para identificar la causa raíz y restaurar el servicio normal lo antes posible. Compartiremos una actualización tan pronto como esté disponible más información.

3. 26 de septiembre de 2026 a las 13:52 UTCmonitoring

   Se ha aplicado una solución, y estamos monitoreando los resultados. Algunos clientes pueden experimentar perturbaciones menores mientras los sistemas se recuperan. Compartiremos actualizaciones si la situación cambia.

4. 26 de septiembre de 2026 a las 13:58 UTCresolved

   La cuestión se ha resuelto y los servicios funcionan normalmente. No se espera ningún nuevo impacto.

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

1. 28 de julio de 2026 a las 11:30 UTCidentified

   Hemos identificado que el problema está relacionado con un proveedor externo. Trabajamos con ellos para investigar y resolver el problema. El servicio puede seguir degradando mientras se está abordando la cuestión. Proporcionaremos una actualización tan pronto como tengamos más detalles o un tiempo estimado para la resolución.

2. 28 de julio de 2026 a las 11:54 UTCinvestigating

   Estamos investigando un problema que afecta a algunos clientes. El problema puede estar relacionado con un proveedor externo, y estamos trabajando para confirmar la causa y restaurar el servicio normal lo antes posible. Compartiremos una actualización tan pronto como esté disponible más información.

3. 28 de julio de 2026 a las 13:49 UTCinvestigating

   Seguimos trabajando con el proveedor de terceros para resolver el problema. En esta etapa, esperamos recibir más información de ellos como parte de su proceso de examen. Proporcionaremos nuestra próxima actualización tan pronto como tengamos información adicional para compartir o hay un cambio significativo en la situación. Gracias por su paciencia.

4. 29 de julio de 2026 a las 13:01 UTCresolved

   Se ha resuelto el problema con los archivos de apertura y los servicios funcionan normalmente. Lo sentimos por cualquier perturbación que esto pueda haber causado y gracias por su paciencia y comprensión.

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

1. 10 de julio de 2026 a las 2:24 UTCinvestigating

   We have identified a problem affecting Workflows. The Infrastructure team is actively investigating. We will share more information as soon as we have updates.

2. 10 de julio de 2026 a las 2:36 UTCidentified

   We’ve identified the issue affecting Workflows and are working on a fix.

3. 10 de julio de 2026 a las 2:38 UTCidentified

   Fix applied, we are waiting for the service to return to normal.

4. 10 de julio de 2026 a las 2:41 UTCresolved

   The issue has been resolved, and we can confirm that services are operating normally again.

1. 12 de junio de 2026 a las 22:25 UTCinvestigating

   We have identified a problem affecting Workflows. The Infrastructure team is actively investigating. We will share more information as soon as we have updates.

2. 12 de junio de 2026 a las 22:33 UTCidentified

   We’ve identified the issue affecting Workflows and are working on a fix.

3. 12 de junio de 2026 a las 22:55 UTCidentified

   Fix applied, we are waiting for the service to return to normal.

4. 12 de junio de 2026 a las 23:07 UTCmonitoring

   The issue was fixed, and we can confirm that services are working correctly again. Some customers may still notice minor disruptions while systems fully recover. We appreciate your patience and will continue to keep you informed if anything changes.

5. 12 de junio de 2026 a las 23:30 UTCresolved

   The issue has been resolved, and we can confirm that services are operating normally again.

1. 25 de mayo de 2026 a las 5:30 UTCinvestigating

   We are investigating an issue affecting some customers. They are unable to generate reports in the Export raw data section for LiveChat. The scheduled reports may also be not delivered by email.

2. 25 de mayo de 2026 a las 6:08 UTCmonitoring

   We implemented a fix, and we are now monitoring the situation to ensure stability. Some customers may still notice delays with receiving the report while the reporting systems fully recover. We appreciate your patience and will continue to keep you informed if anything changes.

3. 25 de mayo de 2026 a las 6:15 UTCresolved

   The issue has been resolved, and services are operating normally. No further impact is expected. We’re sorry for any disruption this may have caused and thank you for your patience and understanding.

1. 19 de mayo de 2026 a las 2:32 UTCinvestigating

   We are investigating an issue affecting some customers. We are working to confirm the cause and restore normal service as quickly as possible. We will share an update as soon as more information is available.

2. 19 de mayo de 2026 a las 3:45 UTCmonitoring

   We implemented a fix, and we are now monitoring the situation to ensure stability. Some customers may still notice minor disruptions while systems fully recover. We appreciate your patience and will continue to keep you informed if anything changes.

3. 19 de mayo de 2026 a las 4:15 UTCresolved

   The issue has been resolved, and services are operating normally. No further impact is expected. We’re sorry for any disruption this may have caused and thank you for your patience and understanding.

1. 13 de mayo de 2026 a las 11:33 UTCinvestigating

   We are investigating an issue that prevents some customers from adding new Knowledge Sources. Our team is working to identify the root cause and restore normal service as quickly as possible. We will share an update as soon as more information is available.

2. 13 de mayo de 2026 a las 11:40 UTCmonitoring

   A fix has been implemented, and we are monitoring the results. The ability to add new Knowledge Sources has been restored.

3. 13 de mayo de 2026 a las 12:06 UTCresolved

   The issue has been resolved, and services are operating normally. No further impact is expected.

1. 25 de febrero de 2026 a las 4:33 UTCinvestigating

   We are currently investigating an issue affecting some customers' ability to access LiveChat and working to understand the cause. We’ll share another update as soon as we have more information.

2. 25 de febrero de 2026 a las 4:37 UTCinvestigating

   We are currently investigating an issue affecting some customers' ability to access LiveChat and working to understand the cause. We detected an issue with our cloud provider. We’ll share another update as soon as we have more information.

3. 25 de febrero de 2026 a las 4:57 UTCidentified

   We have identified the cause of the issue affecting some customers and are working on a fix. Service may still be degraded while we complete the necessary steps. We are working with our Cloud provider to resolve the issue. We’ll share another update as soon as we have more information.

4. 25 de febrero de 2026 a las 5:22 UTCidentified

   Our team is actively working to resolve the issue. We will share another update as soon as we have more details.

5. 25 de febrero de 2026 a las 5:44 UTCidentified

   We are still actively working to resolve the issue. We will provide further updates as we make progress.

6. 25 de febrero de 2026 a las 6:08 UTCidentified

   We are actively implementing steps to resolve the problem. We will share the next update as soon as possible.

7. 25 de febrero de 2026 a las 6:30 UTCidentified

   Work on resolving the issue is ongoing. We will provide another update as soon as we have more information.

8. 25 de febrero de 2026 a las 6:51 UTCidentified

   Our team continues to investigate the issue and work toward a resolution. We will provide further updates as soon as they are available.

9. 25 de febrero de 2026 a las 7:06 UTCidentified

   We are observing ongoing recovery on the side of Google, and our services are gradually returning to normal availability. We will continue to monitor the situation and provide further updates as needed.

10. 25 de febrero de 2026 a las 7:11 UTCmonitoring

    We are seeing improvements in our service availability and are now moving to closely monitor the situation. We will provide further updates when necessary.

11. 25 de febrero de 2026 a las 7:42 UTCmonitoring

    Services are operational, and we are actively monitoring to maintain stability.

12. 25 de febrero de 2026 a las 8:05 UTCmonitoring

    We continue to monitor the situation to ensure everything remains stable.

13. 25 de febrero de 2026 a las 11:25 UTCmonitoring

    **Brief status update and additional context on the ongoing incident** This incident is related to an issue within our cloud provider’s infrastructure (GCP). We’re actively coordinating with their engineering teams since the beginning of the incident and staying in continuous contact as they work through mitigation and recovery steps. The incident hasn’t been resolved on their end yet. Minor performance issues persist, but these are limited in scale and do not affect overall availability for customers.

14. 25 de febrero de 2026 a las 11:57 UTCidentified

    We have identified the cause of the issue affecting some customers and are working on a fix. Access to Archives and Reports may be degraded while we complete the necessary steps.

15. 25 de febrero de 2026 a las 12:48 UTCmonitoring

    We are monitoring the situation to ensure everything remains stable. Some customers may still notice minor disruptions while systems fully recover.

16. 25 de febrero de 2026 a las 13:36 UTCmonitoring

    We continue to monitor the situation to ensure stability. While systems are recovering, some customers may still experience minor disruptions as we await a permanent fix from our service provider. While the issue has not yet been fully resolved on their end, we have been actively coordinating with their engineering teams since the incident began and remain in close contact as they progress through mitigation and recovery efforts.

17. 25 de febrero de 2026 a las 15:02 UTCmonitoring

    We are continuously monitoring the service to ensure continuity and stability while we are waiting for a fix from our service provider. Some customers may experience minor disruptions during that time. We remain in close contact with the provider’s engineering teams, and the issue has not yet been resolved on their end.

18. 25 de febrero de 2026 a las 16:03 UTCmonitoring

    We are continuously monitoring the service to ensure continuity and stability while we await a fix from our service provider. Some customers may still experience degraded performance during this time.

19. 25 de febrero de 2026 a las 17:00 UTCmonitoring

    We are continuously monitoring the service to ensure continuity and stability while we await a fix from our cloud provider’s infrastructure, **Google Cloud Platform (GCP)**. Some customers may still experience degraded performance during this time. We remain in close contact with GCP’s engineering teams, and the issue has not yet been resolved on their end. During this period, customers may experience delays when starting chats or sending messages.

20. 25 de febrero de 2026 a las 17:49 UTCinvestigating

    Our team is working closely with **Google Cloud Platform (GCP)** to resolve the issue. While chats can be started, customers may experience delays or failures when sending messages.

21. 25 de febrero de 2026 a las 18:13 UTCidentified

    We are implementing additional mitigation measures. Chat sessions may start successfully; however, some messages may be delayed or not delivered. We are actively working on a fix, and the estimated time to resolution is approximately 20 minutes.

22. 25 de febrero de 2026 a las 18:28 UTCidentified

    We are continuing to deploy the fix and will provide an update shortly.

23. 25 de febrero de 2026 a las 18:43 UTCmonitoring

    Deployment of the fix is complete. We are monitoring the service to ensure full stability.

24. 26 de febrero de 2026 a las 5:22 UTCinvestigating

    We are currently investigating an issue affecting some customers and working to understand the cause. We’ll share another update as soon as we have more information.

25. 26 de febrero de 2026 a las 5:31 UTCmonitoring

    A fix has been implemented and we are monitoring the situation to ensure everything remains stable. Some customers may still notice minor disruptions while systems fully recover.

26. 26 de febrero de 2026 a las 10:19 UTCresolved

    A fix has been implemented, and we see that our assets become available and reports a healthy status. We’ve been monitoring the situation, and will continue checks

1. 21 de febrero de 2026 a las 18:26 UTCinvestigating

   Many customers experienced delays of up to 30 seconds when sending messages via the chat widget. We are currently investigating the problem

2. 21 de febrero de 2026 a las 18:52 UTCinvestigating

   We are still investigating the problem. The delay was shortened, but it is still occurring.

3. 21 de febrero de 2026 a las 18:54 UTCmonitoring

   The problem should be resolved now. We are moving to monitoring.

4. 21 de febrero de 2026 a las 18:57 UTCresolved

   The incident has been resolved and services are now operating as expected. We will continue to monitor the situation, but no further impact is anticipated.

1. 10 de febrero de 2026 a las 17:04 UTCinvestigating

   We are currently observing delays when sending messages via the chat widget. Our team is investigating the issue and working on a fix. Updates will be shared as we learn more.

2. 10 de febrero de 2026 a las 17:21 UTCinvestigating

   Our team is continuing to investigate the cause of the message delays in the chat widget. We’re actively working toward a resolution and will share further updates shortly.

3. 10 de febrero de 2026 a las 17:32 UTCidentified

   We have identified the cause of the delays affecting message delivery in the chat widget. Our team is working on implementing a fix and will provide an update once resolved.

4. 10 de febrero de 2026 a las 17:51 UTCidentified

   Engineering is still working on the resolution, and we are closely monitoring progress to restore normal functionality as quickly as possible.

5. 10 de febrero de 2026 a las 18:06 UTCmonitoring

   The fix for the chat widget message delays has been implemented. We are monitoring the system to ensure normal functionality is fully restored.

6. 10 de febrero de 2026 a las 18:10 UTCresolved

   This incident has been resolved and services are operating normally. Thank you for your patience.

1. 20 de enero de 2026 a las 23:28 UTCinvestigating

   We noticed a performance degradation in our services related to issues with our cloud provider. We're currently investigating this issue.

2. 21 de enero de 2026 a las 0:08 UTCinvestigating

   We have received a communication from the cloud provider's engineers stating that they are reviewing our case.

3. 21 de enero de 2026 a las 0:48 UTCinvestigating

   We are still investigating the situation and working with our cloud provider engineers to implement the fix.

4. 21 de enero de 2026 a las 1:28 UTCmonitoring

   After discussing the issue with our admins, the cloud provider engineers are still working on the case and investigating further. Currently, we are not seeing any further issues, but we are still monitoring the situation.

5. 21 de enero de 2026 a las 1:43 UTCresolved

   We see that the issue within our cloud provider’s infrastructure has been mitigated, and we can confirm that the infrastructure is healthy, and we are not seeing further errors. Throughout the degradation, our platform was able to maintain service continuity. We appreciate your patience and understanding while we coordinated our efforts with the cloud provider’s engineers to address the issue.

1. 20 de enero de 2026 a las 16:24 UTCinvestigating

   We noticed a performance degradation in our services related to issues with our cloud provider. We're currently investigating this issue.

2. 20 de enero de 2026 a las 16:43 UTCidentified

   We identified the cause of this issue and are actively working on a fix.

3. 20 de enero de 2026 a las 17:01 UTCidentified

   We’re continuing to work on a fix. More updates will be shared soon.

4. 20 de enero de 2026 a las 17:22 UTCidentified

   We are actively working to fully restore normal service performance. Thank you for your patience.

5. 20 de enero de 2026 a las 17:43 UTCidentified

   We’re still working on the fix and continuing to monitor system stability. The issue is not spreading, but parts of the infrastructure are still experiencing degraded performance. Further updates to follow.

6. 20 de enero de 2026 a las 18:04 UTCidentified

   We’re making progress and are currently rolling out a fix. We’ll continue monitoring closely and share further updates as they become available.

7. 20 de enero de 2026 a las 18:32 UTCidentified

   We’re continuing to roll out a fix and are seeing services recover. Work is still ongoing; we’ll share another update shortly.

8. 20 de enero de 2026 a las 18:52 UTCidentified

   We’re continuing to roll out the fix and closely monitoring service health. We’ll provide another update soon.

9. 20 de enero de 2026 a las 19:22 UTCidentified

   **Brief status update and additional context on the ongoing incident** This incident is related to an issue within our cloud provider’s infrastructure. We’re actively coordinating with their engineering teams since the beginning of the incident and staying in continuous contact as they work through mitigation and recovery steps. Our platform has remained available throughout, thanks to built-in redundancy and failover across multiple locations. While parts of the underlying infrastructure are experiencing problems, we are continuing to serve traffic and deliver the service without a full outage. That said, customers may still experience intermittent degraded performance (for example, increased latency or occasional timeouts) while remediation is in progress. We’re monitoring service health closely and will provide further updates as we have more information from the cloud provider, but no later than one hour from now.

10. 20 de enero de 2026 a las 20:12 UTCmonitoring

    The issue within our cloud provider’s infrastructure has been mitigated, and all affected resources have been fully restored. Our platform continues to operate normally, and we are no longer observing the previously reported degraded performance. We are actively and continuously monitoring our internal services to ensure everything is functioning as expected and to confirm sustained stability. We will provide further updates within an hour

11. 20 de enero de 2026 a las 20:36 UTCresolved

    The issue within our cloud provider’s infrastructure has been mitigated, and we can confirm that all affected resources have been fully restored. Our platform has remained available throughout, thanks to built-in redundancy and failover across multiple locations. While parts of the underlying infrastructure were experiencing problems, we continued to serve traffic and deliver the service without a full outage. Thank you for your patience and understanding while we coordinated our efforts with cloud provider’s engineers to address the issue.

1. 20 de enero de 2026 a las 14:50 UTCinvestigating

   Chat widget on Text websites is not responding. Customer’s licenses are not affected.

2. 20 de enero de 2026 a las 14:56 UTCmonitoring

   Fixes have been applied, we are monitoring the performance

3. 20 de enero de 2026 a las 15:08 UTCresolved

   Communication is fully restored now.

1. 20 de enero de 2026 a las 14:49 UTCinvestigating

   Degradation in performance of sending and receiving messages through the chat widget.

2. 20 de enero de 2026 a las 14:56 UTCmonitoring

   Fixes have been applied, we are monitoring the performance

3. 20 de enero de 2026 a las 15:07 UTCresolved

   Full widget performance was restored.

1. 13 de enero de 2026 a las 7:03 UTCinvestigating

   We are currently investigating this issue. We will post further updates as soon as we know more.

2. 13 de enero de 2026 a las 7:11 UTCresolved

   The fix has been implemented and the issue has been resolved.

1. 22 de diciembre de 2025 a las 11:53 UTCinvestigating

   Some agents are experiencing app login issues. We are investigating the case.

2. 22 de diciembre de 2025 a las 11:53 UTCmonitoring

   Issue seems to be fixed. We are monitoring servers' performance.

3. 22 de diciembre de 2025 a las 11:53 UTCresolved

   This problem has been resolved.

1. 22 de diciembre de 2025 a las 11:53 UTCinvestigating

   Due to our CDN provider issues some visitors might have problems with chat window loading.

2. 22 de diciembre de 2025 a las 11:53 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 22 de diciembre de 2025 a las 11:53 UTCresolved

   Problem with CDN provider issues and chat window loading has been resolved.

1. 22 de diciembre de 2025 a las 11:53 UTCinvestigating

   We are under DDoS attack. Some of customers might have issues with the chat.

2. 22 de diciembre de 2025 a las 11:53 UTCmonitoring

   DDoS is under control, service is fully functional again.

3. 22 de diciembre de 2025 a las 11:53 UTCresolved

   Problem with DDoS attack has been resolved.