Last checked: 2 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, 5/17/2023, from approximately 6:20 p.m. until 6:40 p.m. \(UTC\), some users experienced issues loading their PhishER platforms. This incident was caused by increased activity in our full-text search database, which prevented some pages from loading. Once the activity decreased, PhishER was able to return to normal performance by 6:40 p.m. \(UTC\). To prevent this type of issue in the future, we are making adjustments to better handle activity in our full-text search database. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: May 17, 2023, 6:38 p.m.
Description: On Thursday, 05/04/2023, from approximately 5:55 p.m. until 6:17 p.m. \(UTC\), some users were unable to log in to their KMSAT consoles using SAML or passwordless login. Additionally, some users were unable to access the Account Information page or reset their passwords. This incident was caused by a backend update that removed code used by another backend process. Once the update finished deploying, KMSAT was able to return to normal performance by 6:17 p.m. \(UTC\). To prevent this type of issue in the future, we are improving our internal processes for removing code. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Major | Started At: May 4, 2023, 5:54 p.m.
Description: On Monday, 5/1/2023, from approximately 2:22 p.m. until 2:46 p.m. \(UTC\), some users experienced degraded performance in their KMSAT consoles. This incident was caused by a large number of requests due to high traffic. Because of recent improvements, we were able to quickly implement additional resources to handle the requests. Once the issue was resolved, KMSAT was able to return to normal performance by 2:46 p.m. \(UTC\). To prevent this type of issue in the future, we are implementing additional improvements so that our systems can better handle high traffic. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: May 1, 2023, 2:43 p.m.
Description: On Friday, 4/21/2023, from approximately 8:12 p.m. until 11:21 p.m. \(UTC\), some KMSAT partner admins received multiple emails for scheduled reports. This incident was caused by a backend update that prevented some scheduled report jobs from processing. After the issue was fixed, emails were sent for each of these jobs that processed successfully. As a result, partner admins received many duplicate emails. Once we stopped processing the jobs, KMSAT was able to return to normal performance by 11:21 p.m. \(UTC\). To prevent this type of issue in the future, we are optimizing our processes to send only one unique email every 24 hours. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: April 21, 2023, 8:25 p.m.
Description: On Monday, 4/3/2023, from approximately 2:21 p.m. until 8:00 p.m. \(UTC\), some users experienced degraded performance in their KMSAT consoles, including email delays. This incident was caused by a large number of phishing and training campaigns that were scheduled to start on Saturday, 4/1/2023. Because campaigns follow organizations’ business hours, many of these campaigns actually started on Monday, 4/3/2023. This increased pressure on some backend systems, causing delays. Once we paused some nonessential services, KMSAT was able to return to normal performance by 8:00 p.m. \(UTC\). Then, we resumed nonessential services gradually until all services could return to normal functionality by Tuesday, 4/4/2023, at 2:03 a.m. \(UTC\). To prevent this type of issue in the future, we are optimizing several processes related to campaigns. We are also making improvements to help identify background processes that are using a lot of database resources. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: April 3, 2023, 3:02 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.