Is there an KnowBe4 outage?
KnowBe4 status: Systems Active
Last checked: 8 minutes ago
Get notified about any outages, downtime or incidents for KnowBe4 and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 8 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: From Tuesday, August 28, 2024, at approximately 8:50 p.m. until Thursday, August 29, 2024 at approximately 3:44 p.m. \(UTC\), some customers experienced an issue with their PhishML queries not processing. This incident was caused by the removal of legacy code that was still used by a connected service. This issue was mitigated when the code was restored at approximately 10:00 p.m on August 28, 2024 and the console returned to regular performance by 3:44 p.m. on August 29, 2024. To prevent this issue in the future, we have implemented automated monitoring for the affected service and we are reviewing a larger scope of services when removing legacy code. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: Aug. 28, 2024, 9:33 p.m.
Description: From Tuesday, August 28, 2024, at approximately 8:50 p.m. until Thursday, August 29, 2024 at approximately 3:44 p.m. \(UTC\), some customers experienced an issue with their PhishRIP queries not processing. This incident was caused by the removal of legacy code that was still used by a connected service. This issue was mitigated when the code was restored at approximately 10:00 p.m on August 28, 2024. We restored all PhishRIP queries that did not run during this incident and the console returned to regular performance by 3:44 p.m. on August 29, 2024. To prevent this issue in the future, we have implemented automated monitoring for the affected service and we are reviewing a larger scope of services when removing legacy code. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: Aug. 28, 2024, 9:05 p.m.
Description: From Tuesday, August 27, 2024, at approximately 4:56 p.m. until Thursday, August 29, 2024 at approximately 3:44 p.m. \(UTC\), some customers on the US instance of the KnowBe4 PhishER console experienced slow loading and login issues. This incident was caused by an unusually high number of requests which reduced performance for one of our databases. To resolve this issue, we upgraded our database to handle a higher number of requests and we increased the number of simultaneous requests that can be made to the database. This allowed the backed-up queue of requests to be processed and the console returned to regular performance by 3:44 p.m. on August 29, 2024. To prevent this issue in the future, in addition to our database upgrades, we have improved our monitoring of request traffic by increasing visibility and automated alerts. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: Aug. 27, 2024, 4:45 p.m.
Description: On Thursday, August 22nd, 2024, from approximately 3 p.m until 4:30 p.m \(UTC\), some users experienced issues when saving changes to the Account Settings in their KnowBe4 console. This incident was caused when we deployed a code change for standardizing date formats in our CSV reports. The code change was deployed under a feature flag, and included a misconfiguration that unexpectedly affected accounts that had the feature flag enabled. Once we reverted the code change, the KnowBe4 console was able to return to normal performance by 4:30 p.m. \(UTC\). To prevent this type of issue in the future, we added more tests to this workflow. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: Aug. 22, 2024, 3:16 p.m.
Description: On Thursday, August 22, 2024, from approximately 2:06 p.m. until 8:26 p.m. \(UTC\), some customers on the US instance of the KnowBe4 PhishER console experienced slow loading and login issues. This incident was caused by an unusually high number of requests which reduced performance for one of our databases. To resolve this issue, we modified our database configuration and reduced the number of simultaneous requests that can be made to the database. This change allowed the backed-up queue of requests to be processed more quickly and the console returned to regular performance by 8:26 p.m. \(UTC\) on August 22, 2024. To prevent this issue in the future, we have improved our testing processes and monitoring of request traffic by increasing visibility and automated alerts. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: Aug. 22, 2024, 2:18 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.
