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 2 hr ago. Last stored result reached it in 36 ms.
Semua normal
All Systems Operational Halaman status resmi
| Waktu (UTC) | Laporan | Garis dasar | Latensi | Pengecekan gagal |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 116 ms | 0 |
| Mon 14 | 0 | 0.0 | 63 ms | 0 |
| Mon 17 | 0 | 0.0 | 122 ms | 0 |
| Mon 19 | 0 | 0.0 | 181 ms | 0 |
| Mon 21 | 0 | 0.0 | 110 ms | 0 |
| Mon 23 | 0 | 0.0 | 136 ms | 0 |
| Tue 01 | 0 | 0.0 | 101 ms | 0 |
| Tue 03 | 0 | 0.0 | 124 ms | 0 |
| Tue 05 | 0 | 0.0 | 85 ms | 0 |
| Tue 08 | 0 | 0.0 | 87 ms | 0 |
| Tue 10 | 0 | 0.0 | 77 ms | 0 |
| Tue 12 | 0 | 0.0 | 95 ms | 0 |
| Tue 14 | 0 | 0.0 | 61 ms | 0 |
| Tue 16 | 0 | 0.0 | 62 ms | 0 |
| Tue 19 | 0 | 0.0 | 125 ms | 0 |
| Tue 21 | 0 | 0.0 | 120 ms | 0 |
| Tue 23 | 0 | 0.0 | 205 ms | 0 |
| Wed 01 | 0 | 0.0 | 100 ms | 0 |
| Wed 04 | 0 | 0.0 | 60 ms | 0 |
| Wed 06 | 0 | 0.0 | 159 ms | 0 |
| Wed 08 | 0 | 0.0 | 95 ms | 0 |
| Wed 10 | 0 | 0.0 | 120 ms | 0 |
| Wed 13 | 0 | 0.0 | 103 ms | 0 |
| Wed 15 | 0 | 0.0 | 69 ms | 0 |
| Wed 17 | 0 | 0.0 | 102 ms | 0 |
| Wed 19 | 0 | 0.0 | 53 ms | 0 |
| Wed 21 | 0 | 0.0 | 103 ms | 0 |
| Wed 23 | 0 | 0.0 | 138 ms | 0 |
| Thu 02 | 0 | 0.0 | 104 ms | 0 |
| Thu 04 | 0 | 0.0 | 122 ms | 0 |
| Thu 06 | 0 | 0.0 | 84 ms | 0 |
| Thu 08 | 0 | 0.0 | 110 ms | 0 |
| Thu 10 | 0 | 0.0 | 26 ms | 0 |
| Thu 12 | 0 | 0.0 | 82 ms | 0 |
| Thu 14 | 0 | 0.0 | 40 ms | 0 |
| Thu 16 | 0 | 0.0 | 199 ms | 0 |
| Thu 18 | 0 | 0.0 | 139 ms | 0 |
| Thu 20 | 0 | 0.0 | 44 ms | 0 |
| Thu 22 | 0 | 0.0 | 104 ms | 0 |
| Fri 00 | 0 | 0.0 | 104 ms | 0 |
| Fri 02 | 0 | 0.0 | 161 ms | 0 |
| Fri 04 | 0 | 0.0 | 38 ms | 0 |
| Fri 06 | 0 | 0.0 | 56 ms | 0 |
| Fri 07 | 0 | 0.0 | 27 ms | 0 |
| Fri 09 | 0 | 0.0 | 20 ms | 0 |
| Fri 11 | 0 | 0.0 | 84 ms | 0 |
| Fri 13 | 0 | 0.0 | 160 ms | 0 |
| Fri 15 | 0 | 0.0 | 36 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 7 days of data so far, so the 90-day numbers fill in over time.
Automatic patching
Automatic patching window where all VM and other components might be patched.
Patching reserved for Simployer
A scheduled maintenance window for our services is about to commence. Simployer reserves this time for patching critical servers that may cause downtime on our services (but not necessarily). Scheduled maintenance is excluded before measuring SLA's. Status updates will be posted to this page, and it is possible to subscribe to updates and get notifications in your channel of choice.
Planned maintenance – Employee Survey
We will perform scheduled maintenance on Tuesday, November 17 at 19:00 (local time). This update includes important security improvements and upgrades to core services in Employee Survey. Impact: Employee Survey will be temporarily unavailable during the maintenance window. We will monitor the system throughout the release and provide updates if needed.
Pemeliharaan terencana bukan gangguan. Waktu dan kata-katanya berasal dari vendor. Outage Weather →
Belum ada catatan gangguan untuk Simployer. 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 Simployer down dan saat pulih kembali. Gratis. Konfirmasi lewat email, berhenti berlangganan kapan saja.
Mau di kanal tim? Kirim peringatan Simployer ke Slack, Discord, atau webhook — gratis.
Simployer terdaftar di kategori Produktivitas kami dan dicek di simployer.com.
Simployer menerbitkan halaman status resmi di status.simployer.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 7 hari pengecekan. Tidak ada insiden publik yang tercatat sejak pemantauan dimulai 7 hari lalu.
Waktu respons selama 24 jam terakhir: rata-rata 81 ms, rentang 20–161 ms dari 12 pengecekan yang berhasil.
Pengecekan berhasil, laporan pengguna mendekati normal, dan halaman status vendor tidak menunjukkan masalah.
Kami belum mencatat insiden publik Simployer sejak pemantauan dimulai 7 hari lalu.
Dari pengecekan kami sendiri: 100% selama 7 hari pengecekan.
Rata-rata 81 ms selama 24 jam terakhir (20–161 ms).
Ya, di https://status.simployer.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 Simployer di sini secara bersamaan, masalahnya ada di pihak Simployer.
Cara kami mendeteksi dan memverifikasi gangguan · Sanggah laporan ini · Kami meninjau sanggahan dalam 24 jam.
Community comments
Share what you are seeing with Simployer. 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.