KnowBe4 incident

Prevent and Defend Deployment Center Issue

Major Resolved View vendor source →

KnowBe4 experienced a major incident on November 3, 2025 affecting Deployment Center and Deployment Center, lasting 21h 19m. The incident has been resolved; the full update timeline is below.

Started
Nov 03, 2025, 03:14 PM UTC
Resolved
Nov 04, 2025, 12:34 PM UTC
Duration
21h 19m
Detected by Pingoru
Nov 03, 2025, 03:14 PM UTC

Affected components

Deployment CenterDeployment Center

Update timeline

  1. investigating Nov 03, 2025, 03:14 PM UTC

    We have received reports of errors when using the Deployment Center for both Defend and Prevent . We are investigating this issue and will update this page when we have more information.

  2. identified Nov 03, 2025, 06:05 PM UTC

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

  3. monitoring Nov 03, 2025, 06:50 PM UTC

    We’ve implemented a fix for the Deployment Center and we’re monitoring the results to make sure no further issues occur.

  4. monitoring Nov 03, 2025, 06:52 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Nov 04, 2025, 12:34 PM UTC

    This incident has been resolved.

  6. postmortem Dec 08, 2025, 03:28 PM UTC

    On Monday, November 3, from approximately 2:54 p.m. \(UTC\) until Tuesday, November 4, 2025, at 10:04 a.m. \(UTC\), some users were unable to deploy any instances of Defend or Prevent via the deployment center. This incident was caused by an intermittent failure when communicating with Microsoft systems while attempting to provision new groups within customer tenants as part of the product deployment process. To resolve this issue, we changed the group creation process to use Graph API rather than Exchange PowerShell, which allowed the groups to be successfully created within customer tenants. All affected deployments were subsequently retried by customers and completed successfully. To prevent this type of issue in the future, we have implemented additional monitoring for the deployment process. No data loss occurred as a result of this issue.