IP address ranges for the Bitrise build machines
For most users, who host their repositories on cloud-based service providers, there is no need for any network configuration to be able to use Bitrise. All we need is permission to access the repository and for that, an SSH key or an access token is enough.
However, your company security policy might not allow unknown and unauthorized IP addresses to communicate with the servers where your code is being stored - either on your own datacenter or in a private cloud. In that case, Bitrise won’t work unless the relevant IP addresses are added to your allow list.
You will see IP addresses from the following ranges as source when your Bitrise build machines reach out to your services like Git to download your source code, or call into your test backend services, or any other services you run outside Bitrise that are required to be reached as part of your CI workflow.
Allowlist the entire subnet
If the provided public IP address is a subnet, you need to allow the entire subnet on your network! For example, 208.52.166.128/28 means all IP addresses between 208.52.166.128 and 208.52.166.143 (208.52.166.128, 208.52.166.129, 208.52.166.130, and so on, all the way to and including 208.52.166.143) have to be allowlisted.
Multi-tenant vs Single-tenant
The build machine IP ranges listed below are for the Bitrise multi-tenant environment. Depending on your organization's security requirements, it may not be advisable to allow access to your network from the Bitrise multi-tenant IP range. For organizations with enhanced security requirements, you can:
Feel free to contact us if you have questions.
|
Stack type |
Public IP |
|---|---|
|
Xcode stacks If you run your builds using Xcode stacks, they will run on machines with the IP address ranges in the Public IP column. For example, if you run |
74.122.200.224/27 (74.122.200.224 - 74.122.200.255) 74.122.201.224/27 (74.122.201.224 - 74.122.201.255) 74.122.202.224/27 (74.122.202.224 - 74.122.202.255) 74.122.203.224/27 (74.122.203.224 - 74.122.203.255) |
|
185.55.252.224/27 (185.55.252.224 - 185.55.252.255) 185.55.253.224/27 (185.55.253.224 - 185.55.253.255) 185.55.254.224/27 (185.55.254.224 - 185.55.254.255) 185.55.255.224/27 (185.55.255.224 - 185.55.255.255) |
|
|
208.52.166.154/32 and 208.52.166.128/28 |
|
|
207.254.0.248/29 and 207.254.0.208/28 |
|
|
207.254.34.148/32 and 207.254.33.176/28 |
|
|
Linux/Docker stacks If you run your builds using Linux/Docker stacks, they will run on machines with the IP address ranges in the Public IP column. For example, if you run |
74.122.200.224/27 (74.122.200.224 - 74.122.200.255) 74.122.201.224/27 (74.122.201.224 - 74.122.201.255) 74.122.202.224/27 (74.122.202.224 - 74.122.202.255) 74.122.203.224/27 (74.122.203.224 - 74.122.203.255) |
|
185.55.252.224/27 (185.55.252.224 - 185.55.252.255) 185.55.253.224/27 (185.55.253.224 - 185.55.253.255) 185.55.254.224/27 (185.55.254.224 - 185.55.254.255) 185.55.255.224/27 (185.55.255.224 - 185.55.255.255) |
|
|
104.197.15.74/32 |
|
|
34.123.172.192/32 |
|
|
34.125.50.224/32 |
|
|
34.125.82.130/32 |
|
|
34.134.193.138/32 |
|
|
34.138.187.10/32 |
|
|
34.150.152.190/32 |
|
|
34.162.185.129/32 |
|
|
34.162.202.37/32 |
|
|
34.162.229.32/32 |
|
|
34.162.29.153/32 |
|
|
34.162.88.79/32 |
|
|
34.23.207.105/32 |
|
|
34.85.139.176/32 |
|
|
34.85.240.93/32 |
|
|
34.86.56.118/32 |
|
|
35.202.121.43/32 |
|
|
35.225.44.167/32 |
|
|
35.231.56.118/32 |
|
|
35.237.165.17/32 |
|
|
35.243.148.182/32 |
|
|
35.245.56.67/32 |