Synthetics public minion IPs

New Relic Synthetics uses a group of minions to execute your monitors. These minions are deployed in different data centers around the globe, and they are in charge of actually running your monitors.

Because of this, ensure your firewall allows their network requests through it. These minion IP addresses are publicly available in JSON format, so you can easily read and parse them.

Recommendation: For easier maintenance, use these options:

  • Automate your whitelisting rules based on these files.
  • Whitelist by using a custom header.

Daily JSON listings for IP addresses

Some released locations (including Dallas, Fremont, and Newark) do not have static IP addresses. Their IP addresses are subject to change without warning. New Relic updates these JSON listings daily, sometimes multiple times an hour:

Public minion locations and location labels

The following table cross-references the New Relic Synthetic public minion locations with their location labels. In New Relic Insights, you can query the location and locationLabel attributes from the SyntheticCheck and SyntheticRequest events.

End of Life Notice: Three public locations

In September 2019, New Relic Synthetics will be removing three public locations:

  • Dallas, TX
  • Fremont, CA
  • Newark, NJ

We will automatically migrate existing checks to alternate locations beginning the first week of September 2019.

Recommendation: To accommodate any script, alerting, reliability, or geographical considerations, migrate your existing checks to alternate locations before September 2019. For more information, see New Relic's Explorers Hub.

Public minion location Location label
AWS_AP_SOUTH_1 "Mumbai, IN"
AWS_AP_SOUTHEAST_1 "Singapore, SG"
AWS_AP_NORTHEAST_2 "Seoul, KR"
AWS_AP_NORTHEAST_1 "Tokyo, JP"
AWS_AP_SOUTHEAST_2 "Sydney, AU"
AWS_US_WEST_1 "San Francisco, CA, USA"
AWS_US_WEST_2 "Portland, OR, USA"
LINODE_US_WEST_1 "Fremont, CA, USA" (EOL September 2019)
LINODE_US_CENTRAL_1 "Dallas, TX, USA" (EOL September 2019)
AWS_US_EAST_2 "Columbus, OH, USA"
LINODE_US_EAST_1 "Newark, NJ, USA" (EOL September 2019)
AWS_US_EAST_1 "Washington, DC, USA"
AWS_CA_CENTRAL_1 "Montreal, Québec, CA"
AWS_SA_EAST_1 "São Paulo, BR"
AWS_EU_WEST_1 "Dublin, IE"
AWS_EU_WEST_2 "London, England, UK"
AWS_EU_WEST_3 "Paris, FR"
AWS_EU_CENTRAL_1 "Frankfurt, DE"

For more help

Recommendations for learning more: