Laporan pengguna
0
Mendekati normal. 0 dalam satu jam terakhir. Biasanya sekitar 0 per jam.
Damn, is it down?
Semua layanan / Produktivitas
forcepoint.com · Produktivitas
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Status resmi: Web Security Cloud: Connectivity issues for Windows users using NTLM authentication
Sumber: halaman status vendor · Kami tidak berafiliasi dengan Forcepoint ONE.
Perkiraan perbaikan: Not enough Forcepoint ONE history yet; similar Productivity outages lasted 41 min (median, typically 9 min–3 h; 28 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 57 ms.
Insiden kecil
Web Security Cloud: Connectivity issues for Windows users using NTLM authentication Halaman status resmi
| Waktu (UTC) | Laporan | Garis dasar | Latensi | Pengecekan gagal |
|---|---|---|---|---|
| 20:45 | 0 | 0.0 | 205 ms | 0 |
| 21:00 | 0 | 0.0 | 79 ms | 0 |
| 21:15 | 0 | 0.0 | 56 ms | 0 |
| 21:30 | 0 | 0.0 | 77 ms | 0 |
| 21:45 | 0 | 0.0 | 85 ms | 0 |
| 22:00 | 0 | 0.0 | 76 ms | 0 |
| 22:15 | 0 | 0.0 | 68 ms | 0 |
| 22:30 | 0 | 0.0 | 164 ms | 0 |
| 22:45 | 0 | 0.0 | 149 ms | 0 |
| 23:15 | 0 | 0.0 | 376 ms | 0 |
| 23:30 | 0 | 0.0 | 116 ms | 0 |
| 23:45 | 0 | 0.0 | 76 ms | 0 |
| 00:00 | 0 | 0.0 | 197 ms | 0 |
| 00:15 | 0 | 0.0 | 96 ms | 0 |
| 00:30 | 0 | 0.0 | 238 ms | 0 |
| 00:45 | 0 | 0.0 | 99 ms | 0 |
| 01:00 | 0 | 0.0 | 60 ms | 0 |
| 01:15 | 0 | 0.0 | 52 ms | 0 |
| 01:30 | 0 | 0.0 | 354 ms | 0 |
| 01:45 | 0 | 0.0 | 113 ms | 0 |
| 02:00 | 0 | 0.0 | 162 ms | 0 |
| 02:15 | 0 | 0.0 | 198 ms | 0 |
| 02:30 | 0 | 0.0 | 189 ms | 0 |
| 02:45 | 0 | 0.0 | 197 ms | 0 |
| 03:00 | 0 | 0.0 | 205 ms | 0 |
| 03:15 | 0 | 0.0 | 140 ms | 0 |
| 03:30 | 0 | 0.0 | 193 ms | 0 |
| 04:00 | 0 | 0.0 | 196 ms | 0 |
| 04:15 | 0 | 0.0 | 294 ms | 0 |
| 04:30 | 0 | 0.0 | 60 ms | 0 |
| 04:45 | 0 | 0.0 | 239 ms | 0 |
| 05:00 | 0 | 0.0 | 185 ms | 0 |
| 05:15 | 0 | 0.0 | 79 ms | 0 |
| 05:30 | 0 | 0.0 | 208 ms | 0 |
| 05:45 | 0 | 0.0 | 86 ms | 0 |
| 06:00 | 0 | 0.0 | 200 ms | 0 |
| 06:30 | 0 | 0.0 | 113 ms | 0 |
| 06:45 | 0 | 0.0 | 167 ms | 0 |
| 07:00 | 0 | 0.0 | 184 ms | 0 |
| 07:15 | 0 | 0.0 | 191 ms | 0 |
| 07:30 | 0 | 0.0 | 64 ms | 0 |
| 07:45 | 0 | 0.0 | 138 ms | 0 |
| 08:00 | 0 | 0.0 | 63 ms | 0 |
| 08:15 | 0 | 0.0 | 108 ms | 0 |
| 08:30 | 0 | 0.0 | 99 ms | 0 |
| 08:45 | 0 | 0.0 | 88 ms | 0 |
| 09:00 | 0 | 0.0 | 71 ms | 0 |
| 09:15 | 0 | 0.0 | 165 ms | 0 |
99.91% 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.
Planned Maintenance - AUHA vPoP in Frankfurt (Cluster-B) Data Center
Forcepoint will be conducting a planned maintenance in our Frankfurt (Cluster-B) data center on Sunday, November 15th at 03:30 AM UTC for approximately 24 hours. The maintenance activity will involve moving the AUHA vPoP from Frankfurt (Cluster-B) to Riyadh (Cluster-RUHA) to reduce latency for customer requests and provide improved performance of our Cloud services. Riyadh (Cluster-RUHA) data…
Pemeliharaan terencana bukan gangguan. Waktu dan kata-katanya berasal dari vendor. Outage Weather →
Belum ada catatan gangguan untuk Forcepoint ONE. Gangguan selama 10 menit atau lebih mendapat halaman sendiri di sini.
Satu laporan per layanan setiap 10 menit dari jaringan ini. Tanpa akun.
Dapatkan email saat Forcepoint ONE down dan saat pulih kembali. Gratis. Konfirmasi lewat email, berhenti berlangganan kapan saja.
Mau di kanal tim? Kirim peringatan Forcepoint ONE ke Slack, Discord, atau webhook — gratis.
Forcepoint ONE terdaftar di kategori Produktivitas kami dan dicek di forcepoint.com.
Forcepoint ONE menerbitkan halaman status resmi di csg.status.forcepoint.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: 99.91% selama 13 hari pengecekan. Tidak ada insiden publik yang tercatat sejak pemantauan dimulai 13 hari lalu.
Waktu respons selama 24 jam terakhir: rata-rata 134 ms, rentang 31–567 ms dari 175 pengecekan yang berhasil.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Status resmi: Web Security Cloud: Connectivity issues for Windows users using NTLM authentication
Kami belum mencatat insiden publik Forcepoint ONE sejak pemantauan dimulai 13 hari lalu.
Dari pengecekan kami sendiri: 99.91% selama 13 hari pengecekan.
Rata-rata 134 ms selama 24 jam terakhir (31–567 ms).
Ya, di https://csg.status.forcepoint.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 Forcepoint ONE di sini secara bersamaan, masalahnya ada di pihak Forcepoint ONE.
Cara kami mendeteksi dan memverifikasi gangguan · Sanggah laporan ini · Kami meninjau sanggahan dalam 24 jam.
Komentar komunitas
Share what you are seeing with Forcepoint ONE. 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.