> 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/connections/ip-whitelisting.md). # IP whitelisting If you're using CARTO Cloud, CARTO will connect to your databases using a set of static IPs for each region. These static IPs can be whitelisted in your security setups as needed. Hereโ€™s the list of static IPs, with an endpoint that you can use to validate or retrieve them. {% hint style="info" %} **What is my organization's region?** The region (tenant) is specified when creating the organization. Your region is always visible to your admin in the [Organization Settings](/carto-user-manual/settings.md). If you're not an admin you can still check your region by looking at the URL: *`clausa`* stands for US, *`pinea`* for EU, *`thunbergil`* for Japan, and *`radiata`* for Australia. {% endhint %} **๐Ÿ‡บ๐Ÿ‡ธ us-east1** * `35.185.63.239` * `104.196.59.4` * `34.73.63.7` * `34.139.239.104` Get this list via [API](https://workspace-gcp-us-east1.app.carto.com/meta). **๐Ÿ‡ช๐Ÿ‡บ europe-west1** * `34.79.53.57` * `35.195.132.75` * `34.78.167.2` * `35.187.123.190` Get this list via [API](https://workspace-gcp-europe-west1.app.carto.com/meta). **๐Ÿ‡ฏ๐Ÿ‡ต asia-northeast1** * `34.85.15.12` * `35.200.23.186` Get this list via [API](https://workspace-gcp-asia-northeast1.app.carto.com/meta). **๐Ÿ‡ฆ๐Ÿ‡บ australia-southeast1** * `34.151.87.148` * `35.201.15.104` Get this list via [API](https://workspace-gcp-australia-southeast1.app.carto.com/meta). --- # 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/connections/ip-whitelisting.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.