Mindtickle outage history

Summary • Two critical vulnerabilities in the PHP runtime (“PHP2Shell”) were publicly disclosed on Oct 21, 2026. • The Mindtickle platform, including customer learning sites and custom-domain deployments, is built primarily on Go, JavaScript, TypeScript, Python, and Java, and is not affected. Affected component • One supporting component used PHP: the backend service for the in-app “Report an issue” feedback form. It is separate from the help-article search and chat features in the same support panel, which run on other services and are not affected. • It serves the feedback form and receives a report when a user submits one. The service forwards the report to our support team’s helpdesk. • It runs separately from the core Mindtickle platform. It is not part of how learning sites are served, how users sign in, or how learning content and tenant data are stored or processed. It has no access to the systems that hold that data. Remediation • On Oct 23, 2026, we applied the mitigating configuration changes recommended in the PHP security advisory to reduce the risk of exploitation while we prepared the upgrade. • On Oct 24, 2026, we upgraded the component to PHP 8.3.36, the fixed release, across all production regions and verified the fix. • We also added a request-filtering control as a defense-in-depth measure. The component remained in service throughout, with no downtime. Investigation • We reviewed logs from Oct 20, 2026, the day before public disclosure, through remediation on Oct 24, 2026. • We found no evidence of exploitation and no evidence that any customer data was accessed or exposed. No action required • There is no need to rotate passwords, API keys, SSO settings, or integration credentials. • We continue to monitor and will update this page if anything changes. • For questions, supporting evidence, or a formal attestation, email [email protected] .

Users are currently unable to log in to the Mindtickle platform. Users who are already logged in are not impacted and can continue using the platform. Our team is actively investigating the issue.

We have identified the root cause of the login issue and are currently working on a patch.

We are seeing signs of recovery, and some users should now be able to log in to the Mindtickle platform. We are continuing to monitor the recovery and work through the remaining impacted users.

Update: Login functionality has now been restored for the majority of users. We will continue to monitor the platform closely to ensure full recovery and stability.

The login issue affecting the platform has been resolved, and users can now sign in normally. The disruption lasted from 04:52 AM PT to 9:42 AM PT. No customer data was affected. Users who were already logged in to Mindtickle were able to access the platform without any concerns. We're sorry for the disruption this caused. If you're still unable to log in, please contact us @ [email protected]. We'll complete an internal postmortem and publish the RCA here within the next few days.

We are aware of an issue affecting Salesforce-related workflows, caused by an ongoing outage on Salesforce's side. This is not the result of an issue within Mindtickle. What's affected: Customers using the Salesforce integration may see failures or delays in the following: 1. Salesforce Integration (SFDC): CRM data sync, user provisioning/sync, module/assets recommendations, and learner performance sync to Salesforce 2. Digital Sales Room: syncing opportunities, contacts, automatic room creation for Salesforce opportunities, and accounts from Salesforce, and writing room activity back to Salesforce. Core DSR functionality (creating and sharing rooms, content, analytics) remains available. 3. Call AI: mapping recordings to Salesforce records and showing Salesforce opportunity/account fields on a meeting once it's available, pushing call insights back to Salesforce, and Salesforce Dialer call capture. Core Call AI functionality (recording, transcription, insights) remains available. What's not affected: Non-Salesforce workflows, core product functionality, and customers not using the Salesforce integration are all operating normally. We are actively monitoring the Salesforce outage and assessing impact.

The Salesforce-side outage has been resolved, and all affected workflows are now operating normally.

Seller Copilot is experiencing high error rates due to a downstream outage in the Azure data center supporting this use case. Also, Mindtickle chat support may experience failures in generating responses to your queries.

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

a fix has been implemented and we are monitoring the situation.

The incident has been resolved, and all systems are now operational.

We're investigating an issue where a subset of customers may see stale data in certain analytics reports, specifically: SSR, Custom Dashboards, Manager & Relationship reports, and Overview / Adoption / Performance reports. Other reports and product areas are unaffected. If your analytics reflect current data, no action is needed. We'll post an update shortly.

This issue is resolved. All affected reports are now showing current data. Thank you for your patience.

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.

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.

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

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.

# **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.

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.

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.

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.

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.

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.

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

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.

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.

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

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

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

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.

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.

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.

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.

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.

We are continuing to investigate this issue.

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.

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.

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

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

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

[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.

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.

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.

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

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

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

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.

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

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

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.

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

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

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

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

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.

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

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

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

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