LiveChat Outage History

Started Oct 14, 2026, 02:08 AM UTC· resolved Oct 14, 2026, 03:59 AM UTC

1. identified Oct 14, 2026, 02:08 AM UTC

   We are currently investigating the issue with the Workflows. We apologize for any inconvenience this may cause, and our team is working diligently to resolve the issue as quickly as possible.

2. identified Oct 14, 2026, 03:07 AM UTC

   We have identified the root cause of the issue and are working on a fix. Service may remain degraded while we implement the solution. We will provide an update as soon as we have more details or an estimated time to resolution.

3. monitoring Oct 14, 2026, 03:36 AM UTC

   The necessary fixes have been successfully applied to the system. At this moment, we are actively monitoring the results to assess the effectiveness of these changes and ensure everything is functioning as intended.

4. resolved Oct 14, 2026, 03:59 AM UTC

   The issue with Workflows has been resolved, and services are now operating normally. We apologize for any disruption this may have caused and appreciate your patience and understanding.

Read the full incident report →

Started Oct 12, 2026, 05:21 PM UTC· resolved Oct 13, 2026, 12:23 AM UTC

1. identified Oct 12, 2026, 05:21 PM UTC

   We have identified the root cause of the issue and are working on a fix. Service may remain degraded while we implement the solution. We will provide an update as soon as we have more details or an estimated time to resolution.

2. identified Oct 12, 2026, 05:45 PM UTC

   Our team is still actively working on the fix. Workflows may remain degraded in the meantime. We appreciate your patience and will share another update as soon as we have more details or an estimated time to resolution.

3. identified Oct 12, 2026, 06:12 PM UTC

   Our team is continuing to work on the fix. Workflows remain degraded. Next update to follow.

4. identified Oct 12, 2026, 06:40 PM UTC

   We’re still working to resolve this issue, and Workflows continue to be degraded. Our engineers remain focused on implementing the fix, and we’re monitoring the situation closely. We’ll share more information as soon as it becomes available.

5. identified Oct 12, 2026, 07:01 PM UTC

   We’re still actively working on the fix. Service remains impacted, and our engineers are focused on getting things back to normal. Thank you for your patience. We’ll share further information as soon as it’s available.

6. identified Oct 12, 2026, 07:25 PM UTC

   The issue is not yet resolved, and our team is still working on the fix. We’ll update you again as soon as we have more information.

7. identified Oct 12, 2026, 07:55 PM UTC

   We’re still working to restore service, which remains degraded. Our engineers are fully engaged, and we’re sorry for the continued disruption. We’ll share another update as soon as we have progress to report.

8. identified Oct 12, 2026, 08:26 PM UTC

   We’re still working to restore service. We’re sorry for the continued disruption and appreciate your patience. We’ll share another update as soon as we have more to report.

9. identified Oct 12, 2026, 09:04 PM UTC

   We’re still working to restore service. We’re making progress and getting closer to resolving the issue. Thank you for your patience.

10. identified Oct 12, 2026, 10:02 PM UTC

    Service remains degraded, and we know this has been ongoing for several hours. Our team is still working on restoring it. We’re sorry for the extended disruption.

11. identified Oct 12, 2026, 11:12 PM UTC

    The usage of workflows continues to be degraded. Our team is actively working to restore full functionality. We apologize for the prolonged disruption and any inconvenience this may cause.

12. identified Oct 13, 2026, 12:14 AM UTC

    The functionality of workflows is still experiencing degradation. Our team is diligently working to restore it to full capacity. We apologize for the extended disruption and any inconvenience this may create.

13. monitoring Oct 13, 2026, 12:23 AM UTC

    The necessary fixes have been successfully applied to the system. At this moment, we are actively monitoring the results to assess the effectiveness of these changes and ensure everything is functioning as intended.

14. resolved Oct 13, 2026, 01:00 AM UTC

    The issue with Workflows has been resolved, and services are now operating normally. We apologize for any disruption this may have caused and appreciate your patience and understanding.

Read the full incident report →

Started Sep 26, 2026, 01:00 PM UTC· resolved Sep 26, 2026, 01:58 PM UTC

1. investigating Sep 26, 2026, 01:00 PM UTC

   We’re currently experiencing issues with logging in to LiveChat. Our team is aware of the problem and is working on resolving it as soon as possible

2. investigating Sep 26, 2026, 01:18 PM UTC

   We are investigating an issue affecting some customers. 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.

3. monitoring Sep 26, 2026, 01:52 PM UTC

   A fix has been implemented, and we are monitoring the results. Some customers may still experience minor disruptions while systems recover. We will share updates if the situation changes.

4. resolved Sep 26, 2026, 01:58 PM UTC

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

Read the full incident report →

Started Jul 28, 2026, 11:27 AM UTC· resolved Jul 28, 2026, 11:30 AM UTC

1. identified Jul 28, 2026, 11:27 AM UTC

   We have identified that the issue is related to an external provider. We are working with them to investigate and resolve the problem. Service may remain degraded while the issue is being addressed. We will provide an update as soon as we have more details or an estimated time to resolution.

2. identified Jul 28, 2026, 11:30 AM UTC

   We have identified that the issue is related to an external provider. We are working with them to investigate and resolve the problem. Service may remain degraded while the issue is being addressed. We will provide an update as soon as we have more details or an estimated time to resolution.

3. investigating Jul 28, 2026, 11:54 AM UTC

   We are investigating an issue affecting some customers. The problem may be related to an external provider, and 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.

4. investigating Jul 28, 2026, 01:49 PM UTC

   We are continuing to work with the third-party provider to resolve the issue. At this stage, we are awaiting further information from them as part of their review process. We will provide our next update as soon as we have additional information to share or there is a significant change to the situation. Thank you for your patience.

5. resolved Jul 29, 2026, 01:01 PM UTC

   The issue with opening files has been resolved, and services are operating normally. We’re sorry for any disruption this may have caused and thank you for your patience and understanding.

Read the full incident report →

Started Jul 10, 2026, 02:24 AM UTC· resolved Jul 10, 2026, 02:41 AM UTC

1. investigating Jul 10, 2026, 02:24 AM UTC

   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. identified Jul 10, 2026, 02:36 AM UTC

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

3. identified Jul 10, 2026, 02:38 AM UTC

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

4. resolved Jul 10, 2026, 02:41 AM UTC

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

Read the full incident report →

Started Jun 12, 2026, 10:25 PM UTC· resolved Jun 12, 2026, 11:07 PM UTC

1. investigating Jun 12, 2026, 10:25 PM UTC

   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. identified Jun 12, 2026, 10:33 PM UTC

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

3. identified Jun 12, 2026, 10:55 PM UTC

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

4. monitoring Jun 12, 2026, 11:07 PM UTC

   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. resolved Jun 12, 2026, 11:30 PM UTC

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

Read the full incident report →

Started May 25, 2026, 05:30 AM UTC· resolved May 25, 2026, 06:15 AM UTC

1. investigating May 25, 2026, 05:30 AM UTC

   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. monitoring May 25, 2026, 05:46 AM UTC

   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. monitoring May 25, 2026, 06:08 AM UTC

   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.

4. resolved May 25, 2026, 06:15 AM UTC

   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.

Read the full incident report →

Started May 19, 2026, 02:11 AM UTC· resolved May 19, 2026, 04:15 AM UTC

1. investigating May 19, 2026, 02:11 AM UTC

   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. investigating May 19, 2026, 02:32 AM UTC

   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.

3. monitoring May 19, 2026, 02:56 AM UTC

   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.

4. monitoring May 19, 2026, 03:45 AM UTC

   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.

5. resolved May 19, 2026, 04:15 AM UTC

   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.

Read the full incident report →

Started May 13, 2026, 11:33 AM UTC· resolved May 13, 2026, 11:40 AM UTC

1. investigating May 13, 2026, 11:33 AM UTC

   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. monitoring May 13, 2026, 11:40 AM UTC

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

3. resolved May 13, 2026, 12:06 PM UTC

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

Read the full incident report →

Started Feb 25, 2026, 04:33 AM UTC· resolved Feb 26, 2026, 05:31 AM UTC

1. investigating Feb 25, 2026, 04:33 AM UTC

   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. investigating Feb 25, 2026, 04:37 AM UTC

   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. identified Feb 25, 2026, 04:57 AM UTC

   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. identified Feb 25, 2026, 05:22 AM UTC

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

5. identified Feb 25, 2026, 05:44 AM UTC

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

6. identified Feb 25, 2026, 06:08 AM UTC

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

7. identified Feb 25, 2026, 06:30 AM UTC

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

8. identified Feb 25, 2026, 06:51 AM UTC

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

9. identified Feb 25, 2026, 07:06 AM UTC

   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. monitoring Feb 25, 2026, 07:11 AM UTC

    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. monitoring Feb 25, 2026, 07:42 AM UTC

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

12. monitoring Feb 25, 2026, 08:05 AM UTC

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

13. monitoring Feb 25, 2026, 11:25 AM UTC

    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. identified Feb 25, 2026, 11:57 AM UTC

    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. monitoring Feb 25, 2026, 12:02 PM UTC

    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.

16. monitoring Feb 25, 2026, 12:48 PM UTC

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

17. monitoring Feb 25, 2026, 01:36 PM UTC

    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.

18. monitoring Feb 25, 2026, 03:02 PM UTC

    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.

19. monitoring Feb 25, 2026, 04:03 PM UTC

    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.

20. monitoring Feb 25, 2026, 05:00 PM UTC

    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.

21. investigating Feb 25, 2026, 05:49 PM UTC

    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.

22. identified Feb 25, 2026, 06:13 PM UTC

    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.

23. identified Feb 25, 2026, 06:28 PM UTC

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

24. monitoring Feb 25, 2026, 06:43 PM UTC

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

25. investigating Feb 26, 2026, 05:03 AM UTC

    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.

26. investigating Feb 26, 2026, 05:22 AM UTC

    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.

27. monitoring Feb 26, 2026, 05:31 AM UTC

    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.

28. resolved Feb 26, 2026, 10:19 AM UTC

    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

Read the full incident report →

Started Feb 21, 2026, 06:26 PM UTC· resolved Feb 21, 2026, 06:54 PM UTC

1. investigating Feb 21, 2026, 06:26 PM UTC

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

2. investigating Feb 21, 2026, 06:52 PM UTC

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

3. monitoring Feb 21, 2026, 06:54 PM UTC

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

4. resolved Feb 21, 2026, 06:57 PM UTC

   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.

Read the full incident report →

Started Feb 10, 2026, 05:04 PM UTC· resolved Feb 10, 2026, 06:10 PM UTC

1. investigating Feb 10, 2026, 05:04 PM UTC

   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. investigating Feb 10, 2026, 05:21 PM UTC

   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. identified Feb 10, 2026, 05:32 PM UTC

   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. identified Feb 10, 2026, 05:51 PM UTC

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

5. monitoring Feb 10, 2026, 06:06 PM UTC

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

6. resolved Feb 10, 2026, 06:10 PM UTC

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

Read the full incident report →

Started Jan 20, 2026, 11:28 PM UTC· resolved Jan 21, 2026, 01:43 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Jan 20, 2026, 04:24 PM UTC· resolved Jan 20, 2026, 08:36 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Jan 20, 2026, 02:50 PM UTC· resolved Jan 20, 2026, 03:08 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Jan 20, 2026, 02:49 PM UTC· resolved Jan 20, 2026, 03:07 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Jan 13, 2026, 07:03 AM UTC· resolved Jan 13, 2026, 07:11 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →