KnowBe4 Outage History

On Tuesday, January 27, 2026, from approximately 14:46 \(UTC\) to 16:22 \(UTC\), some users experienced issues with loading the **Library** tab of the Learner Experience \(LX\). This incident was caused when an update to the **Library** tab contained a code change that conflicted with another recent update. The conflicting code changes unexpectedly caused an error on the LX that was not detected by our automated testing and monitoring until both updates were deployed to the production environment. To resolve this issue, we rolled back the updates, and the LX returned to normal performance by 16:22 \(UTC\). To prevent this type of issue in the future, we updated the code to prevent the error when the update is redeployed. We also improved the testing and monitoring protocols. No data loss occurred as a result of this issue.

On Monday, December 22, 2025, from approximately 16:12 to 16:50 \(UTC\), some customers experienced errors when attempting to log in and log out across the KSAT console. This issue was caused by a cryptography library update required for a new feature. To resolve this issue, we reverted the update, and the KSAT console returned to normal performance by 16:50 \(UTC\). To prevent this type of issue in the future, we have updated our deployment workflows to require sanitation tests before new deployments are sent. No data loss occurred as a result of this issue.

On December 2, 2025, from approximately 16:30 to 17:00 \(UTC\), some customers experienced issues with using login links in training notifications. This issue was caused by a code deployment for the KSAT login page, which generated incorrect login URLs. To resolve this issue, we reverted the deployment, and the KSAT console returned to normal performance by 17:00 \(UTC\). To prevent this type of issue in the future, we have improved our workflow for similar code deployments to include additional monitoring and testing. No data loss occurred as a result of this issue.

On Tuesday, December 2, 2025, from approximately 16:12 to 18:35 \(UTC\), some US users experienced issues when signing in to the Prevent, Defend, Protect, Secure Web Form, and Workspace products. This incident was caused by the recent deployment of a new monitoring agent. The agent consumed more resources than expected, leading to periodic resource strain and service instability. To resolve this issue, we optimized the agent's resource usage and increased the total system capacity, and the affected products returned to normal performance by 18:35 \(UTC\). To prevent this type of issue in the future, we are maintaining the increased system capacity for current and future projects. No data loss occurred as a result of this issue.

On November 21, 2025, we deployed a configuration change to KSAT messaging. This deployment caused users to experience intermittent HTTP 500 errors from approximately 10:22 to 15:37 \(UTC\), and prevented users from logging in or interacting with the EU instance of the KSAT console. To resolve this issue, we rolled back the configuration change, and the KSAT console returned to normal performance by 15:37 \(UTC\). No data loss occurred as a result of this issue.

On Monday, November 3, from approximately 2:54 p.m. \(UTC\) until Tuesday, November 4, 2025, at 10:04 a.m. \(UTC\), some users were unable to deploy any instances of Defend or Prevent via the deployment center. This incident was caused by an intermittent failure when communicating with Microsoft systems while attempting to provision new groups within customer tenants as part of the product deployment process. To resolve this issue, we changed the group creation process to use Graph API rather than Exchange PowerShell, which allowed the groups to be successfully created within customer tenants. All affected deployments were subsequently retried by customers and completed successfully. To prevent this type of issue in the future, we have implemented additional monitoring for the deployment process. No data loss occurred as a result of this issue.

On Wednesday, September 29, 2025, from approximately 16:39 until Friday, October 7, 2025, at 13:13 \(UTC\), some users experienced delays with their phishing campaigns. This issue was caused by high processing volume that created a backlog in the system responsible for scheduling phishing campaign recipients, resulting in campaigns being delayed rather than being sent at their scheduled times. To resolve this issue, we increased the processing capacity of the affected system and cleared the backlog. Phishing campaigns were able to return to normal performance by 13:13 \(UTC\) on October 7, 2025. To prevent this type of issue in the future, we improved how we monitor and allow the KSAT console to concurrently process phishing campaigns. We also improved the monitoring and processing controls to better manage high-volume periods. No data loss occurred as a result of this issue.