Last checked: 6 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 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.
Status: Postmortem
Impact: Minor | Started At: Aug. 16, 2024, 3:27 p.m.
Description: 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.
Status: Postmortem
Impact: Minor | Started At: Aug. 15, 2024, 6:43 p.m.
Description: 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.
Status: Postmortem
Impact: Minor | Started At: Aug. 6, 2024, noon
Description: 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.
Status: Postmortem
Impact: Minor | Started At: Aug. 5, 2024, 4:30 p.m.
Description: 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.
Status: Postmortem
Impact: Critical | Started At: July 30, 2024, 9:57 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.