--- service: "Cloud.gov" status: "up" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 0 checked_at: "2026-10-31T02:09:14.642Z" url: "https://instatus.com/now/zh-tw/cloud.gov" official_status_page: "https://cloudgov.statuspage.io" website: "https://cloud.gov" --- # Cloud.gov 關閉了嗎？ 沒有，一切正常. 過去一小時 0 份報告。 ## 官方更新 - **General retirement notice - CAPI V2 API** (SCHEDULED, 2027-02-02T13:00:00.000Z): 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 support@cloud.gov - **Cloud Foundry API (CAPI) V2 - Brownout Window #4** (SCHEDULED, 2026-12-01T13:00:00.000Z): 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 support@cloud.gov - **Cloud Foundry API (CAPI) V2 - Brownout Window #3** (SCHEDULED, 2026-11-17T13:00:00.000Z): 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 support@cloud.gov - **Cloud Foundry API (CAPI) V2 - Brownout Window #2** (COMPLETED, 2026-10-28T12:00:00.000Z): The scheduled maintenance has been completed. ## Cloud.gov 故障常見問題 ### Cloud.gov 現在掛了嗎？ 沒有，一切正常. 過去一小時 0 份報告。 ### Cloud.gov 是所有人都壞了，還是只有我？ 看起來只有你遇到。Cloud.gov 的回報量正常，可以試試重新整理、檢查網路連線，或登出後重新登入。 ### 大家回報了 Cloud.gov 的哪些問題？ 過去一小時內沒有人說明 Cloud.gov 哪裡壞了。如果你遇到問題，請在上方選擇，讓其他人看到。 ### Cloud.gov 上次故障是什麼時候？ 過去 30 天內，Cloud.gov 的回報沒有出現暴增。 ### Cloud.gov 有狀態頁面嗎？ 有。Cloud.gov 會在官方狀態頁面發布更新，目前顯示：運行正常。 [前往狀態頁面](https://cloudgov.statuspage.io/) ### Cloud.gov 無法使用時我可以怎麼做？ 查看本頁和 Cloud.gov 的狀態頁面以取得更新，等幾分鐘再試一次。不用重新安裝：如果是服務中斷，要由他們那邊修復。 ### 如何回報 Cloud.gov 的問題？ 點選本頁頂端的「我也有問題」，再選擇哪裡壞了。你的回報會在一分鐘內顯示在即時圖表上，也可以留言告訴其他人你遇到的狀況。 ### Instatus Now 是怎麼知道的？ 我們把此頁面上使用者的回報，與每分鐘檢查一次的 Cloud.gov 官方狀態頁結合起來。