How can we help you?

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Customer Support
Networks and Connectivity

What are the ports, protocols, and IP addresses used by Avatour?

Corporate networks may need to open TCP ports or "whitelist" IP addresses for optimal Avatour performance. This article lists these requirements.

Similar to other real-time communications platforms like Zoom and Microsoft Teams, Avatour recommends the use of UDP transport for best performance. If UDP is unavailable, Avatour will fall back to encrypted TCP over 443, but this increases overhead considerably and reduces quality.

Most home networks and some corporate networks permit UDP connections by default. However, networks with more restrictive firewalls may block such connections.  If your Avatour network test shows an "X" in the UDP column, for best performance you will need to request that your IT team "whitelist" the connections on this page.


Responsive Table
Connection Hostname / DNS IP(s) Port (Protocol)
AVATOUR API dynamic 443 (TCP)
Signaling + SFU (US) (EU) (Asia)
443 (TCP)
Twilio Network Traversal Service (TURN) Dynamic
Network Traversal Service Regions | Twilio
3478 (UDP/TCP)
443 (UDP/TCP)
Edge Cloud Processor (Frankfurt) (London) (Oregan) (Ohio) (Mumbai) (Singapore)
443 (TCP)
Name Server
443 (TCP)
5058 (UDP)
Master Server 443 (TCP)
5055 (UDP)
Telemetry Relay Server 443 (TCP)
5056 (UDP)
Chat Server 443 (TCP)
Cloud Auth Service <dynamic> 443 (TCP)
Cloud Asset Storage <dynamic> 443 (TCP)
Cloud CDN Resource <dynamic> 443 (TCP)

1. Resolving the host names stated in this list requires the DNS query port 53/UDP to be open to a public name server or for a local name server to be available with request forwarding to a public source.