Störungsverlauf von Helpshift

1. 31. August 2026 um 18:02 UTCinvestigating

   Wir sind uns eines anhaltenden Snowflake-Service-Ausfalls bewusst, der sich auf Dienste auswirkt, die von Snowflake für den Datenabruf und die Datenverarbeitung abhängig sind. Customer Impact: Betroffene Dienste können eine eingeschränkte Verfügbarkeit, verzögerte Daten oder Funktionsprobleme aufweisen. Status: Wir überwachen aktiv die Erholung von Snowflake und bewerten die Auswirkungen auf unsere Dienstleistungen. Zu diesem Zeitpunkt sind keine Maßnahmen von Kunden erforderlich. Wir werden weiterhin Updates bereitstellen, wenn die Situation fortschreitet, und werden bestätigen, sobald die betroffenen Dienste wieder normal sind.

2. 31. August 2026 um 18:05 UTCinvestigating

   Wir beobachten die Situation weiterhin genau und werden weitere Updates bereitstellen, wenn das Problem fortschreitet.

3. 31. August 2026 um 20:57 UTCresolved

   Das durch den Snowflake-Ausfall verursachte Problem wurde behoben. Folgende Dienste sind nun voll funktionsfähig: Dashboard Analytics Leistung BI Analytics API Datenabruf und -verarbeitung haben sich wieder normalisiert, und alle betroffenen Dienste funktionieren wie erwartet. Wenn Sie auf verwandte Probleme stoßen, wenden Sie sich bitte gerne an unser Support-Team unter [email protected]. Wir entschuldigen uns für alle Unannehmlichkeiten und schätzen Ihre Geduld und Ihr Verständnis.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 31. Juli 2026 um 12:31 UTCinvestigating

   Wir erleben derzeit eine verminderte Leistung, die sich auf die Web-Support-Seite auswirkt. Benutzer können auf Fehler stoßen, wenn sie versuchen, ein Ticket über das Kontaktformular und Smart Forms zu erstellen.

2. 31. Juli 2026 um 14:23 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 31. Juli 2026 um 14:37 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 24. Juli 2026 um 07:52 UTCinvestigating

   Wir erleben derzeit eine verschlechterte Leistung, die sich auf das Analytics Dashboard auswirkt. Benutzer können feststellen, dass die Scroll-Funktion nicht wie erwartet funktioniert.

2. 24. Juli 2026 um 09:23 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 7. Juli 2026 um 12:49 UTCinvestigating

   Wir haben derzeit ein Problem mit Helpshift, bei dem einige Agenten auf Fehler oder Latenz im Dashboard stoßen.

2. 7. Juli 2026 um 13:06 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 7. Juli 2026 um 13:59 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 7. Juli 2026 um 14:04 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 2. Juli 2026 um 12:03 UTCinvestigating

   Wir erleben derzeit einen Ausfall bei Automatisierungen, Bots und Smart Views. Unser Team untersucht das Problem und arbeitet daran, die Dienste so schnell wie möglich wiederherzustellen.

2. 2. Juli 2026 um 12:23 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 2. Juli 2026 um 12:39 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 2. Juli 2026 um 12:42 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Juni 2026 um 12:40 UTCinvestigating

   We are currently experiencing an outage impacting the Auto-assignment feature. Our team is actively investigating the issue and working to restore normal functionality as quickly as possible.

2. 16. Juni 2026 um 13:07 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 16. Juni 2026 um 13:09 UTCmonitoring

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

4. 16. Juni 2026 um 13:21 UTCresolved

   This incident has been resolved.

1. 4. Juni 2026 um 08:47 UTCinvestigating

   We are currently experiencing a service outage. Our team is investigating the issue and working to restore services as quickly as possible.

2. 4. Juni 2026 um 08:59 UTCinvestigating

   We are continuing to investigate this issue.

3. 4. Juni 2026 um 09:04 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 4. Juni 2026 um 09:12 UTCmonitoring

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

5. 4. Juni 2026 um 09:31 UTCresolved

   This incident has been resolved.

1. 22. Mai 2026 um 17:07 UTCinvestigating

   We are currently experiencing a service disruption impacting the Issue Analytics data pipeline. As a result, the pipeline is not processing data, and analytics data is currently delayed by approximately 6 hours. Affected Components: Analytics → Advanced Analytics → Issues (All) All Endpoints under the Analytics API. For the affected systems, data freshness is currently impacted beyond the last 6 hours. All other systems and platform functionalities remain fully operational. Our engineering team is actively investigating the issue and working continuously to restore normal operations as quickly as possible. We will keep providing updates until normal service is fully restored.

2. 22. Mai 2026 um 18:38 UTCinvestigating

   We are actively continuing our investigation into this issue and working to identify the root cause. We will share further updates as soon as we have more information.

3. 22. Mai 2026 um 18:48 UTCidentified

   We have identified the fix and are actively working on implementing it. The resolution involves restoring data from backups, and due to the large volume of data, the process is taking longer than expected. We will continue to share updates as more information becomes available.

4. 22. Mai 2026 um 20:22 UTCmonitoring

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

5. 22. Mai 2026 um 20:25 UTCresolved

   This incident has been resolved, and all impacted services are now operating as expected. If you encounter any related issues, please contact us at [email protected]. We sincerely apologize for any inconvenience caused.

1. 7. Mai 2026 um 11:19 UTCinvestigating

   We are currently experiencing a disruption in service. Our team is actively investigating the issue and working to restore normal functionality as quickly as possible.

2. 7. Mai 2026 um 11:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 7. Mai 2026 um 11:45 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 7. Mai 2026 um 11:51 UTCmonitoring

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

5. 7. Mai 2026 um 12:09 UTCresolved

   This incident has been resolved.

1. 5. Mai 2026 um 12:19 UTCinvestigating

   We are currently experiencing a disruption in service. Our team is actively investigating the issue and working to restore normal functionality as quickly as possible.

2. 5. Mai 2026 um 13:56 UTCinvestigating

   We are actively continuing our investigation into this issue.

3. 5. Mai 2026 um 15:32 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 5. Mai 2026 um 16:43 UTCmonitoring

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

5. 5. Mai 2026 um 18:11 UTCresolved

   The issue has been resolved, and all affected services are now functioning as expected. If you experience any issues, please contact our support team at [email protected]. We apologize for any inconvenience caused and appreciate your patience.

1. 5. Mai 2026 um 10:04 UTCinvestigating

   We are currently experiencing a disruption in service. Our team is actively investigating the issue and working to restore normal functionality as quickly as possible.

2. 5. Mai 2026 um 11:33 UTCinvestigating

   We are continuing to investigate this issue.

3. 5. Mai 2026 um 11:56 UTCmonitoring

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

4. 5. Mai 2026 um 12:06 UTCresolved

   This incident has been resolved.

1. 5. Mai 2026 um 08:58 UTCinvestigating

   We are currently experiencing a disruption in service. Our team is actively investigating the issue and working to restore normal functionality as quickly as possible.

2. 5. Mai 2026 um 09:23 UTCinvestigating

   We are continuing to investigate this issue.

3. 5. Mai 2026 um 09:31 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 5. Mai 2026 um 09:37 UTCmonitoring

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

5. 5. Mai 2026 um 09:41 UTCresolved

   This incident has been resolved.

1. 14. April 2026 um 12:47 UTCinvestigating

   We are currently experiencing a disruption in service. Our team is actively investigating the issue and working to restore normal functionality as quickly as possible.

2. 14. April 2026 um 13:06 UTCmonitoring

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

3. 14. April 2026 um 13:08 UTCresolved

   This incident has been resolved.

1. 1. April 2026 um 10:16 UTCinvestigating

   We are currently experiencing a service outage affecting Helpshift Automations. At the moment, users may be unable to create new automations or load existing ones. Our engineering team is actively working to restore the service as quickly as possible.

2. 1. April 2026 um 10:28 UTCresolved

   This incident has been resolved.

1. 10. März 2026 um 19:26 UTCinvestigating

   We are currently experiencing degraded performance on the Helpshift Dashboard, which may impact the following services: Chatbots Time-Based Automations New Issue Automations Our team is actively investigating the root cause and will keep you updated with further information.

2. 10. März 2026 um 21:49 UTCidentified

   The root cause of the degraded performance has been determined, and a fix has been applied.

3. 10. März 2026 um 22:20 UTCmonitoring

   The affected services are now functioning as expected, and we are actively monitoring performance to maintain stability.

4. 10. März 2026 um 22:37 UTCresolved

   The issue has now been fully resolved and all services are operating normally. We apologize for any inconvenience caused and appreciate your patience while we worked on this. If you continue to experience any issues, please reach out to us at [email protected].

1. 17. Februar 2026 um 14:58 UTCinvestigating

   We are currently experiencing a partial degradation impacting the Team section of Dashboard Analytics. The following reports are affected: 1. Team – Trends (Overall) 2. Team – Trends (Workload) 3. Team – Summary by Agents

2. 17. Februar 2026 um 15:05 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 17. Februar 2026 um 15:15 UTCresolved

   This incident has been resolved.

1. 19. Dezember 2025 um 09:51 UTCinvestigating

   We are currently experiencing a degraded state with the AI Reply feature. Our engineering team is actively investigating the issue and working toward a resolution.

2. 19. Dezember 2025 um 09:58 UTCinvestigating

   We are continuing to investigate this issue.

3. 19. Dezember 2025 um 11:06 UTCresolved

   This incident has been resolved.

1. 5. Dezember 2025 um 09:06 UTCinvestigating

   We are currently experiencing a service outage caused by an issue with our dependent Cloudflare services. This may impact access to Helpshift features and overall platform availability. As per the Cloudflare status page (https://www.cloudflarestatus.com/), their services are undergoing updates/maintenance, which may be contributing to the disruption.

2. 5. Dezember 2025 um 09:09 UTCresolved

   This incident has been resolved.

1. 5. Dezember 2025 um 07:01 UTCinvestigating

   Currently a Helpshift Service Outage is being experienced. We are actively Investigating the Issue.

2. 5. Dezember 2025 um 07:05 UTCmonitoring

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

3. 5. Dezember 2025 um 07:20 UTCresolved

   This incident has been resolved.

1. 27. November 2025 um 09:32 UTCinvestigating

   We are currently investigating this issue.

2. 27. November 2025 um 09:53 UTCinvestigating

   We are continuing to investigate this issue.

3. 27. November 2025 um 09:58 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 27. November 2025 um 10:17 UTCidentified

   We are continuing to work on a fix for this issue.

5. 27. November 2025 um 10:22 UTCresolved

   This incident has been resolved.