Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Livechat 中断历史

    30 Livechat incidents · 2015年3月 — official updates, affected components, duration and resolution details.

    返回当前状态

    工作流程出故障

    开始时间 2026年10月14日 UTC 02:08 · 1h 51m

    Issues轻微事件
    1. 2026年10月14日 UTC 02:08identified

      我们目前正在与 " 工作流 " 调查这一问题。 我们对此可能造成的任何不便表示歉意,我们的团队正努力尽快解决这一问题.

    2. 2026年10月14日 UTC 03:07identified

      我们查明了问题的根源,并正在设法解决问题。 在我们实施解决方案时,服务可能会继续退化。 一旦掌握更多细节或估计解决时间,我们将提供最新情况.

    3. 2026年10月14日 UTC 03:36monitoring

      必要的纠正措施已成功地应用于该系统。 目前,我们正在积极监测结果,以评估这些变化的有效性,并确保一切如所愿.

    4. 2026年10月14日 UTC 03:59resolved

      与工作流量有关的问题已经解决,服务现已正常运行。 我们为这可能造成的任何干扰道歉,并赞赏你的耐心和理解.

    自动翻译自官方事件更新。

    工作流程出故障

    开始时间 2026年10月12日 UTC 17:21 · 7h 39m

    Outage重大事件
    1. 2026年10月12日 UTC 17:21identified

      我们查明了问题的根源,并正在设法解决问题。 在我们实施解决方案时,服务可能会继续退化。 一旦掌握更多细节或估计解决时间,我们将提供最新情况.

    2. 2026年10月12日 UTC 17:45identified

      我们的团队仍在积极进行修复工作。 与此同时,工作流量可能继续退化。 我们赞赏你的耐心,一旦我们掌握更多细节或估计解决时间,我们将再次介绍最新情况.

    3. 2026年10月12日 UTC 18:12identified

      我们的团队正在继续努力解决问题。 劳动力流动仍然退化。 接下来的更新.

    4. 2026年10月12日 UTC 18:40identified

      我们仍在努力解决这个问题, 我们的工程师仍然专注于执行固定方案,我们正在密切监测情况。 我们一旦获得更多信息.

    5. 2026年10月12日 UTC 19:01identified

      我们仍在积极进行修复工作。 服务仍然受到影响,我们的工程师专注于使事情恢复正常。 谢谢你的耐心 我们一旦获得更多信息.

    6. 2026年10月12日 UTC 19:25identified

      这个问题尚未解决,我们的团队仍在努力解决问题。 我们一旦得到更多信息.

    7. 2026年10月12日 UTC 19:55identified

      我们仍在努力恢复服务, 我们的工程师已经全力投入, 我们一旦有进展可汇报.

    8. 2026年10月12日 UTC 20:26identified

      我们仍在努力恢复服务。 我们为持续中断感到抱歉, 一旦有更多消息要报告.

    9. 2026年10月12日 UTC 21:04identified

      我们仍在努力恢复服务。 我们正取得进展, 谢谢你的耐心.

    10. 2026年10月12日 UTC 22:02identified

      服务仍然退化,我们知道这已经持续了几个小时。 我们的团队仍在努力恢复它。 我们为长时间的中断感到遗憾.

    11. 2026年10月12日 UTC 23:12identified

      工作流程的使用继续被削弱。 我们的团队正在积极努力恢复全部功能。 我们为长期干扰和可能造成的任何不便而道歉.

    12. 2026年10月13日 UTC 00:14identified

      工作流程的功能仍在退化。 我们的团队正努力恢复其全部能力。 我们对长时间的干扰和由此造成的任何不便表示歉意.

    13. 2026年10月13日 UTC 00:23monitoring

      必要的纠正措施已成功地应用于该系统。 目前,我们正在积极监测结果,以评估这些变化的有效性,并确保一切如所愿.

    14. 2026年10月13日 UTC 01:00resolved

      与工作流量有关的问题已经解决,服务现已正常运行。 我们为这可能造成的任何干扰道歉,并赞赏你的耐心和理解.

    自动翻译自官方事件更新。

    登录问题

    开始时间 2026年9月26日 UTC 13:00 · 58m

    Issues轻微事件
    1. 2026年9月26日 UTC 13:00investigating

      目前我们正面临进入LiveChat的问题。 我们的团队意识到了这个问题,并正在努力尽快解决这个问题

    2. 2026年9月26日 UTC 13:18investigating

      我们正在调查一个影响一些客户的问题。 我们的团队正在努力查明根源,并尽快恢复正常服务。 一旦获得更多信息,我们将分享最新情况.

    3. 2026年9月26日 UTC 13:52monitoring

      一项固定措施已经执行,我们正在监测结果。 一些客户在系统恢复的同时可能仍然会遇到轻微的中断. 如果局势发生变化,我们将分享最新情况.

    4. 2026年9月26日 UTC 13:58resolved

      这个问题已经解决,服务正常运行。 预计不会有进一步的影响.

    自动翻译自官方事件更新。

    打开文件的问题

    开始时间 2026年7月28日 UTC 11:27 · 1d 1h

    Issues轻微事件
    1. 2026年7月28日 UTC 11:30identified

      我们确认,这个问题与外部供应商有关。 我们正在同他们一道调查和解决这一问题。 在处理这一问题期间,服务可能继续退化。 一旦掌握更多细节或估计解决时间,我们将提供最新情况.

    2. 2026年7月28日 UTC 11:54investigating

      我们正在调查一个影响一些客户的问题。 这个问题可能与外部供应商有关,我们正在努力确认原因并尽快恢复正常服务。 一旦获得更多信息,我们将分享最新情况.

    3. 2026年7月28日 UTC 13:49investigating

      我们正在继续与第三方提供者合作以解决这一问题。 在现阶段,我们正在等待它们提供更多资料,作为其审查进程的一部分。 一旦我们收到需要分享的更多信息或局势有重大变化,我们将提供下一次最新情况。 谢谢你的耐心.

    4. 2026年7月29日 UTC 13:01resolved

      打开文件的问题已经解决,服务正常运行. 感谢您的耐心和理解.

    自动翻译自官方事件更新。

    Workflow degraded performance

    开始时间 2026年7月10日 UTC 02:24 · 17m

    Issues轻微事件
    1. 2026年7月10日 UTC 02:24investigating

      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. 2026年7月10日 UTC 02:36identified

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

    3. 2026年7月10日 UTC 02:38identified

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

    4. 2026年7月10日 UTC 02:41resolved

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

    Workflow degraded performance

    开始时间 2026年6月12日 UTC 22:25 · 1h 6m

    Issues轻微事件
    1. 2026年6月12日 UTC 22:25investigating

      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. 2026年6月12日 UTC 22:33identified

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

    3. 2026年6月12日 UTC 22:55identified

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

    4. 2026年6月12日 UTC 23:07monitoring

      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. 2026年6月12日 UTC 23:30resolved

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

    LiveChat - Issues with reports from Export Raw Data

    开始时间 2026年5月25日 UTC 05:30 · 44m

    Outage重大事件
    1. 2026年5月25日 UTC 05:30investigating

      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. 2026年5月25日 UTC 06:08monitoring

      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. 2026年5月25日 UTC 06:15resolved

      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.

    Workflows delay

    开始时间 2026年5月19日 UTC 02:11 · 2h 4m

    Pending
    1. 2026年5月19日 UTC 02:32investigating

      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. 2026年5月19日 UTC 03:45monitoring

      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. 2026年5月19日 UTC 04:15resolved

      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.

    Issues with adding new Knowledge Sources

    开始时间 2026年5月13日 UTC 11:33 · 33m

    Issues轻微事件
    1. 2026年5月13日 UTC 11:33investigating

      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. 2026年5月13日 UTC 11:40monitoring

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

    3. 2026年5月13日 UTC 12:06resolved

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

    LiveChat - outage

    开始时间 2026年2月25日 UTC 04:33 · 1d 5h

    Outage严重事件
    1. 2026年2月25日 UTC 04:33investigating

      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. 2026年2月25日 UTC 04:37investigating

      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. 2026年2月25日 UTC 04:57identified

      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. 2026年2月25日 UTC 05:22identified

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

    5. 2026年2月25日 UTC 05:44identified

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

    6. 2026年2月25日 UTC 06:08identified

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

    7. 2026年2月25日 UTC 06:30identified

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

    8. 2026年2月25日 UTC 06:51identified

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

    9. 2026年2月25日 UTC 07:06identified

      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. 2026年2月25日 UTC 07:11monitoring

      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. 2026年2月25日 UTC 07:42monitoring

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

    12. 2026年2月25日 UTC 08:05monitoring

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

    13. 2026年2月25日 UTC 11:25monitoring

      **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. 2026年2月25日 UTC 11:57identified

      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. 2026年2月25日 UTC 12:48monitoring

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

    16. 2026年2月25日 UTC 13:36monitoring

      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. 2026年2月25日 UTC 15:02monitoring

      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. 2026年2月25日 UTC 16:03monitoring

      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. 2026年2月25日 UTC 17:00monitoring

      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. 2026年2月25日 UTC 17:49investigating

      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. 2026年2月25日 UTC 18:13identified

      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. 2026年2月25日 UTC 18:28identified

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

    23. 2026年2月25日 UTC 18:43monitoring

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

    24. 2026年2月26日 UTC 05:22investigating

      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. 2026年2月26日 UTC 05:31monitoring

      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. 2026年2月26日 UTC 10:19resolved

      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

    Messages sent via the chat widget are delayed

    开始时间 2026年2月21日 UTC 18:26 · 32m

    Issues轻微事件
    1. 2026年2月21日 UTC 18:26investigating

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

    2. 2026年2月21日 UTC 18:52investigating

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

    3. 2026年2月21日 UTC 18:54monitoring

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

    4. 2026年2月21日 UTC 18:57resolved

      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.

    Messages sent in the chat widget may be delayed

    开始时间 2026年2月10日 UTC 17:04 · 1h 6m

    Issues轻微事件
    1. 2026年2月10日 UTC 17:04investigating

      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. 2026年2月10日 UTC 17:21investigating

      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. 2026年2月10日 UTC 17:32identified

      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. 2026年2月10日 UTC 17:51identified

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

    5. 2026年2月10日 UTC 18:06monitoring

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

    6. 2026年2月10日 UTC 18:10resolved

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

    Performance degradation of our services

    开始时间 2026年1月20日 UTC 23:28 · 2h 14m

    Issues轻微事件
    1. 2026年1月20日 UTC 23:28investigating

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

    2. 2026年1月21日 UTC 00:08investigating

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

    3. 2026年1月21日 UTC 00:48investigating

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

    4. 2026年1月21日 UTC 01:28monitoring

      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. 2026年1月21日 UTC 01:43resolved

      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.

    Performance degradation of our services

    开始时间 2026年1月20日 UTC 16:24 · 4h 12m

    Issues轻微事件
    1. 2026年1月20日 UTC 16:24investigating

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

    2. 2026年1月20日 UTC 16:43identified

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

    3. 2026年1月20日 UTC 17:01identified

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

    4. 2026年1月20日 UTC 17:22identified

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

    5. 2026年1月20日 UTC 17:43identified

      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. 2026年1月20日 UTC 18:04identified

      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. 2026年1月20日 UTC 18:32identified

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

    8. 2026年1月20日 UTC 18:52identified

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

    9. 2026年1月20日 UTC 19:22identified

      **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. 2026年1月20日 UTC 20:12monitoring

      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. 2026年1月20日 UTC 20:36resolved

      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.

    Chat widget not working on Text websites

    开始时间 2026年1月20日 UTC 14:50 · 18m

    Issues轻微事件
    1. 2026年1月20日 UTC 14:50investigating

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

    2. 2026年1月20日 UTC 14:56monitoring

      Fixes have been applied, we are monitoring the performance

    3. 2026年1月20日 UTC 15:08resolved

      Communication is fully restored now.

    Chat widget performance degradation

    开始时间 2026年1月20日 UTC 14:49 · 18m

    Issues轻微事件
    1. 2026年1月20日 UTC 14:49investigating

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

    2. 2026年1月20日 UTC 14:56monitoring

      Fixes have been applied, we are monitoring the performance

    3. 2026年1月20日 UTC 15:07resolved

      Full widget performance was restored.

    Some users might not be able to access the LiveChat app

    开始时间 2026年1月13日 UTC 07:03 · 9m

    Issues轻微事件
    1. 2026年1月13日 UTC 07:03investigating

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

    2. 2026年1月13日 UTC 07:11resolved

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

    App login issue

    开始时间 2015年12月9日 UTC 19:07 · 0m

    Pending
    1. 2025年12月22日 UTC 11:53investigating

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

    2. 2025年12月22日 UTC 11:53monitoring

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

    3. 2025年12月22日 UTC 11:53resolved

      This problem has been resolved.

    CDN provider issue

    开始时间 2015年12月8日 UTC 20:29 · 0m

    Pending
    1. 2025年12月22日 UTC 11:53investigating

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

    2. 2025年12月22日 UTC 11:53monitoring

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

    3. 2025年12月22日 UTC 11:53resolved

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

    DDoS attack

    开始时间 2015年12月4日 UTC 14:21 · 0m

    Pending
    1. 2025年12月22日 UTC 11:53investigating

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

    2. 2025年12月22日 UTC 11:53monitoring

      DDoS is under control, service is fully functional again.

    3. 2025年12月22日 UTC 11:53resolved

      Problem with DDoS attack has been resolved.