KnowBe4 incident

KSAT - Reports Not Updating (US)

Minor Resolved View vendor source →

KnowBe4 experienced a minor incident on September 15, 2025 affecting Reporting, lasting 2d 17h. The incident has been resolved; the full update timeline is below.

Started
Sep 15, 2025, 07:43 PM UTC
Resolved
Sep 18, 2025, 12:53 PM UTC
Duration
2d 17h
Detected by Pingoru
Sep 15, 2025, 07:43 PM UTC

Affected components

Reporting

Update timeline

  1. identified Sep 15, 2025, 07:43 PM UTC

    We've identified the cause of reports not updating and are working on implementing a fix. We'll continue to post on our status page with any new information or updates.

  2. identified Sep 17, 2025, 03:12 PM UTC

    We have identified and mitigated some of the reporting delays between our reporting services and the KSAT console. Below is a summary of the current status for affected reports and widgets. Recovered: Training Activity Report: Have recovered, with events populated from September 16th and prior. Training Widgets (Executive Reporting): Have recovered, with events populated from September 16th and prior. Risk Score v2 Widgets: Have recovered and updated, and are showing events from September 16th and prior. Partially Delayed / In Recovery: Phishing Activity Report: We are seeing delayed reporting updates, with only partial data showing from September 15th and prior. Phishing Widgets (Executive Reporting): We are seeing delayed reporting updates, with only partial data showing from September 15th and prior. Delayed: PAB Activities Widgets (Executive Reporting): Continues to be delayed. The last updated timestamp is from September 1st. We are actively working on mitigation and the recovery of these events. We will provide another update as more information becomes available.

  3. identified Sep 17, 2025, 05:03 PM UTC

    We have mitigated additional reporting delays between our reporting services and the KSAT console. Below is a updated summary of the current status for affected reports and widgets Recovered: Training Activity Report: Have recovered, with events populated from September 16th and prior. Training Widgets (Executive Reporting): Have recovered, with events populated from September 16th and prior. Risk Score v2 Widgets: Have recovered and updated, and are showing events from September 16th and prior. Phishing Activity Report: Have recovered, with events populated from September 16th and prior. Phishing Widgets (Executive Reporting): Have recovered, with events populated from September 16th and prior. Delayed and Investigating: PAB Activities Widgets (Executive Reporting): Continues to be delayed. The last updated timestamp is from September 1st. We are actively working on mitigation and the recovery of these events. We will provide another update as more information becomes available.

  4. resolved Sep 18, 2025, 12:53 PM UTC

    We have implemented a fix for the ongoing reporting delay between our reporting services and the KSAT console. The PAB Activities Widget is now fully recovered. Below is the updated summary of the current status of impacted reports and widgets: Recovered: PAB Activities Widgets (Executive Reporting): Have been fully recovered, with events now populated Recovered in a Prior Update: Training Activity Report: Recovered, with events populated. Training Widgets (Executive Reporting): Recovered, with events populated. Risk Score v2 Widgets: Recovered, with events populated. Phishing Activity Report: Recovered, with events populated. Phishing Widgets (Executive Reporting): Recovered, with events populated.

  5. postmortem Dec 10, 2025, 04:09 PM UTC

    On Monday, September 15, 2025, we identified an issue with stale KSAT reporting data in our US region. After investigating, we determined the cause to be a routine upgrade to our data processing pipeline that left it in a dysfunctional state. The last pipeline data was from September 1st, September 9th, and September 11th, across 3 different reporting data sources, respectively. We restarted the data pipeline to rehydrate the missing period of data for all 3 sources. Due to the volume of missing data, the rehydration required an extended run-time, approximately 48 hours. To prevent this type of issue in the future, a multitude of efforts are in-progress: * We are adding additional visibility to our reporting data processing pipelines to ensure end-to-end functionality and to catch any issues caused by routine upgrades. * We are adding visibility to a few potentially related areas so that we can quickly identify and fix any similar future issues before they can impact the integrity of the data that powers our reports. * We are making some architectural improvements to the rehydration process that should decrease the time it takes to hydrate large gaps of missing reporting data, should the need arise again * We are accelerating a project to increase overall stability in the existing reporting platform functionality. * Multiple engineering projects are in-flight to bring additional long-term enhancements to reporting for all KnowBe4 products. More information on these future efforts will be available in 2026. Upon completion of the rehydration and associated data processing jobs, we confirmed that there was no permanent data loss as a result of this incident.