Kallidus Outage History

Started Oct 19, 2026, 08:43 AM UTC· resolved Oct 19, 2026, 11:21 AM UTC

1. in progress Oct 19, 2026, 08:43 AM UTC

   We are sorry for the disruption some of our customers are experiencing with Reviews on Kallidus Perform. We understand the impact this may be having and want to assure you that resolving this is our top priority. Our engineers have identified the cause, and are preparing a fix that we expect to have in place as soon as possible. We appreciate your patience and understanding.

2. resolved Oct 19, 2026, 11:21 AM UTC

   We're sorry for the disruption you may have experienced with Reviews in Kallidus Perform. We have now deployed a fix, and this should be working as expected again. Thank you for your patience while we worked on this.

Read the full incident report →

Started Aug 25, 2026, 01:53 PM UTC· resolved Aug 26, 2026, 01:09 PM UTC

1. postmortem Aug 26, 2026, 01:09 PM UTC

   Service disruption: Learn access issue — 25 August 2026 Summary: Between approximately 12:00 and 17:00 on 25 August 2026, a subset of customers were unable to use Learn after logging in — users authenticated successfully but were then stuck on a loading screen. Other parts of the Kallidus platform, including Learn admin, Manager users, Reports and Perform, were unaffected. Status: Resolved. Service was restored at 17:00, and affected users have been able to log in and use Learn normally since. Cause: A configuration change made at approximately 12:00 increased the size of the authentication data issued at login. For a subset of customers, this pushed that data over a size limit enforced by the browser, causing it to be silently discarded — which left affected users stuck in a login loop with no visible error. Remediation: We identified and reverted the change, and are implementing additional safeguards to detect this class of issue before it reaches customers in future. We apologise for the disruption this caused.

Read the full incident report →

Started Jul 30, 2026, 08:35 AM UTC· resolved Jul 31, 2026, 12:45 PM UTC

1. postmortem Jul 31, 2026, 12:45 PM UTC

   Summary Between 08:00 and 09:46 BST on 30 July 2026, HR customers using the Absence Management functionality were unable to access their Kallidus HR system. Customers not using Absence Management were unaffected. Root Cause During a scheduled maintenance window, Kallidus' cloud hosting provider performed maintenance on infrastructure supporting the Kallidus HR Absence Management databases. The maintenance activity exceeded its planned duration, resulting in the databases remaining unavailable beyond the scheduled maintenance window. Kallidus has escalated the incident with its cloud hosting provider and requested a detailed review of the maintenance overrun. This RCA will be updated should additional information become available. We apologise for the disruption caused and thank our customers for their patience while the issue was resolved.

Read the full incident report →

Started Jul 07, 2026, 07:50 AM UTC· resolved Jul 07, 2026, 09:25 AM UTC

1. resolved Jul 07, 2026, 09:25 AM UTC

   We are pleased to confirm that the underlying issue affecting scheduled reporting updates has now been resolved. Our engineers are now processing data loads to update manager dashboards and reporting data. Please note that as the system catches up, it may take a few hours for reporting and manager dashboards to reflect fully up-to-date data. For customers using Business Objects, those reports will be refreshed overnight and should be up to date by tomorrow morning. We appreciate your patience and understanding while we resolved this, and apologise for any inconvenience caused in the meantime.

Read the full incident report →

Started Jun 29, 2026, 02:00 PM UTC· resolved Oct 24, 2026, 12:38 AM UTC

1. investigating Jun 29, 2026, 02:00 PM UTC

   We will be performing scheduled maintenance beginning 2:00 PM BST and we expect service to resume by 5:00 PM BST on Monday 29-06-2025. During this time, dashboards and reports may not reflect the latest data, however existing reports will remain accessible.

Read the full incident report →

Started Jun 16, 2026, 08:50 AM UTC· resolved Jun 16, 2026, 11:31 AM UTC

1. resolved Jun 16, 2026, 11:31 AM UTC

   We are pleased to confirm that the issue affecting lesson and event imports on Kallidus Learn has now been resolved.

Read the full incident report →

Started Jun 15, 2026, 01:39 PM UTC· resolved Jun 22, 2026, 02:59 PM UTC

1. resolved Jun 22, 2026, 02:59 PM UTC

   Following thorough investigation, Microsoft have confirmed that this issue originated within Microsoft's own infrastructure and also impacted other Microsoft customers. Unfortunately, Microsoft have been unable to restore the missing report layout information - the report visualisations and filters were stored within the report artifact and are no longer recoverable. We recognise this is a frustrating outcome, particularly given that the root cause lay outside of Kallidus's control. Thank you for your patience while we worked to reach a resolution. Please reach out to our support if you require further details or assistance.

Read the full incident report →

Started Jun 11, 2026, 09:18 AM UTC· resolved Jun 12, 2026, 09:48 AM UTC

1. postmortem Jun 12, 2026, 09:48 AM UTC

   From 15:30 BST on 10/06/2025 until 11:20 BST on 11/06/2025, Learn mistakenly sent course deadline reminder emails to managers and tutors outside of their configured notification schedules. Emails could have been received after this time as they worked their way through email servers to reach their recipients. In some cases, managers and tutors received emails even where their own notification schedules had been disabled. The content of all emails was accurate, relating to genuine unmet course deadlines, however the recipient logic did not reflect individual customer configuration. The issue was caused by a deployment on the afternoon of 10/06/2025, which included changes to improve the performance of course deadline reminders and to extend refresher training (lesson set) logic to manager and tutor emails. During this deployment, manager and tutor email jobs were incorrectly configured to reference the end-user notification schedule rather than their own dedicated schedules. Email notifications were suspended on the morning of 11/06/2025 whilst the issue was investigated, however the main batch of morning reminder emails had already been processed before this action was taken. Once the root cause was confirmed, the changes were rolled back in full and email notifications were re-enabled. Although we know the precise cause of this issue, the deadline reminder changes will be reviewed and tested thoroughly before being redeployed. We apologise for any disruption caused and thank you for your patience while we worked to resolve this.

Read the full incident report →

Started May 28, 2026, 10:28 AM UTC· resolved May 29, 2026, 02:20 PM UTC

1. postmortem May 29, 2026, 02:20 PM UTC

   From 11:33 BST on 27/05 until 09:30 BST on 29/05, Learn administrators were unable to replace content using the course import process. Uploading new content continued to operate normally; only content replacement was affected. The issue was caused by missing permissions within an Azure storage container following the decommissioning of an older container on 27/05. During the investigation, a recent deployment was initially rolled back as a precautionary measure, however this did not resolve the issue as the root cause was related to storage permissions rather than a code change. Once the missing permissions were identified, they were restored and content replacement functionality was confirmed as operational. Although this was an isolated incident and is unlikely to recur, we have taken additional preventative action by introducing automated testing specifically for this scenario to complement the upload tests already in place.

Read the full incident report →

Started May 11, 2026, 11:31 AM UTC· resolved May 11, 2026, 03:07 PM UTC

1. resolved May 11, 2026, 03:07 PM UTC

   Our engineers have resolved the issue and you should now be able to edit and save job ads.

Read the full incident report →

Started Mar 23, 2026, 08:57 AM UTC· resolved Mar 24, 2026, 06:17 AM UTC

1. resolved Mar 24, 2026, 06:17 AM UTC

   All Power BI dataset refreshes have been successfully completed. We apologise for any impact this may have caused while data was being brought back up to date. If you continue to experience any issues, please let us know.

Read the full incident report →

Started Mar 13, 2026, 10:00 AM UTC· resolved Mar 13, 2026, 05:11 PM UTC

1. resolved Mar 13, 2026, 05:11 PM UTC

   The fix for this has now been successfully deployed, all customers will now begin see their data returning. We apologise again for any inconvenience caused.

Read the full incident report →

Started Feb 24, 2026, 03:23 PM UTC· resolved Feb 24, 2026, 05:46 PM UTC

1. resolved Feb 24, 2026, 05:46 PM UTC

   The issue affecting outbound emails has now been resolved, and email notifications are up and running again. We will be resending any emails that were delayed or blocked earlier today to ensure users receive the necessary communications. Thank you for your patience while we worked to resolve this.

Read the full incident report →

Started Jan 02, 2026, 09:03 AM UTC· resolved Jan 02, 2026, 04:00 PM UTC

1. postmortem Jan 02, 2026, 04:00 PM UTC

   Summary: Between 08:49 and 09:35 GMT on 02/01/2026, UK customers may have encountered errors accessing Kallidus products. Root cause: A critical SSL certificate expired. Kallidus engineers discovered that an automation, responsible for the renewal of SSL certificates, was failing on one of two devices configured to perform the task. Stopping the problem device resolved the issue. Kallidus engineers will be making a number of enhancements to the certificate renewal process in a bid to prevent such an issue from occurring in future. We apologise for any inconvenience caused by this disruption and thank you for your patience while the issue was resolved.

Read the full incident report →

Started Dec 30, 2025, 12:16 PM UTC· resolved Dec 30, 2025, 02:20 PM UTC

1. resolved Dec 30, 2025, 02:20 PM UTC

   Most customers have now reported that they are able to access services as normal. Our investigation did not identify any issues within our platform. The impact appears to be related to an upstream infrastructure issue, and we will continue to monitor in case of any further disruption. We apologise for any inconvenience caused and thank customers for their patience.

Read the full incident report →

Started Dec 19, 2025, 10:43 AM UTC· resolved Dec 19, 2025, 11:50 AM UTC

1. resolved Dec 19, 2025, 11:50 AM UTC

   Following additional testing, we believe the issue has been resolved. Users should now be able to log in normally. We will continue to monitor the situation. We apologise for any inconvenience that this may have caused.

Read the full incident report →

Started Dec 09, 2025, 04:43 PM UTC· resolved Dec 11, 2025, 02:35 PM UTC

1. postmortem Dec 11, 2025, 02:35 PM UTC

   On 09 December 2025, between 16:44 and 16:58 GMT, some Learn customers may have experienced errors when trying to access the product. Root Cause: Our team identified that one of our database servers stopped responding. As soon as this occurred, our monitoring systems alerted us, enabling our engineers to quickly investigate and restart the affected server. We resolved this promptly, and services returned to normal. We sincerely apologise for any inconvenience this may have caused and appreciate your patience while we worked to restore full functionality.

Read the full incident report →

Started Nov 18, 2025, 12:12 PM UTC· resolved Nov 18, 2025, 03:48 PM UTC

1. resolved Nov 18, 2025, 03:48 PM UTC

   All customers should now have full access. We are keeping the workaround in place overnight as a precaution and will review the situation tomorrow. Thank you for your patience.

Read the full incident report →

Started Oct 30, 2025, 07:00 AM UTC· resolved Oct 30, 2025, 08:30 AM UTC

1. resolved Oct 30, 2025, 08:30 AM UTC

   Server maintenance has now been completed.

Read the full incident report →

Started Oct 23, 2025, 08:27 AM UTC· resolved Oct 30, 2025, 01:37 PM UTC

1. postmortem Oct 30, 2025, 01:37 PM UTC

   Between 09:17 and 20:30 GMT on 23-10-2025 our Talent and 360 applications experienced a period of downtime while we investigated and addressed a newly discovered security vulnerability. Root Cause: We identified an exploitable vulnerability in one of our application components. A thorough investigation indicated that no customer data was accessed, exposed or compromised via this method. Upon discovery we immediately took the system offline to prevent any potential further risk and subsequently conducted a full investigation to identify the root issue and to confirm no data exposure. A permanent security patch was applied to the application code to close the vulnerability. Talent and 360 service was safely restored once we confirmed system integrity and security. As a precaution, we are enhancing internal security scanning and code review processes and expanding our automated vulnerability detection and response capabilities. Thank you for your patience while we resolved this issue.

Read the full incident report →

Started Oct 14, 2025, 08:17 AM UTC· resolved Oct 14, 2025, 09:32 AM UTC

1. resolved Oct 14, 2025, 09:32 AM UTC

   Our engineers have now implemented a fix for this and email addresses are displayed. Apologies again for the inconvenience this caused this morning.

Read the full incident report →