KnowBe4 incident

Webforms | Partial Submission Issue (UK only)

Minor Resolved View vendor source →

KnowBe4 experienced a minor incident on September 23, 2026 affecting Secure Web Forms, lasting 5h 58m. The incident has been resolved; the full update timeline is below.

Started
Sep 23, 2026, 09:00 AM UTC
Resolved
Sep 23, 2026, 02:58 PM UTC
Duration
5h 58m
Detected by Pingoru
Sep 23, 2026, 09:00 AM UTC

Affected components

Secure Web Forms

Update timeline

  1. investigating Sep 23, 2026, 09:00 AM UTC

    We have received reports that some users are unable to successfully submit webform submissions. We are investigating this issue and will update this page when we have more information.

  2. identified Sep 23, 2026, 10:47 AM UTC

    The issue has been identified and a fix is been implemented. An update with more information will follow accordingly.

  3. monitoring Sep 23, 2026, 10:58 AM UTC

    The issue has been identified and a fix has been implemented and will update this page when we have more information.

  4. resolved Sep 23, 2026, 02:58 PM UTC

    This incident has been successfully resolved and all systems are fully operational.

  5. postmortem Oct 20, 2026, 03:53 PM UTC

    On Wednesday, September 23, 2026, from approximately 08:15 to 11:18 \(UTC\), some customers experienced slowness and failed form submissions in UK instances of Secure Webforms. This issue was caused by database performance limits in the UK production environment following a recent change. A database setting also caused some queries to run inefficiently. As a result, response times increased and some form submissions failed. To resolve this issue, our team temporarily paused a background synchronization task to reduce load, adjusted the database settings to improve query efficiency, and increased storage throughput. Secure Webforms returned to normal performance by 11:18 \(UTC\). To prevent this type of issue in the future, we’re adding additional monitoring for database bandwidth. We’re also improving the efficiency of the background synchronization task. No data loss occurred as a result of this issue.