Monnit Platform Infrastructure Update – March 17, 2026

Overview

On March 17, 2026, Monnit will perform a scheduled infrastructure update to improve platform redundancy and long-term reliability. As part of this update, the platform will migrate to a cloud-based load balancer.

Most customers will not need to take any action.

However, organizations that restrict outbound network traffic by IP address may need to update their firewall rules to ensure uninterrupted device communication.

Maintenance Window

Information

Item	Details
Date	March 17, 2026
Start Time	10:00 AM Eastern Time
Estimated Duration	Up to 8 hours

When Action Is Required

If your organization restricts outbound connections using IP allow lists, you must add the following IP addresses before the maintenance window.

Failing to allow these addresses may prevent gateways or users from connecting to the Monnit platform.

Required Firewall Allow List

Gateway Communication

Monnit gateways communicate with the platform over TCP and UDP port 3000.

Allow outbound traffic to:

166.117.35.68
166.117.206.175

Port: TCP/UDP 3000

Website and Application Access

Browsers and applications accessing the Monnit platform must allow outbound connections on:

Ports: 80 and 443

Allow outbound traffic to:

44.241.242.96
44.228.29.168

Example Firewall Rules

Below are examples of firewall rules that may be used by network administrators.

These examples allow outbound traffic from an internal network to the required Monnit infrastructure.

Cisco ASA / Cisco Firewall

Shell

access-list MONNIT-OUT extended permit tcp any host 166.117.35.68 eq 3000

access-list MONNIT-OUT extended permit tcp any host 166.117.206.175 eq 3000

access-list MONNIT-OUT extended permit tcp any host 44.241.242.96 eq 80

access-list MONNIT-OUT extended permit tcp any host 44.241.242.96 eq 443

access-list MONNIT-OUT extended permit tcp any host 44.228.29.168 eq 80

access-list MONNIT-OUT extended permit tcp any host 44.228.29.168 eq 443

Palo Alto Firewall

Destination IPs:

166.117.35.68
166.117.206.175

Application:

tcp

Service:

tcp-3000

Website access:

Destination IPs:

44.241.242.96
44.228.29.168

Service:

tcp-80
tcp-443

Windows Firewall

Run in an elevated PowerShell session.

PowerShell

New-NetFirewallRule -DisplayName "Monnit Gateway 1" -Direction Outbound -Protocol TCP -RemoteAddress 166.117.35.68 -RemotePort 3000 -Action Allow

New-NetFirewallRule -DisplayName "Monnit Gateway 2" -Direction Outbound -Protocol TCP -RemoteAddress 166.117.206.175 -RemotePort 3000 -Action Allow

Website access:

PowerShell

New-NetFirewallRule -DisplayName "Monnit Web 1" -Direction Outbound -Protocol TCP -RemoteAddress 44.241.242.96 -RemotePort 80,443 -Action Allow

New-NetFirewallRule -DisplayName "Monnit Web 2" -Direction Outbound -Protocol TCP -RemoteAddress 44.228.29.168 -RemotePort 80,443 -Action Allow

Linux iptables Example

Shell

iptables -A OUTPUT -p tcp -d 166.117.35.68 --dport 3000 -j ACCEPT

iptables -A OUTPUT -p tcp -d 166.117.206.175 --dport 3000 -j ACCEPT

iptables -A OUTPUT -p tcp -d 44.241.242.96 --dport 80 -j ACCEPT

iptables -A OUTPUT -p tcp -d 44.241.242.96 --dport 443 -j ACCEPT

iptables -A OUTPUT -p tcp -d 44.228.29.168 --dport 80 -j ACCEPT

iptables -A OUTPUT -p tcp -d 44.228.29.168 --dport 443 -j ACCEPT

AWS Security Group Example

Type: Custom TCP
Port: 3000
Destination: 166.117.35.68/32

Type: Custom TCP
Port: 3000
Destination: 166.117.206.175/32

Website:

HTTP  -> 44.241.242.96/32
HTTPS -> 44.241.242.96/32

HTTP  -> 44.228.29.168/32
HTTPS -> 44.228.29.168/32

If You Are Unsure

If you are unsure whether your network restricts outbound traffic by IP address:

Forward this article to your IT or network administrator
Ask them to confirm whether outbound allow lists are used

Most networks do not require any changes.