Skip to content
Back to KnowBe4Incident Postmortem
KnowBe4 logo

KnowBe4

Tracked by PulseWatch

Auto-drafted postmortem

KnowBe4 outage on September 17 — 18h 48m disruption

Sep 17, 10:51 PM → Sep 18, 05:39 PM · 18h 48m · high

A high-severity outage affecting the KnowBe4 service was detected via automated signals, including the vendor's own status page. The incident began on September 17, 2026, at 22:51 UTC and was resolved on September 18, 2026, at 17:39 UTC.

Duration
18h 48m
tracked by PulseWatch

Impact

This high-severity incident affected the KnowBe4 service for a duration of 18 hours and 48 minutes. During this period, the service experienced significant disruption as indicated by the vendor's status page. No user-reported data was collected for this incident, and therefore, no specific user-visible impact regarding features, regions, or issue types can be detailed from user reports.

Incident timeline

  1. Sep 17, 10:51 PM

    PulseWatch detected the incident from automated vendor and probe signals (high severity)

  2. Sep 17, 10:51 PM

    Status updated: possible issue

  3. Sep 18, 05:39 PM

    Signals cleared — incident resolved

Official updates

  1. Sep 17, 10:51 PM

    KnowBe4 status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the sources listed above.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash