> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/integrations/cloud-sync/network-access-and-ip-allowlisting.md). # Network access and IP allowlisting The public IP addresses Cloud Sync connects from, and where to allow them on each source. Cloud Sync connects **outbound** from our infrastructure to your data source. If your source restricts inbound connections (a Snowflake Network Policy, a cloud firewall rule, a VPC security group, an SFTP allowlist), you must allow our IP addresses before the connection test will succeed. *** ## Cloud Sync IP addresses Cloud Sync connects to your source from the following fixed public IP addresses and ranges: ``` 51.210.173.180 51.210.173.181 51.254.68.64/28 51.255.13.142 51.255.13.144 51.255.13.147 51.255.13.152 51.255.13.153 51.255.13.154 51.255.13.158 51.255.13.160 51.255.13.162 164.132.241.239 178.33.24.24/29 ``` Allow all of them: a sync can use any one of these addresses, and which one varies between runs. *** ## Where to allow them Allow **inbound TCP** from the addresses above, on the port your source listens on. Where that rule lives depends on your source — refer to your provider's own documentation for the current steps. If you use an SSH tunnel, the addresses above are what reaches your jump server. The jump server's own address is what reaches your database, so allow it accordingly on the database side. *** ## Changes to this list This list can change as our infrastructure evolves. Whenever it does, we notify affected customers **at least 30 days** before the new addresses are used, so you can update your rules ahead of time. *** ## Verifying the connection After adding the rule, create or edit your sync in the Batch dashboard and re-run the connection test. If it still fails, see [Troubleshooting](/integrations/cloud-sync/troubleshooting.md). --- # 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://doc.batch.com/integrations/cloud-sync/network-access-and-ip-allowlisting.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.