ObservePoint Whitelisting and Proxy List
Whitelisting and Proxies
The ObservePoint data collection servers use multiple IP addresses to access your website or mobile app. Your IT department and Analytics administrators need to know these IP addresses for firewall and analytics whitelisting.
- WebAssurance IP Addresses/Proxies
- AppAssurance IP Addresses/Proxies
- LiveConnect IP Addresses/Proxies
- ObservePoint WebAssurance User Agents
For security purposes, the ObservePoint IP addresses should be whitelisted to prevent a firewall from blocking traffic detected from the ObservePoint servers. ObservePoint can hit your website with dozens of page requests per minute as you run audits and web journeys, which can sometimes appear to your security devices as a malicious attack. To prevent your firewall from rejecting traffic from the ObservePoint servers, have your DevOps team whitelist all the IP addresses from the table below.
For web analytics traffic, some analysts prefer not to include ObservePoint traffic in any of their analytics reports. If this is the case, whitelist all IP addresses from the list below in your analytics administration console. See Exclude by IP Address for Adobe Analytics or Exclude Internal Traffic for Google Analytics.
WebAssurance IP Addresses & Proxy Locations
The following chart shows each of the IP addresses used by ObservePoint's technology. Best practice is to whitelist all of these on your firewall. The proxies will be used for geo-location testing.
Note: For HTTPS pages, ObservePoint will automatically allow access to the browsers location when prompted.
These IP Addresses are also available in a downloadable CSV file.
|IP Address||Amazon Proxy||Location||Coordinates||City|
|220.127.116.11||This is a direct server.||Direct—Oregon, US||45.5423706,-122.9345088||Portland|
|18.104.22.168||aws1.west.proxy.observepoint.com||Proxy—N. California, US||38.5617131,-121.5129516||Sacramento|
|22.214.171.124||aws1.west.proxy.observepoint.com||Proxy—N. California, US||38.5617131,-121.5129516||Sacramento|
|126.96.36.199||aws1.east.proxy.observepoint.com||Proxy—N. Virginia, US||38.8151083,-77.1258427||Alexandria|
|188.8.131.52||aws1.east.proxy.observepoint.com||Proxy—N. Virginia, US||38.8151083,-77.1258427||Alexandria|
|184.108.40.206||aws1.bra.proxy.observepoint.com||Proxy—Sao Paulo, Brazil||-22.530593,-50.8787667||Sao Paulo|
|220.127.116.11||aws1.bra.proxy.observepoint.com||Proxy—Sao Paulo, Brazil||-22.530593,-50.8787667||Sao Paulo|
|18.104.22.168||aws2.ca.proxy.observepoint.com|| Proxy—Toronto, Canada
All AppAssurance functionality is hosted in a different data center from WebAssurance. If you have any security restrictions on your APIs or Backend, best practice is to whitelist the following IP Addresses on your servers so that the app can send back data to your servers. Also, to ensure, the test traffic is not adding unnecessary noise to your Analytics data, best practice is to whitelist these addresses in your Analytics tool as well.
|22.214.171.124||Default AppAssurance traffic|
|126.96.36.199/24||Default AppAssurance traffic|
|188.8.131.52||Brazil (new with 2019-05-21)|
|184.108.40.206||Canada (new with 2019-05-21)|
|220.127.116.11||Germany (new with 2019-05-21)|
|18.104.22.168||Japan (new with 2019-05-21)|
|22.214.171.124||Singapore (new with 2019-05-21)|
|126.96.36.199||South Korea (new with 2019-05-21)|
|188.8.131.52||Sweden (new with 2019-05-21)|
|184.108.40.206||United Kingdom (new with 2019-05-21)|
|220.127.116.11||US East (new with 2019-05-21)|
The following IP addresses are also used by our servers when interacting with your apps in AppAssurance. You must whitelist these servers regardless of the country you expect to be testing in.
If you use LiveConnect, your firewall must allow access to the LiveConnect IP address: 18.104.22.168. This may have already been set up if you have configured all the AppAssurance proxies above.
ObservePoint WebAssurance User Agents
You may optionally whitelist our user agents.