Live / KnowBe4 / Incident
KnowBe4: Prevent and Protect Degraded Performance (US Instances)
KnowBe4 · knowbe4.comMinor incidentResolved2026-10-02 10:32 UTC
Public — what happened
Summary
KnowBe4 reported slower-than-normal performance for its Prevent and Protect products on US servers, beginning on 2026-09-28 at 21:10 UTC. On 2026-09-29 at 13:44 UTC, the company said it had found the problem behind the slowdown and put a fix in place, then kept watching the service. KnowBe4 did not describe the cause in its updates. The incident was marked resolved on 2026-10-02 at 10:32.
Timeline
- Started — 2026-09-28 21:10 UTC
- Investigating — 2026-09-28 21:10 UTC
- Monitoring — 2026-09-29 13:44 UTC
- Resolved — 2026-10-02 10:32 UTC · 4 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach KnowBe4 against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for KnowBe4: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the KnowBe4 report →
More from KnowBe4
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.