Is there an KnowBe4 outage?
KnowBe4 status: Systems Active
Last checked: a minute ago
Get notified about any outages, downtime or incidents for KnowBe4 and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: a minute 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 Thursday, 04/04/2024, from approximately 1:12 a.m. until 6:45 p.m. \(UTC\), some users experienced delays when provisioning users in their KnowBe4 Security Awareness Training console. The update queue for user provisioning was stopped during a system update on Wednesday night to make sure the system had enough resources for a backend update. After the update, the system did not resume processing jobs and the queue became backed up. Once we cleared out the backlog of jobs and restarted the queue, syncs resumed processing and the KnowBe4 console was able to return to normal performance by 6:45 p.m. \(UTC\). No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: April 4, 2024, 5:53 p.m.
Description: On Thursday, 04/04/2024, from approximately 1:12 a.m. until 1:07 p.m. \(UTC\), some partner admins experienced issues with using multi-factor authentication \(MFA\) to access their KnowBe4 console. This incident was caused when the MFA login process was updated for partner admins. The database generated new login information for existing partner admins instead of using the existing login information. Once we replaced the new login information with the previous, correct information, the partner admins were able to use multi-factor authentication to log in to their KnowBe4 console. The KnowBe4 console was able to return to normal performance by 1:07 p.m. \(UTC\).
Status: Postmortem
Impact: Minor | Started At: April 4, 2024, 12:22 p.m.
Description: On Tuesday, 03/26/2024, from approximately 3:00 p.m. until 5:30 p.m. \(UTC\), some partner admins experienced issues with searching from the Account tab in their KnowBe4 console. This incident was caused when the system was missing code to allow access permissions for partner admins, and the system defaulted to limited permissions. Once we updated the system to allow access for partner admins who were given permissions, the KnowBe4 console was able to return to normal performance by 5:30 p.m. \(UTC\). No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: March 26, 2024, 8:57 p.m.
Description: On Monday, 03/25/2024, from approximately 2:41 p.m. to 6:06 p.m. \(UTC\), some manager and admin users on the US instance of the KnowBe4 console received training notifications related to their archived users' training status. This incident occurred when we made a change to how training notifications are scheduled. To fix a previous issue where the system failed to send notifications, we had removed a status filter and began to check user statuses at an earlier stage of the process. Without the status filter, the system began sending notifications for all users, causing some admins and managers to receive unnecessary emails about completed campaigns related to archived users who had overdue tasks. To correct this issue, we added a condition to filter out archived users when creating the user list for training notification scheduling. Once this issue was resolved, training notifications were functioning normally by 6:06 p.m. \(UTC\). To prevent this type of issue in the future, we have added more testing to our processes. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: March 25, 2024, 5:11 p.m.
Description: On Tuesday, 03/12/2024, from approximately 10:00 p.m. \(UTC\) until Wednesday, 03/13/2024 at 1:30 a.m. \(UTC\), some users experienced issues with managing phishing campaigns in their KnowBe4 console. This incident was caused when some pages in the KnowBe4 console, including Profile, Users, Account Settings, Training Campaigns, and Phishing Campaigns, did not automatically adjust the time zones for daylight saving time. Once we adjusted the time zones, the KnowBe4 console was able to return to normal performance by Wednesday at 1:30 a.m. \(UTC\). To prevent this type of issue in the future, we plan to add more testing to our workflows. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: March 12, 2024, 7:15 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.
