Laporan pengguna
0
Mendekati normal. 0 dalam satu jam terakhir. Biasanya sekitar 0 per jam.
Damn, is it down?
Semua layanan / Produktivitas
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Status resmi: PAB, PhishER, Prevent, Protect & Defend Degraded Performance
Sumber: halaman status vendor · Kami tidak berafiliasi dengan KnowBe4.
Perkiraan perbaikan: Not enough KnowBe4 history yet; similar Productivity outages lasted 41 min (median, typically 11 min–5 h; 26 outages).
Diagnosis langsung
Menunjukkan lapisan yang paling mungkin (layanan, ISP atau areamu, DNS, atau Wi-Fi-mu) dan memberi dua langkah untuk dicoba.
Tekan Jalankan tesBrowsermu menguji situs tersebut, server kami, dan dua resolver DNS publik. Kami tidak pernah menyimpan IP-mu; hanya hitungan anonim per jaringan dan wilayah.
Reachable from all 4 regions we check from.
Tidak ada laporan dalam 24 jam terakhir.
Titik mewakili seluruh negara bagian, provinsi, atau negara, bukan lokasi persis. Kami tidak pernah menyimpan alamat IP. Setiap laporan dengan tempat yang diketahui dapat muncul di peta. Diperbarui setiap menit.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Mendekati normal. 0 dalam satu jam terakhir. Biasanya sekitar 0 per jam.
Dapat dijangkau
Last checked 8 min ago. Last stored result reached it in 663 ms.
Insiden kecil
PAB, PhishER, Prevent, Protect & Defend Degraded Performance Halaman status resmi
| Waktu (UTC) | Laporan | Garis dasar | Latensi | Pengecekan gagal |
|---|---|---|---|---|
| 21:30 | 0 | 0.0 | 626 ms | 0 |
| 21:45 | 0 | 0.0 | 726 ms | 0 |
| 22:00 | 0 | 0.0 | 1066 ms | 0 |
| 22:15 | 0 | 0.0 | 717 ms | 0 |
| 22:30 | 0 | 0.0 | 618 ms | 0 |
| 22:45 | 0 | 0.0 | 612 ms | 0 |
| 23:00 | 0 | 0.0 | 826 ms | 0 |
| 23:15 | 0 | 0.0 | 630 ms | 0 |
| 23:30 | 0 | 0.0 | 683 ms | 0 |
| 23:45 | 0 | 0.0 | 641 ms | 0 |
| 00:00 | 0 | 0.0 | 698 ms | 0 |
| 00:15 | 0 | 0.0 | 742 ms | 0 |
| 00:30 | 0 | 0.0 | 640 ms | 0 |
| 00:45 | 0 | 0.0 | 574 ms | 0 |
| 01:00 | 0 | 0.0 | 653 ms | 0 |
| 01:15 | 0 | 0.0 | 726 ms | 0 |
| 01:30 | 0 | 0.0 | 657 ms | 0 |
| 01:45 | 0 | 0.0 | 602 ms | 0 |
| 02:00 | 0 | 0.0 | 675 ms | 0 |
| 02:15 | 0 | 0.0 | 560 ms | 0 |
| 02:30 | 0 | 0.0 | 636 ms | 0 |
| 02:45 | 0 | 0.0 | 673 ms | 0 |
| 03:00 | 0 | 0.0 | 604 ms | 0 |
| 03:15 | 0 | 0.0 | 705 ms | 0 |
| 03:30 | 0 | 0.0 | 652 ms | 0 |
| 03:45 | 0 | 0.0 | 597 ms | 0 |
| 04:00 | 0 | 0.0 | 652 ms | 0 |
| 04:15 | 0 | 0.0 | 651 ms | 0 |
| 04:30 | 0 | 0.0 | 690 ms | 0 |
| 04:45 | 0 | 0.0 | 728 ms | 0 |
| 05:00 | 0 | 0.0 | 583 ms | 0 |
| 05:15 | 0 | 0.0 | 610 ms | 0 |
| 05:30 | 0 | 0.0 | 623 ms | 0 |
| 05:45 | 0 | 0.0 | 603 ms | 0 |
| 06:00 | 0 | 0.0 | 692 ms | 0 |
| 06:15 | 0 | 0.0 | 641 ms | 0 |
| 06:30 | 0 | 0.0 | 645 ms | 0 |
| 06:45 | 0 | 0.0 | 678 ms | 0 |
| 07:00 | 0 | 0.0 | 681 ms | 0 |
| 07:15 | 0 | 0.0 | 641 ms | 0 |
| 07:30 | 0 | 0.0 | 583 ms | 0 |
| 07:45 | 0 | 0.0 | 602 ms | 0 |
| 08:00 | 0 | 0.0 | 605 ms | 0 |
| 08:15 | 0 | 0.0 | 560 ms | 0 |
| 08:30 | 0 | 0.0 | 678 ms | 0 |
| 08:45 | 0 | 0.0 | 639 ms | 0 |
| 09:00 | 0 | 0.0 | 599 ms | 0 |
| 09:15 | 0 | 0.0 | 642 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 12 days of data so far, so the 90-day numbers fill in over time.
Secure Workspace Scheduled Maintenance (UK)
We will be performing maintenance work on a subset of Secure Workspace instances in the UK South region on November 16th, 2026 from 19:00 - 21:00 UTC. During this maintenance you may experience a service disruption of up to 60 minutes.
Secure Workspace Scheduled Maintenance (UK)
We will be performing maintenance work on a subset of Secure Workspace instances in the UK South region on November 17th, 2026 from 19:00 - 21:00 UTC. During this maintenance you may experience a service disruption of up to 60 minutes.
Secure Workspace Scheduled Maintenance (UK)
We will be performing maintenance work on a subset of Secure Workspace instances in the UK South region on November 18th, 2026 from 19:00 - 21:00 UTC. During this maintenance you may experience a service disruption of up to 60 minutes.
Secure Workspace Scheduled Maintenance (UK)
We will be performing maintenance work on a subset of Secure Workspace instances in the UK South region on November 19th, 2026 from 19:00 - 21:00 UTC. During this maintenance you may experience a service disruption of up to 60 minutes.
Pemeliharaan terencana bukan gangguan. Waktu dan kata-katanya berasal dari vendor. Outage Weather →
Satu laporan per layanan setiap 10 menit dari jaringan ini. Tanpa akun.
Dapatkan email saat KnowBe4 down dan saat pulih kembali. Gratis. Konfirmasi lewat email, berhenti berlangganan kapan saja.
Mau di kanal tim? Kirim peringatan KnowBe4 ke Slack, Discord, atau webhook — gratis.
KnowBe4 terdaftar di kategori Produktivitas kami dan dicek di knowbe4.com.
KnowBe4 menerbitkan halaman status resmi di status.knowbe4.com; jika dapat kami baca, tingkat insidennya ikut diperhitungkan dalam status yang ditampilkan di sini.
Masalah umum pada layanan Produktivitas: file tidak tersinkron, editor tidak termuat, dan masalah login.
Uptime terukur dari pengecekan kami: 100% selama 12 hari pengecekan. Kami mencatat 1 insiden publik sejak pemantauan dimulai 12 hari lalu.
Waktu respons selama 24 jam terakhir: rata-rata 690 ms, rentang 506–1378 ms dari 179 pengecekan yang berhasil.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Status resmi: PAB, PhishER, Prevent, Protect & Defend Degraded Performance
Insiden publik terbaru yang kami catat dimulai 2026-11-06 dan berlangsung 56 mnt. 1 insiden sejak pemantauan dimulai 12 hari lalu.
Dari pengecekan kami sendiri: 100% selama 12 hari pengecekan.
Rata-rata 690 ms selama 24 jam terakhir (506–1378 ms).
Ya, di https://status.knowbe4.com.
Biasanya masalahnya lokal: coba browser lain atau aplikasinya, beralih antara Wi-Fi dan data seluler, lalu hapus cache. Untuk layanan Produktivitas, perhatikan file tidak tersinkron, editor tidak termuat, dan masalah login. Jika banyak orang melaporkan KnowBe4 di sini secara bersamaan, masalahnya ada di pihak KnowBe4.
Cara kami mendeteksi dan memverifikasi gangguan · Sanggah laporan ini · Kami meninjau sanggahan dalam 24 jam.
Community comments
Share what you are seeing with KnowBe4. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.