Last checked
Secure compliant cloud platform for rapid deployment of modern web applications.
Experiencing an issue?
Cloudgov не работает?
Maintenance
Share your experience to help others stay informed.
Official status checked
Cloudgov has active maintenance
Official provider status0 individual report entries in the last 24 hours. This list includes legacy imports; external source aggregates are shown in the chart.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 0m | Yes | Unknown | ||
| 19h 34m | Yes | Unknown | ||
| 1h 19m | Yes | Unknown | ||
| 17h 26m | Yes | Unknown | ||
| 0m | Yes | Unknown | ||
| 45h 7m | Yes | Minor | ||
| 0m | Yes | Unknown | ||
| 302h 45m | Yes | Unknown |
Uptimus отслеживает Cloudgov по официальному источнику и объединяет инциденты, обслуживание и состояние компонентов в единый статус.
Сейчас страница содержит 43 компонентов, 51 инцидентов, 57 окон обслуживания и 9 дней известной истории.
Uptimus — независимый сервис, не связанный с Cloudgov. Нормальный статус не гарантирует отсутствие проблем у каждого пользователя, устройства или региона.
Получайте уведомления, когда Cloudgov или отслеживаемый компонент сообщает о крупном или критическом сбое. Оповещения доставляются по включённым каналам рабочего пространства, включая email, push и настроенные интеграции. Доступная история содержит 51 инцидентов и даёт оповещениям контекст помимо текущего статуса. Недавний инцидент: «Partial outage for the SES Service Broker».
Получайте уведомления о снижении производительности, частичном влиянии и небольших инцидентах. Uptimus сейчас отслеживает 43 компонентов Cloudgov: Application logs - Intake and storage, Applications, Dashboard, GitHub. Оповещения доставляются по включённым каналам рабочего пространства, включая email, push и настроенные интеграции.
Planned work published by the official provider.
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]
Started 2 февр. 2027 г., 13:00 UTC · Ongoing
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]
Started 1 дек. 2026 г., 13:00 UTC · Ongoing
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]
Started 17 нояб. 2026 г., 13:00 UTC · Ongoing
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]
Started 28 окт. 2026 г., 12:00 UTC · Ongoing
The scheduled maintenance has been completed.
Started 21 окт. 2026 г., 12:30 UTC · Resolved 21 окт. 2026 г., 13:31 UTC
The scheduled maintenance has been completed.
Started 14 окт. 2026 г., 12:00 UTC · Resolved 14 окт. 2026 г., 18:00 UTC
The scheduled maintenance has been completed.
Started 13 окт. 2026 г., 15:00 UTC · Resolved 13 окт. 2026 г., 18:00 UTC
The scheduled maintenance has been completed.
Started 29 окт. 2025 г., 12:30 UTC · Resolved 29 окт. 2025 г., 13:30 UTC
Публичные страницы Downdetector в основном опираются на сообщения пользователей. Uptimus дополняет их официальными инцидентами, обслуживанием и состоянием компонентов, когда провайдер публикует эти данные.
| Критерии сравнения | Uptimus | Downdetector |
|---|---|---|
| Сообщения сообщества о сбоях Cloudgov | Включено | Включено |
| Адаптивная база для отделения единичных сообщений от массового сбоя | Включено | Включено |
| Активность за 24 часа и региональная карта сбоев | Включено | Включено |
| Одно пространство для сайтов, статус-провайдеров, игр Steam и приложений и игр Android | Включено | Отдельный продукт |
| Оповещения по e-mail, push и webhook из одного пространства | Включено | Отдельный продукт |
| Официальные обновления и хронология статуса Cloudgov | Включено | На основе сообщений |
| Состояние компонентов и обслуживание показаны отдельно | Включено | Ограничено на публичных страницах |
The official status page for Cloudgov reports normal operation. 0 reports were recorded for Cloudgov in the last 24 hours. Last official check: .
Откройте для себя другие популярные сервисы и их текущий статус
Оцените эту услугу
Отзывов пока нет
Поделитесь своими мыслями о Cloudgov
Будьте первым, кто оставит комментарий!
