Provider
KnowBe4Incident detail
Users Lists Not Populating
Timeline window
to
Get alerted the next time KnowBe4 breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Investigating
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
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
A fix has been implemented and we are monitoring the results.
Monitoring
A fix has been implemented and we are monitoring the results.
Resolved
This incident has been resolved.
Resolved
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.
Keep exploring
More from KnowBe4
Neighboring incidents on KnowBe4's timeline and the rest of their record on OutageDeck.