This topic explains how companies that operate in work environments that require a static IP (fixed IP) can connect to TagoIO without using the DNS.

TagoIO's back-end servers have static IPs that can be added to your firewall in order to allow end-point devices and web clients to access TagoIO. 

Nevertheless, we do not recommend to program your end-point devices (sensors) to communicate with TagoIO by using a static IP. The reason for this is that when using a static IP you may lose the security offered through our certification system. At some point in the life-cycle of the project, the certificate can be renewed on TagoIO's side without advanced notice, and this can prevent the devices from accessing our servers.

Here is a list of static IPs that you could use:

ServicePrimary IPSecondary IPTCP Ports
API75.2.65.15399.83.158.6480443
Realtime75.2.27.15899.83.235.8480443
MQTT75.2.83.13099.83.172.11918838883


Here is a list of outbound IPs used in our Analysis:

Primary IP
Secondary IP
52.200.36.164
52.200.150.42

Make sure you allow the Primary and Secondary IP addresses

Note that the TagoIO Admin (admin.tago.io) does NOT offer a static IP because it uses a content delivery network (CDN). This means that every time users request resources from the Admin, the system will use the servers closest to them.