Laporan pengguna
0
Mendekati normal. 0 dalam satu jam terakhir. Biasanya sekitar 0 per jam.
Damn, is it down?
Semua layanan / Produktivitas
Pengecekan berhasil, laporan pengguna mendekati normal, dan halaman status vendor tidak menunjukkan masalah.
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.
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 3 min ago. Last stored result reached it in 630 ms.
Semua normal
All Systems Operational Halaman status resmi
| Waktu (UTC) | Laporan | Garis dasar | Latensi | Pengecekan gagal |
|---|---|---|---|---|
| 20:15 | 0 | 0.0 | 813 ms | 0 |
| 20:30 | 0 | 0.0 | 636 ms | 0 |
| 20:45 | 0 | 0.0 | 682 ms | 0 |
| 21:00 | 0 | 0.0 | 589 ms | 0 |
| 21:15 | 0 | 0.0 | 596 ms | 0 |
| 21:30 | 0 | 0.0 | 767 ms | 0 |
| 21:45 | 0 | 0.0 | 629 ms | 0 |
| 22:00 | 0 | 0.0 | 698 ms | 0 |
| 22:15 | 0 | 0.0 | 608 ms | 0 |
| 22:30 | 0 | 0.0 | 770 ms | 0 |
| 22:45 | 0 | 0.0 | 650 ms | 0 |
| 23:00 | 0 | 0.0 | 633 ms | 0 |
| 23:15 | 0 | 0.0 | 1087 ms | 0 |
| 23:30 | 0 | 0.0 | 607 ms | 0 |
| 23:45 | 0 | 0.0 | 626 ms | 0 |
| 00:00 | 0 | 0.0 | 693 ms | 0 |
| 00:15 | 0 | 0.0 | 542 ms | 0 |
| 00:30 | 0 | 0.0 | 585 ms | 0 |
| 00:45 | 0 | 0.0 | 569 ms | 0 |
| 01:00 | 0 | 0.0 | 605 ms | 0 |
| 01:15 | 0 | 0.0 | 614 ms | 0 |
| 01:30 | 0 | 0.0 | 547 ms | 0 |
| 01:45 | 0 | 0.0 | 591 ms | 0 |
| 02:00 | 0 | 0.0 | 506 ms | 0 |
| 02:15 | 0 | 0.0 | 604 ms | 0 |
| 02:30 | 0 | 0.0 | 619 ms | 0 |
| 02:45 | 0 | 0.0 | 561 ms | 0 |
| 03:00 | 0 | 0.0 | 623 ms | 0 |
| 03:15 | 0 | 0.0 | 600 ms | 0 |
| 03:30 | 0 | 0.0 | 569 ms | 0 |
| 03:45 | 0 | 0.0 | 636 ms | 0 |
| 04:00 | 0 | 0.0 | 619 ms | 0 |
| 04:15 | 0 | 0.0 | 600 ms | 0 |
| 04:30 | 0 | 0.0 | 614 ms | 0 |
| 04:45 | 0 | 0.0 | 587 ms | 0 |
| 05:00 | 0 | 0.0 | 711 ms | 0 |
| 05:15 | 0 | 0.0 | 725 ms | 0 |
| 05:30 | 0 | 0.0 | 535 ms | 0 |
| 05:45 | 0 | 0.0 | 642 ms | 0 |
| 06:00 | 0 | 0.0 | 632 ms | 0 |
| 06:15 | 0 | 0.0 | 549 ms | 0 |
| 06:30 | 0 | 0.0 | 565 ms | 0 |
| 06:45 | 0 | 0.0 | 611 ms | 0 |
| 07:00 | 0 | 0.0 | 557 ms | 0 |
| 07:15 | 0 | 0.0 | 600 ms | 0 |
| 07:30 | 0 | 0.0 | 524 ms | 0 |
| 07:45 | 0 | 0.0 | 677 ms | 0 |
| 08:00 | 0 | 0.0 | 603 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 13 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 13 hari pengecekan. Kami mencatat 1 insiden publik sejak pemantauan dimulai 13 hari lalu.
Waktu respons selama 24 jam terakhir: rata-rata 655 ms, rentang 455–1537 ms dari 209 pengecekan yang berhasil.
Pengecekan berhasil, laporan pengguna mendekati normal, dan halaman status vendor tidak menunjukkan masalah.
Insiden publik terbaru yang kami catat dimulai 2026-11-06 dan berlangsung 56 mnt. 1 insiden sejak pemantauan dimulai 13 hari lalu.
Dari pengecekan kami sendiri: 100% selama 13 hari pengecekan.
Rata-rata 655 ms selama 24 jam terakhir (455–1537 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.
Komentar komunitas
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.