- Detected by Pingoru
- Jun 03, 2026, 05:06 PM UTC
- Resolved
- Jun 02, 2026, 02:19 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 03, 2026, 05:06 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 03:29 PM UTC
- Resolved
- May 21, 2026, 06:30 PM UTC
- Duration
- 3h
Affected: Mission
Timeline · 6 updates
-
investigating May 21, 2026, 03:29 PM UTC
Users may experience issues starting Two-Way Roleplay sessions. In addition, completed roleplays may not be accessible, and admins may be unable to create new roleplays. The team is actively investigating the issue and working toward resolution.
-
identified May 21, 2026, 03:59 PM UTC
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.
-
identified May 21, 2026, 05:07 PM UTC
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.
-
identified May 21, 2026, 05:18 PM UTC
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.
-
monitoring May 21, 2026, 05:49 PM UTC
The impacted systems are now operational again, and roleplay workflows are functioning successfully. We are continuing to monitor the systems closely to ensure stability.
-
resolved May 21, 2026, 06:30 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 01:17 PM UTC
- Resolved
- May 18, 2026, 01:55 PM UTC
- Duration
- 38m
Affected: Mindtickle PlatformAsset Hub
Timeline · 4 updates
-
investigating May 18, 2026, 01:17 PM UTC
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.
-
identified May 18, 2026, 01:21 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring May 18, 2026, 01:31 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 18, 2026, 01:55 PM UTC
This incident has been resolved. The 'Featured Hubs' widget is now loading as expected, and the Mindtickle platform is fully operational.
Read the full incident report →
- Detected by Pingoru
- May 11, 2026, 02:25 PM UTC
- Resolved
- May 11, 2026, 04:35 PM UTC
- Duration
- 2h 10m
Affected: Call AI
Timeline · 2 updates
-
investigating May 11, 2026, 02:25 PM UTC
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.
-
resolved May 11, 2026, 04:35 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 11:50 AM UTC
- Resolved
- Mar 24, 2026, 03:00 PM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 02:33 PM UTC
- Resolved
- Feb 19, 2026, 02:52 PM UTC
- Duration
- 18m
Affected: In-Platform Analytics
Timeline · 3 updates
-
investigating Feb 19, 2026, 02:33 PM UTC
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.
-
investigating Feb 19, 2026, 02:50 PM UTC
We are continuing to investigate this issue.
-
resolved Feb 19, 2026, 02:52 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Feb 12, 2026, 03:28 AM UTC
- Resolved
- Feb 12, 2026, 03:37 AM UTC
- Duration
- 8m
Affected: Course / Quick-Update / AssessmentMissionIn-Platform AnalyticsLoginMindtickle PlatformAdmin SiteContent CenterMindtickle CopilotCoaching SessionsInstructor-Led TrainingReporting APIUser SyncLearning SiteAsset HubMobile AppSpaced ReinforcementRule AutomationCall AIDigital Sales Rooms (DSR)Notifications
Timeline · 4 updates
-
investigating Feb 12, 2026, 03:29 AM UTC
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.
-
identified Feb 12, 2026, 03:29 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Feb 12, 2026, 03:36 AM UTC
We have implemented a fix and are monitoring the progress. We are seeing the error rates coming down.
-
resolved Feb 12, 2026, 03:37 AM UTC
The incident has been resolved. All admins and end users should be able to access the platform without any concerns.
Read the full incident report →
- Detected by Pingoru
- Feb 06, 2026, 01:23 PM UTC
- Resolved
- Feb 06, 2026, 07:15 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 06, 2026, 01:23 PM UTC
[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.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 02:45 PM UTC
- Resolved
- Nov 18, 2025, 05:17 PM UTC
- Duration
- 2h 31m
Affected: Mission
Timeline · 4 updates
-
identified Nov 18, 2025, 02:45 PM UTC
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.
-
monitoring Nov 18, 2025, 02:54 PM UTC
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.
-
monitoring Nov 18, 2025, 03:37 PM UTC
Two-Way Roleplay Missions are operational. We will continue to monitor the platform closely to ensure stability before marking this incident as fully resolved.
-
resolved Nov 18, 2025, 05:17 PM UTC
All services are normal. A detailed Root Cause Analysis (RCA) will be published shortly.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 04:30 PM UTC
- Resolved
- Oct 20, 2025, 08:55 PM UTC
- Duration
- 4h 25m
Affected: Mindtickle Platform
Timeline · 4 updates
-
identified Oct 20, 2025, 04:30 PM UTC
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
-
identified Oct 20, 2025, 05:51 PM UTC
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.
-
monitoring Oct 20, 2025, 07:43 PM UTC
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
-
resolved Oct 20, 2025, 08:55 PM UTC
The incident has been resolved, and the Mindtickle platform is now operating normally. We continue to closely monitor performance to ensure everything remains stable.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 10:07 AM UTC
- Resolved
- Oct 20, 2025, 11:03 AM UTC
- Duration
- 55m
Timeline · 2 updates
-
monitoring Oct 20, 2025, 10:07 AM UTC
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.
-
resolved Oct 20, 2025, 11:03 AM UTC
The incident has been resolved, and the Mindtickle platform is operating normally.
Read the full incident report →
- Detected by Pingoru
- Oct 16, 2025, 03:54 AM UTC
- Resolved
- Oct 16, 2025, 04:50 AM UTC
- Duration
- 55m
Affected: In-Platform AnalyticsReporting API
Timeline · 3 updates
-
investigating Oct 16, 2025, 03:54 AM UTC
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
-
monitoring Oct 16, 2025, 04:29 AM UTC
A fix has been implemented and we are running a sanity check at our end.
-
resolved Oct 16, 2025, 04:50 AM UTC
This incident has been resolved. We will share an RCA once the postmortem is complete.
Read the full incident report →
- Detected by Pingoru
- Oct 15, 2025, 11:19 AM UTC
- Resolved
- Oct 14, 2025, 07:10 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 15, 2025, 11:19 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Sep 24, 2025, 09:01 AM UTC
- Resolved
- Sep 24, 2025, 10:09 AM UTC
- Duration
- 1h 8m
Affected: In-Platform Analytics
Timeline · 4 updates
-
investigating Sep 24, 2025, 09:01 AM UTC
We're currently experiencing an high error rate in our in-platform analytics and are actively investigating the root cause to restore full functionality.
-
identified Sep 24, 2025, 09:40 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Sep 24, 2025, 09:51 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 24, 2025, 10:09 AM UTC
A fix has been applied, and the incident has been resolved. We are continuing to monitor this closely.
Read the full incident report →
- Detected by Pingoru
- Sep 20, 2025, 10:29 AM UTC
- Resolved
- Sep 20, 2025, 06:40 AM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →
Notice September 12, 2025 - Detected by Pingoru
- Sep 12, 2025, 02:42 PM UTC
- Resolved
- Sep 12, 2025, 02:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 12, 2025, 02:42 PM UTC
Mindtickle was not impacted by the Salesloft Drift data breach, and no customer data was compromised. Mindtickle does not use or integrate with the Drift platform or any other Salesloft products. Our systems, including those that integrate with Salesforce, have not been compromised or pose a similar risk to the Salesloft Drift incident. We are proactively reviewing our third-party vendors and sub-processors. To date, we have not received any notification of incidents or data breaches from any of these third parties. We'll continue to actively monitor for any potential impact and provide updates as appropriate. For questions regarding this update, please contact [email protected].
Read the full incident report →
- Detected by Pingoru
- Sep 03, 2025, 04:58 AM UTC
- Resolved
- Aug 29, 2025, 07:49 PM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2025, 09:12 AM UTC
- Resolved
- Jun 05, 2025, 08:36 AM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2025, 04:39 PM UTC
- Resolved
- May 24, 2025, 05:30 PM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- May 22, 2025, 06:10 AM UTC
- Resolved
- May 22, 2025, 06:44 AM UTC
- Duration
- 34m
Affected: Course / Quick-Update / AssessmentMissionIn-Platform AnalyticsLoginMindtickle PlatformAdmin SiteContent CenterMindtickle CopilotCoaching SessionsInstructor-Led TrainingReporting APIUser SyncLearning SiteAsset HubMobile AppSpaced ReinforcementRule AutomationCall AIDigital Sales Rooms (DSR)Notifications
Timeline · 3 updates
-
investigating May 22, 2025, 06:10 AM UTC
Our team is actively investigating the issue and working to restore full access as quickly as possible.
-
identified May 22, 2025, 06:34 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved May 22, 2025, 06:44 AM UTC
This incident has been resolved, we will publish a detail root cause analysis soon.
Read the full incident report →
- Detected by Pingoru
- May 06, 2025, 01:51 AM UTC
- Resolved
- May 05, 2025, 08:00 PM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Mar 07, 2025, 06:38 PM UTC
- Resolved
- Mar 06, 2025, 05:26 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 07, 2025, 06:38 PM UTC
Between March 05, 21:26 PT, and March 06, 20:17 PT, we encountered an issue that prevented Zoom call recordings due to an unexpected change in Zoom permissions affecting the Mindtickle integration. We have fully resolved the issue, and your Zoom calls are now being recorded as expected. We sincerely apologize for any disruption this may have caused and are implementing additional safeguards to prevent similar occurrences in the future. A detailed root cause analysis (RCA) will be shared on this status page next week.
Read the full incident report →
Critical January 21, 2025 - Detected by Pingoru
- Jan 21, 2025, 06:44 AM UTC
- Resolved
- Jan 21, 2025, 06:58 AM UTC
- Duration
- 13m
Affected: Course / Quick-Update / AssessmentMissionIn-Platform AnalyticsLoginMindtickle PlatformAdmin SiteContent CenterMindtickle CopilotCoaching SessionsInstructor-Led TrainingReporting APIUser SyncLearning SiteAsset HubMobile AppSpaced ReinforcementRule AutomationCall AIDigital Sales Rooms (DSR)Notifications
Timeline · 2 updates
-
investigating Jan 21, 2025, 06:44 AM UTC
We are currently investigating this issue.
-
resolved Jan 21, 2025, 06:58 AM UTC
Mindtickle platform is up and running. A root cause analysis will be published shortly.
Read the full incident report →
- Detected by Pingoru
- Jan 10, 2025, 07:47 AM UTC
- Resolved
- Jan 10, 2025, 09:41 AM UTC
- Duration
- 1h 53m
Affected: MissionMindtickle CopilotCall AI
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Jan 02, 2025, 04:50 PM UTC
- Resolved
- Jan 02, 2025, 04:50 PM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →