Approve & Exclude ObservePoint Traffic
Overview
The ObservePoint data collection servers use multiple private IP addresses to access your website.
Your IT department and Analytics administrators need to know these IP addresses to approve traffic blocked by firewalls (and other bot detection methods) and exclude traffic from analytics.
Note: You are NOT required to approve all of them, but if you don't, it will limit the proxies you have available to you in the platform.
Firewall Approval
For security purposes, the ObservePoint IP addresses should be approved by your IT teams 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 Journeys, which can sometimes appear to your security devices as a malicious attack.
To prevent your firewall from rejecting traffic from ObservePoint servers, have your Security teams approve all the IP addresses from the table below.
Note: If firewall approval is not an option, review these other methods with your Security teams to ensure ObservePoint can securely access your web properties.
Exclude ObservePoint Traffic from Analytics
It is a best practice to exclude ObservePoint traffic from inflating your analytics reports. To do so, EXCLUDE all IP addresses listed below in your analytics administration console.
Note: See Exclude by IP Address for Adobe Analytics or Exclude Internal Traffic for Google Analytics.
IP Addresses & Proxy Locations
The following chart shows each of the IP addresses used by ObservePoint's Audits & Journeys. The proxies will be used for geo-location testing.
These IP Addresses are also available in a downloadable CSV file.
Note: For HTTPS pages, ObservePoint will automatically allow access to the browsers location when prompted.
IP Address | Amazon Proxy | Location | Coordinates | City |
---|---|---|---|---|
35.161.29.125 | This is a direct server. | Direct—Oregon, US | 45.5423706,-122.9345088 | Portland |
54.241.3.7 | aws1.west.proxy.observepoint.com | Proxy—N. California, US | 38.5617131,-121.5129516 | Sacramento |
54.215.6.50 | aws2.west.proxy.observepoint.com | Proxy—N. California, US | 38.5617131,-121.5129516 | Sacramento |
54.235.253.73 | aws1.east.proxy.observepoint.com | Proxy—N. Virginia, US | 38.8151083,-77.1258427 | Alexandria |
54.83.59.214 | aws2.east.proxy.observepoint.com | Proxy—N. Virginia, US | 38.8151083,-77.1258427 | Alexandria |
54.246.83.204 | aws1.emea.proxy.observepoint.com | Proxy—Dublin, Ireland | 53.3242381,-6.3857834 | Dublin |
79.125.118.108 | aws2.emea.proxy.observepoint.com | Proxy—Dublin, Ireland | 53.3242381,-6.3857834 | Dublin |
54.248.228.95 | aws1.apac.proxy.observepoint.com | Proxy—Tokyo, Japan | 35.6682234,139.6708286 | Tokyo |
54.250.119.103 | aws2.apac.proxy.observepoint.com | Proxy—Tokyo, Japan | 35.6682234,139.6708286 | Tokyo |
54.233.189.245 | aws1.bra.proxy.observepoint.com | Proxy—Sao Paulo, Brazil | -22.530593,-50.8787667 | Sao Paulo |
54.233.210.11 | aws2.bra.proxy.observepoint.com | Proxy—Sao Paulo, Brazil | -22.530593,-50.8787667 | Sao Paulo |
35.176.213.160 | aws1.lon.proxy.observepoint.com | Proxy—London, England | 51.5285582,-0.2416782 | London |
35.176.42.87 | aws2.lon.proxy.observepoint.com | Proxy—London, England | 51.5285582,-0.2416782 | London |
35.157.253.184 | aws1.deu.proxy.observepoint.com | Proxy—Frankfurt, Germany | 50.1211909,8.566525 | Frankfurt |
35.159.7.189 | aws2.deu.proxy.observepoint.com | Proxy—Frankfurt, Germany | 50.1211909,8.566525 | Frankfurt |
13.228.165.163 | aws1.sgp.proxy.observepoint.com | Proxy—Singapore | 1.3142837,103.7475779 | Singapore |
13.228.165.59 | aws2.sgp.proxy.observepoint.com | Proxy—Singapore | 1.3142837,103.7475779 | Singapore |
52.65.182.248 | aws1.aus.proxy.observepoint.com | Proxy—Sydney, Australia | -33.8479271,150.6518023 | Sydney |
54.79.15.183 | aws2.aus.proxy.observepoint.com | Proxy—Sydney, Australia | -33.8479271,150.6518023 | Sydney |
15.222.131.206 | aws1.ca.proxy.observepoint.com | Proxy—Toronto, Canada | 43.7181557,-79.5181383 | Toronto |
52.60.121.52 | aws2.ca.proxy.observepoint.com | Proxy—Toronto, Canada |
43.7181557,-79.5181383 | Toronto |
3.36.203.19 | aws1.seoul.proxy.observepoint.com | Proxy - Seoul, Korea |
37.57014467452795,126.98294318229894 |
Seoul |
3.37.11.36 | aws2.seoul.proxy.observepoint.com | Proxy - Seoul, Korea |
37.57014467452795,126.98294318229894 |
Seoul |
LiveConnect Proxy
If you use LiveConnect, your firewall must allow access to the LiveConnect IP address:
IP Address |
Amazon Proxy | Location | Coordinates |
13.57.103.60 |
??? | Direct—Oregon, US |
??? |
ObservePoint User Agents
You may use ObservePoint user agents to identify and exclude or approve traffic coming from our servers.
Note: All User Agent strings contain the name "ObservePoint"