Störungsverlauf von Livechat

1. 14. Oktober 2026 um 02:08 UTCidentified

   Wir untersuchen derzeit das Problem mit den Workflows. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursachen kann, und unser Team arbeitet fleißig daran, das Problem so schnell wie möglich zu lösen.

2. 14. Oktober 2026 um 03:07 UTCidentified

   Wir haben die Ursache des Problems identifiziert und arbeiten an einem Fix. Der Service kann beeinträchtigt bleiben, während wir die Lösung implementieren. Wir werden ein Update bereitstellen, sobald wir mehr Details oder eine geschätzte Zeit bis zur Lösung haben.

3. 14. Oktober 2026 um 03:36 UTCmonitoring

   Die notwendigen Fixes wurden erfolgreich auf das System angewendet. In diesem Moment überwachen wir aktiv die Ergebnisse, um die Wirksamkeit dieser Änderungen zu bewerten und sicherzustellen, dass alles wie beabsichtigt funktioniert.

4. 14. Oktober 2026 um 03:59 UTCresolved

   Das Problem mit Workflows wurde behoben und die Dienste funktionieren jetzt normal. Wir entschuldigen uns für jede Störung, die dies verursacht haben könnte und schätzen Ihre Geduld und Ihr Verständnis.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 12. Oktober 2026 um 17:21 UTCidentified

   Wir haben die Ursache des Problems identifiziert und arbeiten an einem Fix. Der Service kann beeinträchtigt bleiben, während wir die Lösung implementieren. Wir werden ein Update bereitstellen, sobald wir mehr Details oder eine geschätzte Zeit bis zur Lösung haben.

2. 12. Oktober 2026 um 17:45 UTCidentified

   Unser Team arbeitet noch immer aktiv an dem Fix. Workflows können in der Zwischenzeit abgebaut werden. Wir schätzen Ihre Geduld und werden ein weiteres Update teilen, sobald wir mehr Details oder eine geschätzte Zeit bis zur Lösung haben.

3. 12. Oktober 2026 um 18:12 UTCidentified

   Unser Team arbeitet weiter an dem Fix. Workflows bleiben degradiert. Nächstes Update folgt.

4. 12. Oktober 2026 um 18:40 UTCidentified

   Wir arbeiten immer noch daran, dieses Problem zu lösen, und die Workflows werden weiterhin abgebaut. Unsere Ingenieure konzentrieren sich weiterhin auf die Implementierung des Fixes und wir beobachten die Situation genau. Wir werden weitere Informationen teilen, sobald sie verfügbar sind.

5. 12. Oktober 2026 um 19:01 UTCidentified

   Wir arbeiten noch aktiv am Fix. Der Service bleibt betroffen und unsere Ingenieure konzentrieren sich darauf, die Dinge wieder normal zu machen. Vielen Dank für Ihre Geduld. Wir werden weitere Informationen teilen, sobald sie verfügbar sind.

6. 12. Oktober 2026 um 19:25 UTCidentified

   Das Problem ist noch nicht gelöst und unser Team arbeitet noch an der Lösung. Wir werden Sie erneut aktualisieren, sobald wir weitere Informationen haben.

7. 12. Oktober 2026 um 19:55 UTCidentified

   Wir arbeiten immer noch daran, den Service wiederherzustellen, der degradiert bleibt. Unsere Ingenieure sind voll engagiert und es tut uns leid für die anhaltende Störung. Wir werden ein weiteres Update teilen, sobald wir Fortschritte zu berichten haben.

8. 12. Oktober 2026 um 20:26 UTCidentified

   Wir arbeiten immer noch daran, den Service wiederherzustellen. Es tut uns leid für die anhaltende Störung und schätzen Ihre Geduld. Wir werden ein weiteres Update teilen, sobald wir mehr zu berichten haben.

9. 12. Oktober 2026 um 21:04 UTCidentified

   Wir arbeiten immer noch daran, den Service wiederherzustellen. Wir machen Fortschritte und kommen der Lösung des Problems näher. Vielen Dank für Ihre Geduld.

10. 12. Oktober 2026 um 22:02 UTCidentified

    Der Service bleibt degradiert, und wir wissen, dass dies seit mehreren Stunden andauert. Unser Team arbeitet noch daran, es wiederherzustellen. Es tut uns leid für die ausgedehnte Störung.

11. 12. Oktober 2026 um 23:12 UTCidentified

    Die Nutzung von Workflows wird weiter beeinträchtigt. Unser Team arbeitet aktiv daran, die volle Funktionalität wiederherzustellen. Wir entschuldigen uns für die anhaltende Störung und alle Unannehmlichkeiten, die dies verursachen kann.

12. 13. Oktober 2026 um 00:14 UTCidentified

    Die Funktionalität von Workflows erlebt immer noch eine Verschlechterung. Unser Team arbeitet fleißig daran, die volle Kapazität wiederherzustellen. Wir entschuldigen uns für die ausgedehnte Störung und alle Unannehmlichkeiten, die dies verursachen kann.

13. 13. Oktober 2026 um 00:23 UTCmonitoring

    Die notwendigen Fixes wurden erfolgreich auf das System angewendet. In diesem Moment überwachen wir aktiv die Ergebnisse, um die Wirksamkeit dieser Änderungen zu bewerten und sicherzustellen, dass alles wie beabsichtigt funktioniert.

14. 13. Oktober 2026 um 01:00 UTCresolved

    Das Problem mit Workflows wurde behoben und die Dienste funktionieren jetzt normal. Wir entschuldigen uns für jede Störung, die dies verursacht haben könnte und schätzen Ihre Geduld und Ihr Verständnis.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 26. September 2026 um 13:00 UTCinvestigating

   Wir haben derzeit probleme mit der anmeldung bei livechat. Unser Team ist sich des Problems bewusst und arbeitet daran, es so schnell wie möglich zu lösen

2. 26. September 2026 um 13:18 UTCinvestigating

   Wir untersuchen ein Problem, das einige Kunden betrifft. Unser Team arbeitet daran, die Ursache zu identifizieren und den normalen Service so schnell wie möglich wiederherzustellen. Wir werden ein Update teilen, sobald weitere Informationen verfügbar sind.

3. 26. September 2026 um 13:52 UTCmonitoring

   Es wurde ein Fix implementiert, und wir überwachen die Ergebnisse. Einige Kunden können immer noch kleinere Störungen auftreten, während sich die Systeme erholen. Wir werden Updates teilen, wenn sich die Situation ändert.

4. 26. September 2026 um 13:58 UTCresolved

   Das Problem wurde behoben und die Dienste funktionieren normal. Es sind keine weiteren Auswirkungen zu erwarten.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 28. Juli 2026 um 11:30 UTCidentified

   Wir haben festgestellt, dass sich das Problem auf einen externen Anbieter bezieht. Wir arbeiten mit ihnen zusammen, um das Problem zu untersuchen und zu lösen. Der Service kann beeinträchtigt bleiben, während das Problem behoben wird. Wir werden ein Update bereitstellen, sobald wir mehr Details oder eine geschätzte Zeit bis zur Lösung haben.

2. 28. Juli 2026 um 11:54 UTCinvestigating

   Wir untersuchen ein Problem, das einige Kunden betrifft. Das Problem kann mit einem externen Anbieter zusammenhängen, und wir arbeiten daran, die Ursache zu bestätigen und den normalen Service so schnell wie möglich wiederherzustellen. Wir werden ein Update teilen, sobald weitere Informationen verfügbar sind.

3. 28. Juli 2026 um 13:49 UTCinvestigating

   Wir arbeiten weiterhin mit dem Drittanbieter zusammen, um das Problem zu lösen. In diesem Stadium erwarten wir weitere Informationen von ihnen als Teil ihres Überprüfungsprozesses. Wir werden unser nächstes Update zur Verfügung stellen, sobald wir zusätzliche Informationen zu teilen haben oder es eine signifikante Änderung der Situation gibt. Vielen Dank für Ihre Geduld.

4. 29. Juli 2026 um 13:01 UTCresolved

   Das Problem mit dem Öffnen von Dateien wurde behoben, und die Dienste funktionieren normal. Es tut uns leid für jede Störung, die dies verursacht haben könnte, und ich danke Ihnen für Ihre Geduld und Ihr Verständnis.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 10. Juli 2026 um 02: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. Juli 2026 um 02:36 UTCidentified

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

3. 10. Juli 2026 um 02:38 UTCidentified

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

4. 10. Juli 2026 um 02:41 UTCresolved

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

1. 12. Juni 2026 um 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. Juni 2026 um 22:33 UTCidentified

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

3. 12. Juni 2026 um 22:55 UTCidentified

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

4. 12. Juni 2026 um 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. Juni 2026 um 23:30 UTCresolved

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

1. 25. Mai 2026 um 05: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. Mai 2026 um 06: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. Mai 2026 um 06: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. Mai 2026 um 02: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. Mai 2026 um 03: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. Mai 2026 um 04: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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 12:06 UTCresolved

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

1. 25. Februar 2026 um 04: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. Februar 2026 um 04: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. Februar 2026 um 04: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. Februar 2026 um 05: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. Februar 2026 um 05:44 UTCidentified

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

6. 25. Februar 2026 um 06:08 UTCidentified

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

7. 25. Februar 2026 um 06:30 UTCidentified

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

8. 25. Februar 2026 um 06: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. Februar 2026 um 07: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. Februar 2026 um 07: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. Februar 2026 um 07:42 UTCmonitoring

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

12. 25. Februar 2026 um 08:05 UTCmonitoring

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

13. 25. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 18:28 UTCidentified

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

23. 25. Februar 2026 um 18:43 UTCmonitoring

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

24. 26. Februar 2026 um 05: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. Februar 2026 um 05: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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 18:52 UTCinvestigating

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

3. 21. Februar 2026 um 18:54 UTCmonitoring

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

4. 21. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 18:10 UTCresolved

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

1. 20. Januar 2026 um 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. Januar 2026 um 00:08 UTCinvestigating

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

3. 21. Januar 2026 um 00:48 UTCinvestigating

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

4. 21. Januar 2026 um 01: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. Januar 2026 um 01: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. Januar 2026 um 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. Januar 2026 um 16:43 UTCidentified

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

3. 20. Januar 2026 um 17:01 UTCidentified

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

4. 20. Januar 2026 um 17:22 UTCidentified

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

5. 20. Januar 2026 um 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. Januar 2026 um 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. Januar 2026 um 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. Januar 2026 um 18:52 UTCidentified

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

9. 20. Januar 2026 um 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. Januar 2026 um 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. Januar 2026 um 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. Januar 2026 um 14:50 UTCinvestigating

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

2. 20. Januar 2026 um 14:56 UTCmonitoring

   Fixes have been applied, we are monitoring the performance

3. 20. Januar 2026 um 15:08 UTCresolved

   Communication is fully restored now.

1. 20. Januar 2026 um 14:49 UTCinvestigating

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

2. 20. Januar 2026 um 14:56 UTCmonitoring

   Fixes have been applied, we are monitoring the performance

3. 20. Januar 2026 um 15:07 UTCresolved

   Full widget performance was restored.

1. 13. Januar 2026 um 07:03 UTCinvestigating

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

2. 13. Januar 2026 um 07:11 UTCresolved

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

1. 22. Dezember 2025 um 11:53 UTCinvestigating

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

2. 22. Dezember 2025 um 11:53 UTCmonitoring

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

3. 22. Dezember 2025 um 11:53 UTCresolved

   This problem has been resolved.

1. 22. Dezember 2025 um 11:53 UTCinvestigating

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

2. 22. Dezember 2025 um 11:53 UTCmonitoring

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

3. 22. Dezember 2025 um 11:53 UTCresolved

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

1. 22. Dezember 2025 um 11:53 UTCinvestigating

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

2. 22. Dezember 2025 um 11:53 UTCmonitoring

   DDoS is under control, service is fully functional again.

3. 22. Dezember 2025 um 11:53 UTCresolved

   Problem with DDoS attack has been resolved.