> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-user-manual/overview/carto-cloud-regions.md).
# CARTO Cloud Regions
For new CARTO [**cloud deployments**](/faqs/deployment-options.md), users can choose between four different regions. These correspond to four separate CARTO tenants, each located in a different geographical location:
* United States East
* Europe West (located in the EU)
* Asia Northeast (located in Japan)
* Australia Southeast
These tenants are fully managed CARTO deployments that we host on our own cloud (on the Google Cloud Platform). We manage configuration, updates, and versioning. Changes to CARTO are pushed simultaneously to these four tenants, so they are functionally equivalent.
All your organization’s data such as maps, workflows, applications, etc; will be stored in the selected region. In addition, the [CARTO Data Warehouse](/carto-user-manual/connections/carto-data-warehouse.md) of your organization will be located in that region as well.
### Choosing a region
There are a two main considerations when choosing a region:
* Proximity to your data
* Compliance and data regulations
Ideally, you should choose the region that is closest to your data to reduce latency and improve performance. For example, if you’re planning to connect CARTO to your Google BigQuery or Snowflake data in any US region, we recommend you choose the CARTO US region for optimal performance.
Some organizations might also have to choose a region that complies with specific data protection and privacy regulations, such as GDPR in the EU.
For additional help, you can use [**Google Cloud's Region Picker**](https://googlecloudplatform.github.io/region-picker/) to help you select a cloud region.
### Checking my organization's region
The region of your organization is visible from the admin panel in the [Organization Settings](/carto-user-manual/settings.md).
If you're not an admin, you can still check your organization's region by looking at the URL:
* *clausa* stands for United States East
* *pinea* for Europe West
* *thunbergii* for Asia Northeast
* *radiata* for Australia Southeast\
\
\\
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.carto.com/carto-user-manual/overview/carto-cloud-regions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
