--- service: "Cloud.gov" status: "up" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 0 checked_at: "2026-10-31T18:12:45.442Z" url: "https://instatus.com/now/pl/cloud.gov" official_status_page: "https://cloudgov.statuspage.io" website: "https://cloud.gov" --- # Czy Cloud.gov nie działa? Nie, działa. 0 raportów w ostatniej godzinie. ## Oficjalne aktualizacje - **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 – awarie: FAQ ### Czy Cloud.gov jest teraz wyłączony? Nie, działa. 0 raportów w ostatniej godzinie. ### Czy Cloud.gov nie działa u wszystkich, czy tylko u mnie? Wygląda na to, że problem jest tylko u Ciebie. Zgłoszenia dla Cloud.gov są na zwykłym poziomie, więc spróbuj odświeżyć stronę, sprawdzić połączenie albo wylogować się i zalogować ponownie. ### Jakie problemy zgłaszają ludzie z Cloud.gov? W ostatniej godzinie nikt nie napisał, co nie działa w Cloud.gov. Jeśli u Ciebie coś nie działa, wybierz to powyżej, żeby inni to zobaczyli. ### Kiedy była ostatnia awaria Cloud.gov? Zgłoszenia dla Cloud.gov nie nasiliły się w ciągu ostatnich 30 dni. ### Czy Cloud.gov ma stronę statusu? Tak. Cloud.gov publikuje aktualizacje na oficjalnej stronie statusu, która obecnie podaje: poprawne działanie. [Przejdź do strony statusu](https://cloudgov.statuspage.io/) ### Co mogę zrobić, jeśli Cloud.gov nie działa? Sprawdź tę stronę i stronę statusu Cloud.gov, żeby poznać aktualizacje, i odczekaj kilka minut przed kolejną próbą. Nie instaluj ponownie: jeśli to awaria, naprawa leży po ich stronie. ### Jak zgłosić problem z Cloud.gov? Kliknij „Ja też mam problem” u góry tej strony i wybierz, co nie działa. Twoje zgłoszenie pojawi się na wykresie na żywo w ciągu minuty, a komentarzem możesz dać znać innym, co widzisz. ### Skąd Instatus Now to wie? Łączymy zgłoszenia osób z tej strony z oficjalną stroną statusu Cloud.gov, którą sprawdzamy co minutę.