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:
104.16.60.227, 104.16.61.227, 104.16.62.227, 104.16.63.227, 104.16.64.227

IPv6:
2606:4700::6810:3ce3, 2606:4700::6810:3de3, 2606:4700::6810:3ee3, 2606:4700::6810:3fe3, 2606:4700::6810:40e3

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 2025