---
service: "Cloud.gov"
status: "up"
reports_last_hour: 0
reports_last_12_hours: 0
baseline_reports_per_hour: 0
checked_at: "2026-10-31T03:23:29.554Z"
url: "https://instatus.com/now/fr-ca/cloud.gov"
official_status_page: "https://cloudgov.statuspage.io"
website: "https://cloud.gov"
---

# Cloud.gov est-il en panne?

Non, ça marche. 0 rapports au cours de la dernière heure.

## Mises à jour officielles

- **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.

## FAQ sur les pannes de Cloud.gov

### Cloud.gov est-il en panne en ce moment?

Non, ça marche. 0 rapports au cours de la dernière heure.

### Cloud.gov est-il en panne pour tout le monde ou seulement pour moi?

On dirait que ça ne vient que de vous. Les signalements pour Cloud.gov sont à leur niveau habituel : essayez de recharger la page, de vérifier votre connexion ou de vous déconnecter puis reconnecter.

### Quels problèmes les gens signalent-ils avec Cloud.gov?

Personne n'a précisé ce qui ne marche pas avec Cloud.gov dans la dernière heure. Si quelque chose ne fonctionne pas pour vous, choisissez-le ci-dessus pour que les autres le voient.

### Quand a eu lieu la dernière panne de Cloud.gov?

Les signalements pour Cloud.gov n'ont pas augmenté ces 30 derniers jours.

### Cloud.gov a-t-il une page d'état?

Oui. Cloud.gov publie des mises à jour sur sa page d'état officielle, qui indique actuellement : opérationnel.

[Aller à la page de statut](https://cloudgov.statuspage.io/)

### Que faire si Cloud.gov ne fonctionne pas?

Consultez cette page et la page d'état de Cloud.gov pour les mises à jour, et attendez quelques minutes avant de réessayer. Inutile de réinstaller : s'il s'agit d'une panne, la solution est de leur côté.

### Comment signaler un problème avec Cloud.gov?

Appuyez sur « j'ai un problème aussi » en haut de cette page et choisissez ce qui ne marche pas. Votre signalement apparaît sur le graphique en direct en moins d'une minute, et vous pouvez laisser un commentaire pour dire aux autres ce que vous constatez.

### Comment Instatus Now le sait-il?

Nous combinons les signalements des personnes sur cette page avec la page d'état officielle de Cloud.gov, que nous consultons chaque minute.
