Is there an KnowBe4 outage?
KnowBe4 status: Systems Active
Last checked: 3 minutes ago
Get notified about any outages, downtime or incidents for KnowBe4 and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 3 minutes ago
Get notified about any outages, downtime or incidents for KnowBe4 and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for KnowBe4.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Free Tools | Active |
| KnowBe4.com | Active |
| KnowBe4 Community | Active |
| Phish Alert Button | Active |
| Support.KnowBe4.com | Active |
| KCM GRC | Active |
| Console | Active |
| KnowBe4 Security Awareness Training (KSAT) | Active |
| Account Settings | Active |
| Account Settings | Active |
| API | Active |
| Audit Log | Active |
| Console | Active |
| Email Delivery | Active |
| Learner Experience (LX) | Active |
| ModStore | Active |
| Phishing | Active |
| PIQ | Active |
| Reporting | Active |
| Training | Active |
| User Provisioning | Active |
| PhishER | Active |
| Console | Active |
| Inbox | Active |
| Integrations | Active |
| Notification Service | Active |
| PhishML | Active |
| PhishRIP | Active |
| Rooms | Active |
| Webhooks | Active |
| SecurityCoach | Active |
| Coaching Delivery | Active |
| Console | Active |
| Real-Time Coaching Campaigns | Active |
| Security Vendor Integration Service | Active |
| User Mapping Engine | Active |
View the latest incidents for KnowBe4 and check for official updates:
Description: 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.
Status: Postmortem
Impact: Major | Started At: July 23, 2024, 1:21 p.m.
Description: 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.
Status: Postmortem
Impact: Critical | Started At: July 18, 2024, 4:54 p.m.
Description: 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.
Status: Postmortem
Impact: Minor | Started At: July 9, 2024, 12:57 p.m.
Description: 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.
Status: Postmortem
Impact: Major | Started At: June 19, 2024, 6:53 p.m.
Description: 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.
Status: Postmortem
Impact: Minor | Started At: June 7, 2024, 5:23 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
