Historique des pannes de Helpshift

1. 31 août 2026 à 18:02 UTCinvestigating

   Nous sommes au courant d'une interruption continue de service du flocon des neiges qui a des répercussions sur les services qui dépendent du flocon des neiges pour la récupération et le traitement des données. Impact client : Les services touchés peuvent connaître des problèmes de disponibilité dégradée, de données retardées ou de fonctionnalité. État : Nous surveillons activement le rétablissement de Snowflake et évaluons l'impact sur nos services. Aucune action n'est nécessaire pour le moment. Nous continuerons de fournir des mises à jour au fur et à mesure que la situation progressera et confirmerons une fois que les services touchés seront revenus à la normale.

2. 31 août 2026 à 18:05 UTCinvestigating

   Nous continuons de suivre de près la situation et fournirons d'autres mises à jour à mesure que la question progressera.

3. 31 août 2026 à 20:57 UTCresolved

   Le problème causé par la panne de flocons de neige a été résolu. Les services suivants sont désormais pleinement opérationnels : Tableau de bord analytique Puissance BI API analytique La récupération et le traitement des données sont revenus à la normale, et tous les services touchés fonctionnent comme prévu. Si vous rencontrez des problèmes connexes, n'hésitez pas à contacter notre équipe de support à [email protected]. Nous nous excusons pour tout désagrément causé et apprécions votre patience et votre compréhension.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 31 juillet 2026 à 12:31 UTCinvestigating

   Nous vivons actuellement une dégradation de la performance impactant la page de support Web. Les utilisateurs peuvent rencontrer des erreurs lorsqu'ils tentent de créer un ticket via le formulaire Contactez-nous et les formulaires intelligents.

2. 31 juillet 2026 à 14:23 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

3. 31 juillet 2026 à 14:37 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 24 juillet 2026 à 07:52 UTCinvestigating

   Nous connaissons actuellement des performances dégradées affectant le tableau de bord analytique. Les utilisateurs peuvent remarquer que la fonction de défilement ne fonctionne pas comme prévu.

2. 24 juillet 2026 à 09:23 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 7 juillet 2026 à 12:49 UTCinvestigating

   Nous rencontrons actuellement un problème avec Helpshift, où certains agents rencontrent des erreurs ou des latences sur le tableau de bord.

2. 7 juillet 2026 à 13:06 UTCinvestigating

   Nous continuons d'enquêter sur cette question.

3. 7 juillet 2026 à 13:59 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

4. 7 juillet 2026 à 14:04 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 2 juillet 2026 à 12:03 UTCinvestigating

   Nous vivons actuellement une panne autour d'Automations, Bottes et Smart Views. Notre équipe enquête sur la question et travaille à restaurer les services le plus rapidement possible.

2. 2 juillet 2026 à 12:23 UTCidentified

   Le problème a été identifié et une solution est en cours de mise en oeuvre.

3. 2 juillet 2026 à 12:39 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

4. 2 juillet 2026 à 12:42 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 16 juin 2026 à 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 juin 2026 à 13:07 UTCidentified

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

3. 16 juin 2026 à 13:09 UTCmonitoring

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

4. 16 juin 2026 à 13:21 UTCresolved

   This incident has been resolved.

1. 4 juin 2026 à 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 juin 2026 à 08:59 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 juin 2026 à 09:04 UTCidentified

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

4. 4 juin 2026 à 09:12 UTCmonitoring

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

5. 4 juin 2026 à 09:31 UTCresolved

   This incident has been resolved.

1. 22 mai 2026 à 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 à 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 à 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 à 20:22 UTCmonitoring

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

5. 22 mai 2026 à 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 à 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 à 11:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 7 mai 2026 à 11:45 UTCidentified

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

4. 7 mai 2026 à 11:51 UTCmonitoring

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

5. 7 mai 2026 à 12:09 UTCresolved

   This incident has been resolved.

1. 5 mai 2026 à 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 à 13:56 UTCinvestigating

   We are actively continuing our investigation into this issue.

3. 5 mai 2026 à 15:32 UTCidentified

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

4. 5 mai 2026 à 16:43 UTCmonitoring

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

5. 5 mai 2026 à 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 à 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 à 11:33 UTCinvestigating

   We are continuing to investigate this issue.

3. 5 mai 2026 à 11:56 UTCmonitoring

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

4. 5 mai 2026 à 12:06 UTCresolved

   This incident has been resolved.

1. 5 mai 2026 à 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 à 09:23 UTCinvestigating

   We are continuing to investigate this issue.

3. 5 mai 2026 à 09:31 UTCidentified

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

4. 5 mai 2026 à 09:37 UTCmonitoring

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

5. 5 mai 2026 à 09:41 UTCresolved

   This incident has been resolved.

1. 14 avril 2026 à 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 avril 2026 à 13:06 UTCmonitoring

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

3. 14 avril 2026 à 13:08 UTCresolved

   This incident has been resolved.

1. 1 avril 2026 à 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 avril 2026 à 10:28 UTCresolved

   This incident has been resolved.

1. 10 mars 2026 à 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 mars 2026 à 21:49 UTCidentified

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

3. 10 mars 2026 à 22:20 UTCmonitoring

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

4. 10 mars 2026 à 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 février 2026 à 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 février 2026 à 15:05 UTCidentified

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

3. 17 février 2026 à 15:15 UTCresolved

   This incident has been resolved.

1. 19 décembre 2025 à 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 décembre 2025 à 09:58 UTCinvestigating

   We are continuing to investigate this issue.

3. 19 décembre 2025 à 11:06 UTCresolved

   This incident has been resolved.

1. 5 décembre 2025 à 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 décembre 2025 à 09:09 UTCresolved

   This incident has been resolved.

1. 5 décembre 2025 à 07:01 UTCinvestigating

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

2. 5 décembre 2025 à 07:05 UTCmonitoring

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

3. 5 décembre 2025 à 07:20 UTCresolved

   This incident has been resolved.

1. 27 novembre 2025 à 09:32 UTCinvestigating

   We are currently investigating this issue.

2. 27 novembre 2025 à 09:53 UTCinvestigating

   We are continuing to investigate this issue.

3. 27 novembre 2025 à 09:58 UTCidentified

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

4. 27 novembre 2025 à 10:17 UTCidentified

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

5. 27 novembre 2025 à 10:22 UTCresolved

   This incident has been resolved.