OEM - What IP addresses should I allow through my firewall?
Written by Matthew Clark-Massera
Updated at July 5th, 2023
Table of Contents
As of May 2019, OEM server was migrated to Azure servers hosted in the US. Below are the IP addresses used by OEM server. Integrators will 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.
| Traffic Type | DNS Entry | IP Address |
| Device to OEM Server (Incoming device data) |
s0.oemserver.com, s1.oemserver.com, s2.oemserver.com |
104.45.188.217 |
| External parties to OEM Web API and Website (Incoming HTTP traffic) |
www.oemserver.com, api.oemserver.com |
104.45.178.83 |
| Device Data from OEM Server to Software Platforms (Outgoing device data from OEM, incoming to Software Platforms) |
104.45.178.34 52.188.216.242 52.226.91.133 52.191.90.98 40.76.131.46 52.151.246.3 52.188.180.27 52.149.254.194 52.186.38.21 |
|
| Firmware/Aiding Data files hosted on OEM OEM hosts some files needed by different devices |
ublox.oemserver.com nrf.oemserver.com lr1110.oemserver.com |
20.188.210.208 (same for all 3 DNS entries) |
uBlox Aiding Data
| Server Description | DNS Entry |
|
The device will also periodically connect in to the uBlox servers, so these entries should be white listed also. 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 |
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.