KnowBe4 had 62 outages in the last 2 years totaling 389h 15m of downtime — averaging 2.5 incidents per month.
There were 62 KnowBe4 outages since June 24, 2025 totaling 389h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.
We've identified an issue that has resulted in inconsistent reporting, and our engineering team is looking into a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
This incident has been resolved.
We have received reports of 500 errors occurring when navigating to user profiles. We are investigating this issue and will update this page when we have more information.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue preventing customers from uploading custom content to the new Modstore
We have identified an issue with uploading custom content to the new Modstore and implemented a fix. Customers should be able to upload custom content successfully.
We have received reports that there is a Intermittent issue sending emails for Protect. We are investigating this issue and will update this page when we have more information.
We’ve implemented a fix and we’re monitoring the results to make sure no further issues occur.
This incident has been resolved.
We've received reports that customers are unable to access the new Modstore experience and are receiving 500 errors. We are investigating these issues and will update this page when we have more information.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are seeing errors when using the Microsoft Ribbon Phish Alert Button (PAB) to report emails in Classic Outlook. Our team is aware and investigating these errors.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our team has identified an issue causing latency with the KSAT console. A fix has been implemented and we will continue to monitor.
Our team has identified and resolved the issue causing latency with the KSAT console
We are investigating access issues with the KnowBe4 Academy. We will update this page when we have more information.
Access to the KnowBe4 Academy has been restored. We are monitoring to ensure there are no further issues.
This incident has been resolved.
On Wednesday, May 13, 2026, from approximately 18:00 until 18:45 \(UTC\), some users experienced issues with accessing the KnowBe4 Academy. This incident was caused by a service disruption with an external service provider. The provider restored service and the Academy returned to normal performance by 18:45 \(UTC\). No data loss occurred as a result of this issue.
Users will not be able to upload items to US Workspaces, however, downloading is still available. Any Webforms which utilize Workspace will not be able to save items.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
On Tuesday, May 12, 2026, from approximately 10:12 until 11:43 \(UTC\), some US customers experienced issues while attempting to upload files or process data within the Workspace console. This incident was caused by a networking disruption that affected a backend messaging service, preventing it from properly syncing data. While file downloads remained available, new file uploads and certain background tasks were blocked. To resolve this issue, we temporarily paused new network traffic and restored the messaging service. The Workspace console returned to normal performance by 11:43 \(UTC\). To prevent this type of issue in the future, we are reviewing our messaging service configuration and improving network monitoring to more quickly identify synchronization issues. No data loss occurred as a result of this issue.
We are investigating an issue impacting the ability to login to PhishER in the US instance.
This incident has been resolved.
On Friday, May 8, 2026, from approximately 01:45 to 03:08 \(UTC\), some US customers experienced issues accessing the PhishER console and PasswordIQ. This incident was caused by a localized infrastructure failure at our cloud service provider, which affected authentication traffic and prevented login verifications. To resolve this issue, we reprovisioned our authentication resources to healthy environments. After we rerouted login traffic to the healthy environments, PhishER and PasswordIQ returned to regular performance by 03:08 \(UTC\). No data loss occurred as a result of this issue.
We have identified an issue with customers signing into PhishER in the UK instance.
We have identified an issue with customers signing into PhishER in the UK instance and implemented a fix which we will continue to monitor. Customers should be able to login successfully.
We have identified an issue with customers signing into PhishER in the UK instance and implemented a fix. Customers should be able to login successfully.
We have identified an issue with customers pushing ADI files to KSAT. We are actively investigating this issue and will update this page with more information when it is available.
We have identified an issue with customers pushing ADI files and training policy uploads to KSAT. We are actively investigating this issue and will update this page with more information when it is available.
We have identified an issue with customers pushing ADI files and training policy uploads to KSAT. Our team has implemented a fix and this has now been resolved.
We are investigating an issue affecting the ability to login to the PhishER platform. Our team is working on this issue and we will update this page when we have more information.
This incident has been resolved.
We are investigating reports of latency when viewing or sending emails via Web Access
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.
We've identified the issue that was resulting in a Restricted error when attempting to access the PhishER console for UK and CA customers and have implemented a fix. Impacted users may need to refresh the page to access the PhishER console.
We've identified an issue that is resulting in a Restricted error when attempting to access the PhishER console for UK and CA customers, and we are working on implementing a resolution.
We've identified an issue that resulted in a Restricted error when attempting to access the PhishER console for UK and CA customers. Our team has implemented a fix and this has now been resolved.
We've identified some users are receiving multiple abuse mailbox submissions. We've identified a fix which should resolve the issue.
We've implemented a fix and are continuing to monitor to ensure this is resolved
This incident has been resolved.
On Tuesday, March 31, 2026, from approximately 15:00 \(UTC\) to 16:10 \(UTC\), some users experienced issues with the Defend Abuse Mailbox service. This incident was caused by a service update that started sending duplicate phishing submission notifications to users. To resolve this issue, we corrected the service update code that caused the duplicate notifications, and the Defend Abuse Mailbox service returned to normal performance by 16:10 \(UTC\). To prevent this type of issue in the future, we are reviewing and improving our service upgrade workflow. No data loss occurred as a result of this issue.
We have received reports that access to the KnowBe4 Administration Panel is slow or inaccessible. We are investigating this issue and will update this page when we have more information.
We’ve implemented a fix and we’re monitoring the results to make sure no further issues occur.
This incident has been resolved.
On Thursday, March 19, 2026, from approximately 11:56 \(UTC\) until 13:14 \(UTC\), some UK users experienced intermittent issues while attempting to log in to Prevent and Protect consoles. This incident was caused by a configuration timeout in our session management system. To resolve this issue, we increased the timeout limit, and the Prevent and Protect consoles returned to normal performance by 13:14 \(UTC\). To prevent this type of issue in the future, we have improved our timeout monitoring process and are verifying configuration consistency and optimization across our environments. No data loss occurred as a result of this issue.
We are currently experiencing an issue with Webforms not loading and are currently investigating.
A fix has been implemented and we are monitoring the results.
During a scheduled registrar migration of internal and test domains, a production domain was inadvertently included and not caught in the pre-checks. The initial migration action included updates to the configured Name Servers which resulted in potential service interruptions from 16:00 GMT on March 17 until confirmed full restoration post-propagation at 13:00 GMT on March 18. We have isolated the process issue and remediated. A review of DNS monitoring options is underway to identify opportunities for faster detection.
From Tuesday, March 17, 2026, at approximately 16:00 \(UTC\), to Wednesday, March 18, 2026, at approximately 13:00 \(UTC\), some users experienced errors while submitting Workspace webforms. This incident was caused by a configuration error during a domain migration. To resolve this issue, we corrected the domain configuration, and webform submissions returned to normal performance by 13:00 \(UTC\) on March 18, 2026. To prevent this type of issue in the future, we are reviewing and updating our domain migration process. No data loss occurred as a result of this issue.
Our development team has identified an issue causing ingested messages in PhishER to display the incorrect sender address.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
On Tuesday, March 10, 2026, from approximately 15:22 until 20:35 \(UTC\), the EU and US instances of the PhishER console displayed an incorrect subject line for some messages reported with the Phish Alert Button \(PAB\). This incident was caused by a configuration change to the PhishER message ingester service, which unexpectedly affected messages that were reported with some PAB versions. Once we reverted the change and updated the ingester service, PhishER was able to return to normal performance by 20:35 \(UTC\). To prevent this type of issue in the future, we reviewed the ingester service processes and implemented additional testing for messages reported with the PAB. No data loss occurred as a result of this issue.
We've identified the cause of the certificate error when navigating to the Defend and Prevent admin consoles and are working on implementing a fix. We'll continue to post on our status page with any new information or updates.
We’ve implemented a fix for the certificate issue for Defend and Prevent admin consoles. A new certificate has been deployed and most traffic is restored while propagation completes across our global edge network.
This incident has been resolved.
On Thursday, March 5, 2026, from approximately 02:20 until 03:10 \(UTC\), some customers experienced expired SSL certificate warnings when accessing their Defend and Prevent admin consoles. This incident was caused by an expired certificate for an internal service. To resolve this issue, we deployed a new certificate and updated all affected instances. The Defend and Prevent consoles returned to normal performance by 03:10 \(UTC\). To prevent this type of issue in the future, we are improving our certificate monitoring. No data loss occurred as a result of this issue.
We are currently investigating an issue with PhishER integration delays in our EU instance.
A fix has been implemented and we are monitoring the results.
A fix was identified and applied and we are continuing to monitor for any further issues.
This incident has been resolved.
On Tuesday, February 10, 2026, from approximately 13:57 to 16:01 \(UTC\), some users experienced delays with the integration service on the EU instance of the PhishER console. This incident was caused by a system upgrade that unexpectedly affected the integration service, causing errors in the production environment. To resolve this issue, we reverted the update, and the PhishER console returned to normal performance by 16:01 \(UTC\). No data loss occurred as a result of this issue.
We are currently investigating an issue with inbound email delivery delay
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
On Wednesday, February 4, 2026, from approximately 15:30 to 16:00 \(UTC\), some US users experienced email delivery delays in the Defend product. This issue was caused by a brief networking fluctuation, resulting in email delivery delays of up to 10 minutes during the affected period. Once the cloud environment returned to healthy operating levels, Defend returned to normal performance, and all delayed emails were delivered by 16:00 \(UTC\). No data loss occurred as a result of this issue.