IP ranges

Cloud

Introduction

IP ranges is a feature for CircleCI customers who need to configure IP-based access to their restricted environments using existing workflows and platforms. As part of this feature, CircleCI provides a list of well-defined IP address ranges associated with the CircleCI service. CircleCI jobs that have this feature enabled will have their traffic routed through one of the defined IP address ranges during job execution.

The feature is available to customers on a Performance or Scale Plan. This feature consumes 450 credits from your account for each GB of data used for jobs with IP ranges enabled.

IP ranges use cases

IP ranges let you limit inbound connections to your infrastructure to IP address ranges that are verifiably associated with CircleCI.

Some example of where IP-based restricted access might be desired include:

Accessing private artifact repositories
Pulling dependencies from a CocoaPods proxy hosted behind a firewall
Running test cases on an internal environment
Performing integration testing against private AWS resources
Deploying an internal app with sensitive data
Granting access to a production network

Example configuration file using IP ranges

version: 2.1

jobs:
  build:
    circleci_ip_ranges: true # opts the job into the IP ranges feature
    docker:
      - image: cimg/ruby:3.2.2
    steps:
      - run: echo “Hello World”
workflows:
  build-workflow:
    jobs:
      - build

Example configuration file using IP ranges with pipeline parameters.

Use conditional logic to control when IP ranges is enabled with pipeline parameters.

version: 2.1

parameters:
  ip_ranges:
    type: boolean
    default: false

jobs:
  build:
    circleci_ip_ranges: << pipeline.parameters.ip_ranges >>
    docker:
      - image: cimg/ruby:3.2.2
    steps:
      - run: echo “Hello World”
workflows:
  build-workflow:
    jobs:
      - build

List of IP address ranges associated with feature

Last updated: 2022-04-06

Jobs that have been opted into the IP ranges feature will have one of the following IP address ranges associated with them:

3.228.39.90
18.213.67.41
34.194.94.201
34.194.144.202
34.197.6.234
35.169.17.173
35.174.253.146
52.3.128.216
52.4.195.249
52.5.58.121
52.21.153.129
52.72.72.233
54.92.235.88
54.161.182.76
54.164.161.41
54.166.105.113
54.167.72.230
54.172.26.132
54.205.138.102
54.208.72.234
54.209.115.53

Jobs can use any of the address ranges above. It is also important to note that the address ranges are shared by all CircleCI customers who have opted into using the feature.

List of IP address ranges for core services

These are the IP address ranges for core services (used to trigger jobs, exchange information about users between CircleCI and GitHub etc):

18.214.70.5
52.20.166.242
18.214.156.84
54.236.156.101
52.22.215.219
52.206.105.184
52.6.77.249
34.197.216.176
35.174.249.131
3.210.128.175

List of IP address ranges changelog

2024-11-05

Added support for parameters.

Use parameters like << pipeline.parameters.ip_ranges >> to determine if IP ranges should be enabled.

2021-08-23

Added new items to the list of IP address ranges for core services.

The machine-consumable lists have also been updated to reflect the new IP address ranges.

2022-04-06

Added and removed new IP addresses as part of enabling Docker pulls to go through the list of IP addresses.

The machine-consumable lists have also been updated to reflect the new IP address ranges.

Machine-consumable lists can be found by querying the DNS A records below:

IP address ranges for jobs: jobs.knownips.circleci.com.
IP address ranges for core services: core.knownips.circleci.com.
All IP address ranges: all.knownips.circleci.com.

To query these, you can use any DNS resolver. Here is an example using dig with the default resolver:

dig all.knownips.circleci.com A +short

Notifications of a change to this list will be sent out by email to all customers who have at least one job opted into the IP ranges feature. 30 days notice will be given before changes are made to the existing set of IP address ranges. This page and the machine-consumable list will also be updated when there are upcoming changes.

Pricing

Pricing is calculated based on the data usage of jobs opted into the IP ranges feature. It is possible to mix jobs with and without the IP ranges feature within the same workflow or pipeline. Data used to pull in the Docker image to the container before the job starts executing does not incur usage costs for jobs with IP ranges enabled.

This feature consumes 450 credits from your account for each GB of data used for jobs with IP ranges enabled.

IP ranges usage is visible in the Plan Usage section of the CircleCI app:

Screenshot showing the location of the IP ranges feature

On the Resources tab within the Job Details UI page, you can view approximations of network transfer for any Docker job, even those without the IP ranges feature enabled. This approximation can be used to predict the cost of enabling the IP ranges feature on a job without having to turn the feature on. See more details on the CircleCI blog. You can also view whether or not the job has IP ranges enabled by viewing the IP Ranges badge.

Screenshot showing the approximate network transfer

AWS and GCP IP Addresses

The machines that execute all jobs on CircleCI’s platform, not just jobs opted into IP ranges, are hosted on Amazon Web Services (AWS), Google Cloud Platform (GCP), and CircleCI’s macOS Cloud (see below). An exhaustive list of IP addresses that CircleCI’s traffic may come from on these cloud providers’ platforms can be found by looking up each cloud provider’s IP address ranges. AWS & GCP offer endpoints to find this information.

AWS: CircleCI uses the us-east-1 and us-east-2 regions
GCP: CircleCI uses the us-east1 and us-central1 regions

CircleCI does not recommend configuring an IP-based firewall based on the AWS or GCP IP addresses, as the vast majority are not CircleCI’s machines. There is no guarantee that the addresses in the AWS or GCP endpoints persist from day-to-day, as these addresses are reassigned continuously.

CircleCI macOS cloud

In addition to AWS and GCP (see above), CircleCI’s macOS cloud hosts jobs executed by machines. The following IP address ranges are used by CircleCI macOS Cloud:

100.27.248.128/25
100.29.139.128/25
98.80.165.0/24
38.23.41.0/24
38.23.42.0/24
38.23.43.0/24
207.254.116.0/24
207.254.118.0/24
18.97.4.0/24
18.97.6.0/24
18.97.7.0/24

A machine-readable list of these IP ranges is available as well

This list of IP Ranges can also be downloaded and saved using the following curl command:

curl -O https://circleci.com/docs/ip-ranges-list.json

IP ranges is the recommended method for configuring an IP-based firewall to allow traffic from CircleCI’s platform.

macOS builds are automatically restricted within the IP ranges listed here. In other words, you do not have to explicitly set circleci_ip_ranges: true for macOS builds.

macOS IP ranges are not included in the machine-consumable lists maintained in DNS. Refer to the list above for the most up-to-date macOS IPs. Information about changes to macOS IP ranges will be included in the changelog and will be sent to the technical contact(s) listed under Organization Settings Overview.

Known limitations

IP ranges is currently available for the Docker executor, not including remote_docker. Jobs that attempt to use the IP ranges feature with a Machine executor, or with setup_remote_docker, will fail with an error. See this Discuss post for details.