Laporan pengguna
0
Mendekati normal. 0 dalam satu jam terakhir. Biasanya sekitar 0 per jam.
Damn, is it down?
Semua layanan / Produktivitas
grasshopper.com · 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 56 min ago. Last stored result reached it in 260 ms.
Semua normal
All Systems Operational Halaman status resmi
| Waktu (UTC) | Laporan | Garis dasar | Latensi | Pengecekan gagal |
|---|---|---|---|---|
| Tue 08 | 0 | 0.0 | 409 ms | 0 |
| Tue 10 | 0 | 0.0 | 333 ms | 0 |
| Tue 13 | 0 | 0.0 | 348 ms | 0 |
| Tue 15 | 0 | 0.0 | 502 ms | 0 |
| Tue 17 | 0 | 0.0 | 633 ms | 0 |
| Tue 19 | 0 | 0.0 | 482 ms | 0 |
| Tue 21 | 0 | 0.0 | 404 ms | 0 |
| Tue 23 | 0 | 0.0 | 771 ms | 0 |
| Wed 01 | 0 | 0.0 | 439 ms | 0 |
| Wed 03 | 0 | 0.0 | 346 ms | 0 |
| Wed 06 | 0 | 0.0 | 242 ms | 0 |
| Wed 08 | 0 | 0.0 | 442 ms | 0 |
| Wed 10 | 0 | 0.0 | 379 ms | 0 |
| Wed 11 | 0 | 0.0 | 530 ms | 0 |
| Wed 13 | 0 | 0.0 | 526 ms | 0 |
| Wed 15 | 0 | 0.0 | 501 ms | 0 |
| Wed 17 | 0 | 0.0 | 205 ms | 0 |
| Wed 19 | 0 | 0.0 | 518 ms | 0 |
| Wed 21 | 0 | 0.0 | 785 ms | 0 |
| Wed 22 | 0 | 0.0 | 240 ms | 0 |
| Thu 00 | 0 | 0.0 | 657 ms | 0 |
| Thu 02 | 0 | 0.0 | 598 ms | 0 |
| Thu 04 | 0 | 0.0 | 580 ms | 0 |
| Thu 06 | 0 | 0.0 | 573 ms | 0 |
| Thu 08 | 0 | 0.0 | 373 ms | 0 |
| Thu 10 | 0 | 0.0 | 405 ms | 0 |
| Thu 12 | 0 | 0.0 | 617 ms | 0 |
| Thu 14 | 0 | 0.0 | 437 ms | 0 |
| Thu 16 | 0 | 0.0 | 695 ms | 0 |
| Thu 18 | 0 | 0.0 | 796 ms | 0 |
| Thu 20 | 0 | 0.0 | 488 ms | 0 |
| Thu 21 | 0 | 0.0 | 570 ms | 0 |
| Thu 23 | 0 | 0.0 | 376 ms | 0 |
| Fri 01 | 0 | 0.0 | 635 ms | 0 |
| Fri 03 | 0 | 0.0 | 382 ms | 0 |
| Fri 06 | 0 | 0.0 | 623 ms | 0 |
| Fri 08 | 0 | 0.0 | 412 ms | 0 |
| Fri 10 | 0 | 0.0 | 372 ms | 0 |
| Fri 11 | 0 | 0.0 | 164 ms | 0 |
| Fri 12 | 0 | 0.0 | 377 ms | 0 |
| Fri 14 | 0 | 0.0 | 360 ms | 0 |
| Fri 16 | 0 | 0.0 | 472 ms | 0 |
| Fri 18 | 0 | 0.0 | 533 ms | 0 |
| Fri 19 | 0 | 0.0 | 873 ms | 0 |
| Fri 20 | 0 | 0.0 | 427 ms | 0 |
| Fri 21 | 0 | 0.0 | 579 ms | 0 |
| Fri 23 | 0 | 0.0 | 374 ms | 0 |
| Sat 01 | 0 | 0.0 | 260 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 11 days of data so far, so the 90-day numbers fill in over time.
Rescue - Maintenance
We will be undergoing scheduled maintenance during this time.
LogMeIn Pro, LogMeIn Central, Hamachi, Join.me, GoToMyPC - Maintenance
As part of our commitment to provide exceptional service and reliability to our customers, GoTo will be conducting a scheduled maintenance affecting LogMeIn Pro and Central, join.me, Hamachi, and GoToMyPC on the date and time listed below. Our team will take all appropriate actions to minimize service interruptions during this event. Date and Time: Saturday, November 14, 2026, 06:30 AM UTC to…
GoTo Products - Scheduled Maintenance
As part of GoTo’s commitment to provide exceptional service and reliability to our customers, we are performing maintenance to improve infrastructure resiliency. During the maintenance, customers may experience increased latency issues and slower response times. GoTo will be conducting service maintenance for all products. Our team will be taking all appropriate actions to minimize service…
Pemeliharaan terencana bukan gangguan. Waktu dan kata-katanya berasal dari vendor. Outage Weather →
Belum ada catatan gangguan untuk Grasshopper. 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 Grasshopper down dan saat pulih kembali. Gratis. Konfirmasi lewat email, berhenti berlangganan kapan saja.
Mau di kanal tim? Kirim peringatan Grasshopper ke Slack, Discord, atau webhook — gratis.
Grasshopper terdaftar di kategori Produktivitas kami dan dicek di grasshopper.com.
Grasshopper menerbitkan halaman status resmi di status.grasshopper.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 11 hari pengecekan. Tidak ada insiden publik yang tercatat sejak pemantauan dimulai 11 hari lalu.
Waktu respons selama 24 jam terakhir: rata-rata 449 ms, rentang 164–873 ms dari 15 pengecekan yang berhasil.
Pengecekan berhasil, laporan pengguna mendekati normal, dan halaman status vendor tidak menunjukkan masalah.
Kami belum mencatat insiden publik Grasshopper sejak pemantauan dimulai 11 hari lalu.
Dari pengecekan kami sendiri: 100% selama 11 hari pengecekan.
Rata-rata 449 ms selama 24 jam terakhir (164–873 ms).
Ya, di https://status.grasshopper.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 Grasshopper di sini secara bersamaan, masalahnya ada di pihak Grasshopper.
Cara kami mendeteksi dan memverifikasi gangguan · Sanggah laporan ini · Kami meninjau sanggahan dalam 24 jam.
Komentar komunitas
Share what you are seeing with Grasshopper. 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.