Is there an KnowBe4 outage?
KnowBe4 status: Systems Active
Last checked: 11 minutes ago
Get notified about any outages, downtime or incidents for KnowBe4 and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 11 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 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.
Status: Postmortem
Impact: Minor | Started At: May 29, 2024, 2:06 p.m.
Description: On Wednesday, 05/15/2024, from approximately 12:35 p.m. until 3:15 p.m. \(UTC\), some users experienced issues with loading information about accounts in their KSAT console. This incident was caused when we deployed an update for an upcoming feature. The update unexpectedly affected the index page for accounts, and as a result, partners did not have access permissions for the updated information. Once we added the proper permissions, partners were able to access the page again by 3:15 p.m. \(UTC\). To prevent this type of issue in the future, we are increasing additional testing in our workflow to check for similar errors before updates are deployed. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: May 15, 2024, 2:40 p.m.
Description: On Monday, 05/06/2024, from approximately 3:20 p.m. until 6:45 p.m. \(UTC\), the PhishER platform stopped ingesting messages. This incident was caused by a new service deployment that interfered with the PhishER ingester service. This resulted in messages being queued in a backlog but not processed in PhishER. Once the ingester service was restored, the backlog began processing again and PhishER was able to return to normal performance by 6:45 p.m. \(UTC\). Messages delayed during this incident were fully processed by Tuesday, 05/14/2024. To prevent this type of issue in the future, we have implemented additional checks to verify that new service deployments will not interfere with existing services. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Major | Started At: May 6, 2024, 5:30 p.m.
Description: From approximately 4:00 p.m. Sunday, 04/28/2024, through 7:45 p.m. \(UTC\) Tuesday, 04/30/2024, the US instance of the KSAT console experienced issues with user provisioning. This incident was caused by a large number of sync error reports. This congested the sync queue due to a recent backend change to how syncs are handled. To resolve this issue, we increased resources to process the queue backlog, and the user provisioning was able to return to normal performance by 7:45 p.m. \(UTC\) on Tuesday, 04/30/2024. To prevent this type of issue in the future, we have changed the backend process to allow for greater control and quick adjustments when the queue experiences higher activity than normal. We will also be updating how user provisioning syncs are handled to increase efficiency and reduce the impact of unusually high sync error reporting activity. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: May 1, 2024, midnight
Description: On Wednesday, 04/26/2024, from approximately 12:20 p.m. until 2:30 p.m. \(UTC\), some users experienced issues with the PhishER platform failing to load. This incident was caused by an unusually high number of PhishER web requests in a short period of time. The incident was resolved when request levels lowered and PhishER was able to return to normal performance by 2:30 p.m. \(UTC\). To prevent this type of issue in the future, we are actively improving our web request infrastructure and how web requests are handled. We are also implementing an additional tool to increase stability and performance during periods of high activity. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: April 26, 2024, 12:36 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.
