Skip to content
PulseWatchOUTAGE.INTEL
KnowBe4 logo

Other

Is KnowBe4 down right now?

NormalOfficial status last polled Oct 12, 2026 17:08 UTCwww.knowbe4.comOfficial status page

Are you on the KnowBe4 team and see something inaccurate? Report it to us. We respond within one business day.

Is KnowBe4 down right now?

No. KnowBe4 has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 12, 2026 18:19 UTC

Normal

KnowBe4 is operating normally

As of Oct 12, 2026 18:19 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

0

Last incident

Sep 29, 2026 14:19 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for KnowBe4.

10

Incident days

20

No recorded incident

85h 25m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for KnowBe4. Hover a day for detail.

Sep 13Sep 18Sep 23Sep 28Oct 3Oct 801234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

10

Days with incidents

1 incident

Busiest day

85h 25m

Recorded duration

Report volume

0 reports in last 24H

06:15 PM09:45 PM01:15 AM04:45 AM08:15 AM11:45 AM03:15 PM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

KnowBe4: vendor-reported minor incident on September 28 (tracked 16h 44m)

Sep 28, 09:34 PM → Sep 29, 02:19 PM · 16h 44m · medium

KnowBe4 reported a minor-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 16h 44m, from Mon, 28 Sep 2026 21:34:34 GMT to Tue, 29 Sep 2026 14:19:20 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
16h 44m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

  1. Sep 28, 09:34 PM

    The vendor reported a minor-impact incident on its own status page; PulseWatch began tracking it

  2. Sep 28, 09:34 PM

    Status updated: possible issue

  3. Sep 29, 02:19 PM

    PulseWatch closed the incident

Official updates

  1. Sep 28, 09:34 PM

    KnowBe4 reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.

Reliability

Detected by PulseWatch

30-day uptime

88.1%

90-day uptime

95.6%

Calculated from KnowBe4's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedMedium

KnowBe4: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/28/2026, 9:34:34 PM · 16h 44m

09:34 PM02:19 PM
Detection9/28/2026, 9:34:34 PM · 13d ago

Detected — medium severity

KnowBe4: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

KnowBe4: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/24/2026, 6:31:21 PM · 14h 59m

06:31 PM09:30 AM
Detection9/24/2026, 6:31:21 PM · 17d ago

Detected — medium severity

KnowBe4: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedHigh

KnowBe4: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch KnowBe4 or have an alert rule on it can be alerted, labelled vendor-reported.

9/23/2026, 9:35:11 AM · 6h 29m

09:35 AM04:04 PM
Detection9/23/2026, 9:35:11 AM · 19d ago

Detected — high severity

KnowBe4: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch KnowBe4 or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedMedium

KnowBe4: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/21/2026, 9:34:16 AM · 1d 0h

09:34 AM10:19 AM
Detection9/21/2026, 9:34:16 AM · 21d ago

Detected — medium severity

KnowBe4: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedHigh

KnowBe4: the vendor reports a critical-impact incident on its own status page. Single origin, not independently confirmed. Users who watch KnowBe4 or have an alert rule on it can be alerted, labelled vendor-reported.

9/17/2026, 10:51:02 PM · 18h 48m

10:51 PM05:39 PM
Detection9/17/2026, 10:51:02 PM · 24d ago

Detected — high severity

KnowBe4: the vendor reports a critical-impact incident on its own status page. Single origin, not independently confirmed. Users who watch KnowBe4 or have an alert rule on it can be alerted, labelled vendor-reported.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment KnowBe4 enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

www.knowbe4.com