New Relic Synthetics: IPs & Locations
Verified New Relic Synthetics IP Addresses. Copy-Paste Firewall-Setups.
Every official New Relic Synthetics monitoring IP: verified in real-time against the canonical source, featuring ready-to-use firewall templates. Stop false downtime alerts caused by blocked checking nodes on your infrastructure.
Made and Hosted in the
European Union
GDPR-Compliant Hosting
in Germany
GEO-Redundant Replica
across the EU
Three-Step Activation & Frictionless Firewall Alignment
Bring your perimeter security rules up to date in three simple steps. Our production-ready configuration templates for common server architectures eliminate fragmented routing filters and costly check flapping.
63 IPv4 ranges from 20 public minion locations: one click below copies everything as a plain list or as ready-to-paste UFW, nginx, or Apache config.
Add every address to your allow list: UFW, nginx, Apache, or a Cloudflare/WAF skip rule. Partial lists cause flapping checks and false alerts.
New Relic Synthetics updates its list occasionally. This page was verified on 2026-06-12 against the official source. Re-check after unexplained alerts or automate the sync.
Official New Relic Synthetics Monitoring IPs
New Relic publishes the ranges as location-grouped JSON, linked from the synthetic public minion IPs documentation.
New Relic Synthetics runs ping, API, and scripted browser checks from "public minions": managed check runners in 20 locations worldwide. The egress addresses are published as CIDR ranges grouped by location.
If your firewall blocks some locations, monitors fail location-dependently and look flaky. Whitelist all ranges below, or, if your monitors only use specific locations, at least every location you selected.
This list contains 63 IPv4 ranges, verified against the official source on 2026-06-12.
IPv4 addresses 63
- 44.202.178.0/24
- 44.202.180.0/23
- 44.210.68.0/24
- 44.210.110.0/25
- 152.38.128.64/26
- 152.38.132.0/24
- 64.251.196.0/24
- 152.38.129.96/27
- 64.251.197.0/24
- 152.38.130.0/26
- 64.251.198.0/24
- 152.38.130.64/26
- 152.38.130.128/28
- 152.38.131.64/26
- 64.251.199.0/24
- 3.99.200.0/24
- 3.99.193.0/26
- 3.99.253.128/25
- 212.32.1.128/25
- 212.32.1.64/26
- 212.32.1.32/28
- 212.32.0.64/26
- 212.32.0.128/25
- 212.32.0.32/27
- 212.32.3.0/25
- 13.38.68.128/25
- 13.38.68.64/26
- 13.38.202.128/26
- 13.38.202.192/28
- 212.32.2.128/25
- 212.32.2.64/26
- 16.16.1.128/25
- 13.50.68.0/26
- 15.160.105.128/25
- 18.102.58.0/26
- 35.77.208.0/24
- 35.79.233.64/26
- 35.79.233.128/28
- 3.38.229.128/25
- 15.165.193.192/26
- 13.214.242.0/25
- 13.214.223.192/26
- 18.141.238.128/25
- 64.251.192.128/25
- 64.251.193.0/28
- 64.251.192.64/26
- 3.110.73.192/26
- 3.111.138.0/25
- 43.205.150.128/26
- 43.204.166.240/28
- 16.163.86.128/26
- 16.163.220.0/25
- 43.198.20.64/26
- 43.198.20.128/28
- 15.228.171.128/25
- 15.229.44.0/26
- 15.229.52.128/26
- 15.229.52.80/28
- 157.241.17.0/26
- 157.241.55.64/26
- 13.245.248.192/26
- 13.245.248.160/27
- 13.246.147.0/26
Last verified: 2026-06-12
Official source: https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/administration/synthetic-public-minion-ips/
Where New Relic Synthetics Checks From
Official location data from the provider: addresses grouped by check location.
| Location | IP addresses |
|---|---|
| Washington, DC, USA | 44.202.178.0/24 · 44.202.180.0/23 · 44.210.68.0/24 · 44.210.110.0/25 · 152.38.128.64/26 · 152.38.132.0/24 · 64.251.196.0/24 |
| Columbus, OH, USA | 152.38.129.96/27 · 64.251.197.0/24 |
| San Francisco, CA, USA | 152.38.130.0/26 · 64.251.198.0/24 · 152.38.130.64/26 · 152.38.130.128/28 |
| Portland, OR, USA | 152.38.131.64/26 · 64.251.199.0/24 |
| Montreal, Québec, CA | 3.99.200.0/24 · 3.99.193.0/26 · 3.99.253.128/25 |
| Dublin, IE | 212.32.1.128/25 · 212.32.1.64/26 · 212.32.1.32/28 |
| London, England, UK | 212.32.0.64/26 · 212.32.0.128/25 · 212.32.0.32/27 · 212.32.3.0/25 |
| Paris, FR | 13.38.68.128/25 · 13.38.68.64/26 · 13.38.202.128/26 · 13.38.202.192/28 |
| Frankfurt, DE | 212.32.2.128/25 · 212.32.2.64/26 |
| Stockholm, SE | 16.16.1.128/25 · 13.50.68.0/26 |
| Milan, IT | 15.160.105.128/25 · 18.102.58.0/26 |
| Tokyo, JP | 35.77.208.0/24 · 35.79.233.64/26 · 35.79.233.128/28 |
| Seoul, KR | 3.38.229.128/25 · 15.165.193.192/26 |
| Singapore, SG | 13.214.242.0/25 · 13.214.223.192/26 · 18.141.238.128/25 |
| Sydney, AU | 64.251.192.128/25 · 64.251.193.0/28 · 64.251.192.64/26 |
| Mumbai, IN | 3.110.73.192/26 · 3.111.138.0/25 · 43.205.150.128/26 · 43.204.166.240/28 |
| Hong Kong, HK | 16.163.86.128/26 · 16.163.220.0/25 · 43.198.20.64/26 · 43.198.20.128/28 |
| São Paulo, BR | 15.228.171.128/25 · 15.229.44.0/26 · 15.229.52.128/26 · 15.229.52.80/28 |
| Manama, BH | 157.241.17.0/26 · 157.241.55.64/26 |
| Cape Town, ZA | 13.245.248.192/26 · 13.245.248.160/27 · 13.246.147.0/26 |
Whitelisting New Relic Synthetics-Monitoring IPs
Pick a format. The block below contains the complete config for every address in the list above. The plain list is also available as a .txt download.
ufw allow from 44.202.178.0/24 ufw allow from 44.202.180.0/23 ufw allow from 44.210.68.0/24 ufw allow from 44.210.110.0/25 ufw allow from 152.38.128.64/26 ufw allow from 152.38.132.0/24 ufw allow from 64.251.196.0/24 ufw allow from 152.38.129.96/27 ufw allow from 64.251.197.0/24 ufw allow from 152.38.130.0/26 ufw allow from 64.251.198.0/24 ufw allow from 152.38.130.64/26 ufw allow from 152.38.130.128/28 ufw allow from 152.38.131.64/26 ufw allow from 64.251.199.0/24 ufw allow from 3.99.200.0/24 ufw allow from 3.99.193.0/26 ufw allow from 3.99.253.128/25 ufw allow from 212.32.1.128/25 ufw allow from 212.32.1.64/26 ufw allow from 212.32.1.32/28 ufw allow from 212.32.0.64/26 ufw allow from 212.32.0.128/25 ufw allow from 212.32.0.32/27 ufw allow from 212.32.3.0/25 ufw allow from 13.38.68.128/25 ufw allow from 13.38.68.64/26 ufw allow from 13.38.202.128/26 ufw allow from 13.38.202.192/28 ufw allow from 212.32.2.128/25 ufw allow from 212.32.2.64/26 ufw allow from 16.16.1.128/25 ufw allow from 13.50.68.0/26 ufw allow from 15.160.105.128/25 ufw allow from 18.102.58.0/26 ufw allow from 35.77.208.0/24 ufw allow from 35.79.233.64/26 ufw allow from 35.79.233.128/28 ufw allow from 3.38.229.128/25 ufw allow from 15.165.193.192/26 ufw allow from 13.214.242.0/25 ufw allow from 13.214.223.192/26 ufw allow from 18.141.238.128/25 ufw allow from 64.251.192.128/25 ufw allow from 64.251.193.0/28 ufw allow from 64.251.192.64/26 ufw allow from 3.110.73.192/26 ufw allow from 3.111.138.0/25 ufw allow from 43.205.150.128/26 ufw allow from 43.204.166.240/28 ufw allow from 16.163.86.128/26 ufw allow from 16.163.220.0/25 ufw allow from 43.198.20.64/26 ufw allow from 43.198.20.128/28 ufw allow from 15.228.171.128/25 ufw allow from 15.229.44.0/26 ufw allow from 15.229.52.128/26 ufw allow from 15.229.52.80/28 ufw allow from 157.241.17.0/26 ufw allow from 157.241.55.64/26 ufw allow from 13.245.248.192/26 ufw allow from 13.245.248.160/27 ufw allow from 13.246.147.0/26
Cloudflare / WAF: create an IP Access Rule (or custom WAF skip rule) with action Allow for the addresses above, so bot fight mode and managed challenges never block probe traffic.
Whitelisting only exempts these addresses from blocking and rate-limiting rules. It grants no access beyond what your site already serves publicly.
Frequently Asked Questions
A minion is New Relic's name for the managed runner that executes synthetic checks. Public minions run in New Relic's cloud locations; their egress IP ranges are published per location.
Whitelisting everything is the safest option. If your monitors are pinned to specific locations, the location-grouped table below lets you restrict the allow list to exactly those. Remember to update it when you add locations.
The official public minion list is IPv4-only (CIDR ranges).
New Relic updates the JSON when locations are added or re-homed. Re-sync it periodically. The documentation page links the canonical file.
Both: wherever requests can be blocked. If your site sits behind a CDN or WAF (Cloudflare, AWS WAF, Akamai…), add an allow/skip rule there so probes are never challenged; if your origin firewall also filters traffic, whitelist them there too. A single missed layer is enough to cause false alerts.
Most providers expose a machine-readable source (linked above). Fetch it on a schedule, a small cron job that pulls the list and updates your firewall ruleset, instead of hardcoding addresses by hand. This page is re-verified against the official source regularly, but automation on your side is the most reliable option.
No. Allow-listing only exempts known monitoring addresses from blocking and rate-limiting rules. It grants no access beyond what your site already serves publicly, and authentication, authorization, and TLS are unchanged. You are simply telling your firewall "these are not attackers".
A blocklist keeps known-bad addresses out; an allow/whitelist makes sure known-good addresses, here, the monitoring probes, never end up caught in a block or rate-limit rule. The two coexist: you keep blocking attackers while explicitly exempting the probes.
The IP addresses on this page belong to New Relic Synthetics and are published by New Relic Synthetics for whitelisting purposes. List verified on 2026-06-12 against the official source. Always cross-check with the official documentation before locking down production firewalls. All product names and trademarks are the property of their respective owners; Uptimeify is not affiliated with New Relic Synthetics. Uptimeify's own worker IPs are published at /ips.txt; a feature comparison is on our comparison page.
Monitoring Without IP Guesswork.
Protect your clients' digital assets and lock down your webserver routing. Leverage our verified network catalogs for clean whitelist setups, or migrate directly to the rock-solid, EU-only architecture of Uptimeify.