New Relic IP ranges

Official New Relic ranges from the vendor's publication, split by purpose: agents, synthetics. The ranges below render live from the signed slash0 feed.

purpose	direction	IPv4	IPv6
`new-relic/agents`	egress	·	·
`new-relic/synthetics`	ingress	·	·

new-relic/agents

Direction: egress. Ranges your workloads connect out to; use them in security group egress rules.

loading ranges from the feed…

Terraform

data "ipranges_egress" "new_relic_agents" {
  service = "new-relic"
  purpose = "agents"
}

resource "aws_security_group_rule" "new_relic_agents" {
  type              = "egress"
  from_port         = 443
  to_port           = 443
  protocol          = "tcp"
  cidr_blocks       = data.ipranges_egress.new_relic_agents.ipv4_cidrs
  ipv6_cidr_blocks  = data.ipranges_egress.new_relic_agents.ipv6_cidrs
  security_group_id = aws_security_group.app.id
}

new-relic/synthetics

Direction: ingress. Ranges New Relic connects from (webhook delivery); use them in security group ingress rules on your receiving endpoints.

loading ranges from the feed…

Terraform

data "ipranges_ingress" "new_relic_synthetics" {
  service = "new-relic"
  purpose = "synthetics"
}

resource "aws_security_group_rule" "new_relic_synthetics" {
  type              = "ingress"
  from_port         = 443
  to_port           = 443
  protocol          = "tcp"
  cidr_blocks       = data.ipranges_ingress.new_relic_synthetics.ipv4_cidrs
  security_group_id = aws_security_group.app.id
}

keep rules current automatically

Terraform data sources refresh only when you run an apply. The hosted tier publishes the same data via AWS managed prefix lists (slash0.new-relic.agents.v4 and so on), shared into your account via AWS RAM: rules reference one pl-… id and update within a minute of a vendor change, with removals held through a 72 hour grace window. Request early access or read how it works.

provenance

Ranges come from New Relic's official publication: https://docs.newrelic.com/docs/new-relic-solutions/get-started/networks/. Fetched sources:

Every publish is signed (ECDSA P-256 over the feed index, each service document hash-chained to it) and every range change is recorded in the changelog. Verification steps: security. Provider setup: quickstart.