IP Addresses used by MXO
To fully integrate MXO with your existing systems, for example, to connect your backend systems with MXO through your corporate firewall, you may want to whitelist the IP addresses MXO uses to connect with those systems. You can do this by adding both inbound and outbound rules to your firewalls.
This section provides details of the latest set of IP addresses for MXO servers running with our cloud provider.
Outbound Connections from MXO
For Data Adapters making outbound calls to external web services, such as your CRM system, whitelist the following IP addresses.
You need only whitelist the IP addresses for the MXO server to which you connect.
| Tenancies on | NA5 (North American Data Centers) | EU2 (European Data Centers) | AP1 (Asia Pacific Data Centers) |
|---|---|---|---|
| 13.83.66.141 | 52.155.160.82 | 20.188.216.218 | |
| 13.83.66.149 | 52.155.161.16 | 20.40.121.138 | |
| 13.83.65.48 | 52.155.161.125 | 20.40.126.196 | |
| 13.83.66.160 | 52.156.204.60 | 20.40.126.202 | |
| 52.224.188.108 | 40.119.147.54 | 20.40.164.21 | |
| 52.224.188.155 | 40.119.148.6 | 20.40.165.176 | |
| 52.224.188.166 | 40.119.151.248 | 20.40.167.23 | |
| 52.224.188.229 | 40.74.0.3 | 20.40.167.25 | |
| 40.112.221.171 | 40.118.22.50 | 52.187.228.70 | |
| 23.99.64.138 | 40.118.17.46 | 104.210.68.170 | |
| 20.62.223.17 |
Why do I have to whitelist so many Outbound IP addresses?
We list our IP addresses on a per data-center basis, to reduce the total number of IP addresses that any brand needs to whitelist. Each region, however, requires you to whitelist several IP addresses for the following reasons:
- It allows us to continue the expansion of our platform in each region.
- It provides us with the ability to deprecate older IP addresses, in the future, as and when required by changes to Microsoft Azure.
- It enables us to offer continued improvements in terms of availability, maintenance processes, and disaster recovery processes.
Inbound Connections to MXO
For requests coming in to MXO , such as the one-tag.js (for web) or SDKs (for mobile) sending events, as well as OAuth and Server-side API requests, whitelist the following IP addresses.
| ALL TENANCIES | IP ADDRESSES |
|---|---|
20.188.220.17 20.40.185.168 20.40.167.240 20.40.165.8 20.219.148.21 20.204.211.208 51.105.108.194 51.105.161.240 13.64.36.208 13.83.249.234 52.188.78.106 52.151.228.105 52.142.82.147 52.142.83.128 191.233.245.23 191.233.244.233 |
Why are Inbound IP addresses not separated by region?
We use a Point-of-Presence architecture providing a global set of endpoints to which you and your clients can connect. For example, clients in Europe, connecting to our data center in the USA, connect to a local Point-of-Presence and their traffic is routed to the USA by dedicated network backbones.
