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: This incident has been resolved. We've removed code that validates expiration dates for customer SAML/SSO certificates, and we'll be adding that validation as an optional opt-in feature in the future.
Status: Resolved
Impact: Minor | Started At: Nov. 19, 2024, 1:06 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Nov. 11, 2024, 2:33 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Nov. 11, 2024, 1:51 p.m.
Description: On Thursday, November 8, 2024, from approximately 4:48 p.m. to 5:55 p.m. \(UTC\), the PhishER console experienced delays in ingesting reported messages. This issue was caused by a third-party vendor’s software update that changed how our PhishER software package updates are deployed. The deployment changes caused the PhishER message ingester service to look for a prior archived package instead of the latest package. As a result, the service was unable to scale and experienced delays. To resolve this issue, we added the new update requirements to our code and redeployed the update at 5:31 p.m. \(UTC\). The ingester service resumed, and the PhishER console returned to normal performance by 5:55 p.m. \(UTC\). To prevent this type of issue in the future, we have improved our deployment code to accommodate the third-party vendor’s new update requirements. No data loss occurred as a result of this issue.
Status: Postmortem
Impact: Minor | Started At: Nov. 8, 2024, 6:05 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Nov. 7, 2024, 12:30 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.