Historial de interrupciones de Livechat

1. July 28, 2026 at 11:30 AM 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. July 28, 2026 at 11:54 AM 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. July 28, 2026 at 1:49 PM 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. July 29, 2026 at 1:01 PM 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. July 10, 2026 at 2:24 AM 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. July 10, 2026 at 2:36 AM UTCidentified

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

3. July 10, 2026 at 2:38 AM UTCidentified

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

4. July 10, 2026 at 2:41 AM UTCresolved

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

1. June 12, 2026 at 10:25 PM 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. June 12, 2026 at 10:33 PM UTCidentified

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

3. June 12, 2026 at 10:55 PM UTCidentified

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

4. June 12, 2026 at 11:07 PM 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. June 12, 2026 at 11:30 PM UTCresolved

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

1. May 25, 2026 at 5:30 AM 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. May 25, 2026 at 6:08 AM 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. May 25, 2026 at 6:15 AM 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. May 19, 2026 at 2:32 AM 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. May 19, 2026 at 3:45 AM 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. May 19, 2026 at 4:15 AM 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. May 13, 2026 at 11:33 AM 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. May 13, 2026 at 11:40 AM UTCmonitoring

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

3. May 13, 2026 at 12:06 PM UTCresolved

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

1. February 25, 2026 at 4:33 AM 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. February 25, 2026 at 4:37 AM 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. February 25, 2026 at 4:57 AM 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. February 25, 2026 at 5:22 AM UTCidentified

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

5. February 25, 2026 at 5:44 AM UTCidentified

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

6. February 25, 2026 at 6:08 AM UTCidentified

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

7. February 25, 2026 at 6:30 AM UTCidentified

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

8. February 25, 2026 at 6:51 AM 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. February 25, 2026 at 7:06 AM 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. February 25, 2026 at 7:11 AM 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. February 25, 2026 at 7:42 AM UTCmonitoring

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

12. February 25, 2026 at 8:05 AM UTCmonitoring

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

13. February 25, 2026 at 11:25 AM 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. February 25, 2026 at 11:57 AM 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. February 25, 2026 at 12:48 PM UTCmonitoring

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

16. February 25, 2026 at 1:36 PM 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. February 25, 2026 at 3:02 PM 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. February 25, 2026 at 4:03 PM 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. February 25, 2026 at 5:00 PM 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. February 25, 2026 at 5:49 PM 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. February 25, 2026 at 6:13 PM 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. February 25, 2026 at 6:28 PM UTCidentified

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

23. February 25, 2026 at 6:43 PM UTCmonitoring

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

24. February 26, 2026 at 5:22 AM 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. February 26, 2026 at 5:31 AM 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. February 26, 2026 at 10:19 AM 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. February 21, 2026 at 6:26 PM UTCinvestigating

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

2. February 21, 2026 at 6:52 PM UTCinvestigating

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

3. February 21, 2026 at 6:54 PM UTCmonitoring

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

4. February 21, 2026 at 6:57 PM 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. February 10, 2026 at 5:04 PM 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. February 10, 2026 at 5:21 PM 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. February 10, 2026 at 5:32 PM 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. February 10, 2026 at 5:51 PM UTCidentified

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

5. February 10, 2026 at 6:06 PM 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. February 10, 2026 at 6:10 PM UTCresolved

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

1. January 20, 2026 at 11:28 PM UTCinvestigating

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

2. January 21, 2026 at 12:08 AM UTCinvestigating

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

3. January 21, 2026 at 12:48 AM UTCinvestigating

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

4. January 21, 2026 at 1:28 AM 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. January 21, 2026 at 1:43 AM 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. January 20, 2026 at 4:24 PM UTCinvestigating

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

2. January 20, 2026 at 4:43 PM UTCidentified

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

3. January 20, 2026 at 5:01 PM UTCidentified

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

4. January 20, 2026 at 5:22 PM UTCidentified

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

5. January 20, 2026 at 5:43 PM 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. January 20, 2026 at 6:04 PM 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. January 20, 2026 at 6:32 PM 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. January 20, 2026 at 6:52 PM UTCidentified

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

9. January 20, 2026 at 7:22 PM 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. January 20, 2026 at 8:12 PM 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. January 20, 2026 at 8:36 PM 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. January 20, 2026 at 2:50 PM UTCinvestigating

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

2. January 20, 2026 at 2:56 PM UTCmonitoring

   Fixes have been applied, we are monitoring the performance

3. January 20, 2026 at 3:08 PM UTCresolved

   Communication is fully restored now.

1. January 20, 2026 at 2:49 PM UTCinvestigating

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

2. January 20, 2026 at 2:56 PM UTCmonitoring

   Fixes have been applied, we are monitoring the performance

3. January 20, 2026 at 3:07 PM UTCresolved

   Full widget performance was restored.

1. January 13, 2026 at 7:03 AM UTCinvestigating

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

2. January 13, 2026 at 7:11 AM UTCresolved

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

1. December 22, 2025 at 11:53 AM UTCinvestigating

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

2. December 22, 2025 at 11:53 AM UTCresolved

   This problem has been resolved.

3. December 22, 2025 at 11:53 AM UTCmonitoring

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

1. December 22, 2025 at 11:53 AM UTCinvestigating

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

2. December 22, 2025 at 11:53 AM UTCmonitoring

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

3. December 22, 2025 at 11:53 AM UTCresolved

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

1. December 22, 2025 at 11:53 AM UTCinvestigating

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

2. December 22, 2025 at 11:53 AM UTCmonitoring

   DDoS is under control, service is fully functional again.

3. December 22, 2025 at 11:53 AM UTCresolved

   Problem with DDoS attack has been resolved.

1. December 22, 2025 at 11:53 AM UTCresolved

   Problem with DDoS attack has been resolved.

2. December 22, 2025 at 11:53 AM UTCmonitoring

   DDoS is under control, customers should be able to connect without any problems now.

3. December 22, 2025 at 11:53 AM UTCinvestigating

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

1. December 22, 2025 at 11:53 AM UTCinvestigating

   Some customers are having connection issues. We are checking that with our IT team.

2. December 22, 2025 at 11:53 AM UTCidentified

   Issue has been identified. Working on a fix.

3. December 22, 2025 at 11:53 AM UTCmonitoring

   Fix deployed. Everything should be back to normal, we are monitoring the situation.

4. December 22, 2025 at 11:53 AM UTCresolved

   The issue has been resolved.

1. December 22, 2025 at 11:53 AM UTCidentified

   Chat window is struggling with DNS issues. Our network team is working on a fix.

2. December 22, 2025 at 11:53 AM UTCmonitoring

   We changed our DNS settings and the widget is back on. If you still see the issue please reach us through [email protected]

3. December 22, 2025 at 11:53 AM UTCresolved

   The DNS issue has been resolved.