Livechat 장애 기록

1. 2026년 7월 28일 AM 11:30 UTCidentified

   우리는 문제가 외부 공급자와 관련되었는지 확인했습니다. 우리는 그들을 조사하고 문제를 해결하기 위해 노력하고 있습니다. 서비스는 문제가 해결되는 동안 degraded 남아있을 수 있습니다. 우리는 우리가 더 세부사항 또는 해결책에 예상한 시간을 가지고 있기 때문에 갱신을 제공할 것입니다.

2. 2026년 7월 28일 AM 11:54 UTCinvestigating

   우리는 몇몇 고객에 영향을 미치는 문제점을 조사하고 있습니다. 문제는 외부 공급자와 관련이있을 수 있고, 우리는 원인을 확인하고 가능한 한 빨리 정상적인 서비스를 복원하기 위해 노력하고 있습니다. 우리는 더 많은 정보를 사용할 수 있기 때문에 업데이트를 공유합니다.

3. 2026년 7월 28일 PM 1:49 UTCinvestigating

   우리는 문제를 해결하기 위해 제 3 자 제공 업체와 함께 일하고 있습니다. 이 단계에서 우리는 검토 과정의 일부로 그들로부터 더 많은 정보를 기다리고 있습니다. 우리는 우리가 공유하거나 상황에 중요한 변화가 있는 추가 정보가 있기 때문에 우리의 다음 갱신을 제공할 것입니다. 감사합니다.

4. 2026년 7월 29일 PM 1:01 UTCresolved

   파일 열기를 가진 문제는 해결되고, 서비스는 일반적으로 운영됩니다. 우리는이 발생하고 당신의 인내와 이해에 감사드립니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 10일 AM 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. 2026년 7월 10일 AM 2:36 UTCidentified

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

3. 2026년 7월 10일 AM 2:38 UTCidentified

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

4. 2026년 7월 10일 AM 2:41 UTCresolved

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

1. 2026년 6월 12일 PM 10: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. 2026년 6월 12일 PM 10:33 UTCidentified

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

3. 2026년 6월 12일 PM 10:55 UTCidentified

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

4. 2026년 6월 12일 PM 11: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. 2026년 6월 12일 PM 11:30 UTCresolved

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

1. 2026년 5월 25일 AM 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. 2026년 5월 25일 AM 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. 2026년 5월 25일 AM 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. 2026년 5월 19일 AM 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. 2026년 5월 19일 AM 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. 2026년 5월 19일 AM 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. 2026년 5월 13일 AM 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. 2026년 5월 13일 AM 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. 2026년 5월 13일 PM 12:06 UTCresolved

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

1. 2026년 2월 25일 AM 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. 2026년 2월 25일 AM 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. 2026년 2월 25일 AM 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. 2026년 2월 25일 AM 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. 2026년 2월 25일 AM 5:44 UTCidentified

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

6. 2026년 2월 25일 AM 6:08 UTCidentified

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

7. 2026년 2월 25일 AM 6:30 UTCidentified

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

8. 2026년 2월 25일 AM 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. 2026년 2월 25일 AM 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. 2026년 2월 25일 AM 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. 2026년 2월 25일 AM 7:42 UTCmonitoring

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

12. 2026년 2월 25일 AM 8:05 UTCmonitoring

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

13. 2026년 2월 25일 AM 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. 2026년 2월 25일 AM 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. 2026년 2월 25일 PM 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. 2026년 2월 25일 PM 1: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. 2026년 2월 25일 PM 3: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. 2026년 2월 25일 PM 4: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. 2026년 2월 25일 PM 5: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. 2026년 2월 25일 PM 5: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. 2026년 2월 25일 PM 6: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. 2026년 2월 25일 PM 6:28 UTCidentified

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

23. 2026년 2월 25일 PM 6:43 UTCmonitoring

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

24. 2026년 2월 26일 AM 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. 2026년 2월 26일 AM 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. 2026년 2월 26일 AM 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. 2026년 2월 21일 PM 6: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. 2026년 2월 21일 PM 6:52 UTCinvestigating

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

3. 2026년 2월 21일 PM 6:54 UTCmonitoring

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

4. 2026년 2월 21일 PM 6: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. 2026년 2월 10일 PM 5: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. 2026년 2월 10일 PM 5: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. 2026년 2월 10일 PM 5: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. 2026년 2월 10일 PM 5:51 UTCidentified

   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일 PM 6: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. 2026년 2월 10일 PM 6:10 UTCresolved

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

1. 2026년 1월 20일 PM 11:28 UTCinvestigating

   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일 AM 12:08 UTCinvestigating

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

3. 2026년 1월 21일 AM 12:48 UTCinvestigating

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

4. 2026년 1월 21일 AM 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. 2026년 1월 21일 AM 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. 2026년 1월 20일 PM 4:24 UTCinvestigating

   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일 PM 4:43 UTCidentified

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

3. 2026년 1월 20일 PM 5:01 UTCidentified

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

4. 2026년 1월 20일 PM 5:22 UTCidentified

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

5. 2026년 1월 20일 PM 5: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. 2026년 1월 20일 PM 6: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. 2026년 1월 20일 PM 6: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. 2026년 1월 20일 PM 6:52 UTCidentified

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

9. 2026년 1월 20일 PM 7: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. 2026년 1월 20일 PM 8: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. 2026년 1월 20일 PM 8: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. 2026년 1월 20일 PM 2:50 UTCinvestigating

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

2. 2026년 1월 20일 PM 2:56 UTCmonitoring

   Fixes have been applied, we are monitoring the performance

3. 2026년 1월 20일 PM 3:08 UTCresolved

   Communication is fully restored now.

1. 2026년 1월 20일 PM 2:49 UTCinvestigating

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

2. 2026년 1월 20일 PM 2:56 UTCmonitoring

   Fixes have been applied, we are monitoring the performance

3. 2026년 1월 20일 PM 3:07 UTCresolved

   Full widget performance was restored.

1. 2026년 1월 13일 AM 7:03 UTCinvestigating

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

2. 2026년 1월 13일 AM 7:11 UTCresolved

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

1. 2025년 12월 22일 AM 11:53 UTCinvestigating

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

2. 2025년 12월 22일 AM 11:53 UTCresolved

   This problem has been resolved.

3. 2025년 12월 22일 AM 11:53 UTCmonitoring

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

1. 2025년 12월 22일 AM 11:53 UTCinvestigating

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

2. 2025년 12월 22일 AM 11:53 UTCmonitoring

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

3. 2025년 12월 22일 AM 11:53 UTCresolved

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

1. 2025년 12월 22일 AM 11:53 UTCinvestigating

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

2. 2025년 12월 22일 AM 11:53 UTCmonitoring

   DDoS is under control, service is fully functional again.

3. 2025년 12월 22일 AM 11:53 UTCresolved

   Problem with DDoS attack has been resolved.

1. 2025년 12월 22일 AM 11:53 UTCresolved

   Problem with DDoS attack has been resolved.

2. 2025년 12월 22일 AM 11:53 UTCmonitoring

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

3. 2025년 12월 22일 AM 11:53 UTCinvestigating

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

1. 2025년 12월 22일 AM 11:53 UTCinvestigating

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

2. 2025년 12월 22일 AM 11:53 UTCidentified

   Issue has been identified. Working on a fix.

3. 2025년 12월 22일 AM 11:53 UTCmonitoring

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

4. 2025년 12월 22일 AM 11:53 UTCresolved

   The issue has been resolved.

1. 2025년 12월 22일 AM 11:53 UTCidentified

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

2. 2025년 12월 22일 AM 11:53 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. 2025년 12월 22일 AM 11:53 UTCresolved

   The DNS issue has been resolved.