Đã khắc phục · kéo dài 2 giờ

Sự cố KnowBe4 ngày 13 tháng 10

Báo cáo về KnowBe4 tăng vọt lên 151 mỗi giờ và duy trì ở mức cao trong 2 giờ.

Bắt đầu
14:00
13 tháng 10, 2026 · UTC
Trở lại bình thường
16:00
2 giờ sau
Đỉnh
151/giờ
gấp 151× bình thường
Sự cố của KnowBe4
1 giờ 13 phút
Console Login Issues

Báo cáo trong thời gian sự cố

12:0017:50 UTC

KnowBe4 đã nói gì

status.knowbe4.com
Đã khắc phục15:03–16:15 · 1 giờ 13 phút

Console Login Issues

  1. Đã khắc phục · 14:29

    ## **Summary** On October 13, 2026, from approximately 14:19 to 15:05 \(UTC\), customers in all regions were unable to log in to the KnowBe4 Security Awareness Training \(SAT\) console, the KnowBe4 Learner Experience, and the PhishER console through KnowBe4 SAT. SAML and password logins returned errors, and the KnowBe4 SAT console didn't appear in the KnowBe4 platform. Some background processes, including user synchronization and training emails, also failed during this time. The incident was caused by a production release that conflicted with another change in our code. We reverted the release, and logins recovered across regions between 14:59 and 15:05 \(UTC\). No data loss occurred as a result of this issue. ## **Root Cause** A code deployment removed a startup configuration value to speed up application startup time. A separate component, added to our code after the original change was tested, didn’t account for that changed value. As a result, every attempt to save a user record raised an error, including the update that records sign-in attempts. ## **Customer Impact** Customers across all regions couldn't log in to the KSAT console via SAML or password. They were also unable to access the Learner Experience, and couldn’t access the PhishER console through the KnowBe4 SAT console. New user creation, user synchronization, and training emails failed during this time but were automatically retried after the deployment was reverted. ## **Mitigation and Remediation** We found that the deployment removed a configuration value that another component still required. This was mitigated by reverting the release, and we confirmed recovery across all regions through direct checks and automated tests. We also reverted the original change in our source code and prepared a corrected version that includes a compatibility fix, so the original improvement can be reintroduced safely. ## **Preventative Measures** We're adding additional code verifications and testing for deployments.

  2. Đã khắc phục · 16:15

    This incident has been resolved.

  3. Đang theo dõi · 15:07

    A fix has been implemented and we are monitoring the results.

  4. Đang điều tra · 15:03

    We are currently investigating an issue affecting console login. We will provide more updates here when available.

KnowBe4 đăng cập nhật đầu tiên 1 giờ 03 phút sau khi báo cáo bắt đầu tăng.

KnowBe4 có đang bị gián đoạn không?

Trạng thái trực tiếp, báo cáo hôm nay và các sự cố trước đây khác.

Trạng thái KnowBe4 hiện tại →