Provider
KnowBe4Incident detail
Data and User Inconsistencies in Reporting
Resolved incidentMinor
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 KnowBe4 posted, oldest to newest, exactly as it appeared on their official status page.
Investigating
We've identified an issue that has resulted in inconsistent reporting, and our engineering team is looking into a fix.
Monitoring
A fix has been implemented and we are monitoring the results.
Resolved
This incident has been resolved.
Resolved
From Tuesday, June 16, 2026, at approximately 22:23 (UTC), to Wednesday, June 17, 2026, at approximately 20:19 (UTC), some customers experienced inaccurate user counts in KSAT reporting. Downstream features that rely on this data were also affected, including AIDA Orchestration, Risk Score, and ModStore recommendations.
This issue was caused by an incomplete rebuild of the users' data table. A data storage policy removed historical data earlier than intended, so when a full table rebuild ran, some older data was unavailable, causing user counts to drop. To resolve this issue, our team performed a full data migration sync on the users' table and retriggered the dependent data pipelines to update downstream systems. We then tested and confirmed that user counts were returning correct results, and the KSAT console returned to normal performance by June 17, 2026, at 20:19 (UTC).
To prevent this type of issue in the future, we are correcting the underlying data storage policy to ensure complete historical data is retained for the full rebuild process.
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.