Is KnowBe4 down?

We've identified the cause of domain registration being unable to give advice and are working on implementing a fix. We'll continue to post on our status page with any new information or updates.

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

This incident has been resolved.

We are currently investigating an issue affecting console login. We will provide more updates here when available.

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

This incident has been resolved.

## **Summary** On October 13, 2026, from approximately 14:19 to 15:05 \(UTC\), customers in all regions were unable to log in to the KnowBe4 Security Awareness Training \(SAT\) console, the KnowBe4 Learner Experience, and the PhishER console through KnowBe4 SAT. SAML and password logins returned errors, and the KnowBe4 SAT console didn't appear in the KnowBe4 platform. Some background processes, including user synchronization and training emails, also failed during this time. The incident was caused by a production release that conflicted with another change in our code. We reverted the release, and logins recovered across regions between 14:59 and 15:05 \(UTC\). No data loss occurred as a result of this issue. ## **Root Cause** A code deployment removed a startup configuration value to speed up application startup time. A separate component, added to our code after the original change was tested, didn’t account for that changed value. As a result, every attempt to save a user record raised an error, including the update that records sign-in attempts. ## **Customer Impact** Customers across all regions couldn't log in to the KSAT console via SAML or password. They were also unable to access the Learner Experience, and couldn’t access the PhishER console through the KnowBe4 SAT console. New user creation, user synchronization, and training emails failed during this time but were automatically retried after the deployment was reverted. ## **Mitigation and Remediation** We found that the deployment removed a configuration value that another component still required. This was mitigated by reverting the release, and we confirmed recovery across all regions through direct checks and automated tests. We also reverted the original change in our source code and prepared a corrected version that includes a compatibility fix, so the original improvement can be reintroduced safely. ## **Preventative Measures** We're adding additional code verifications and testing for deployments.

We have received reports that the KnowBe4 Email Security Add-in is showing the error "The add-in KnowBe4 email security is preventing this message from being sent" when sending emails. We are investigating this issue and will update this page when we have more information.

We’ve implemented a fix for the Web Add-in sending errors and we’re monitoring the results to make sure no further issues occur.

This incident has been resolved.

From Monday, October 12, 2026, at approximately 14:25 \(UTC\), to Tuesday, October 13, 2026, at around 15:07 \(UTC\), some customers in EU instances of Prevent and Protect had difficulty sending emails from Microsoft Outlook. Affected messages weren't sent, and the KnowBe4 Email Security add-in displayed the following error: "The add-in KnowBe4 Email Security is preventing this message from being sent." This issue was caused by an error in how an add-in version was prepared for release, which produced two slightly different copies of the same version. When Outlook loads the add-in, it downloads a set of files that must match. In EU instances, Outlook sometimes received files from both copies, so the add-in couldn't finish loading, and the message wasn't sent. Some devices also saved the failed download, so the error continued on those devices until a fix was applied. To resolve this issue, our team corrected the EU add-in files so that every customer receives a matching set. We then released an updated version of the add-in to all regions, which cleared any saved errors. The KnowBe4 Email Security add-in returned to normal performance by about 15:07 \(UTC\) on October 13, 2026. To prevent this type of issue in the future, we're changing how add-in versions are prepared and released, so that each version always produces the same set of files and every customer receives the same version at the same time. We're also changing the add-in so that failed downloads of add-in files aren't saved on devices. Lastly, we're adding alerts for add-in loading errors to detect them sooner. No data loss occurred as a result of this issue.

We are currently investigating an issue regarding degraded performance for Prevent and Protect on our US servers.

We have identified an issue with the US instances of Prevent and Protect that has resulted in degraded performance. A fix has been implemented, and we will continue to monitor this issue.

This incident has been resolved.

From Monday, September 28, 2026, at approximately 20:43 \(UTC\), to Friday, October 2, 2026, at approximately 10:24 \(UTC\), some customers experienced delayed mail flow and intermittent console access issues in US instances of Prevent and Protect. This issue was caused by a capacity limit in the network firewalls in front of our US mail-processing services. During peak traffic, the firewalls could not process connections fast enough, which caused internal requests between services to be delayed or time out. As a result, mail processing slowed, and messages queued. To resolve this issue, our team increased the capacity of the US firewalls. Prevent and Protect handled peak traffic without further issue and returned to normal performance by approximately 10:24 \(UTC\) on October 2, 2026. To prevent this type of issue in the future, we have expanded our firewall monitoring to track network health indicators in addition to compute use. We have also added logging to improve visibility into failed internal requests. No data loss occurred as a result of this issue.

We have identified an issue with Protect that has resulted in degraded performance, and our engineering team is looking into a fix.

We have identified an issue with Protect that has resulted in degraded performance. A fix has been implemented, and we will continue to monitor this issue.

We have identified an issue with Protect & Prevent that has resulted in degraded performance, 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.

From Thursday, September 24, 2026, at approximately 17:07 \(UTC\), to Friday, September 25, 2026, at approximately 09:16 \(UTC\), some customers experienced intermittent slowness, errors and delayed mail flow in US instances of Protect and Prevent. This issue was caused by an unusually large spike in email traffic. The increased volume placed a sustained load on our network services, which operated within fixed capacity limits. As a result, mail processing slowed, some internal requests failed, and messages queued. Our team monitored the affected systems while the elevated volume subsided and load returned to normal. Protect and Prevent returned to normal performance by approximately 09:16 \(UTC\) on September 25, 2026. To prevent this type of issue in the future, we are improving our monitoring of unusual increases in email volume. We’re also evaluating ways to scale our network capacity more dynamically during sudden traffic spikes. No data loss occurred as a result of this issue.