This article outlines the required network configuration and whitelisting needed to ensure full communication between EloView 3 and managed devices. Please ensure the following domains, IPs, and ports are accessible.

Required EloView 3 Domains

Additional Required IPs

Armor Hosts:

• 74.120.218.143

• 74.120.218.144

Cloudflare CDN

EloView 3 services also rely on Cloudflare’s global content delivery network (CDN).

• Recommendation: Always whitelist by domain name (the EloView domains above).

• Why: Cloudflare IP addresses are dynamic and subject to change. IP whitelisting can cause unexpected service interruptions.

• Reference only: If your firewall requires explicit IPs, the following are currently in use:

IPv4:

• 103.21.244.0/22
• 103.22.200.0/22
• 103.31.4.0/22
• 104.16.0.0/13
• 104.24.0.0/14
• 108.162.192.0/18
• 131.0.72.0/22
• 141.101.64.0/18
• 162.158.0.0/15
• 172.64.0.0/13
• 173.245.48.0/20
• 188.114.96.0/20
• 190.93.240.0/20
• 197.234.240.0/22
• 198.41.128.0/17

IPv6:

• 2400:cb00::/32
• 2606:4700::/32
• 2803:f800::/32
• 2405:b500::/32
• 2405:8100::/32
• 2a06:98c0::/29
• 2c0f:f248::/32

Required Ports & Protocols

• 443 (HTTPS): Full access to all EloView domains (*.eloview.com) is required

• 123 (UDP – NTP): Required for time synchronization via 2.android.pool.ntp.org

Note: EloView-enabled Android devices use WebSocket (WSS) for secure, persistent communication with the EloView cloud. All sessions are device-initiated.

✅ Summary:
For EloView 3 devices to function correctly, whitelist the EloView domains, allow access to the listed Armor IPs, ensure the required ports are open, and allow NTP synchronization. Always use domain-based rules instead of IPs to prevent service disruptions.

Last updated: September 2026