Download PDF
Download page SaaS Domains and IP Ranges.
SaaS Domains and IP Ranges
This page lists the current Splunk AppDynamics SaaS IP ranges and domains for each region. Due to the SaaS architecture, you need to configure all ranges and individual IP addresses in your allowlists to ensure successful connectivity. Note that the IP addresses are subject to change. See Firewall Considerations for configuring the platform endpoints and tips for setting up firewalls.
Controller Tenants
SaaS Controller Tenants listen for incoming communication from agents on port 443. Thus, unless there is a DDOS attack, SaaS Controller Tenants have no rules to block any traffic on port 443.
All Splunk AppDynamics-hosted Components/Services
The Splunk AppDynamics-hosted components and services only support the TCP protocol. The list of domains on this page is not exhaustive. You might encounter domains and IP addresses not listed on the page that might require firewall access. If you determine that such domains require firewall access, you can include them in the firewall allow-list.
Americas
Platform Components | Domains | AWS Region | IP Addresses/Ranges |
---|---|---|---|
Cisco Cloud Observability | https://observe.appdynamics.com | us-west-2-pdx-1a (AWS Local Zone) | |
Splunk AppDynamics Content Delivery Network (CDN) | https://cdn.appdynamics.com | Splunk AppDynamics uses Amazon CloudFront for the CDN. See the CloudFront IP ranges for the possible IP addresses used for the Splunk AppDynamics CDN. | |
Splunk AppDynamics OpenTelemetry Service (SaaS Controller) | https://pdx-sls-agent-api.saas.appdynamics.com | us-west-2 | Please refer to the AWS IP range JSON file for the IP ranges for the us-west-2 region. |
Serverless Service | |||
Analytics | https://analytics.api.appdynamics.com | ||
Controller Tenant |
| Splunk AppDynamics will provide a unique set of IP addresses at the time of provisioning the Controller Tenant within AWS. | |
EUM Cloud | https://col.eum-appdynamics.com or http://pdx-col.eum-appdynamics.com (EUM Collector)As part of a critical infrastructure upgrade, Splunk AppDynamics will be deprecating support for static IP ranges for the PDX/Oregon SaaS EUM collector If you have any questions or concerns, please contact customer support or use our support portal. | Please refer to the AWS IP range JSON file for the IP ranges for the | |
IoT REST API | https://iot-col.eum-appdynamics.com | ||
Screenshot Service | https://image.eum-appdynamics.com | ||
Synthetic Server | https://synthetic.api.appdynamics.com |
| |
Synthetic Server Feeder | wss://synthetic-feeder.api.appdynamics.com | Please refer to the AWS IP range JSON file for the IP ranges for the us-west-2 region. | |
Synthetic Hosted Agents | See Synthetic Hosted Agents. |
Notes:
All traffic originating from the Oregon Datacenter environment will have one of the following source IP addresses:
34.218.183.67
52.88.49.75
34.218.135.55
44.224.91.190
44.224.93.208
100.21.44.47
35.163.240.75
100.21.168.150
44.224.41.204
Platform Components | Domains | AWS Region | IP Addresses/Ranges |
---|---|---|---|
Splunk AppDynamics Content Delivery Network (CDN) | https://cdn.appdynamics.com | Splunk AppDynamics uses Amazon CloudFront for the CDN. See the CloudFront IP ranges for the possible IP addresses used for the Splunk AppDynamics CDN. | |
Splunk AppDynamics OpenTelemetry Service (SaaS Controller) | https://gru-sls-agent-api.saas.appdynamics.com | sa-east-1 | Please refer to the AWS IP range JSON file for the IP ranges for the sa-east-1 region. |
Serverless Service | |||
Analytics | https://gru-ana-api.saas.appdynamics.com | ||
Controller Tenant |
| Splunk AppDynamics will provide a unique set of IP addresses at the time of provisioning the Controller Tenant within AWS. | |
EUM Cloud |
| Please refer to the AWS IP range JSON file for the IP ranges for the | |
IoT REST API | https://gru-iot-col.eum-appdynamics.com | ||
Synthetic Server Feeder |
| ||
Synthetic Server |
| ||
Synthetic Server Feeder | https://gru-image.eum-appdynamics.com | ||
Synthetic Hosted Agents | See Synthetic Hosted Agents. |
Notes:
All traffic originating from the Sao Paolo Datacenter environment will have one of the following source IP addresses:
54.94.50.188
54.233.178.89
18.229.226.158
Platform Components | Domains | Azure Region | IP Addresses/Ranges |
---|---|---|---|
Splunk AppDynamics Content Delivery Network (CDN) | https://ui-cdn-fd.saas.appdynamics.com/saas | Global | Please refer to the Azure IP range JSON file for the IP ranges for Global region. |
Splunk AppDynamics OpenTelemetry Service (SaaS Controller) | https://yyz-sls-api.saas.appdynamics.com
| Canada Central | 130.107.35.41 |
Serverless Service | |||
Analytics | 130.107.34.215 | ||
Controller Tenant | https://my-controller-tenant.saas.appdynamics.com | 4.248.243.254 | |
EUM Cloud | https://yyz-eum-collector.saas.appdynamics.com (EUM Collector) https://yyz-eum-api.saas.appdynamics.com (EUM API) | 4.248.232.170 | |
Screenshot Service | https://yyz-eum-image.saas.appdynamics.com | 4.248.232.170 |
The following platform components are not supported in the Azure regions:
- IoT REST API
- Synthetic Server Feeder
- Synthetic Server
- Synthetic Server Feeder
- Synthetic Hosted Agents
EMEA
Platform Components | Domains | AWS Region | IP Addresses/Range |
---|---|---|---|
Splunk AppDynamics Content Delivery Network (CDN) | https://cdn.appdynamics.com | Splunk AppDynamics uses Amazon CloudFront for the CDN. See the CloudFront IP ranges for the possible IP addresses used for the Splunk AppDynamics CDN. | |
Splunk AppDynamics OpenTelemetry Service (SaaS Controller) | https://fra-sls-agent-api.saas.appdynamics.com | eu-central-1 | Please refer to the AWS IP range JSON file for the IP range for the AWS region eu-central-1 . |
Serverless Service | |||
Analytics | https://fra-ana-api.saas.appdynamics.com | ||
Controller Tenant | https://my-controller-tenant.saas.appdynamics.com | Splunk AppDynamics will provide a unique set of IP addresses at the time of provisioning the Controller Tenant within AWS. | |
EUM Cloud |
| Please refer to the AWS IP range JSON file for the IP range for the AWS region | |
IoT REST API | https://fra-iot-col.eum-appdynamics.com | ||
Screenshot Service | https://fra-image.eum-appdynamics.com | ||
Synthetic Server | https://fra-synthetic.eum-appdynamics.com |
| |
Synthetic Server Feeder | wss://fra-synthetic-feeder.eum-appdynamics.com | Please refer to the AWS IP range JSON file for the IP range for the AWS region eu-central-1 . | |
Synthetic Hosted Agents | See Synthetic Hosted Agents. |
Notes:
All traffic originating from the Frankfurt Datacenter environment will have one of the following source IP addresses:
18.195.41.33
18.195.153.182
18.195.58.148
Platform Components | Domains | AWS Region | IP Addresses/Range |
---|---|---|---|
Splunk AppDynamics Content Delivery Network (CDN) | https://cdn.appdynamics.com | Splunk AppDynamics uses Amazon CloudFront for the CDN. See the CloudFront IP ranges for the possible IP addresses used for the Splunk AppDynamics CDN. | |
Splunk AppDynamics OpenTelemetry Service (SaaS Controller) | Coming soon | eu-west-2 | Please refer to the AWS IP range JSON file for the IP range for the AWS region eu-west-2 . |
Serverless Service | |||
Analytics | https://lon-ana-api.saas.appdynamics.com | ||
Controller Tenant | https://my-controller-tenant.saas.appdynamics.com | Splunk AppDynamics will provide a unique set of IP addresses at the time of provisioning the Controller Tenant within AWS. | |
EUM Cloud |
| Please refer to the AWS IP range JSON file for the IP range for the AWS region | |
IoT REST API | https://lon-iot-col.eum-appdynamics.com | ||
Screenshot Service | https://lon-image.eum-appdynamics.com | ||
Synthetic Server Feeder |
| ||
Synthetic Server | https://lon-synthetic.eum-appdynamics.com | ||
Synthetic Server Feeder | wss://lon-synthetic-feeder.eum-appdynamics.com | ||
Synthetic Hosted Agents | See Synthetic Hosted Agents. |
Notes:
All traffic originating from the London Datacenter environment will have one of the following source IP addresses:
3.8.253.170
18.135.187.156
18.135.213.75
APAC
Platform Components | Domains | AWS Region | IP Addresses/Range |
---|---|---|---|
Splunk AppDynamics Content Delivery Network (CDN) | https://cdn.appdynamics.com | Splunk AppDynamics uses Amazon CloudFront for the CDN. See the CloudFront IP ranges for the possible IP addresses used for the Splunk AppDynamics CDN. | |
Splunk AppDynamics OpenTelemetry Service (SaaS Controller) |
| ap-south-1 | Please refer to the AWS IP range JSON file for the IP range for the AWS region ap-south-1. |
Serverless Service | |||
Analytics | https://bom-ana-api.saas.appdynamics.com | ||
Controller Tenant | https://my-controller-tenant.saas.appdynamics.com | Splunk AppDynamics will provide a unique set of IP addresses at the time of provisioning the Controller Tenant within AWS. | |
EUM Cloud |
| Please refer to the AWS IP range JSON file for the IP range for the AWS region | |
IoT REST API |
| Please refer to the AWS IP range JSON file for the IP range for the AWS region | |
Screenshot Service | https://bom-image.eum-appdynamics.com | ||
Synthetic Server Feeder |
| ||
Synthetic Server |
| ||
Synthetic Hosted Agents | See Synthetic Hosted Agents. |
Notes:
All traffic originating from the Mumbai Datacenter environment will have one of the following source IP addresses:
13.232.191.174
3.7.186.32
13.127.49.48
Platform Components | Domains | AWS Region | IP Addresses/Range |
---|---|---|---|
Splunk AppDynamics Content Delivery Network (CDN) | https://cdn.appdynamics.com | Splunk AppDynamics uses Amazon CloudFront for the CDN. See the CloudFront IP ranges for the possible IP addresses used for the Splunk AppDynamics CDN. | |
Splunk AppDynamics for OpenTelemetry |
|
| Please refer to the AWS IP range JSON file for the IP range for the AWS region ap-southeast-1 . |
Serverless Service | |||
Analytics | https://sin-ana-api.saas.appdynamics.com | ||
Controller Tenant | https://my-controller-tenant.saas.appdynamics.com | Splunk AppDynamics will provide a unique set of IP addresses at the time of provisioning the Controller Tenant within AWS. | |
EUM Cloud |
| Please refer to the AWS IP range JSON file for the IP range for the AWS region | |
IoT REST API |
| ||
Screenshot Service | https://sin-image.eum-appdynamics.com | ||
Synthetic Server |
| ||
Synthetic Server Feeder | wss://sin-synthetic-feeder.eum-appdynamics.com | ||
Synthetic Hosted Agents | See Synthetic Hosted Agents. |
Notes:
All traffic originating from the Singapore Datacenter environment will have one of the following source IP addresses:
13.228.123.222
54.169.20.120
13.229.165.25
Platform Components | Domains | AWS Region | IP Addresses/Range |
---|---|---|---|
Splunk AppDynamics Content Delivery Network (CDN) | https://cdn.appdynamics.com | Splunk AppDynamics uses Amazon CloudFront for the CDN. See the CloudFront IP ranges for the possible IP addresses used for the Splunk AppDynamics CDN. | |
Splunk AppDynamics OpenTelemetry Service (SaaS Controller) | https://syd-sls-agent-api.saas.appdynamics.com | ap-southeast-2 | Please refer to the AWS IP range JSON file for the IP range for the AWS region ap-southeast-2 . |
Serverless Service | |||
Analytics | https://syd-ana-api.saas.appdynamics.com | ||
Controller Tenant | https://my-controller-tenant.saas.appdynamics.com | Splunk AppDynamics will provide a unique set of IP addresses at the time of provisioning the Controller Tenant within AWS. | |
EUM Cloud |
| Please refer to the AWS IP range JSON file for the IP range for the AWS region | |
IoT REST API |
| ||
Screenshot Service | https://syd-image.eum-appdynamics.com | ||
Synthetic Server |
| ||
Synthetic Server Feeder | wss://syd-synthetic-feeder.eum-appdynamics.com | ||
Synthetic Hosted Agents | See Synthetic Hosted Agents. |
Notes:
All traffic originating from the Sydney Datacenter environment will have one of the following source IP addresses:
13.210.238.7
13.54.206.49
13.55.209.28
Synthetic Hosted Agents
Agent Location | Region | IP Address |
---|---|---|
Ashburn | us-east-1 |
|
San Francisco | us-west-1 |
|
Oregon | us-west-2 |
|
Mumbai | ap-south-1 |
|
Seoul | ap-northeast-2 |
|
Singapore | ap-southeast-1 |
|
Sydney | ap-southeast-2 |
|
Tokyo | ap-northeast-1 |
|
Montreal | ca-central-1 |
|
Frankfurt | eu-central-1 |
|
Dublin | eu-west-1 |
|
London | eu-west-2 |
|
Milan | eu-south-1 |
|
Paris | eu-west-3 |
|
Sao Paulo | sa-east-1 |
|
Cape Town |
|
|
Splunk AppDynamics provides the following Azure cloud regions. Each region, in addition, provides a selection of agent locations.
Linux-based Synthetic Hosted Agent
Azure Cloud Region | IP Adress | Agent Location in Controller UI |
---|---|---|
Oregon |
| Amsterdam |
| Chennai | |
| Melbourne | |
52.183.192.32/28 | San Antonio | |
| Toronto | |
Sydney | 4.200.129.176/28 | Melbourne |
Mumbai | 20.235.179.192/28 | Chennai |
52.183.192.32/28 | San Antonio |
Mapping of Execution Containers and Browser Locations
The table below lists the available browser locations as well as the corresponding provider and container location.
* Browser Location | Provider | Container Location |
---|---|---|
Ashburn, Virginia | AWS | US East (N. Virginia) |
Montreal, Québec | AWS | |
Toronto, Ontario | Azure | |
Amsterdam, Netherlands | Azure | EU (Ireland) |
Dublin, Ireland | AWS | |
Frankfurt, Germany | AWS | |
London, United Kingdom | AWS | |
Milan, Italy | AWS | |
Paris, France | AWS | |
Hong Kong, China | AWS | Asia Pacific (Tokyo) |
Seoul, South Korea | AWS | |
Tokyo, Japan | AWS | |
Chennai, India | Azure | Asia Pacific (Singapore) |
Mumbai, India | AWS | |
Singapore | AWS | |
Melbourne, Australia | Azure | Asia Pacific (Sydney) |
Sydney, Australia | AWS | |
Boardman, Oregon | AWS | US West (Oregon) |
San Francisco, California | AWS | |
Sao Paulo, Brazil | AWS | |
San Antonio, Texas | Azure |
Info |
---|
*Some of the locations are enabled only based on requests in the new regional clouds. To add missing locations in any regional cloud, raise a support ticket with the list of required locations. |
Hosted Agent Coverage Variations
Synthetic hosted agents have the following coverage variations:
- The US EUM cloud has access to both AWS and Azure locations.
- The Frankfurt EUM cloud has access to only AWS locations.
- The Sydney EUM cloud has access to only AWS locations.
The Bombay EUM cloud has access to only AWS locations.
- The GRU EUM cloud has access to only AWS locations.