Is KnowBe4 Down Right Now? Check if there is a current outage ongoing.

We are currently investigating an issue with management consoles not allowing logins.

We have received reports that some users are experiencing loading issues with their KSAT consoles when accessing the SecurityCoach and PasswordIQ tabs. We are investigating this issue and will update this page when we have more information.

On Tuesday, May 27, 2025, from approximately 1:08 p.m. to 4:25 p.m. \(UTC\), some customers experienced errors when attempting to access the Learner Experience \(LX\). These issues were caused by a third-party vendor service outage that disrupted an LX framework update. During this outage, our system defaulted to routing users to an older and unsupported framework, causing access errors. The vendor resolved their service outage by 4:25 p.m. \(UTC\), and the LX returned to normal performance shortly after. To prevent this type of issue in the future, we are updating our code to remove the dependency on the vendor service for this LX framework update and to route users to the new LX framework by default. No data loss occurred as a result of this issue.

This incident has been resolved.

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

We are currently investigating an issue with the Learner Experience dashboard not loading.

This incident has been resolved.

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

We are currently investigating an issue with the Learner Experience dashboard not loading.

On Wednesday, April 30, 2025, from approximately 7:15 p.m. to 7:36 p.m. \(UTC\), some customers experienced errors when viewing inactive training campaigns and user provisioning details. These issues were caused by an update to fix a filter bug. This filter update caused URL errors when displaying multiple results in the inactive campaigns subtab and the user provisioning details pages. To resolve this issue, we updated our code to accommodate multiple results again. Both features returned to normal performance by 7:36 p.m. \(UTC\). To prevent this type of issue in the future, we have improved our testing workflows. We also enhanced our code to improve the loading of multiple pages for user provisioning details. No data loss occurred as a result of this issue.

This incident has been resolved.

We have received reports that Pages are not loading. We are investigating this issue and will update this page when we have more information.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be performing maintenance on all instances of PasswordIQ on May 29, 2025 from 1:00 - 2:00 a.m. (UTC). During this maintenance, PasswordIQ features will be unavailable for approximately 5 minutes.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be performing maintenance on all instances of SecurityCoach on May 29, 2025 from 1:00 a.m. - 2:00 a.m. (UTC). During this maintenance, the Security Coach console will be unavailable for approximately 30 minutes.

On Wednesday, April 28, 2025, from approximately 9:08 a.m. to 8:21 p.m. \(UTC\), some customers experienced errors when accessing their Email Exposure Check Pro \(EEC Pro\) reports. These issues were caused by a third-party vendor outage that resulted in intermittent errors for EEC Pro during heavy traffic. To resolve this issue, we improved our code to reduce calls to the vendor and stabilize performance. EEC Pro returned to normal performance by April 28, 2025, at 8:21 p.m. \(UTC\). To prevent this type of issue in the future, we have also improved our code to enable EEC Pro reporting to function independently during third-party vendor outages. No data loss occurred as a result of this issue.

This incident has been resolved.

A fix for this issue has been implemented, and we are currently monitoring the results.

We have received reports that new EEC Pro reports are not accessible. We've identified the cause and are working on implementing a fix. We'll continue to post on our status page with any new information or updates.

On Monday, May 12, 2025, from approximately 3:58 p.m. to Tuesday, May 13, 2025, at 1:41 p.m. \(UTC\), some customers experienced errors when using the Microsoft Ribbon Phish Alert Button \(PAB\). These issues were caused by an update to resolve API token compatibility issues for the Microsoft Ribbon PAB and the Hybrid PAB. This update improved how tokens are handled, but it also caused Microsoft Ribbon PAB errors for certain classic Microsoft Outlook environments with legacy Microsoft Exchange tokens blocked. To resolve this issue, we updated our code to account for the blocked legacy tokens, and the Microsoft Ribbon PAB returned to normal performance by May 13, 2025, at 1:41 p.m. \(UTC\). To prevent this type of issue in the future, we have improved our testing workflow by adding more Microsoft Outlook version testing for Microsoft Ribbon PAB updates. We have also further improved our update processes to account for environmental variations specific to the Microsoft Ribbon PAB. Lastly, we have also updated the [Prerequisites](https://support.knowbe4.com/hc/en-us/articles/26106205842707-Microsoft-Ribbon-Phish-Alert-Button-PAB-Product-Manual#h_01HE87AA8X69TW8AEYT6KYXWCT) section of our [Microsoft Ribbon Phish Alert Button \(PAB\) Product Manual](https://support.knowbe4.com/hc/en-us/articles/26106205842707-Microsoft-Ribbon-Phish-Alert-Button-PAB-Product-Manual) to notify of potential compatibility issues when using classic Microsoft Outlook with the Microsoft Ribbon PAB. No data loss occurred as a result of this issue.

This incident has been resolved.

We are currently investigating this issue.

On Wednesday, April 30, 2025, from approximately 1:25 p.m. to 1:41 p.m. \(UTC\), some customers experienced an error where certain scheduled phishing campaigns would not start. These issues were caused by a legacy phishing templates update meant to support using the console’s default phishing language when localization was unavailable. This update caused an error for certain templates that were unavailable in the console’s default phishing language. Phishing campaigns using only the affected templates were also unable to start because there were no eligible templates. To resolve this issue, we reverted the update to allow the templates to send. The templates returned to normal performance by April 30, 2025, at 1:41 p.m. \(UTC\). To prevent this type of issue in the future, we are maintaining the existing functionality to send legacy templates without requiring the console’s default phishing language. No data loss occurred as a result of this issue.

This incident has been resolved.

We’ve implemented a fix, and Phishing Campaigns should run as expected. We’re monitoring the results to make sure no further issues occur.

We have received reports that some Phishing Campaigns are not starting. We are investigating this issue and will update this page when we have more information.

On Monday, March 3, 2025, from approximately 7:00 p.m. to Tuesday, March 4, 2025, at 11:40 p.m. \(UTC\), some customers experienced ADI user provisioning errors. These issues were caused by a prior update to ADI user provisioning to improve error handling. This update did not account for a certain token validation process, which caused validation errors to occur. To resolve this issue, we improved our code to accommodate the token validation and allow it to pass. The KSAT console loading times returned to normal performance by 11:40 p.m. \(UTC\). To prevent this type of issue in the future, we have improved our testing workflows and expanded our testing coverage for error handling and exceptions. No data loss occurred as a result of this issue.

This incident has been resolved.

A fix has been implemented for this issue and we are now seeing ADI tokens being accepted during the installation of the ADI Sync Tool. We will continue to monitor the status of this fix and provide updates as we have them.

We are receiving reports of ADI tokens not being recognized by the ADI Sync Tool during the installation process. We are looking into this issue and will provide an update once we have more information

On Thursday, April 17, 2025, from approximately 1:10 a.m. to 6:46 a.m. \(UTC\), some customers were unable to access their PhishER console. This issue was caused by a planned maintenance update to PhishER. During the maintenance, an unexpected configuration issue caused errors for our database clusters, and PhishER data could not be loaded. To resolve this issue, we identified the affected clusters and initiated restorative processes. All database clusters were restored to full operation by 5:10 a.m., and the PhishER console returned to normal performance by 6:46 a.m. \(UTC\). To prevent this type of issue in the future, we have added additional safeguards and testing protocols for future updates. We have also improved configuration controls for similar database updates. No data loss occurred as a result of this issue.

We have been closely monitoring PhishER in all regions after last night's maintenance, and we have not identified any lingering effects. This is resolved.

All services appear to have returned to normal. We will continue to monitor PhishER to ensure complete functionality.

Impacted regions are beginning to recover from the unanticipated downtime. The inbox is available in our US region. The inbox in other regions and other services in all regions - such as email ingestion - are beginning to recover at this time.

Progress is being made on addressing the unanticipated downtime that resulted from this planned maintenance and we are working on bringing affected regions back online one-by-one.

During our maintenance window this evening, PhishER is experiencing unanticipated downtime. The engineering team has identified the cause and is currently working to address the issue. This is affecting PhishER in all regions.

On Monday, March 3, 2025, from approximately 6:15 p.m. to Tuesday, March 4, 2025, at 9:30 p.m. \(UTC\), some customers experienced issues with downloading training modules from the ModStore. These issues were caused by an update to a third-party component used in the ModStore, which made the component incompatible with certain code. To resolve this issue, the component update was rolled back, and the KSAT console returned to normal performance by March 4, 2025, at 9:30 p.m. \(UTC\). To prevent this type of issue in the future, we have updated our code to prevent automatic updates to the third-party component and maintain a reliable component version. No data loss occurred as a result of this issue.

This incident has been resolved.

A fix has been implemented for this issue and we are now seeing training modules download successfully from the Library and Content Manager tabs within the Modstore. We will continue to monitor the status of this fix and provide updates as we have them.

We are receiving reports that training module downloads are not completing from the Modstore Library and Content Manager tabs. Our team is currently investigating this issue and we will provide updates here as we receive them.

On Wednesday, March 5, 2025, from approximately 7:45 p.m. to Friday, March 7, 2025, at 1:30 a.m. \(UTC\), some customers experienced an issue with SecurityCoach real-time coaching campaigns not sending SecurityTips. This issue was caused by a prior code update to improve real-time campaign enrollments. This update bypassed a certain callback event, which prevented real-time coaching campaigns from sending SecurityTips for detections. To resolve this issue, we improved the code to account for the callback event. The SecurityCoach console returned to normal performance by March 7, 2025, at 1:30 a.m. \(UTC\). To prevent this type of issue in the future, we have also improved our code to verify that the callback event occurs. No data loss occurred as a result of this issue.

This incident has been resolved.

We’ve implemented a fix for the Real-Time Coaching Campaign issue and we’re monitoring the results to make sure no further issues occur.

We've identified the cause of this issue and are working on implementing a fix. We'll continue to post on our status page with any new information or updates.

We have received reports that Real-Time Coaching Campaigns are not sending SecurityTips. We are investigating this issue and will update this page when we have more information.

On Wednesday, March 19, 2025, from approximately 3:18 p.m. to 4:02 p.m. \(UTC\), some customers experienced errors while using the KSAT console. This issue was caused by a prior code version update that was deployed. The new code version was incompatible with a related application, and this caused SAML login errors for some customers. To resolve this issue, we reverted the update, and the KSAT console returned to normal performance by 4:02 p.m. \(UTC\). To prevent this type of issue in the future, we have implemented additional testing workflows for similar updates, including additional testing for application compatibility. No data loss occurred as a result of this issue.

This incident has been resolved.

We have deployed a fix for these issues and will monitor for any ongoing problems.

We've received reports that some KSAT customers are unable to log in to their consoles and are receiving 500 errors. We are investigating and will update this page when we have more information.

On Wednesday, January 29, 2024, from approximately 9:37 p.m. to 10:34 p.m. \(UTC\), some customers experienced issues with loading parts of the KSAT console. These issues were caused by an update to our **Dashboard** tab. This update changed how Risk Score values were read and caused errors for areas of the console that used the Risk Score feature. To resolve this issue, we rolled back the update, and the KSAT console returned to normal performance by 10:34 p.m. \(UTC\). To prevent this type of issue in the future, we have improved our workflows to include additional manual and automated testing of different KSAT console areas before similar future updates. No data loss occurred as a result of this issue.

This incident has been resolved.

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

We have identified general loading issues in the KSAT console. We are working on implementing a fix and we'll update our status page with any new information or updates.

On Wednesday, January 29, 2025, from approximately 4:21 p.m. to 6:36 p.m. \(UTC\), some customers experienced issues creating and updating PhishRIP actions in the PhishER console. These issues were caused by an earlier update for the PhishER console. This update caused PhishRIP actions to no longer be flagged in the PhishER console, which delayed the creation of PhishRIP actions and any updates to existing actions. To resolve this issue, we updated our code to ensure actions were flagged again correctly. The PhishER console and all affected PhishRIP actions returned to normal performance by 6:36 p.m. \(UTC\). To prevent this type of issue in the future, we have updated our workflows to ensure that PhishRIP actions are flagged correctly in future updates. No data loss occurred as a result of this issue.

This incident has been resolved.

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

We have identified the cause of these issues and we are working on implementing a fix. We'll update this page with any new information or updates.

We have received reports that some customers are experiencing issues with PhishER actions that are not properly triggering PhishRIPs. We are investigating this issue and will update this page when we have more information.

On Thursday, January 30, 2025, from approximately 12:41 p.m. to 1:58 p.m. \(UTC\), some customers experienced issues with loading policies for training campaigns. These issues were caused by an update to our KSAT console framework. This update did not account for viewing PDF files and caused access errors for PDF policy training. To resolve this issue, we reverted the update and the KSAT console returned to normal performance by 1:58 p.m. \(UTC\). To prevent this type of issue in the future, we have improved our workflows to include additional verifications for features related to policies when deploying similar updates. No data loss occurred as a result of this issue.

This incident has been resolved.

We have received reports that training campaign policies are not loading. Our team has implemented a fix for this issue and we are currently monitoring the results.

On Tuesday, February 13, 2025, from approximately 2:04 p.m. to 9:08 p.m. \(UTC\), some customers experienced increased errors with using the Hybrid Phish Alert Button \(PAB\) for on-prem Exchange. These issues were caused by an update to the PAB to support Nested App Authentication Single-Sign On \(NAA-SSO\). This update introduced new checks for the PAB mode of operation and for shared mailboxes, which caused certain on-prem Exchange PAB deployments to experience errors during these checks. To resolve this issue, we updated the PAB to check for on-prem Exchange and provide an alternative login method if it is detected. The Hybrid PAB returned to normal performance by 9:08 p.m. \(UTC\). To prevent this type of issue in the future, we have improved our code to account for the new checks for on-prem Exchange. No data loss occurred as a result of this issue.

This incident has been resolved.

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

We have received reports that some customers are experiencing errors when trying to load the Hybrid Phish Alert Button in on-prem Exchange environments. We are investigating this issue and will update this page when we have more information.

On Thursday, January 16, 2025, from approximately 2:00 p.m. \(UTC\) to Friday, January 17, 2025, at 10:10 p.m. \(UTC\), some customers experienced AIDA training campaign enrollment delays for all instances of the KSAT console. These issues were caused by an update to the KSAT console that added an invalid API field, preventing simulated phishing failure events from being sent to AIDA training campaigns. To resolve this issue, we updated the invalid field to be valid and reprocessed the delayed events. The KSAT console returned to normal performance by 10:10 p.m. \(UTC\), and all queued phishing failure events were processed by January 23 at 2:05 p.m. \(UTC\). To prevent this type of issue in the future, we’ve improved our deployment workflows and verifications to account for the affected field and similar field changes. We’re also adding a new monitoring system to ensure a quick response if a similar issue occurs, and we’re improving our code to automatically retry when phishing failure events are delayed. No data loss occurred as a result of this issue.

This incident has been resolved.

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

We have discovered an issue where AIDA training campaigns are not showing all phishing failure data. We are investigating this issue and will update this page when we have more information.

This incident has been resolved.

We have identified the cause of this issue and currently investigating further. We will update this page when we have more information.

We have identified an issue where customers are unable to access Email Exposure Check Pro (EEC Pro) data from within their KSAT console, the EEC Pro tool, or the Password Exposure Test (PET) tool. We are investigating this issue and will update this page when we have more information.

On Wednesday, December 4, 2024, from approximately 6:26 p.m. to 8:45 p.m. \(UTC\), some customers experienced errors when accessing user details for EU and US instances of the KSAT console. These issues were caused by an update to the KSAT console. Certain database schema were not aligned during this update, causing user Risk Scores to return empty values and generate errors when accessing user details. To resolve these issues, we reverted the update, and the KSAT console returned to normal performance by 8:45 p.m. \(UTC\). To prevent this type of issue in the future, we are researching the use of additional testing methods when deploying similar updates. No data loss occurred as a result of this issue

This incident has been resolved.

We’ve implemented a fix for the user details errors in the KSAT console and we’re monitoring the results to make sure no further issues occur.

We have received reports that admins are experiencing errors when accessing the User Details page in the KSAT console. We are investigating this issue and will update this page when we have more information.

On Tuesday, December 17, 2024, from approximately 1:00 a.m. to 4:00 a.m. \(UTC\), some customers experienced login errors for the DE instance of the KSAT console. This issue was caused by unusually high console traffic. The extra load on the database revealed an inefficiency in processing enrollment queries, which caused longer loading times for the console. To mitigate this issue, additional resources were assigned to process the queued queries, and the console returned to normal performance by 4:00 a.m. \(UTC\). To prevent this type of issue in the future, we have upgraded our database code to increase efficiency in completing enrollment queries. No data loss occurred as a result of this issue.

This incident has been resolved.

We experienced db contention issues that affected most processes within the KSAT console. The db issues were resolved and we're now monitoring for residual issues.

On Monday, December 2, 2024, from approximately 1:15 p.m. until 3:28 p.m. \(UTC\), some users experienced issues with loading the Learner Experience \(LX\) on the US instance of the KSAT console. This incident was caused when we deployed an update to improve the LX’s efficiency in loading recommended training modules. The update gradually caused an overload on our server’s CPU due to inefficient backend processes. To resolve this issue, the update was reverted and the KSAT console returned to normal performance by 3.28 p.m. \(UTC\). To prevent this type of issue in the future, we are adding improvements to the scaling, monitoring, and alert systems for the LX before we redeploy the update. No data loss occurred as a result of this issue.

This incident has been resolved.

We’ve implemented a fix for the loading issue with the KSAT Learner Experience and we’re monitoring the results to make sure no further issues occur.

We have received reports that the KSAT Learner Experience is not loading. We are investigating this issue and will update this page when we have more information.

On Tuesday, November 19, 2024, from approximately 12:48 p.m. to 1:22 p.m. \(UTC\), some customers were unable to log into the KSAT console using SAML single sign-on \(SSO\). This issue was caused by an update that added code to validate the expiration date of SAML single sign-on \(SSO\) certificates sent during login from the user’s identity provider \(IdP\). Some IdP certificate expiration dates did not pass this validation and the user’s login was blocked as a result. To resolve this issue, we rolled back this update to allow those certificates to be used to process the SSO in the SAML authentication so that users could log in. The KSAT console returned to normal performance by 1:22 p.m. \(UTC\). To prevent this type of issue in the future, we are implementing this additional certificate validation as an optional opt-in feature in a future update. No data loss occurred as a result of this issue.

This incident has been resolved. We've removed code that validates expiration dates for customer SAML/SSO certificates, and we'll be adding that validation as an optional opt-in feature in the future.

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

We've received reports that some KSAT customers who are using SAML/SSO are unable to log in to their consoles. We are investigating and will update this page when we have more information.

From Friday, November 8, 2024, at 5:50 p.m. to Monday, November 11, 2024, at 2:08 p.m. \(UTC\), newly uploaded custom content failed to complete the automatic verification process. This issue impacted newly uploaded SCORM and MP4 video files in the US, EU, and CA instances of the KSAT console. This incident was caused when we deployed an infrastructure update without a necessary configuration parameter. On Monday, November 11, 2024, at 2:08 p.m. \(UTC\), we resolved the issue by adding the missing parameter. To prevent this type of issue in the future, we are adding additional logging, test cases, and documentation to our customer content management service. We are also implementing additional testing procedures to identify and manage issues in our test and production environments. If you attempted to upload custom content during this incident timeframe but the content failed to complete the automatic verification process, you will need to remove and re-submit the affected content.

This incident has been resolved.

We received earlier reports that custom content items, specifically SCORM and MP4 video files, were not able to complete the automatic verification process. The issue has been resolved, but if you are still experiencing issues, reach out to our support team.

On Monday, November 4, 2024, from approximately 11:00 p.m. to Wednesday, November 6, 2024, at 3:13 a.m. \(UTC\), some customers experienced delays with loading audit log events in US instances of the KSAT console. This issue was caused by a bug that occurred during a system upgrade. This bug caused the deletion of an event subscription, disrupting the KSAT console’s connection to audit log event data. To resolve this issue, we improved our code to address the bug and restore the subscription, and the KSAT console returned to normal performance by November 6, 2024, at 3:13 a.m. \(UTC\). To prevent this type of issue in the future, we’ve improved our code to ensure this bug no longer occurs during update deployments. We’ve also added additional checks when adjusting that connection, and we’ll be implementing additional boundaries between event subscriptions and the KSAT console. No data loss occurred as a result of this issue.

This incident has been resolved.

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

We have an identified an issue where certain KSAT events are not loading in the console. Affected events include Audit Log, User Timeline, and training campaign data. We are working on implementing a fix and we'll update our status page with any new information or updates.

On Thursday, November 7, 2024, from approximately 11:51 a.m. to 2:45 p.m. \(UTC\), some customers experienced delays with user provisioning for the KSAT console. These issues were caused by a system upgrade, which affected the user provisioning process that detects duplicate users. This process was updated using an outdated software package, and user provisioning became stuck in the pending state. To resolve this issue, the update to this process was rolled back, and the KSAT console returned to normal performance by 2:45 p.m. \(UTC\). To prevent this type of issue in the future, we’re implementing additional testing for future system upgrades and we’re adding new monitoring systems for the affected process to ensure a quick response if the user provisioning process gets stuck. No data loss occurred as a result of this issue.

This incident has been resolved.

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

We have identified an issue where User Provisioning Syncs are delayed in across all KSAT consoles. We are working on implementing a fix and we'll update our status page with any new information or updates

On Friday, November 8, 2024, from approximately 1:28 p.m. to November 11, 2024, at 1:45 p.m. \(UTC\), customers experienced issues with loading the leaderboard and team dashboard in the Learner Experience \(LX\). This issue was caused by a system upgrade that affected the leaderboard and team dashboard features. During this upgrade, updates to both features caused them to revert to a default disabled state. To resolve this issue, both features were re-enabled, and the LX console returned to normal performance by November 11, 2024, at 1:45 p.m. \(UTC\). To prevent this type of issue in the future, we are improving our code to ensure that permanent features remain enabled by default, and we are implementing additional checks during updates to determine if a feature should be disabled. No data loss occurred as a result of this issue.

This incident has been resolved.

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

We are investigating an issue that affects the visibility of the Team Dashboard and Leaderboard in the Learner Experience. We will update this page when we have more information.

On Thursday, November 8, 2024, from approximately 4:48 p.m. to 5:55 p.m. \(UTC\), the PhishER console experienced delays in ingesting reported messages. This issue was caused by a third-party vendor’s software update that changed how our PhishER software package updates are deployed. The deployment changes caused the PhishER message ingester service to look for a prior archived package instead of the latest package. As a result, the service was unable to scale and experienced delays. To resolve this issue, we added the new update requirements to our code and redeployed the update at 5:31 p.m. \(UTC\). The ingester service resumed, and the PhishER console returned to normal performance by 5:55 p.m. \(UTC\). To prevent this type of issue in the future, we have improved our deployment code to accommodate the third-party vendor’s new update requirements. No data loss occurred as a result of this issue.

This incident has been resolved.

We’ve implemented a fix for the issue with ingesting messages to the inbox and we’re monitoring the results to make sure no further issues occur.

We have identified an issue where the PhishER console is not ingesting messages to the inbox. We are investigating this issue and will update this page when we have more information.

On Friday, October 18, 2024, from approximately 6:30 p.m. until 7:05 p.m. \(UTC\), some users experienced login issues with the KSAT console. This incident was caused by an error that occurred during an update to a backend KSAT environment. The error caused the update to unexpectedly affect all KSAT environments, leading to delays between the KSAT console and the backend service and to increased error rates when some users tried to log in. Once the update was completed, the KSAT console returned to normal performance by 7:05 p.m. \(UTC\). No data loss occurred as a result of this issue.

This incident has been resolved.

We’ve implemented a fix for an issue with KSAT console logins and we’re monitoring the results to make sure no further issues occur.

On Monday, October 21, 2024, from approximately 5:34 p.m. to 6:21 p.m. \(UTC\), some customers experienced 500 errors and login issues with the KSAT console. These issues were caused by a code deployment that affected backend caching. This deployment slowed the caching service and caused loading delays and 500 errors for the KSAT console. To resolve this issue, the code deployment was reverted, and the KSAT console returned to normal performance by October 21, 2024, at 6:21 p.m. \(UTC\). To prevent this type of issue in the future, we are improving our workflows and coordination between teams when deploying code that will affect caching services. No data loss occurred as a result of this issue.

This incident has been resolved.

We've implemented a fix for the KSAT login issues and we're monitoring the results to make sure no further issues occur.

We have received reports that some customers are experiencing 500 errors when logging in to the KSAT console. We are investigating this issue and will update this page when we have more information.

On Tuesday, October 15, 2024, from approximately 6:33 p.m. until 6:54 p.m. \(UTC\), the US instance of the KSAT console experienced elevated error rates. This incident was caused by a database query enhancement that took longer than expected to apply and prevented some new connection requests from being processed. This issue blocked certain database operations and led to increased error rates. Upon evaluating the impact, the change was canceled and the KSAT console returned to normal performance by 6:54 p.m. \(UTC\). To prevent this issue in the future, we altered our enhancement strategy and implemented a new procedure for these types of updates in the future, including expanded usage of our maintenance window where required. No data loss occurred as a result of this issue.

This incident has been resolved.

We have identified the cause of increased error rates on the US instance of the KSAT console. We are working on implementing a fix and we'll update this page with any new information or updates.

On Wednesday, October 22, 2024, from approximately 10:15 a.m. to 12:20 p.m. \(UTC\), some customers experienced increased delays and errors for US and CA instances of the KSAT console. These issues were caused by unusually high traffic in developer testing environments. These testing environments shared certain cloud computing limits with KSAT console instances, which caused slower loading times for both environments. To resolve this issue, the testing environments were adjusted to use fewer resources. The KSAT console loading times returned to normal performance by October 22, 2024, at 12:20 p.m. \(UTC\), and all queued tasks were completed by 2:11 p.m. \(UTC\). To prevent this type of issue in the future, we have an ongoing project to separate these limits for our testing environment resources and KSAT console resources. This project is due to be completed in November 2024. No data loss occurred as a result of this issue.

This incident has been resolved.

We’ve implemented a fix for the delay and error issues and we’re monitoring the results to make sure no further issues occur.

We've identified the cause of these issues and we are working on a fix.

We are investigating increased delays and elevated error rates in the US and CA regions of KSAT and PhishER. We will update this page when we have more information.

On Monday, October 7, 2024, from approximately 4:08 p.m. to 9:29 p.m. \(UTC\), some customers experienced issues with downloading reports in the Download Center on the US instance of their KSAT console. This incident was caused by a high number of requests, which backed up the report generation queue. To resolve this issue, we increased the number of simultaneous requests that can be made to the database. This change allowed the backed-up queue of requests to be processed. We also found and resolved a related issue for partner admins who were unable to generate Training and Phishing Activities reports. This issue was caused by a new CSV setting for reports. Once we adjusted the setting, the reports began generating again. Once these issues were resolved, the console returned to regular performance by 9:29 p.m. on October 7, 2024. No data loss occurred as a result of this issue.

This incident has been resolved.

We’ve resolved the issue with download processing and identified the cause of an issue that partners are experiencing when generating reports. We’re working on implementing a fix and we'll continue to update this page when we have more information.

We’ve implemented a fix for the download processing issue and we’re monitoring the results to make sure no further issues occur.

We have received reports that downloads are processing slowly. We are investigating this issue and will update this page when we have more information.

On Wednesday, October 16th, 2024, from approximately 8:36 a.m. to 2:30 p.m. \(UTC\), some customers experienced login issues with the KSAT console and loading issues with the Modstore. These issues were caused by an earlier incident from October 15th, 2024: [KSAT - Increased Error Rates \(US Only\)](https://status.knowbe4.com/incidents/3jgnh0y7p4m6). The earlier incident cause was identified and a fix was developed, but these secondary issues occurred before the fix was fully deployed. Upon releasing the fix, the KSAT console and the ModStore returned to normal performance by October 16th, 2024 at 2:30 p.m. \(UTC\). To prevent this type of issue in the future, we have updated our engineering procedures to prioritize the deployment of fixes of this type. No data loss occurred as a result of this issue.

This incident has been resolved.

We’ve implemented a fix for the KSAT console loading issues and we’re monitoring the results to make sure no further issues occur.

We have received reports that customers are experiencing latency and loading errors in the KSAT console. We are continuing to investigate this issue and will update this page when we have more information.

We have received reports that some customers are experiencing loading errors in the KSAT Modstore. We are investigating this issue and will update this page when we have more information.

On Tuesday, October 1, 2024, from approximately 12:00 p.m. until 10:00 p.m. \(UTC\), some users experienced issues with phishing and training campaigns not starting as expected, training modules not being marked as complete, and some reports not downloading on the US instance of their KSAT console. This incident was caused when a system update to improve user enrollments did not update our scaling system and caused our queues to become backed up. To resolve this issue, we adjusted the system settings to allow the console to scale for increased traffic. Once the settings were adjusted, KSAT was able to return to normal performance by 10:00 p.m. \(UTC\). To prevent this type of issue in the future, we updated the default settings in our code to prevent similar slowdowns. We also implemented additional monitoring for the scaling system. No data loss occurred as a result of this issue.

This incident has been resolved.

We’ve implemented a fix for the issues and we’re monitoring the results to make sure no further issues occur.

We've identified the cause of the issues related to phishing campaigns, training campaigns, and training modules. We’re working on implementing a fix and we'll continue to post on our status page with any new information or updates.

We have received reports that phishing and training campaigns are not starting as expected, and training modules are not being marked as complete. We are investigating this issue and will update this page when we have more information.

On Wednesday, September 11th, 2024, from approximately 6:58 p.m. to 9:11 p.m. \(UTC\), some customers experienced loading issues with the Learner Experience. This incident was caused by an update that removed legacy code no longer used by one service but was found to still be in use by another service. We restored the code at approximately 8:58 p.m., and the Learner Experience returned to regular performance by 9:11 p.m. To prevent this type of issue in the future, we have implemented additional testing and additional coordination across teams prior to updating. No data loss occurred as a result of this issue.

This incident has been resolved.

We have identified an issue where some customers are experiencing loading issues in their Learner Experience and a fix has been implemented. We are now monitoring the results.

On Thursday, September 12th, 2024, from approximately 8:20 a.m. to 12:48 p.m. \(UTC\), some customers on the CA and EU instances of the KSAT console experienced loading issues with training campaigns and the Learner Experience. This incident was caused by code changes during a database upgrade. The new code worked initially, but over a longer period of time, the code needed additional configurations. We implemented those additional configurations at approximately 12:48 p.m. \(UTC\), and the console returned to regular performance. To prevent this type of issue in the future, we have implemented additional monitoring for the affected code and additional testing when we update it. We also contacted the database’s third-party vendor and validated that the new configurations were accurately applied. No data loss occurred as a result of this issue.

This incident has been resolved.

We have received reports that some customers in the EU are experiencing console loading issues and errors. We have released a fix and are monitoring the results.

From Tuesday, August 27, 2024, at approximately 4:56 p.m. until Thursday, August 29, 2024 at approximately 3:44 p.m. \(UTC\), some customers on the US instance of the KnowBe4 PhishER console experienced slow loading and login issues. This incident was caused by an unusually high number of requests which reduced performance for one of our databases. To resolve this issue, we upgraded our database to handle a higher number of requests and we increased the number of simultaneous requests that can be made to the database. This allowed the backed-up queue of requests to be processed and the console returned to regular performance by 3:44 p.m. on August 29, 2024. To prevent this issue in the future, in addition to our database upgrades, we have improved our monitoring of request traffic by increasing visibility and automated alerts. No data loss occurred as a result of this issue.

This incident has been resolved.

We’ve implemented a fix for the PhishER console login issues, and we’re monitoring the results to make sure no further issues occur.

We've identified the cause of the PhishER console login issues and we are working on implementing a fix. We'll update our status page with any new information or updates.

We have received new reports that some customers are unable to log in to the PhishER console. We are investigating this issue and will update this page when we have more information.

We have received new reports that some customers are unable to log in to the PhishER console. We are investigating this issue and will update this page when we have more information.

We’ve implemented a fix for the issue with slow loading in the PhishER console, and we’re monitoring the results to make sure no further issues occur.

We've identified the cause of the PhishER console's slow loading times and we are working on implementing a fix. We'll update our status page with any new information or updates.

We have identified an issue with the PhishER console experiencing slow loading times. We are investigating this issue and will update this page when we have more information.

On Thursday, August 22, 2024, from approximately 2:06 p.m. until 8:26 p.m. \(UTC\), some customers on the US instance of the KnowBe4 PhishER console experienced slow loading and login issues. This incident was caused by an unusually high number of requests which reduced performance for one of our databases. To resolve this issue, we modified our database configuration and reduced the number of simultaneous requests that can be made to the database. This change allowed the backed-up queue of requests to be processed more quickly and the console returned to regular performance by 8:26 p.m. \(UTC\) on August 22, 2024. To prevent this issue in the future, we have improved our testing processes and monitoring of request traffic by increasing visibility and automated alerts. No data loss occurred as a result of this issue.

PhishER console has returned to normal operation.

We’ve implemented a fix for the issue in the PhishER console, and we’re monitoring the results to make sure no further issues occur.

We are investigating an issue where some customers are unable to log in to the PhishER console or are experiencing longer loading times. We will update this page when we have more information.

From Tuesday, August 28, 2024, at approximately 8:50 p.m. until Thursday, August 29, 2024 at approximately 3:44 p.m. \(UTC\), some customers experienced an issue with their PhishML queries not processing. This incident was caused by the removal of legacy code that was still used by a connected service. This issue was mitigated when the code was restored at approximately 10:00 p.m on August 28, 2024 and the console returned to regular performance by 3:44 p.m. on August 29, 2024. To prevent this issue in the future, we have implemented automated monitoring for the affected service and we are reviewing a larger scope of services when removing legacy code. No data loss occurred as a result of this issue.

This incident has been resolved.

We’ve implemented a fix for the PhishER PhishML issues, and we’re monitoring the results to make sure no further issues occur.

We've identified the cause of the PhishER PhishML issues and we are working on implementing a fix. We'll update our status page with any new information or updates.

We have received reports that PhishML is not processing new messages. We are investigating this issue and will update this page when we have more information.

From Tuesday, August 28, 2024, at approximately 8:50 p.m. until Thursday, August 29, 2024 at approximately 3:44 p.m. \(UTC\), some customers experienced an issue with their PhishRIP queries not processing. This incident was caused by the removal of legacy code that was still used by a connected service. This issue was mitigated when the code was restored at approximately 10:00 p.m on August 28, 2024. We restored all PhishRIP queries that did not run during this incident and the console returned to regular performance by 3:44 p.m. on August 29, 2024. To prevent this issue in the future, we have implemented automated monitoring for the affected service and we are reviewing a larger scope of services when removing legacy code. No data loss occurred as a result of this issue.

This incident has been resolved.

We’ve implemented a fix for the PhishER PhishRip issues, and we’re monitoring the results to make sure no further issues occur.

We've identified the cause of the PhishER PhishRIP issues, and we are working on implementing a fix. We'll update our status page with any new information or updates.

We have received reports that PhishRIPs are not processing. We are investigating this issue and will update this page when we have more information.

On Thursday, August 16, 2024, from approximately 3:17 p.m. to 3:45 p.m. \(UTC\), some customers were unable to access their Account Settings in the KnowBe4 console. This incident was caused by a configuration change to a backend database. During the update, two fields with a null value caused errors when they were searched for. Another update was deployed to account for the null values and the console returned to regular performance by 3:45 p.m. No data loss occurred as a result of this issue.

This incident has been resolved.

We’ve implemented a fix for the issue with the KSAT account settings and we’re monitoring the results to make sure no further issues occur.

We have identified an issue with KSAT account settings not loading and we are working on implementing a fix. We'll update our status page with any new information or updates.

On Thursday, August 15, 2024, from approximately 6:10 p.m. to 7:08 p.m. \(UTC\), some US customers were unable to log in to their KnowBe4 console. This incident was caused by a third-party vendor update. An Amazon Web Services \(AWS\) planned configuration change increased API error rates for the KnowBe4 console. An AWS rollback was automatically triggered at 6:17 p.m. and service was fully restored by 7:08 p.m. For more information, see [Amazon’s AWS Service History post on their website](https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/SQS/AWS_SQS_OPERATIONAL_ISSUE/AWS_SQS_OPERATIONAL_ISSUE_7AB2F_D2A7D1D0D34). No data loss occurred as a result of this issue.

This incident has been resolved.

The issues with KSAT console logins and 500 errors have been resolved. We're monitoring the results to make sure no further issues occur.

We are continuing to investigate this issue.

We have identified an issue with KSAT console logins and 500 errors. We are working on implementing a fix and we'll update this page with any new information or updates.

On Monday, August 5th, 2024, from approximately 6:05 p.m. until August 6th, 2024, at 2:05 p.m. \(UTC\), some customers on the EU instance of the KSAT console experienced issues with starting campaigns, generating reports, adding users to campaigns, and mapping users in SecurityCoach. This incident was caused by an update to resolve the prior incident [KSAT - Campaign Delays](https://status.knowbe4.com/incidents/2dy7trnhx6s2) that occurred on August 5th, 2024. This update caused the affected tasks to appear to be successful in the backend despite not completing. Another update was deployed to address the issue and restart the processes. The console returned to regular performance by 2:05 p.m on August 6th, 2024. To prevent this type of issue in the future, we have enhanced our logging and monitoring capabilities to allow for improved visibility into our task processing.

This incident has been resolved.

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

The issue has been identified and a fix is being implemented.

We have received reports that campaigns are delayed, as well as reports about other issues with KSAT and SecurityCoach. We are looking into these reports and will update this page when we have more information.

On Thursday, 07/18/2024 from approximately 4:31 p.m to 5:40 p.m. \(UTC\), users experienced loading issues with the KSAT console. This was caused by a database update that removed a certain field from the search index. Searches made using that field were not able to be completed and caused database slowness. To resolve this issue, we updated the database again to restore the field to the search index. To prevent this issue in the future, we have improved our deployment workflows to ensure all essential fields are available in the search index. No data loss occurred as a result of this issue.

This incident has been resolved.

The issues with KSAT console logins, campaign delays, and authenticating the PAB have been resolved. We're monitoring the results to make sure no further issues occur.

We have identified an issue with KSAT console logins, campaign delays, and PAB authentication, and we are working on implementing a fix. We'll update on our status page with any new information or updates.

On Thursday, August 22nd, 2024, from approximately 3 p.m until 4:30 p.m \(UTC\), some users experienced issues when saving changes to the Account Settings in their KnowBe4 console.  This incident was caused when we deployed a code change for standardizing date formats in our CSV reports. The code change was deployed under a feature flag, and included a misconfiguration that unexpectedly affected accounts that had the feature flag enabled. Once we reverted the code change, the KnowBe4 console was able to return to normal performance by 4:30 p.m. \(UTC\). To prevent this type of issue in the future, we added more tests to this workflow. No data loss occurred as a result of this issue.

This incident has been resolved.

We’ve implemented a fix for the issue with saving Account Settings in the KSAT console. and we’re monitoring the results to make sure no further issues occur.

We have received reports that some customers are unable to save Account Settings in the KSAT console. We are investigating this issue and will update this page when we have more information.

On Tuesday, 07/23/2024, from approximately 1:14 p.m. to 3:50 p.m. \(UTC\), some users experienced login issues with the KnowBe4 console. This incident was caused by excessive server requests from a long-running query on one of our backend databases. To resolve the issue, we removed legacy code that was causing the query, and the KnowBe4 console returned to normal performance by 3:50 p.m. To prevent this type of issue in the future, we have improved our code to remove the need for the query that caused this issue. No data loss occurred as a result of this issue.

This incident has been resolved.

The issues with KSAT console logins and 500 errors has been resolved. We're monitoring the results to make sure no further issues occur.

We have identified an issue with KSAT console logins and 500 errors. We are working on implementing a fix and we'll update this page with any new information or updates.

We have received reports that some customers are unable to log in to their KSAT console. We are investigating this issue and will update this page when we have more information.

On Monday, 08/05/2024, from approximately 3:45 p.m. until 5:50 p.m. \(UTC\), all instances of the KSAT console experienced delays with training and phishing campaigns. This incident was caused when we deployed an update to the database access layer for one of our services. The update unexpectedly prevented some background jobs from completing successfully. While we manually implemented some mitigation steps, the US instance of the KSAT console also experienced approximately 15 minutes of downtime. Once the update finished deploying, KSAT was able to return to normal performance by 5:50 p.m. \(UTC\). Any jobs that failed to process during the deployment were able to be completed successfully after the deployment was completed. To prevent this type of issue in the future, we made adjustments to our updating and testing processes. We also completed additional, after-hours maintenance on the remaining environments on Thursday, 08/08/2024, at 1 a.m. \(UTC\). No data loss occurred as a result of this issue.

This incident has been resolved.

The US instance of the KSAT web console experienced approximately 15 minutes of downtime while we implemented the fix for the previous issue. This issue has been mitigated as well. No additional issues are expected from this incident. Some after-hours maintenance will be performed this Wednesday at 9pm EDT to reconcile some other components of this release.

We’ve implemented a fix for the issue causing delays in the KSAT console, and we’re monitoring the results to make sure no further issues occur.

We've identified the cause of an issue causing delays with training and phishing campaigns in the KSAT console. We are implementing a fix, and we'll continue to post on our status page with any new information or updates.

On Tuesday, 07/30/2024, from approximately 9:56 p.m. to Wednesday, 07/31/2024 at 2:20 a.m. \(UTC\), all of KnowBe4's products on the US instance experienced elevated error rates and intermittent service disruption. This incident was caused by an unexpected technical issue that impacted many of our systems. The disruption began to recover around Wednesday, 07/31/2024, at 1:47 a.m. \(UTC\), KnowBe4's products were able to return to normal performance by 2:20 a.m. \(UTC\) No data loss occurred as a result of this issue.

This incident has been resolved.

At 2:20am UTC, our error rate returned to normal. It has remained low for 30 minutes, and we have seen signs of all impacted features and services reaching or nearing a full recovery. We will leave this incident in Monitoring status for the next few hours as we continue to ensure the health of our products and features.

We are seeing good signs of recovery and a significant reduction in our error rate. Most delayed background jobs were able to process successfully around 2:00 UTC. We are still working towards a full recovery.

We are continuing to work on resolving this incident. Some services are showing early signs of recovery, though we are still experiencing elevated error rate. Most background jobs are still processing successfully with some elevated delays or latency.

We have identified the cause of this incident, and we are continuing to investigate the scope of this issue.

We are continuing to investigate this issue.

We are currently investigating an issue with the KSAT Console in the US region.

On Monday, 07/08/2024, from approximately 8:50 a.m. until 12:05 p.m. \(UTC\), some users experienced issues in the US instance of the KSAT Learner Experience \(LX\). Videos did not play properly, and training sessions expired unexpectedly or did not record completion. This incident was caused by a software component in one of our libraries that left behind unnecessary data over time, which led to our system's memory storage running out of space. Once we updated the software component and removed unnecessary data, KSAT was able to return to normal performance by 12:05 p.m. \(UTC\). To prevent this type of issue in the future, we increased the system’s memory storage space, upgraded the system after updating the software component, and set up regular cleanup tasks to remove old data. During this incident, some training progress was not tracked. Users who were completing training may have needed to redo the training that was in progress during this incident.

This incident has been resolved.

We have received reports of videos not playing properly, sessions expiring, and training being closed out in the KSAT Learner Experience (LX). We are investigating this issue and will update this page when we have more information.

On Wednesday, 06/19/2024, from approximately 6:39 p.m. until 7:09 p.m. \(UTC\), some users were unable to log in to their KSAT console or authenticate the Phish Alert Button \(PAB\). At approximately 6:35 p.m. \(UTC\), we deployed a framework update to our KSAT product that removed legacy information. The update was deployed using a new version of our application framework, and this new version’s functionality unexpectedly prevented the console from allowing users to log in or authenticate the PAB. Once the update finished deploying, KSAT returned to normal performance by 7:09 p.m. \(UTC\). To prevent this type of issue in the future, we have updated our deployment processes to account for the new framework requirements. No data loss occurred as a result of this issue.

This incident has been resolved.

The issues with logging in to the KSAT console and authenticating the PAB have been resolved. We're monitoring the results to make sure no further issues occur.

We have received reports that some customers are unable to log in to their KSAT console or authenticate the PAB. We are investigating this issue and will update this page when we have more information.

On Friday, 06/07/2024, from approximately 5:23 p.m. until Monday, 06/10/2024 at 7:00 p.m. \(UTC\), some users experienced slow loading times in the US instance of their PhishER platform. This incident was caused by an internal service that called an incorrect endpoint on the PhishER API, which resulted in long-running queries to the database and slowness on the PhishER platform. The incident was resolved when the internal service completed its tasks, and PhishER was able to return to normal performance by Friday, 06/07/2024, at 7:30 p.m. \(UTC\). To prevent this type of issue in the future, we updated the internal service on Monday, 06/10/2024 at 7:00 p.m. \(UTC\). The update prevents the internal service from calling the wrong endpoint with additional data validation. No data loss occurred as a result of this issue.

This incident has been resolved.

We’ve implemented a fix for the slow loading times for PhishER and we’re monitoring the results to make sure no further issues occur.

We have received reports from some users about slow loading times for PhishER. We are looking into this issue and will update this page when we have more information.

On Wednesday, 05/29/2024, from 1:06 p.m. to 6:06 p.m. \(UTC\), Active Directory Integration \(ADI\) syncs in the KnowBe4 console were stuck in a “processing” status. Upon investigation, we determined that the issue occurred when a software update to a third-party library caused the syncs to stop processing. We corrected the issue by updating our software to match the third-party library’s new format and ADI syncing returned to normal performance by 6:06 p.m. \(UTC\). To prevent this issue in the future, we have error alerts to notify us of potential user sync issues so we can catch and respond to problems as soon as possible. No data loss occurred as a result of this issue.

This incident has been resolved.

We have deployed a fix to resolve the user provisioning delays affecting KSAT. We will continue to monitor to ensure no further issues occur.

We have received reports that some accounts are experiencing delays with User Provisioning in their KSAT Console. We are investigating this issue and will provide updates as we have additional details.