Is there an KnowBe4 outage?
KnowBe4 status: Systems Active
Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for KnowBe4 and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 4 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 Monday, 02/19/2024, from approximately 2:30 p.m. to Tuesday, 02/20/2024 at 10:30 a.m. \(UTC\), the KnowBe4 console did not send audit logs from one part of our system to another. This incident was caused by a code change to our non-production environment that unexpectedly affected the production environment. Once we fixed the code, the KnowBe4 console was able to return to normal performance by 10:30 a.m. \(UTC\). To prevent this type of issue in the future, we are improving our monitoring processes, adding more environment testing to our deployment processes, and adjusting our deployment schedule. The data for the audit logs was not saved during the affected time period. All other system logs and records were unaffected.
Status: Postmortem
Impact: None | Started At: Feb. 22, 2024, 11:01 p.m.
Description: On Wednesday, 02/07/2024, from approximately 2:00 p.m. to Wednesday, 02/14/2024 at 7:00 p.m. \(UTC\), an alert message displayed when the email template editor loaded in users’ KnowBe4 console or PhishER platform. This incident was caused when our HTML editor provider released a new version of their editor. Older versions of the editor were no longer considered secure, and as a result, the provider displayed an alert message in the editor of the KnowBe4 console and PhishER platform. Once we updated the KnowBe4 console and PhishER platform to use the latest version, the editor was considered secure and the alert message no longer displayed. To prevent this type of issue in the future, we plan to monitor the third-party editor provider’s release notes to prepare for new version releases. No data was lost as a result of this incident. The level of vulnerabilities for the third-party editor provider was low to moderate. We released a fix in a week, and this timeframe is in the expected remediation timeline for our SLA. For more information about our policy on vulnerability timeframes, visit [Security | KnowBe4](https://www.knowbe4.com/security).
Status: Postmortem
Impact: Minor | Started At: Feb. 7, 2024, 8:12 p.m.
Description: On Friday, 02/02/2024, from approximately 8:05 p.m. to Monday, 02/05/2024, at approximately 1:24 p.m. \(UTC\), users experienced delays when provisioning users in the US instance of their KnowBe4 consoles. This incident was caused by a previous incident that affected a backend storage system and prevented jobs from processing. After the initial incident was resolved, the system did not resume processing jobs and our queues became backed up over the weekend. Once we increased the resources available to the system to process the backlog of jobs, the KnowBe4 console was able to return to normal performance by 1:24 p.m. \(UTC\) on Monday. To prevent this type of issue in the future, we are improving our monitoring processes to track the responsiveness of system processes. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: Feb. 5, 2024, 1:22 p.m.
Description: On Wednesday, 01/31/2024, from approximately 7:36 p.m. to 9:47 p.m. \(UTC\), users experienced issues with accessing the CA, DE, EU, and UK instances of the PhishER platform. This incident was caused by a frontend update that deployed successfully to the US instance, but failed for the above-mentioned instances. The unsuccessful deployment caused errors that affected the frontend of the platform while the backend and automated actions continued to function across all environments. Once we deployed a fix to each environment, PhishER was able to return to normal performance by 9:47 p.m. \(UTC\). To prevent this type of issue in the future, we are adjusting our deployment schedule and adding more environment testing to our deployment processes. No data was lost as a result of this incident.
Status: Postmortem
Impact: Minor | Started At: Jan. 31, 2024, 8:51 p.m.
Description: On Tuesday, 01/16/2024, from approximately 9:30 a.m. to 5:30 p.m. \(UTC\), some users experienced issues viewing policies in the KnowBe4 Learner Experience. This incident was caused by a code change that unexpectedly affected access to the console for users with limited permissions, which prevented some policies from loading successfully. Once the code change was reverted, the KnowBe4 console was able to return to normal performance by 5:30 p.m. \(UTC\). To prevent this type of issue in the future, we are adding additional testing and reviews to our workflow. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: Jan. 16, 2024, 5:01 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.
