Reportes de usuarios
0
En niveles normales. 0 en la última hora. Lo habitual son unos 0 por hora.
Damn, is it down?
Todos los servicios / Nube y desarrolladores
cloudsigma.com · Nube y desarrolladores
Las comprobaciones funcionan, los reportes de usuarios están en niveles normales y la página de estado del proveedor no muestra incidencias.
Diagnóstico en directo
Indica la capa más probable (el servicio, tu operador o zona, el DNS o tu Wi-Fi) y te da dos pasos para probar.
Pulsa «Iniciar prueba»Tu navegador prueba el sitio, nuestro servidor y dos resolutores DNS públicos. Nunca guardamos tu IP, solo recuentos anónimos por red y región.
Sin reportes en las últimas 24 horas.
Los puntos representan estados, provincias o países enteros, nunca ubicaciones exactas. Nunca guardamos direcciones IP. Cada reporte con un lugar conocido puede aparecer en el mapa. Se actualiza cada minuto.
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
En niveles normales. 0 en la última hora. Lo habitual son unos 0 por hora.
Accesible
Last checked 8 min ago. Last stored result reached it in 219 ms.
Todo en orden
All Systems Operational Página de estado oficial
| Hora (UTC) | Reportes | Nivel habitual | Latencia | Comprobaciones fallidas |
|---|---|---|---|---|
| 21:30 | 0 | 0.0 | 255 ms | 0 |
| 21:45 | 0 | 0.0 | 275 ms | 0 |
| 22:00 | 0 | 0.0 | 355 ms | 0 |
| 22:15 | 0 | 0.0 | 418 ms | 0 |
| 22:30 | 0 | 0.0 | 235 ms | 0 |
| 22:45 | 0 | 0.0 | 481 ms | 0 |
| 23:00 | 0 | 0.0 | 291 ms | 0 |
| 23:15 | 0 | 0.0 | 256 ms | 0 |
| 23:30 | 0 | 0.0 | 272 ms | 0 |
| 23:45 | 0 | 0.0 | 295 ms | 0 |
| 00:00 | 0 | 0.0 | 323 ms | 0 |
| 00:15 | 0 | 0.0 | 273 ms | 0 |
| 00:30 | 0 | 0.0 | 313 ms | 0 |
| 00:45 | 0 | 0.0 | 341 ms | 0 |
| 01:00 | 0 | 0.0 | 326 ms | 0 |
| 01:15 | 0 | 0.0 | 302 ms | 0 |
| 01:30 | 0 | 0.0 | 206 ms | 0 |
| 01:45 | 0 | 0.0 | 278 ms | 0 |
| 02:00 | 0 | 0.0 | 458 ms | 0 |
| 02:15 | 0 | 0.0 | 295 ms | 0 |
| 02:30 | 0 | 0.0 | 320 ms | 0 |
| 02:45 | 0 | 0.0 | 456 ms | 0 |
| 03:00 | 0 | 0.0 | 303 ms | 0 |
| 03:15 | 0 | 0.0 | 291 ms | 0 |
| 03:30 | 0 | 0.0 | 231 ms | 0 |
| 03:45 | 0 | 0.0 | 225 ms | 0 |
| 04:00 | 0 | 0.0 | 334 ms | 0 |
| 04:15 | 0 | 0.0 | 312 ms | 0 |
| 04:30 | 0 | 0.0 | 436 ms | 0 |
| 04:45 | 0 | 0.0 | 261 ms | 0 |
| 05:00 | 0 | 0.0 | 259 ms | 0 |
| 05:15 | 0 | 0.0 | 194 ms | 0 |
| 05:30 | 0 | 0.0 | 784 ms | 0 |
| 05:45 | 0 | 0.0 | 265 ms | 0 |
| 06:00 | 0 | 0.0 | 330 ms | 0 |
| 06:15 | 0 | 0.0 | 252 ms | 0 |
| 06:30 | 0 | 0.0 | 276 ms | 0 |
| 06:45 | 0 | 0.0 | 213 ms | 0 |
| 07:00 | 0 | 0.0 | 423 ms | 0 |
| 07:15 | 0 | 0.0 | 263 ms | 0 |
| 07:30 | 0 | 0.0 | 373 ms | 0 |
| 07:45 | 0 | 0.0 | 256 ms | 0 |
| 08:00 | 0 | 0.0 | 547 ms | 0 |
| 08:15 | 0 | 0.0 | 216 ms | 0 |
| 08:30 | 0 | 0.0 | 236 ms | 0 |
| 08:45 | 0 | 0.0 | 256 ms | 0 |
| 09:00 | 0 | 0.0 | 248 ms | 0 |
| 09:15 | 0 | 0.0 | 219 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 12 days of data so far, so the 90-day numbers fill in over time.
[TYO] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Tokyo 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…
[CRK] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Clark 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…
[DUS] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Düsseldorf 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…
[DUB] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Dublin 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…
[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.
El mantenimiento planificado no es una caída. Los horarios y el texto son del propio proveedor. Outage Weather →
Aún no hay caídas registradas de Cloudsigma. Las caídas de 10 minutos o más tienen aquí su propia página.
Un reporte por servicio cada 10 minutos desde esta red. Sin cuenta.
Recibe un correo cuando Cloudsigma se caiga y cuando se recupere. Gratis. Confirmación por correo; puedes darte de baja cuando quieras.
¿Lo quieres en un canal del equipo? Enviar alertas de Cloudsigma a Slack, Discord o un webhook — gratis.
Cloudsigma figura en nuestra categoría Nube y desarrolladores y se comprueba en cloudsigma.com.
Cloudsigma publica una página de estado oficial en status.cloudsigma.com; cuando podemos leerla, su nivel de incidente se incluye en el estado que mostramos aquí.
Problemas habituales en los servicios de Nube y desarrolladores: errores de API, despliegues o compilaciones fallidos y caídas del panel o la consola.
Disponibilidad medida con nuestras comprobaciones: 100% en 12 días de comprobaciones. No se han registrado incidentes públicos desde que empezó la monitorización hace 12 días.
Tiempo de respuesta en las últimas 24 horas: 310 ms de media, rango de 94–784 ms en 180 comprobaciones correctas.
Las comprobaciones funcionan, los reportes de usuarios están en niveles normales y la página de estado del proveedor no muestra incidencias.
No hemos registrado ningún incidente público de Cloudsigma desde que empezó la monitorización hace 12 días.
Según nuestras propias comprobaciones: 100% en 12 días de comprobaciones.
310 ms de media en las últimas 24 horas (94–784 ms).
Sí, en https://status.cloudsigma.com.
Normalmente es algo local: prueba otro navegador o la app, cambia entre wifi y datos móviles y borra la caché. En los servicios de Nube y desarrolladores, fíjate en errores de API, despliegues o compilaciones fallidos y caídas del panel o la consola. Si mucha gente reporta Cloudsigma aquí a la vez, el problema es de Cloudsigma.
Cómo detectamos y verificamos caídas · Disputar este informe · Revisamos las disputas en un plazo de 24 horas.
Community comments
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.