Device Manager - What IP addresses should I allow through my firewall?
Below are the IP addresses used by Device Manager (OEM Server).
Integrators (or even network operators) may need to white list the IPs shown under "Device Data from OEM server to Software Platforms" to ensure that data can make it through their firewall.
US | EU | |||
Traffic Type | DNS Entry | IP Address | DNS Entry | IP Address |
Device to OEM Server (Incoming device data) |
104.45.188.217 | eu1.oemserver.com | 13.69.27.101 | |
External parties to OEM Web API and Website (Incoming HTTP traffic) |
104.45.178.83 | 52.137.6.178 | ||
Device Data from OEM Server to Software Platforms (Outgoing device data from OEM, incoming to Software Platforms) |
4.156.126.50 104.45.178.34 104.45.185.0 40.76.129.151 40.76.131.46 40.76.132.83 52.149.254.194 52.151.234.162 52.151.246.3 52.186.38.21 52.188.180.27 52.188.216.242 52.188.217.241 52.191.90.98 52.226.91.133 57.152.16.244 135.237.66.82 135.237.56.128 |
13.80.182.189 20.126.65.156 |
||
Firmware/Aiding Data files hosted on OEM
OEM hosts some files needed by different devices |
20.188.210.208 (same for all 3 DNS entries) |
20.188.210.208 (same for all 3 DNS entries) |
Location Engine
Location Engine does not use Static IP addresses (even though it is an extension of OEM server).
Location Engine is hosted on Azure's ‘East US’ servers. The IP addresses used by these servers can be found here.
uBlox Aiding Data (deprecated)
Some older devices will connect directly to uBlox servers in order to download GNSS aiding data.
(Bolt, Dart2, Eagle, Falcon, G120, G62, Oyster2, Remora2, Yabby GPS, Yabby Wi-Fi)
All current devices download aiding data via Device Manager Server.
Server Description | DNS Entry |
uBlox aiding data server The IP addresses frequently change so it is important to add the DNS entry |
online-live1.services.u-blox.com online-live2.services.u-blox.com offline-live1.services.u-blox.com offline-live2.services.u-blox.com |