Última comprobación
Secure compliant cloud platform for rapid deployment of modern web applications.
¿Tienes algún problema?
¿Cloudgov está caído?
Estado no disponible
Comparte tu experiencia para mantener informados a los demás.
Verificación del estado pendiente
The latest official observation is not fresh enough to confirm current service health.
Estado oficial del proveedor0 reportes individuales en las últimas 24 horas. Esta lista incluye importaciones históricas; los agregados de fuentes externas se muestran en el gráfico.
Observaciones del estado oficial, no mediciones directas de disponibilidad.
Los incidentes oficiales, las alertas tempranas y los reportes de la comunidad se identifican por separado. Las alertas tempranas abarcan las últimas 24 horas. Las fechas usan tu zona horaria.
| Nombre del incidente | Duración | InicioUTC | Confirmación oficial | Gravedad |
|---|---|---|---|---|
| 0m | Sí | Desconocido | ||
| 19h 34m | Sí | Desconocido | ||
| 1h 19m | Sí | Desconocido | ||
| 17h 26m | Sí | Desconocido | ||
| 0m | Sí | Desconocido | ||
| 45h 7m | Sí | Leve | ||
| 0m | Sí | Desconocido | ||
| 302h 45m | Sí | Desconocido |
Uptimus supervisa Cloudgov mediante su fuente oficial y normaliza incidencias, mantenimiento y componentes en un estado coherente.
Esta página incluye actualmente 43 componentes supervisados, 51 incidencias, 57 mantenimientos y 8 días de historial conocido.
Uptimus es un servicio independiente y no está afiliado con Cloudgov. Un estado saludable no garantiza que todos los usuarios, dispositivos o regiones estén libres de problemas.
Recibe alertas cuando Cloudgov o uno de sus componentes supervisados informa de una interrupción grave o crítica. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas. El historial disponible contiene 51 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «Partial outage for the SES Service Broker».
Recibe alertas sobre rendimiento degradado, impacto parcial e incidencias que no representan una interrupción completa. Uptimus supervisa actualmente 43 componentes de Cloudgov: Application logs - Intake and storage, Applications, Dashboard, GitHub. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.
Trabajos programados publicados por el proveedor oficial.
Cloud.gov is retiring the Cloud Foundry API (CAPI) V2 on Tuesday, February 2, 2027. As we announced on January 7, 2025 ( https://docs.cloud.gov/news/2025/01/02/v2api-deprecation ), we are retiring version 2 of Cloud Foundry API (CAPI V2), and will soon use only version 3 of the API (CAPI V3). Over the last 20 months, our Cloud.gov community has done a terrific job in adopting CAPI V3, and CAPI V2 only accounts for 0.15% of all our CAPI traffic. On February 2, 2027, CAPI V2 will be permanently disabled on Cloud.gov. Tools that depend on V2, including CF CLI v6 and v7, will stop working and will not work again. Ahead of that date, Cloud.gov will run four scheduled brownouts: temporary, planned windows during which we disable V2 endpoints so you can discover if any of your tools depend on them – while there is still time to fix them. Service returns to normal at the end of each window. As a customer, you need to: Check that you are using V3 compatible tooling (see below) Test your deployment and other automated processes during the V2 brownouts to see if anything breaks -- indicating a possible V2 dependency. Brownout schedule Window #1 - Wed Oct 14, 2026 - 8:00 AM EDT thru Wed Oct 14, 2026, 2:00 PM EDT - length 6 hours Window #2 - Wed Oct 28, 2026 - 8:00 AM EDT thru Wed Oct 28, 2026, 2:00 PM EDT - length 6 hours Window #3 - Tue Nov 17, 2026 - 8:00 AM EST thru Wed Nov 18, 2026, 2:00 PM EST - length 30 hours Window #4 - Tue Dec 1, 2026 - 8:00 AM EST thru Thu Dec 3, 2026, 2:00 PM EST - length 54 hours Final retirement: Tuesday, February 2, 2027, 8:00 AM EST. This is not a maintenance window. V2 will not be re-enabled afterward. For more details and next steps, please see: https://docs.cloud.gov/news/2026/10/02/capi-v2-brownouts/ If you have any questions please contact support at [email protected]
Inicio 2 feb 2027, 13:00 UTC · En curso
Cloud.gov is retiring the Cloud Foundry API (CAPI) V2 on Tuesday, February 2, 2027. As we announced on January 7, 2025 ( https://docs.cloud.gov/news/2025/01/02/v2api-deprecation ), we are retiring version 2 of Cloud Foundry API (CAPI V2), and will soon use only version 3 of the API (CAPI V3). Over the last 20 months, our Cloud.gov community has done a terrific job in adopting CAPI V3, and CAPI V2 only accounts for 0.15% of all our CAPI traffic. On February 2, 2027, CAPI V2 will be permanently disabled on Cloud.gov. Tools that depend on V2, including CF CLI v6 and v7, will stop working and will not work again. Ahead of that date, Cloud.gov will run four scheduled brownouts: temporary, planned windows during which we disable V2 endpoints so you can discover if any of your tools depend on them – while there is still time to fix them. Service returns to normal at the end of each window. As a customer, you need to: Check that you are using V3 compatible tooling (see below) Test your deployment and other automated processes during the V2 brownouts to see if anything breaks -- indicating a possible V2 dependency. Brownout schedule Window #1 - Wed Oct 14, 2026 - 8:00 AM EDT thru Wed Oct 14, 2026, 2:00 PM EDT - length 6 hours Window #2 - Wed Oct 28, 2026 - 8:00 AM EDT thru Wed Oct 28, 2026, 2:00 PM EDT - length 6 hours Window #3 - Tue Nov 17, 2026 - 8:00 AM EST thru Wed Nov 18, 2026, 2:00 PM EST - length 30 hours Window #4 - Tue Dec 1, 2026 - 8:00 AM EST thru Thu Dec 3, 2026, 2:00 PM EST - length 54 hours Final retirement: Tuesday, February 2, 2027, 8:00 AM EST. This is not a maintenance window. V2 will not be re-enabled afterward. For more details and next steps, please see: https://docs.cloud.gov/news/2026/10/02/capi-v2-brownouts/ If you have any questions please contact support at [email protected]
Inicio 1 dic 2026, 13:00 UTC · En curso
Cloud.gov is retiring the Cloud Foundry API (CAPI) V2 on Tuesday, February 2, 2027. As we announced on January 7, 2025 ( https://docs.cloud.gov/news/2025/01/02/v2api-deprecation ), we are retiring version 2 of Cloud Foundry API (CAPI V2), and will soon use only version 3 of the API (CAPI V3). Over the last 20 months, our Cloud.gov community has done a terrific job in adopting CAPI V3, and CAPI V2 only accounts for 0.15% of all our CAPI traffic. On February 2, 2027, CAPI V2 will be permanently disabled on Cloud.gov. Tools that depend on V2, including CF CLI v6 and v7, will stop working and will not work again. Ahead of that date, Cloud.gov will run four scheduled brownouts: temporary, planned windows during which we disable V2 endpoints so you can discover if any of your tools depend on them – while there is still time to fix them. Service returns to normal at the end of each window. As a customer, you need to: Check that you are using V3 compatible tooling (see below) Test your deployment and other automated processes during the V2 brownouts to see if anything breaks -- indicating a possible V2 dependency. Brownout schedule Window #1 - Wed Oct 14, 2026 - 8:00 AM EDT thru Wed Oct 14, 2026, 2:00 PM EDT - length 6 hours Window #2 - Wed Oct 28, 2026 - 8:00 AM EDT thru Wed Oct 28, 2026, 2:00 PM EDT - length 6 hours Window #3 - Tue Nov 17, 2026 - 8:00 AM EST thru Wed Nov 18, 2026, 2:00 PM EST - length 30 hours Window #4 - Tue Dec 1, 2026 - 8:00 AM EST thru Thu Dec 3, 2026, 2:00 PM EST - length 54 hours Final retirement: Tuesday, February 2, 2027, 8:00 AM EST. This is not a maintenance window. V2 will not be re-enabled afterward. For more details and next steps, please see: https://docs.cloud.gov/news/2026/10/02/capi-v2-brownouts/ If you have any questions please contact support at [email protected]
Inicio 17 nov 2026, 13:00 UTC · En curso
Cloud.gov is retiring the Cloud Foundry API (CAPI) V2 on Tuesday, February 2, 2027. As we announced on January 7, 2025 ( https://docs.cloud.gov/news/2025/01/02/v2api-deprecation ), we are retiring version 2 of Cloud Foundry API (CAPI V2), and will soon use only version 3 of the API (CAPI V3). Over the last 20 months, our Cloud.gov community has done a terrific job in adopting CAPI V3, and CAPI V2 only accounts for 0.15% of all our CAPI traffic. On February 2, 2027, CAPI V2 will be permanently disabled on Cloud.gov. Tools that depend on V2, including CF CLI v6 and v7, will stop working and will not work again. Ahead of that date, Cloud.gov will run four scheduled brownouts: temporary, planned windows during which we disable V2 endpoints so you can discover if any of your tools depend on them – while there is still time to fix them. Service returns to normal at the end of each window. As a customer, you need to: Check that you are using V3 compatible tooling (see below) Test your deployment and other automated processes during the V2 brownouts to see if anything breaks -- indicating a possible V2 dependency. Brownout schedule Window #1 - Wed Oct 14, 2026 - 8:00 AM EDT thru Wed Oct 14, 2026, 2:00 PM EDT - length 6 hours Window #2 - Wed Oct 28, 2026 - 8:00 AM EDT thru Wed Oct 28, 2026, 2:00 PM EDT - length 6 hours Window #3 - Tue Nov 17, 2026 - 8:00 AM EST thru Wed Nov 18, 2026, 2:00 PM EST - length 30 hours Window #4 - Tue Dec 1, 2026 - 8:00 AM EST thru Thu Dec 3, 2026, 2:00 PM EST - length 54 hours Final retirement: Tuesday, February 2, 2027, 8:00 AM EST. This is not a maintenance window. V2 will not be re-enabled afterward. For more details and next steps, please see: https://docs.cloud.gov/news/2026/10/02/capi-v2-brownouts/ If you have any questions please contact support at [email protected]
Inicio 28 oct 2026, 12:00 UTC · En curso
The scheduled maintenance has been completed.
Inicio 21 oct 2026, 12:30 UTC · Resuelto 21 oct 2026, 13:31 UTC
The scheduled maintenance has been completed.
Inicio 14 oct 2026, 12:00 UTC · Resuelto 14 oct 2026, 18:00 UTC
The scheduled maintenance has been completed.
Inicio 13 oct 2026, 15:00 UTC · Resuelto 13 oct 2026, 18:00 UTC
The scheduled maintenance has been completed.
Inicio 29 oct 2025, 12:30 UTC · Resuelto 29 oct 2025, 13:30 UTC
Las páginas públicas de Downdetector se centran en los reportes de usuarios. Uptimus combina esa actividad con incidentes oficiales, mantenimientos y salud de componentes cuando el proveedor los publica.
| Criterios de comparación | Uptimus | Downdetector |
|---|---|---|
| Reportes de la comunidad sobre Cloudgov | Incluido | Incluido |
| Línea base adaptativa que separa casos aislados de una interrupción amplia | Incluido | Incluido |
| Actividad de reportes de 24 horas y vista regional de interrupciones | Incluido | Incluido |
| Un espacio para sitios web, proveedores de estado, juegos de Steam y aplicaciones y juegos Android | Incluido | Producto separado |
| Alertas por correo, push y webhook desde el mismo espacio | Incluido | Producto separado |
| Actualizaciones oficiales de incidentes y cronología de Cloudgov | Incluido | Basado en reportes |
| Salud de componentes y mantenimientos mostrados por separado | Incluido | Limitado en páginas públicas |
No se puede verificar el estado oficial actual de Cloudgov. La última observación guardada del proveedor indicaba funcionamiento normal. Se registraron 0 reportes de Cloudgov en las últimas 24 horas. Última comprobación oficial: .
Descubre otros servicios populares y su estado actual
Califica este servicio
Aún no hay reseñas
Comparte tus pensamientos sobre Cloudgov
¡Sé el primero en comentar!
