| copyright |
|
||
|---|---|---|---|
| lastupdated | 2026-03-30 | ||
| keywords | Continuous Delivery endpoints, available regions, locations | ||
| subcollection | ContinuousDelivery |
{{site.data.keyword.attribute-definition-list}}
{: #regions}
{{site.data.keyword.contdelivery_short}} will be discontinued in the following regions on 10 April 2026: eu-es and jp-osa. This discontinuation also applies to any features provided within the service, including Code Risk Analyzer and {{site.data.keyword.DRA_short}}. Learn more {: important}
{{site.data.keyword.contdelivery_short}} will be discontinued in the following regions on 12 February 2027: au-syd, ca-mon, ca-tor, us-east. Code Risk Analyzer and {{site.data.keyword.DRA_short}} will also be deprecated in all regions on that date. However, if a region has no active usage of these features, the features in that region may be discontinued earlier and stop accepting new instances. Learn more {: important}
Review region and connectivity options for interacting with {{site.data.keyword.contdelivery_full}}. {: shortdesc}
{: #available-regions}
{{site.data.keyword.contdelivery_short}} is available in the following regions (borders and geographic features in the illustration are artistic representations):
{: caption="Displays the regions where you can create and manage {{site.data.keyword.contdelivery_short}} resources." caption-side="bottom"}
Montreal (ca-mon) is a limited-availability region and not generally available. {: important}
You can create {{site.data.keyword.contdelivery_short}} resources, including toolchains, in one of the supported {{site.data.keyword.cloud_notm}} regions, which represent the geographic area where your {{site.data.keyword.contdelivery_short}} requests are handled and processed. To learn more, see {{site.data.keyword.contdelivery_short}} high availability and disaster recovery.
{: #service-endpoints}
{{site.data.keyword.contdelivery_short}} offers two connectivity options for interacting with its service APIs: public endpoints (available in all regions) and private endpoints (available in selected regions).
{: #public-endpoints}
By default, you can connect to resources in your account over the {{site.data.keyword.cloud_notm}} public network. Your data is encrypted in transit by using supported ciphers of the Transport Security Layer (TLS) 1.2 and 1.3 protocol. For more information about TLS and these ciphers, see Securing your data in {{site.data.keyword.contdelivery_short}}.
Review the following table to determine the public API endpoints to use when you connect to the {{site.data.keyword.contdelivery_short}} API{: external}.
| Region | Public endpoints |
|---|---|
| Dallas | us-south.devops.cloud.ibm.com |
| Washington DC (deprecated) | us-east.devops.cloud.ibm.com |
| London | eu-gb.devops.cloud.ibm.com |
| Frankfurt | eu-de.devops.cloud.ibm.com |
| Sydney (deprecated) | au-syd.devops.cloud.ibm.com |
| Tokyo | jp-tok.devops.cloud.ibm.com |
| Montreal (deprecated) | ca-mon.devops.cloud.ibm.com |
| Toronto (deprecated) | ca-tor.devops.cloud.ibm.com |
| São-Paulo | br-sao.devops.cloud.ibm.com |
| {: caption="Public endpoints for interacting with {{site.data.keyword.contdelivery_short}} APIs over IBM Cloud's public network" caption-side="top"} |
The following table lists the public endpoints for the Delivery Pipeline private worker service.
| Region | Private endpoints |
|---|---|
| Dallas | private-worker-service.us-south.devops.cloud.ibm.com |
| Washington DC (deprecated) | private-worker-service.us-east.devops.cloud.ibm.com |
| London | private-worker-service.eu-gb.devops.cloud.ibm.com |
| Frankfurt | private-worker-service.eu-de.devops.cloud.ibm.com |
| {: caption="Private endpoints for interacting with the private worker service" caption-side="top"} |
{: #private-endpoints}
You can also enable virtual routing and forwarding (VRF) and service endpoints for your infrastructure account. When you enable VRF for your account, you can connect to {{site.data.keyword.contdelivery_short}} in selected regions by using a private IP address that is accessible only by using the {{site.data.keyword.cloud_notm}} private network.
To learn more about VRF, see Virtual routing and forwarding on {{site.data.keyword.cloud_notm}}.
To learn how to configure Delivery Pipeline Private Workers to connect to {{site.data.keyword.contdelivery_short}} by using private endpoints, see Configuring the Delivery Pipeline Private Worker to use private endpoints.
The following table lists the private endpoints for the Delivery Pipeline private worker service.
| Region | Private endpoints |
|---|---|
| Dallas | private-worker-service.private.us-south.devops.cloud.ibm.com |
| Washington DC (deprecated) | private-worker-service.private.us-east.devops.cloud.ibm.com |
| London | private-worker-service.private.eu-gb.devops.cloud.ibm.com |
| Frankfurt | private-worker-service.private.eu-de.devops.cloud.ibm.com |
| {: caption="Private endpoints for interacting with the private worker service" caption-side="top"} |
Review the following table to determine the private API endpoints to use when you connect to the {{site.data.keyword.contdelivery_short}} API{: external}.
| Region | Private endpoints |
|---|---|
| Dallas | private.us-south.devops.cloud.ibm.com |
| Washington DC (deprecated) | private.us-east.devops.cloud.ibm.com |
| London | private.eu-gb.devops.cloud.ibm.com |
| Frankfurt | private.eu-de.devops.cloud.ibm.com |
| {: caption="Private endpoints for interacting with {{site.data.keyword.contdelivery_short}} APIs over IBM Cloud's private network" caption-side="top"} |