Histórico de interrupções do Mindtickle

1. 24 Here 2026 da 13:19 UTCresolved

   Resumo • Duas vulnerabilidades críticas na execução do PHP (“PHP2Shell”) foram divulgadas publicamente em 21 de outubro de 2026. • A plataforma Mindtickle, incluindo sites de aprendizagem de clientes e implantações de domínio personalizado, é construída principalmente em Go, JavaScript, TypeScript, Python e Java, e não é afetada. Componente afectado • Um componente de suporte usou PHP: o serviço de infraestrutura para o formulário de feedback “Relatar um problema” no aplicativo. Está separado dos recursos de pesquisa e chat de artigos de ajuda no mesmo painel de suporte, que são executados em outros serviços e não são afetados. • Serve o formulário de feedback e recebe um relatório quando um usuário envia um. O serviço encaminha o relatório para o helpdesk da nossa equipe de apoio. • Funciona separadamente da plataforma Mindtickle central. Não faz parte de como os sites de aprendizagem são servidos, como os usuários entram, ou como o conteúdo de aprendizagem e os dados do inquilino são armazenados ou processados. Não tem acesso aos sistemas que mantêm esses dados. Remediação • Em 23 de outubro de 2026, aplicamos as alterações de configuração atenuantes recomendadas no parecer de segurança do PHP para reduzir o risco de exploração enquanto preparamos a atualização. • Em 24 de outubro de 2026, atualizamos o componente para PHP 8.3.36, o lançamento fixo, em todas as regiões de produção e verificamos a correção. • Também adicionamos um controle de filtragem de pedidos como medida de defesa em profundidade. O componente permaneceu em serviço durante todo o período, sem tempo de parada. Inquérito • Revisamos logs de 20 de outubro de 2026, um dia antes da divulgação pública, através de remediação em 24 de outubro de 2026. • Nós não encontramos nenhuma evidência de exploração e nenhuma evidência de que qualquer dado do cliente foi acessado ou exposto. Nenhuma ação necessária • Não há necessidade de rodar senhas, chaves de API, configurações de SSO ou credenciais de integração. • Continuamos a monitorar e atualizaremos esta página se alguma coisa mudar. • Para perguntas, evidências de suporte, ou um atestado formal, email [email protected] .

Traduzido automaticamente da atualização oficial do incidente.

1. 21 Gwengolo 2026 da 13:13 UTCinvestigating

   Actualmente, os utilizadores não conseguem aceder à plataforma Mindtickle. Usuários que já estão conectados não são afetados e podem continuar usando a plataforma. A nossa equipa está a investigar a questão.

2. 21 Gwengolo 2026 da 13:53 UTCidentified

   Identificamos a causa raiz do problema de login e estamos atualmente trabalhando em um patch.

3. 21 Gwengolo 2026 da 15:10 UTCmonitoring

   Estamos vendo sinais de recuperação, e alguns usuários devem agora ser capazes de fazer login na plataforma Mindtickle. Continuamos a monitorizar a recuperação e o trabalho através dos restantes utilizadores afectados.

4. 21 Gwengolo 2026 da 15:46 UTCmonitoring

   Atualização: A funcionalidade de login agora foi restaurada para a maioria dos usuários. Continuaremos a monitorar a plataforma de perto para garantir a plena recuperação e estabilidade.

5. 21 Gwengolo 2026 da 16:42 UTCresolved

   O problema de login que afeta a plataforma foi resolvido, e os usuários agora podem entrar normalmente. A interrupção durou de 04:52 AM PT a 9:42 AM PT. Nenhum dado do cliente foi afetado. Usuários que já estavam conectados à Mindtickle foram capazes de acessar a plataforma sem preocupações. Lamentamos a interrupção que isto causou. Se você ainda não conseguir entrar, entre em contato conosco @ [email protected]. Completaremos uma autópsia interna e publicaremos a RCA aqui nos próximos dias.

Traduzido automaticamente da atualização oficial do incidente.

1. 16 Gwengolo 2026 da 13:33 UTCidentified

   Estamos cientes de um problema que afeta fluxos de trabalho relacionados à Salesforce, causado por uma falha contínua do lado da Salesforce. Este não é o resultado de um problema dentro de Mindtickle. O que é afetado: Os clientes que usam a integração Salesforce podem ver falhas ou atrasos no seguinte: 1. Salesforce Integration (SFDC): Sincronização de dados de CRM, provisionamento/sincronização de usuários, recomendações de módulo/avaliadores e sincronização de desempenho do aprendiz para Salesforce 2. Sala de Vendas Digital: oportunidades de sincronização, contatos, criação automática de sala para oportunidades Salesforce, e contas da Salesforce, e atividade de sala de escrita de volta para Salesforce. A funcionalidade DSR principal (criação e compartilhamento de salas, conteúdo, análise) permanece disponível. 3. Call AI: mapeando gravações para registros da Salesforce e mostrando campos de oportunidade/conta da Salesforce em uma reunião uma vez disponível, empurrando insights de chamada de volta para a Salesforce, e captura de chamada da Salesforce Dialer. A funcionalidade AI da chamada principal (gravação, transcrição, insights) permanece disponível. O que não é afetado: fluxos de trabalho não-vendas, funcionalidade do produto principal e clientes que não usam a integração da Salesforce estão todos funcionando normalmente. Estamos monitorando ativamente a falha da Salesforce e avaliando o impacto.

2. 16 Gwengolo 2026 da 17:01 UTCresolved

   A falha do Salesforce-side foi resolvida, e todos os fluxos de trabalho afetados estão agora funcionando normalmente.

Traduzido automaticamente da atualização oficial do incidente.

1. 31 Eost 2026 da 11:08 UTCinvestigating

   Seller Copilot está tendo altas taxas de erro devido a uma interrupção a jusante no centro de dados Azure que suporta este caso de uso. Além disso, o suporte de chat Mindtickle pode experimentar falhas na geração de respostas às suas consultas.

2. 31 Eost 2026 da 11:40 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 31 Eost 2026 da 12:10 UTCmonitoring

   foi implementada uma solução e estamos a acompanhar a situação.

4. 31 Eost 2026 da 13:06 UTCresolved

   O incidente foi resolvido e todos os sistemas estão operacionais.

Traduzido automaticamente da atualização oficial do incidente.

1. 19 Eost 2026 da 17:16 UTCinvestigating

   Estamos investigando um problema em que um subconjunto de clientes pode ver dados obsoletos em determinados relatórios de análise, especificamente: SSR, Custom Dashboards, Manager & Relationship reports, e Visão geral / Adoção / Relatórios de desempenho. Outros relatórios e áreas de produtos não são afetados. Se suas análises refletem dados atuais, nenhuma ação é necessária. Publicaremos uma actualização em breve.

2. 20 Eost 2026 da 02:07 UTCresolved

   Esta questão está resolvida. Todos os relatórios afetados estão agora mostrando dados atuais. Obrigado pela vossa paciência.

Traduzido automaticamente da atualização oficial do incidente.

1. 13 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 13:21 UTCidentified

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

3. 18 Mae 2026 da 13:31 UTCmonitoring

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

4. 18 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 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 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 14:50 UTCinvestigating

   We are continuing to investigate this issue.

3. 19 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 03:29 UTCidentified

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

3. 12 Cʼhwevrer 2026 da 03:36 UTCmonitoring

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

4. 12 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 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 Du 2025 da 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 Du 2025 da 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 Du 2025 da 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 Du 2025 da 17:17 UTCresolved

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

1. 20 Here 2025 da 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 Here 2025 da 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 Here 2025 da 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 Here 2025 da 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 Here 2025 da 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 Here 2025 da 11:03 UTCresolved

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

1. 16 Here 2025 da 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 Here 2025 da 04:29 UTCmonitoring

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

3. 16 Here 2025 da 04:50 UTCresolved

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

1. 15 Here 2025 da 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 Gwengolo 2025 da 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 Gwengolo 2025 da 09:40 UTCidentified

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

3. 24 Gwengolo 2025 da 09:51 UTCmonitoring

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

4. 24 Gwengolo 2025 da 10:09 UTCresolved

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