KnowBe4 experienced a minor incident on December 15, 2025 affecting Console, lasting 19h 5m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Dec 15, 2025, 06:54 PM UTC
We are investigating an issue preventing user lists from being populated in KSAT. This is impacting the Users tab, user lists within Phishing campaigns and user groups. We'll continue to post on our status page with any new information or updates.
- investigating Dec 15, 2025, 07:06 PM UTC
We are continuing to investigate an issue preventing user lists from being populated in KSAT. This is impacting the Users tab, user lists within groups and within campaign subtabs. We'll continue to post on our status page with any new information or updates.
- monitoring Dec 15, 2025, 07:55 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Dec 15, 2025, 07:58 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 16, 2025, 01:59 PM UTC
This incident has been resolved.
- postmortem Jan 20, 2026, 07:10 PM UTC
On Monday, December 15, 2025, from approximately 18:39 to 19:32 \(UTC\), customers were unable to load user data across all regions of the KSAT console. This issue was immediately identified by our monitoring systems, and the root cause was traced to a database migration during a product deployment. During the migration, a column was intentionally removed from the database as part of a feature deprecation task. However, due to a caching inconsistency between the application images and the database structure, a synchronization gap was created. Our schema cache system retained old references to the deleted column in the running application images. Because the old application image was still querying for the deleted column and the database no longer contained it, active instances began throwing errors. This issue resulted in a failure to load user data across all regions. Our engineering team restored service by re-adding the deleted column to both tables. This action resolved the database query inconsistency and allowed the system to load user data correctly. The KSAT console returned to normal performance by 19:32 \(UTC\). No data loss occurred as a result of this issue.