User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
knowbe4.com · Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 713 ms · 4 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 512 ms | 0 |
| 03:15 | 0 | 0.0 | 616 ms | 0 |
| 03:30 | 0 | 0.0 | 596 ms | 0 |
| 03:45 | 0 | 0.0 | 751 ms | 0 |
| 04:00 | 0 | 0.0 | 742 ms | 0 |
| 04:15 | 0 | 0.0 | 669 ms | 0 |
| 04:30 | 0 | 0.0 | 835 ms | 0 |
| 04:45 | 0 | 0.0 | 594 ms | 0 |
| 05:00 | 0 | 0.0 | 688 ms | 0 |
| 05:15 | 0 | 0.0 | 600 ms | 0 |
| 05:30 | 0 | 0.0 | 563 ms | 0 |
| 05:45 | 0 | 0.0 | 559 ms | 0 |
| 06:00 | 0 | 0.0 | 719 ms | 0 |
| 06:15 | 0 | 0.0 | 690 ms | 0 |
| 06:30 | 0 | 0.0 | 952 ms | 0 |
| 06:45 | 0 | 0.0 | 699 ms | 0 |
| 07:00 | 0 | 0.0 | 659 ms | 0 |
| 07:15 | 0 | 0.0 | 662 ms | 0 |
| 07:30 | 0 | 0.0 | 762 ms | 0 |
| 07:45 | 0 | 0.0 | 535 ms | 0 |
| 08:00 | 0 | 0.0 | 785 ms | 0 |
| 08:15 | 0 | 0.0 | 636 ms | 0 |
| 08:30 | 0 | 0.0 | 564 ms | 0 |
| 08:45 | 0 | 0.0 | 656 ms | 0 |
| 09:00 | 0 | 0.0 | 737 ms | 0 |
| 09:15 | 0 | 0.0 | 704 ms | 0 |
| 09:30 | 0 | 0.0 | 787 ms | 0 |
| 09:45 | 0 | 0.0 | 908 ms | 0 |
| 10:00 | 0 | 0.0 | 830 ms | 0 |
| 10:15 | 0 | 0.0 | 773 ms | 0 |
| 10:30 | 0 | 0.0 | 818 ms | 0 |
| 10:45 | 0 | 0.0 | 918 ms | 0 |
| 11:00 | 0 | 0.0 | 504 ms | 0 |
| 11:15 | 0 | 0.0 | 649 ms | 0 |
| 11:30 | 0 | 0.0 | 825 ms | 0 |
| 11:45 | 0 | 0.0 | 766 ms | 0 |
| 12:00 | 0 | 0.0 | 790 ms | 0 |
| 12:15 | 0 | 0.0 | 713 ms | 0 |
| 12:30 | 0 | 0.0 | 686 ms | 0 |
| 12:45 | 0 | 0.0 | 662 ms | 0 |
| 13:00 | 0 | 0.0 | 658 ms | 0 |
| 13:15 | 0 | 0.0 | 1007 ms | 0 |
| 13:30 | 0 | 0.0 | 713 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for KnowBe4 yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when KnowBe4 goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send KnowBe4 alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If KnowBe4 is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on KnowBe4's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.