CAPI V2 End-of-Life: Brownouts start Oct 14; EOL on Feb 2, 2027

Cloud.gov is retiring the Cloud Foundry API (CAPI) V2 on Tuesday, February 2, 2027

As we announced on January 7, 2025, 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 Cloud Foundry CLI (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.

All the details are below. We expect this change will have no impact on most customers, but you are responsible for testing your own tooling.

Contents

• Brownout schedule
• Who is affected
• What you need to do
• What to expect during a brownout
• Why this is happening

Brownout schedule

#	Start	End	Duration
1	Wed Oct 14, 2026, 8:00 AM EDT	Wed Oct 14, 2026, 2:00 PM EDT	6 hours
2	Wed Oct 28, 2026, 8:00 AM EDT	Wed Oct 28, 2026, 2:00 PM EDT	6 hours
3	Tue Nov 17, 2026, 8:00 AM EST	Wed Nov 18, 2026, 2:00 PM EST	30 hours
4	Tue Dec 1, 2026, 8:00 AM EST	Thu Dec 3, 2026, 2:00 PM EST	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.

Who is affected

You are affected if any tool you use to interact with Cloud.gov still makes V2 API calls. The most common cases:

• CF CLI v6 or v7. Both are unsupported upstream and rely on V2.
• The cf connect-to-service plugin installed before September 14, 2026.
• The legacy community Terraform provider (cloudfoundry-community/terraform-provider-cf). It is V2-based and unmaintained.
• Scripts or automation calling /v2/... endpoints directly.
• Third-party or vendor tooling that has not been updated for V3.

You are not affected if you interact with Cloud.gov only through the dashboard or Pages.

What you need to do

1. Ensure your interactive tooling is up-to-date

Check your CF CLI version now:

cf version

If it reports v6 or v7, upgrade to v8 or later from github.com/cloudfoundry/cli.

If you use the cf connect-to-service plugin, upgrade to plugin version 2.0.x by running cf install-plugin, e.g. for macOS:

cf install-plugin -f https://github.com/cloud-gov/cf-service-connect/releases/download/v2.0.0/cf-service-connect_darwin_arm64

or for Windows:

cf install-plugin -f https://github.com/cloud-gov/cf-service-connect/releases/download/v2.0.0/cf-service-connect_windows_amd64

2. If you interact with Cloud.gov programmatically

1. Ensure your shell scripts use CF CLI v8 (see above), or that your libraries (cf-python-client, go-cfclient, etc.) have been released in the last year.
2. If you call the API directly, move your calls to V3.
   • See the V3 API documentation. Substituting /v3 for /v2 will not work for every call, because parts of the API were redesigned. Read the Upgrade Guide section for the concepts that changed.
   • /v2/info is the one exception. It remains supported in CAPI V3 and will stay available during the brownouts and after retirement, so clients of all types can continue to retrieve platform version information. Note that because /v2/info stays up, some older clients will authenticate successfully and then fail on subsequent commands. A successful cf login alone does not mean you are unaffected.

3. If you use Terraform, confirm which provider you are using

The supported provider is the official Cloud Foundry terraform-provider-cloudfoundry, which uses V3. If you are using the older community-supported provider, cloudfoundry-community/terraform-provider-cf, upgrading is not enough. You must migrate to the official provider. Start this now; it is a configuration change, not a version bump.

4. Use the brownouts as your test

The most reliable way to find a V2 dependency is to run your normal deployment and automation during a brownout window. If it works then, it will work after retirement.

If you cannot be ready by February 2, 2027 — for example, because a vendor fix requires a procurement cycle — contact support@cloud.gov before December 15, 2026 so we can work through it with you. Do not wait until the retirement date.

What to expect during a brownout

All brownouts will be announced and tracked on StatusPage.

If your tooling is current, or you use only the dashboard or Pages, you should see no impact at all.

If a tool cannot log in, or logs in but then fails on specific commands, it is making V2 calls and must be updated.

During brownout windows, affected tools will work again once the window closes. After February 2, 2027, they will not. Treat every brownout as a rehearsal for a permanent change.

If we observe unexpected platform impact (e.g. your production applications are affected) during a brownout, we will re-enable V2 early and post an update. If you experience such impact, open an urgent support request.

Why this is happening

Cloud.gov runs on Cloud Foundry and uses the Cloud Foundry API, known as CAPI. Nearly everything that talks to the platform goes through CAPI: the CF CLI, direct HTTPS requests, Terraform, and CI/CD tooling.

CAPI V2 dates to 2013 and was superseded by V3 in 2019. As of mid-2026, V2 is disabled by default in current Cloud Foundry releases, and the Cloud Foundry working groups plan to remove the V2 subsystem entirely in early 2027. Removing it reduces the platform's API surface, which improves both performance and security.

Cloud.gov has kept V2 enabled while we migrated our own internal systems, including service brokers and platform components, to native V3 calls. That work is complete. The remaining V2 traffic on the platform is customer traffic, which is why we are now asking you to verify your own tooling.

If you have any questions, please contact support at support@cloud.gov.