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/29Allow 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.