## 2.2 Regions
You can deploy applications in different regions . Each region represents a geographical location (for example, Europe, US East) where applications, data, or services are hosted.
## About SAP BTP Regions
<!-- image -->
Regions are provided either by SAP or by our Infrastructure-as-a-Service (IaaS) partners Amazon Web Services (AWS), Microsoft Azure, Google Cloud, and Alibaba Cloud. The third-party region providers operate the infrastructure layer of the regions, whereas SAP operates the platform layer and Cloud Foundry.
<!-- image -->
For an overview of all available regions, see SAP Discovery Center :
<!-- image -->
## Selecting a Region
A region is chosen at the subaccount level. For each subaccount, you select exactly one region. The selection of a region is dependent on many factors: For example, application performance (response time, latency) can be optimized by selecting a region close to the user. For more information, see Selecting a Region.
## Deploying Applications in Regions
When deploying applications, consider that a subaccount is associated with a particular region and that this is independent of your own location. You may be located in the United States, for example, but operate your subaccount in a region in Europe. For more information on subaccounts, see Subaccounts [page 112].
To deploy an application in more than one region, execute the deployment separately for each host. For more information, see Deploy an Application [page 2580].
Within a region, there can be multiple instances of the SAP BTP, Cloud Foundry environment. When creating a subaccount, SAP BTP automatically assigns the account to a specific instance of the environment. Several subaccounts of the same global account can be located in different datacenters in one region. This also affects the format of the API endpoint URL that is displayed in the cockpit after enabling Cloud Foundry in your subaccount. There are two possible formats for the API endpoint URL, either displayed with or without an index. Here's an example for eu10 :
##  Example
- https:/ /api.cf.eu10.hana.ondemand.com
- https:/ /api.cf.eu10-&lt;XXX&gt;.hana.ondemand.com
In both cases, the subaccount is located in the region eu10. The differences in the URLs are only an indicator of technical details on the side of SAP BTP and do not affect the functionality of your applications. For information on enabling Cloud Foundry, see Create Orgs [page 2514].
## High Availability
SAP has a number of processes in place to support resilience in SAP BTP, and provides different offerings so that you can support the high availability of your applications. For more information, see Resilience, High Availability, and Disaster Recovery [page 53].
## EU Access
Some customer contracts include EU Access, which restricts processing of personal data to EEA/Switzerland. If the global account is marked with EU Access, the actual EU Access compliance status of subaccounts will be displayed during creation of subaccounts.
##  Note
If you require a subaccount with EU Access, make sure to select a provider and region where EU Access is available. Regions that allow for EU Access are labeled as such in the map view filter in the SAP Discovery Center.
For some services, EU Access is generally not available, not even if the provider and region support EU Access.
## Related Information
Regions and API Endpoints Available for the Cloud Foundry Environment [page 19]
Regions and API Endpoints for the ABAP Environment [page 42] Regions for the Kyma Environment [page 48]