Laporan pengguna
0
Mendekati normal. 0 dalam satu jam terakhir. Biasanya sekitar 0 per jam.
Damn, is it down?
Semua layanan / Cloud & developer
cloudsigma.com · Cloud & developer
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 141 ms.
Semua normal
All Systems Operational Halaman status resmi
| Waktu (UTC) | Laporan | Garis dasar | Latensi | Pengecekan gagal |
|---|---|---|---|---|
| 14:00 | 0 | 0.0 | 292 ms | 0 |
| 14:15 | 0 | 0.0 | 256 ms | 0 |
| 14:30 | 0 | 0.0 | 254 ms | 0 |
| 14:45 | 0 | 0.0 | 258 ms | 0 |
| 15:00 | 0 | 0.0 | 204 ms | 0 |
| 15:15 | 0 | 0.0 | 294 ms | 0 |
| 15:30 | 0 | 0.0 | 273 ms | 0 |
| 15:45 | 0 | 0.0 | 258 ms | 0 |
| 16:00 | 0 | 0.0 | 278 ms | 0 |
| 16:15 | 0 | 0.0 | 329 ms | 0 |
| 16:30 | 0 | 0.0 | 265 ms | 0 |
| 16:45 | 0 | 0.0 | 428 ms | 0 |
| 17:00 | 0 | 0.0 | 302 ms | 0 |
| 17:15 | 0 | 0.0 | 230 ms | 0 |
| 17:45 | 0 | 0.0 | 318 ms | 0 |
| 18:00 | 0 | 0.0 | 261 ms | 0 |
| 18:15 | 0 | 0.0 | 255 ms | 0 |
| 18:30 | 0 | 0.0 | 296 ms | 0 |
| 18:45 | 0 | 0.0 | 302 ms | 0 |
| 19:00 | 0 | 0.0 | 243 ms | 0 |
| 19:15 | 0 | 0.0 | 210 ms | 0 |
| 19:30 | 0 | 0.0 | 255 ms | 0 |
| 19:45 | 0 | 0.0 | 288 ms | 0 |
| 20:00 | 0 | 0.0 | 295 ms | 0 |
| 20:15 | 0 | 0.0 | 328 ms | 0 |
| 20:30 | 0 | 0.0 | 373 ms | 0 |
| 20:45 | 0 | 0.0 | 253 ms | 0 |
| 21:00 | 0 | 0.0 | 237 ms | 0 |
| 21:15 | 0 | 0.0 | 490 ms | 0 |
| 21:30 | 0 | 0.0 | 274 ms | 0 |
| 21:45 | 0 | 0.0 | 298 ms | 0 |
| 22:00 | 0 | 0.0 | 266 ms | 0 |
| 22:15 | 0 | 0.0 | 261 ms | 0 |
| 22:30 | 0 | 0.0 | 355 ms | 0 |
| 22:45 | 0 | 0.0 | 252 ms | 0 |
| 23:00 | 0 | 0.0 | 195 ms | 0 |
| 23:15 | 0 | 0.0 | 298 ms | 0 |
| 23:30 | 0 | 0.0 | 251 ms | 0 |
| 23:45 | 0 | 0.0 | 250 ms | 0 |
| 00:00 | 0 | 0.0 | 248 ms | 0 |
| 00:15 | 0 | 0.0 | 372 ms | 0 |
| 00:30 | 0 | 0.0 | 327 ms | 0 |
| 00:45 | 0 | 0.0 | 232 ms | 0 |
| 01:00 | 0 | 0.0 | 286 ms | 0 |
| 01:15 | 0 | 0.0 | 249 ms | 0 |
| 01:30 | 0 | 0.0 | 211 ms | 0 |
| 01:45 | 0 | 0.0 | 193 ms | 0 |
| 02:00 | 0 | 0.0 | 221 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.
[GVA] API Server Maintenance
CloudSigma would like to inform you of scheduled maintenance on the API server in our Geneva/Zurich cloud location. The purpose of this maintenance is to complete the decommissioning of the former API endpoint, zrh.cloudsigma.com, following the migration to gva.cloudsigma.com on 19 September 2026. This maintenance will ensure that all API requests are handled exclusively through the new…
[RUH] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform an emergency maintenance of our API server in the Riyadh cloud location. IMPACT: There will be no impact on already existing/running customer’s virtual machines, hosts, network accessibility, and/or any other running services. During the maintenance, customers will not be able to perform any calls to the API, directly or through…
[MNL2] Network Maintenance
CloudSigma would like to inform you that we are planning to perform a scheduled maintenance of our Network infrastructure of the Manila 2 cloud. More precisely, we will be performing upgrades on the routers supporting the cloud. IMPACT: There will be no impact on already existing/running customers’ virtual machines, hosts, network accessibility, and/or any other running services.
[MNL2] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Manila 2 cloud location. The maintenance is required to address a critical security vulnerability and ensure the continued security and reliability of our services. IMPACT: There will be no impact on already existing/running customer’s virtual machines, hosts, network accessibility…
[PER] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Perth cloud location. The maintenance is required to address a critical security vulnerability and ensure the continued security and reliability of our services. IMPACT: There will be no impact on already existing/running customer’s virtual machines, hosts, network accessibility…
[CAI] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Cairo cloud location. The maintenance is required to address a critical security vulnerability and ensure the continued security and reliability of our services. IMPACT: There will be no impact on already existing/running customer’s virtual machines, hosts, network accessibility…
[FRA] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Frankfurt cloud location. The maintenance is required to address a critical security vulnerability and ensure the continued security and reliability of our services. IMPACT: There will be no impact on already existing/running customer’s virtual machines, hosts, network accessibility…
[MNL2] Network Maintenance
CloudSigma would like to inform you that we are planning to perform a scheduled maintenance of our Network infrastructure of the Manila 2 cloud. More precisely, we will be performing upgrades on the routers supporting the cloud. IMPACT: There will be no impact on already existing/running customers’ virtual machines, hosts, network accessibility, and/or any other running services.
[JHB] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Johor cloud location. The maintenance is required to address a critical security vulnerability and ensure the continued security and reliability of our services. IMPACT: There will be no impact on already existing/running customer’s virtual machines, hosts, network accessibility…
[FRA] Storage Cluster Maintenance
CloudSigma would like to inform you that we are planning to do scheduled maintenance of our storage cluster in the Frankfurt cloud location. The maintenance aims to perform OS upgrades of the storage nodes sustaining the cloud's storage cluster. IMPACT: There will be no service impact, except a slight increase in the I/O operations.
[FRA] Storage Cluster Maintenance - Stage 2
CloudSigma would like to inform you that we are planning to do scheduled maintenance of our storage cluster in the Frankfurt cloud location. The maintenance aims to perform OS upgrades of the storage nodes sustaining the cloud's storage cluster. IMPACT: There will be no service impact, except a slight increase in the I/O operations.
[MNL] Network Maintenance
CloudSigma would like to inform you that we are planning to perform a scheduled maintenance of our Network infrastructure of the Manila cloud. More precisely, we will be performing upgrades on the routers supporting the cloud. IMPACT: There will be no impact on already existing/running customers’ virtual machines, hosts, network accessibility, and/or any other running services.
Pemeliharaan terencana bukan gangguan. Waktu dan kata-katanya berasal dari vendor. Outage Weather →
Belum ada catatan gangguan untuk Cloudsigma. 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 Cloudsigma down dan saat pulih kembali. Gratis. Konfirmasi lewat email, berhenti berlangganan kapan saja.
Mau di kanal tim? Kirim peringatan Cloudsigma ke Slack, Discord, atau webhook — gratis.
Cloudsigma terdaftar di kategori Cloud & developer kami dan dicek di cloudsigma.com.
Cloudsigma menerbitkan halaman status resmi di status.cloudsigma.com; jika dapat kami baca, tingkat insidennya ikut diperhitungkan dalam status yang ditampilkan di sini.
Masalah umum pada layanan Cloud & developer: galat API, deploy atau build gagal, serta dashboard atau konsol yang down.
Uptime terukur dari pengecekan kami: 100% selama 13 hari pengecekan. Tidak ada insiden publik yang tercatat sejak pemantauan dimulai 13 hari lalu.
Waktu respons selama 24 jam terakhir: rata-rata 287 ms, rentang 79–784 ms dari 198 pengecekan yang berhasil.
Pengecekan berhasil, laporan pengguna mendekati normal, dan halaman status vendor tidak menunjukkan masalah.
Kami belum mencatat insiden publik Cloudsigma sejak pemantauan dimulai 13 hari lalu.
Dari pengecekan kami sendiri: 100% selama 13 hari pengecekan.
Rata-rata 287 ms selama 24 jam terakhir (79–784 ms).
Ya, di https://status.cloudsigma.com.
Biasanya masalahnya lokal: coba browser lain atau aplikasinya, beralih antara Wi-Fi dan data seluler, lalu hapus cache. Untuk layanan Cloud & developer, perhatikan galat API, deploy atau build gagal, serta dashboard atau konsol yang down. Jika banyak orang melaporkan Cloudsigma di sini secara bersamaan, masalahnya ada di pihak Cloudsigma.
Cara kami mendeteksi dan memverifikasi gangguan · Sanggah laporan ini · Kami meninjau sanggahan dalam 24 jam.
Komentar komunitas
Share what you are seeing with Cloudsigma. 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.