Historique des pannes de Mindtickle

1. 24 octobre 2026 à 13:19 UTCresolved

   Résumé • Deux vulnérabilités critiques dans le temps d'exécution PHP ont été divulguées le 21 octobre 2026. • La plateforme Mindtickle, y compris les sites d'apprentissage des clients et les déploiements sur mesure, est construite principalement sur Go, JavaScript, TypeScript, Python et Java, et n'est pas affectée. Composante affectée • Un composant de support a utilisé PHP: le service de backend pour l'application. Il est séparé des fonctions de recherche d'articles d'aide et de chat dans le même panneau de support, qui fonctionnent sur d'autres services et ne sont pas affectés. • Il sert le formulaire de rétroaction et reçoit un rapport lorsqu'un utilisateur en soumet un. Le service transmet le rapport à notre service d'assistance. • Il fonctionne séparément de la plate-forme Mindtickle centrale. Il ne fait pas partie de la façon dont les sites d'apprentissage sont desservis, de la façon dont les utilisateurs se connectent, ni de la façon dont le contenu d'apprentissage et les données des locataires sont stockés ou traités. Elle n'a pas accès aux systèmes qui détiennent ces données. Réparation • Le 23 octobre 2026, nous avons appliqué les modifications de configuration d'atténuation recommandées dans l'avis de sécurité PHP pour réduire le risque d'exploitation pendant que nous préparions la mise à niveau. • Le 24 octobre 2026, nous avons mis le composant à niveau en PHP 8.3.36, la version fixe, dans toutes les régions de production et avons vérifié la correction. • Nous avons également ajouté un contrôle de filtrage des requêtes comme mesure de défense en profondeur. La composante est restée en service tout au long de la période sans interruption. Enquête • Nous avons examiné les registres depuis le 20 octobre 2026, la veille de la divulgation publique, grâce à des mesures correctives le 24 octobre 2026. • Nous n'avons trouvé aucune preuve d'exploitation et aucune preuve d'accès ou d'exposition aux données des clients. Aucune mesure nécessaire • Il n'est pas nécessaire de faire pivoter les mots de passe, les clés API, les paramètres SSO ou les identifiants d'intégration. • Nous continuons à surveiller et mettrons à jour cette page si quelque chose change. • Pour toute question, preuve à l'appui ou attestation formelle, envoyez un courriel à [email protected] .

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

1. 21 septembre 2026 à 13:13 UTCinvestigating

   Les utilisateurs sont actuellement incapables de se connecter à la plate-forme Mindtickle. Les utilisateurs déjà connectés ne sont pas touchés et peuvent continuer à utiliser la plateforme. Notre équipe enquête activement sur le problème.

2. 21 septembre 2026 à 13:53 UTCidentified

   Nous avons identifié la cause profonde du problème de connexion et travaillons actuellement sur un patch.

3. 21 septembre 2026 à 15:10 UTCmonitoring

   Nous voyons des signes de récupération, et certains utilisateurs devraient maintenant être en mesure de se connecter à la plate-forme Mindtickle. Nous continuons de surveiller le rétablissement et de travailler auprès des autres utilisateurs touchés.

4. 21 septembre 2026 à 15:46 UTCmonitoring

   Mise à jour : La fonctionnalité de connexion a été restaurée pour la majorité des utilisateurs. Nous continuerons de surveiller de près la plate-forme pour assurer une reprise et une stabilité complètes.

5. 21 septembre 2026 à 16:42 UTCresolved

   Le problème de connexion touchant la plateforme a été résolu et les utilisateurs peuvent désormais se connecter normalement. La perturbation a duré de 04h52 à 09h42. Aucune donnée client n'a été affectée. Les utilisateurs qui étaient déjà connectés à Mindtickle ont pu accéder à la plate-forme sans aucune préoccupation. Nous sommes désolés pour cette perturbation. Si vous êtes toujours incapable de vous connecter, veuillez nous contacter @ [email protected]. Nous allons terminer un postmortem interne et publier le RCA ici dans les prochains jours.

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

1. 16 septembre 2026 à 13:33 UTCidentified

   Nous sommes conscients d'un problème touchant les workflows liés à Salesforce, causé par une panne continue du côté de Salesforce. Ce n'est pas le résultat d'un problème au sein de Mindtickle. Ce qui est affecté : Les clients qui utilisent l'intégration Salesforce peuvent constater des défaillances ou des retards dans les cas suivants : 1. Intégration de Salesforce (SFDC): synchronisation des données CRM, fourniture/sync de l'utilisateur, recommandations de module/actifs et synchronisation des performances de l'apprenant vers Salesforce 2. Salle de vente numérique: possibilité de synchronisation, contacts, création automatique de salles pour les opportunités Salesforce, et comptes de Salesforce, et activité de salle d'écriture retour à Salesforce. La fonctionnalité de base DSR (création et partage de salles, contenu, analyse) reste disponible. 3. Appeler AI : cartographier les enregistrements vers Salesforce et montrer les champs d'opportunité/compte de Salesforce lors d'une réunion une fois disponible, pousser les informations sur les appels à Salesforce et à Salesforce Dialer. La fonctionnalité Core Call AI (enregistrement, transcription, informations) reste disponible. Ce qui n'est pas affecté : Les workflows non-salesforce, les fonctionnalités de base du produit et les clients qui n'utilisent pas l'intégration Salesforce fonctionnent normalement. Nous surveillons activement la panne de Salesforce et évaluons l'impact.

2. 16 septembre 2026 à 17:01 UTCresolved

   La panne du côté Salesforce a été résolue, et tous les workflows concernés fonctionnent maintenant normalement.

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

1. 31 août 2026 à 11:08 UTCinvestigating

   Vendeur Copilot connaît des taux d'erreur élevés en raison d'une panne en aval dans le centre de données Azure supportant ce cas d'utilisation. En outre, le support de chat Mindtickle peut éprouver des échecs dans la génération de réponses à vos requêtes.

2. 31 août 2026 à 11:40 UTCidentified

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

3. 31 août 2026 à 12:10 UTCmonitoring

   un correctif a été mis en œuvre et nous suivons la situation.

4. 31 août 2026 à 13:06 UTCresolved

   L'incident a été résolu et tous les systèmes sont maintenant opérationnels.

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

1. 19 août 2026 à 17:16 UTCinvestigating

   Nous enquêtons sur un problème où un sous-ensemble de clients peuvent voir des données statiques dans certains rapports d'analyse, en particulier: SSR, tableaux de bord personnalisés, rapports de gestionnaire et de relation, et rapports d'aperçu / adoption / performance. D'autres rapports et zones de produits ne sont pas touchés. Si votre analyse reflète les données actuelles, aucune action n'est nécessaire. Nous publierons bientôt une mise à jour.

2. 20 août 2026 à 02:07 UTCresolved

   Cette question est résolue. Tous les rapports touchés montrent maintenant les données actuelles. Merci de votre patience.

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

1. 13 juin 2026 à 00:35 UTCinvestigating

   We are currently experiencing a partial service disruption on Mindtickle platform. Users may encounter errors, intermittent failures, or degraded performance across the platform. Our engineering team is actively investigating and mitigating the issue while closely monitoring recovery efforts.

2. 13 juin 2026 à 00:51 UTCidentified

   We have identified the cause of the elevated error rates and are deploying mitigation measures. We are monitoring the platform closely and working to restore normal service.

3. 13 juin 2026 à 01:01 UTCmonitoring

   Mitigation has been deployed and services are operating normally. We are continuing to monitor the platform closely to ensure stability.

4. 15 juin 2026 à 03:36 UTCresolved

   The incident has been resolved and services are operating normally. We will continue to monitor the platform to ensure stability. A detailed Root Cause Analysis will be shared shortly.

5. 18 juin 2026 à 12:24 UTCpostmortem

   # **Incident Summary** On June 12, 2026, Mindtickle experienced a service disruption caused by an unexpected surge in processing activity within one of our backend workflows. The resulting increase in downstream traffic exceeded the capacity of a critical platform dependency, leading to service degradation and eventual unavailability. The issue was mitigated by reducing processing throughput and allowing affected systems to recover. **Impact Duration:** **3 hours and 15 minutes**. ## **Impact** During the incident window, customers may have experienced: * Delays in invitation-related workflows * Elevated latency and intermittent errors across affected services * Temporary degradation of platform functionality dependent on the impacted backend systems ## **Incident Timeline** * ‌**Jun 12, 03:00 PM**: A critical backend dependency becomes saturated, resulting in service degradation and elevated error rates. * **Jun 12, 03:15 PM**: The issue is detected through automated monitoring and customer reports. Investigation begins. * **Jun 12, 04:50 PM**: Mitigation measures are implemented to reduce processing throughput and stabilize affected systems. * **Jun 12, 05:46 PM**: Platform functionality is restored fully ## **Root Cause** A backend workflow generated a significantly higher volume of processing activity than historical norms. As the system worked through the resulting backlog, requests propagated through multiple downstream services, creating sustained load across the platform. While each component behaved as designed, the combined volume exposed capacity and protection gaps within the processing chain. The resulting amplification effect overwhelmed a critical backend dependency, causing service degradation and eventual unavailability. ## **Resolution** The team mitigated the incident by reducing the rate at which backlog processing occurred, allowing downstream systems to stabilize and recover. Once traffic levels returned to normal operating ranges, affected services resumed normal operation and platform functionality was fully restored. ## **Corrective and Preventive Actions** * Introduce rate limiting and additional safeguards for high-volume processing workflows to prevent a single workflow from generating excessive downstream load. * Implement backpressure, circuit-breaking, and load-shedding mechanisms across critical processing paths to better protect downstream dependencies during traffic spikes. * Review platform capacity limits, concurrency settings, and monitoring to improve resilience and provide earlier visibility into abnormal processing patterns.

1. 3 juin 2026 à 17:06 UTCresolved

   On June 2nd, between 7:19 AM PDT and 9:21 AM PDT, our third-party recording provider experienced a disruption that prevented the Call AI bot from joining meetings. A limited number of customers were impacted, and unfortunately, the affected recordings are non-recoverable. We sincerely apologize for the disruption and any impact to your workflows. The issue is fully resolved, and recordings are functioning normally. If your account was affected, your account team will reach out with specific details.

1. 21 mai 2026 à 15:29 UTCinvestigating

   Users may experience issues starting Two-Way Roleplay sessions. In addition admins may be unable to preview roleplays. The team is actively investigating the issue and working toward resolution.

2. 21 mai 2026 à 15:59 UTCidentified

   We have identified the root cause as a service disruption at a third-party provider that powers parts of the Two-Way Roleplay workflow. We are actively working with the vendor to restore the service and recover impacted functionality as quickly as possible.

3. 21 mai 2026 à 17:07 UTCidentified

   Recovery efforts are still ongoing, and we continue to work closely with our third-party partners to restore the impacted service. Our teams remain actively engaged on the issue.

4. 21 mai 2026 à 17:18 UTCidentified

   We are seeing partial recovery in the impacted service, and some roleplay attempts are now completing successfully. We continue to work with the third-party provider toward full restoration.

5. 21 mai 2026 à 17:49 UTCmonitoring

   The impacted systems are now operational again, and roleplay workflows are functioning successfully. We are continuing to monitor the systems closely to ensure stability.

6. 21 mai 2026 à 18:30 UTCresolved

   All impacted systems are now operating normally, and Two-Way Roleplay functionality has been fully restored. We will continue to monitor the systems closely. The incident is now resolved.

1. 18 mai 2026 à 13:17 UTCinvestigating

   The 'Featured Hubs' widget, wherever used on the Mindtickle platform, is not loading. The Hubs and individual media/assets are working properly. We are currently investigating this. All other capabilities of the Mindtickle platform are operating normally.

2. 18 mai 2026 à 13:21 UTCidentified

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

3. 18 mai 2026 à 13:31 UTCmonitoring

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

4. 18 mai 2026 à 13:55 UTCresolved

   This incident has been resolved. The 'Featured Hubs' widget is now loading as expected, and the Mindtickle platform is fully operational.

1. 11 mai 2026 à 14:25 UTCinvestigating

   We are currently investigating an issue impacting call recordings in Call AI. Users may experience failures while recording calls. The team is actively working on identifying the root cause and restoring normal functionality. Further updates will be shared shortly.

2. 11 mai 2026 à 16:35 UTCresolved

   The issue has now been identified and resolved, and Call AI services are operating normally again. We will share a detailed Root Cause Analysis (RCA) shortly.

1. 26 mars 2026 à 11:50 UTCresolved

   Between 07:50 AM and 11:25 AM PT on March 24, 2026, the Mindtickle platform experienced a service disruption affecting Call Recordings. Full service was restored by 11:25 AM PT. We are currently conducting a thorough investigation and will publish a detailed Root Cause Analysis (RCA) shortly.

2. 27 mars 2026 à 03:50 UTCpostmortem

   We experienced a service disruption impacting **Call AI bot functionality**. During this time, **select scheduled meetings were affected**, where Call AI bots were unable to join and record. The issue has been fully resolved, and services have returned to normal operation. ‌ **Impact** * Call AI bots were unable to join **select scheduled meetings** * Call recordings and transcriptions were not generated for impacted meetings ‌ **Timeline** * **07:50 AM PT:** Incident began; bots unable to join select meetings * **07:52 AM PT:** Alerts triggered; issue detected and investigation initiated * **09:00 AM PT:** Root cause identified within Call AI bot infrastructure * **10:15 AM PT:** Mitigation measures applied; service recovery in progress * **11:25 AM PT:** Service fully restored; bots resumed normal operation ‌ **Root Cause** This incident was caused by a **transient issue within the Call AI bot infrastructure**, which impacted service availability during the affected period. ‌ **Next Steps** * Exploring & implement enhanced failover mechanisms to improve system resilience * Introducing more granular monitoring and alerting for faster detection ‌ We apologize for the inconvenience caused and appreciate your patience.

1. 19 février 2026 à 14:33 UTCinvestigating

   we are currently investigating an issue affecting the Analytics Platform. While out of the box dashboards remain functional, users may be unable to open existing custom reports or create new ones. Our engineering team is identifying the root cause, and we will provide an update as soon as more information is available. We apologize for the interruption to your workflow.

2. 19 février 2026 à 14:50 UTCinvestigating

   We are continuing to investigate this issue.

3. 19 février 2026 à 14:52 UTCresolved

   We have successfully resolved the issue affecting the Analytics Platform. All custom reports should now load correctly, and the ability to create new reports has been fully restored. Our team has verified the fix, and we are monitoring the system to ensure continued stability. Thank you for your patience while we worked to get this back online.

1. 12 février 2026 à 03:29 UTCinvestigating

   We are observing high error rates for both admins and end users for select customer instances. We are investigating the issue and will share an update shortly.

2. 12 février 2026 à 03:29 UTCidentified

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

3. 12 février 2026 à 03:36 UTCmonitoring

   We have implemented a fix and are monitoring the progress. We are seeing the error rates coming down.

4. 12 février 2026 à 03:37 UTCresolved

   The incident has been resolved. All admins and end users should be able to access the platform without any concerns.

1. 6 février 2026 à 13:23 UTCresolved

   [Resolved] A subset of customers (admins only) experienced intermittent failures when admins attempted to upload content to the platform. End users were not impacted and were able to view existing content without issues. The issue has been resolved, and all admin content upload workflows are operating as expected. Incident Timeline Start Time: 05 Feb 2026, 11:15 PM PT Resolved Time: 06 Feb 2026, 05:12 AM PT We will share a detailed RCA once the post-incident review is complete.

1. 18 novembre 2025 à 14:45 UTCidentified

   The Two-Way Roleplay Missions feature is currently experiencing an outage and is inaccessible. This is a direct consequence of the ongoing, widespread Cloudflare network outage. We are closely monitoring Cloudflare's recovery efforts and expect the service to be restored as soon as their network disruption is resolved.

2. 18 novembre 2025 à 14:54 UTCmonitoring

   Cloudflare has confirmed the deployment of a fix for the underlying network issue. We are now observing a significant decrease in error rates on our platform, with Two-Way Roleplay Missions starting to become accessible again. We will continue to monitor the platform closely as services stabilize, and will post a final resolution notice once all operations are confirmed to be fully back to normal.

3. 18 novembre 2025 à 15:37 UTCmonitoring

   Two-Way Roleplay Missions are operational. We will continue to monitor the platform closely to ensure stability before marking this incident as fully resolved.

4. 18 novembre 2025 à 17:17 UTCresolved

   All services are normal. A detailed Root Cause Analysis (RCA) will be published shortly.

1. 20 octobre 2025 à 16:30 UTCidentified

   There has been a second surge of error rates and latencies reported due to an AWS outage in the US-East-1 region. The AWS team is actively working on this and we are monitoring the status closely. Though the platform is up and some features are working, select customers and users may face intermittent failues in accessing the platform. We will keep updating the status page as soon as we receive updates from AWS. We apologize for the inconvenience caused here. AWS Outage Status: https://health.aws.amazon.com/health/status

2. 20 octobre 2025 à 17:51 UTCidentified

   As per AWS, their internal subsystems are now showing early signs of recovering in a few Availability Zones (AZs) in the US-EAST-1 Region. They are now applying mitigations to the remaining AZs at which point we expect launch errors and network connectivity issues to subside. We will share an update once the AWS team has applied the mitigations and we have verified at our end.

3. 20 octobre 2025 à 19:43 UTCmonitoring

   Post the recovery and fix from the AWS team, we are observing a significant improvement in the Mindtickle platform performance. Most Mindtickle workflows are now functioning normally. Our teams continue to monitor the situation closely and will provide an update once the issue is fully resolved. AWS Outage Status: https://health.aws.amazon.com/health/status

4. 20 octobre 2025 à 20:55 UTCresolved

   The incident has been resolved, and the Mindtickle platform is now operating normally. We continue to closely monitor performance to ensure everything remains stable.

1. 20 octobre 2025 à 10:07 UTCmonitoring

   Earlier today, some Mindtickle customers experienced high error rates and intermittent service disruptions due to an AWS outage in the US-East-1 region. AWS has since deployed a fix, and we’re observing steady recovery across our systems. Error rates are declining, and most services are returning to normal. Our teams continue to monitor the platform closely to ensure full stability. We’ll share a final update once all systems are fully restored. Thank you for your patience and understanding.

2. 20 octobre 2025 à 11:03 UTCresolved

   The incident has been resolved, and the Mindtickle platform is operating normally.

1. 16 octobre 2025 à 03:54 UTCinvestigating

   We’ve identified an issue where specific pages within the Analytics section are displaying stale or incorrect data for select customers. Our team is actively investigating the issue and will share further updates as soon as possible. Impacted Areas: 1. OData Routes (Partial Routes) – Stale data visible 2. Analytics Platform Pages (Series, Modules, Learner & Learner Groups) – Incorrect data displayed 3. Custom Reports shared with customers via Email (in the last 12 hours) – Incorrect data displayed

2. 16 octobre 2025 à 04:29 UTCmonitoring

   A fix has been implemented and we are running a sanity check at our end.

3. 16 octobre 2025 à 04:50 UTCresolved

   This incident has been resolved. We will share an RCA once the postmortem is complete.

1. 15 octobre 2025 à 11:19 UTCresolved

   Between October 14, 2025, 12:10 AM PT and October 15, 2025, 3:00 AM PT, select Call AI customers experienced a delay in the processing of call recordings. Impact: 1. Call recordings generated during this period were temporarily not visible on the Call Listing page. What Continued to Work: 1. All recordings captured before the incident window remained accessible on the Call Listing page. 2. For calls recorded during the incident, Recording Ready emails were successfully sent to end users, allowing access to the recordings via the email links. We are conducting a post-incident analysis to identify the root cause. A detailed Root Cause Analysis (RCA) report will be shared once the investigation is complete.

1. 24 septembre 2025 à 09:01 UTCinvestigating

   We're currently experiencing an high error rate in our in-platform analytics and are actively investigating the root cause to restore full functionality.

2. 24 septembre 2025 à 09:40 UTCidentified

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

3. 24 septembre 2025 à 09:51 UTCmonitoring

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

4. 24 septembre 2025 à 10:09 UTCresolved

   A fix has been applied, and the incident has been resolved. We are continuing to monitor this closely.