KnowBe4 incident

Webform submission failures (UK & EMEA)

Major Resolved View vendor source →

KnowBe4 experienced a major incident on March 10, 2026 affecting Secure Web Forms, lasting 1d 10h. The incident has been resolved; the full update timeline is below.

Started
Mar 10, 2026, 12:09 AM UTC
Resolved
Mar 11, 2026, 10:57 AM UTC
Duration
1d 10h
Detected by Pingoru
Mar 10, 2026, 12:09 AM UTC

Affected components

Secure Web Forms

Update timeline

  1. investigating Mar 10, 2026, 12:09 AM UTC

    We are currently experiencing an issue with some customers showing an error when trying to submit a form using Webforms. We are aware of the issue and are working on resolving this as quickly as possible.

  2. resolved Mar 11, 2026, 10:57 AM UTC

    This incident has been resolved.

  3. postmortem May 27, 2026, 09:15 PM UTC

    From Monday, March 9, 2026, at approximately 19:00 \(UTC\) until Tuesday, March 10, 2026, at approximately 17:00 \(UTC\), a subset of Workspace customers experienced Secure Webform submission failures. This incident was caused when a renewed multi-SAN certificate used by our shared authentication infrastructure \(Core ESI\) referenced a newer Certificate Authority \(CA\) root. This update caused dependent infrastructure systems running extended-support operating systems to reject authentication requests due to missing trust anchors, leading to TLS validation failures. To resolve this issue, the required CA root was deployed to the trust stores of the affected systems and service containers, restoring normal authentication behavior. Failed submissions were successfully replayed. Workspace returned to normal performance by approximately 17:00 \(UTC\) on March 10, 2026. To prevent this type of issue in the future, we have reviewed the validation and monitoring processes associated with certificate changes, and we are expanding procedures to include checks from dependent systems and re-architecting systems relying on extended support to ensure required CA roots are available. No data loss occurred as a result of this issue.