Firewall Configuration

Port and firewall rules required for VSee services to function correctly.

Using Zscaler? See VSee calls behind Zscaler for the exact bypass settings.

Overview

VSee services will attempt to navigate network architecture to the best of their ability. However, in order to guarantee the best results, please add the following port and firewall rules to your corporate firewall / router systems.

Please note that VSee is not able to provide fixed IP addresses for these servers. However, these IP addresses are relatively stationary, and any changes will be posted here at least 1 month in advance.

All firewall rules are subject to change with at least 1 month of prior notice.

Network Security Diagram

VSee Security Network Diagram — shows communication paths between end users (Browser Call, Messenger Kit, Messenger, Phone dial-in) and AWS VPC services (Relay/coTurn, Messenger, XMPP Directory, API, Clinic application servers)

VSee Security Network Diagram v3.2

The diagram predates the October 15, 2026 port update. Where they differ, the port tables below are authoritative.

Simplified Rules

If *.vsee.com can be whitelisted, please add this into your firewall rules with the following ports:

PurposeProtocol: PortDetail Servers
VSee Directory, Relay, Call management, Diagnostics, etc.
Required for VSee Messenger authentication, address book services, establishing video calls, video packets relay, VSee Messenger chat communication. Measure bandwidth for video quality adjustment.
TCP: 80, 443, 5222, 3478 (TURN fallback, Optional) UDP: 3478, 10000, 49152 - 65535 (TURN allocated, Optional)*.vsee.com
Call presence and reporting
Update VSee user's status, e.g. Offline, Online, In a call, Busy, etc.
TCP: 443vsee-activeapi.firebaseio.com
Cloud recording service (Optional, depends on contract)
Record video calls performed via VSee Messenger and/or in-browser calls. The calls will be recorded on the server side and will be available via a cloud link.
TCP: 443s3.amazonaws.com

Detailed Rules (US Customers)

Please note the servers listed below are for calls within the United States only.

If *.vsee.com cannot be whitelisted, the following subdomains and ports are required.

Messenger Service

PurposeProtocol: PortServersIP Addresses
VSee Directory
Authentication and address book services for VSee Messenger and in-browser call and chat.
TCP: 5222, 443talk.vsee.com xmpp01.vsee.com xmpp02.vsee.com xmpp03.vsee.com xmpp04.vsee.com52.52.36.123 52.52.111.88 52.52.245.139 54.215.77.199
US TURN Servers
Servers that relay packets during video calls in case no direct peer-to-peer connection can be established.
Protocol: PortNeedPurpose
UDP: 3478RequiredRelayed call media
TCP: 443RequiredFallback when UDP is blocked (TLS)
TCP: 3478OptionalSecond fallback when UDP is blocked
UDP: 49152-65535OptionalRelay ports
cl-coturn.vsee.com cl-coturn-use01.vsee.com cl-coturn-use02.vsee.com cl-coturn-use03.vsee.com cl-coturn-use04.vsee.com cl-coturn-use05.vsee.com cl-coturn-usw01.vsee.com cl-coturn-usw02.vsee.com cl-coturn-usw03.vsee.com cl-coturn-usw04.vsee.com cl-coturn-ohio01.vsee.com cl-coturn-oregon01.vsee.com cl-coturn-oregon02.vsee.com34.195.60.220 3.91.120.247 18.204.252.34 34.198.123.188 3.94.156.192 52.52.31.136 13.52.175.91 52.9.63.102 54.177.39.6 3.15.110.201 34.210.252.42 44.231.34.161
Region Identification Service
Used to detect the VSee user's region and to choose the optimal video bridge server for better call performance.
TCP: 443region.vsee.com54.255.19.27 3.211.169.195 54.177.209.83
Video Bridge
During a VSee video call, networking packets may pass through a video bridge server for best performance.
Protocol: PortNeedPurpose
UDP: 10000RequiredCall media and bridge messages
jvb01-ncal.vsee.com jvb02-ncal.vsee.com jvb03-ncal.vsee.com jvb04-ncal.vsee.com jvb05-ncal.vsee.com jvb06-ncal.vsee.com jvb07-ncal.vsee.com jvb08-ncal.vsee.com jvb09-ncal.vsee.com jvb10-ncal.vsee.com jvb01-nvir.vsee.com jvb02-nvir.vsee.com jvb03-nvir.vsee.com jvb04-nvir.vsee.com jvb05-nvir.vsee.com jvb06-nvir.vsee.com jvb07-nvir.vsee.com jvb08-nvir.vsee.com jvb09-nvir.vsee.com jvb10-nvir.vsee.com54.151.67.234 54.177.202.54 54.215.26.79 54.219.55.241 184.169.198.132 54.177.84.55 54.67.10.243 54.176.204.219 184.72.28.249 50.18.195.100 35.174.23.28 34.237.10.5 34.232.244.246 18.214.46.241 18.214.51.10 54.242.133.141 54.147.165.97 34.236.235.124 54.204.161.153 174.129.121.60
Messenger update service
Automated check for new versions of VSee Messenger.
TCP: 443cloudfront.vsee.com
Profile management
Managing VSee user profile, changing password, etc.
TCP: 443vsee.com my.vsee.com13.248.147.98 76.223.29.204
Messenger diagnostics
Diagnostic information gathered by VSee Messenger.
TCP: 443ironmq.vsee.com rtc-stats-v3.vsee.com13.248.147.98 76.223.29.204

The relay ports are optional. They are used only on direct calls that go through the other participant's TURN relay. Calls work with UDP 3478 to the TURN servers and UDP 10000 to the video bridges alone.

Clinic Service

PurposeProtocol: PortServersIP Addresses
Clinic web and API cluster
Basic Clinic functionality.
TCP: 443*.vsee.me99.83.175.218 75.2.83.122 15.197.200.74 3.33.250.220 15.197.231.104 3.33.211.220
Call presence and reporting
Update VSee users' presence status.
TCP: 443vsee-activeapi.firebaseio.com presence.vsee.com conferences.vsee.com13.248.147.98 76.223.29.204

Optional Firewall Rules

PurposeProtocol: PortServersIP Addresses
MFA / SSO (Depends on contract)
Enables login with MFA or using an SSO identity provider.
TCP: 443auth.vsee.comSee Auth0 IP Allow List
Cloud recording (Depends on contract)
Record video calls performed via VSee Messenger and/or in-browser calls. The calls will be recorded on the server side and will be available via a cloud link.
TCP: 443s3.amazonaws.com
Connectivity Testing Service
A set of test tools to define if the VSee user's network conditions are good enough for video calls, checking the reachability of critical VSee infrastructure.
TCP: 443test.vsee.com13.248.147.98 76.223.29.204

Detailed Rules (International Customers)

For international customers, please apply all rules in the US Customers section as well as the following:

PurposeProtocol: PortDetail ServersIP Addresses
International TURN Servers
Protocol: PortNeedPurpose
UDP: 3478RequiredRelayed call media
TCP: 443RequiredFallback when UDP is blocked (TLS)
TCP: 3478OptionalSecond fallback when UDP is blocked
UDP: 49152-65535OptionalRelay ports
cl-coturn.vsee.com cl-coturn-me01.vsee.com cl-coturn-sg01.vsee.com cl-coturn-sg02.vsee.com cl-coturn-euw01.vsee.com cl-coturn-euc01.vsee.com cl-coturn-euc02.vsee.com15.185.164.222 18.138.7.255 18.138.205.235 108.128.27.231 3.65.98.56 18.153.238.27
Video Bridge
During a VSee video call, networking packets may pass through a video bridge server for best performance.
Protocol: PortNeedPurpose
UDP: 10000RequiredCall media and bridge messages
jvb01-sg.vsee.com jvb01-eu.vsee.com jvb02-eu.vsee.com54.151.243.67 18.156.139.225 54.93.197.61

Legacy clients

Current VSee Messenger and Clinic Meet versions do not need the ports below. Open them only for users who still run older VSee software.

PurposeProtocol: PortServersWho needs it
Video Bridge (US and International)
Bridge messages (active speaker, video quality requests), not media.
TCP: 443The Video Bridge servers listed aboveVSee Messenger 4.25.x or older, and browser calls on Clinic Meet 9111.x or older. These versions carry bridge messages over this port. Current VSee Messenger and Clinic Meet versions send them over UDP 10000 instead.
VSee desktopUDP: 1853, 6000, 6001, 6256*.vsee.comUsed only by retired VSee desktop versions. Current VSee Messenger and Clinic Meet do not use this. Keep it open only if you still run an older VSee app.

Proxy Servers

Many organizations utilize proxy servers with their networks. However, as VSee network traffic is already encrypted, passing this traffic through a proxy server does not make it any more secure. On the other hand, proxy servers can introduce performance problems. Proxy servers can introduce latency and packet loss, which can degrade audio and video quality where real-time streams are essential. Thus, bypassing proxies for VSee traffic is recommended as routing through all traffic through a proxy server might impact connectivity and A/V performance.

If proxy servers cannot be bypassed, VSee services can connect to the above hosts via a proxy server. We recommend the following for better performance with a proxy server:

  • Proxy servers should allow persistent TCP connections.
  • Proxy servers should be configured to allow UDP traffic to the VSee TURN Servers at port 3478 and the Video Bridges at port 10000 to proceed directly.

Testing VSee Connectivity

VSee provides a suite of tools to help test that firewall rules are configured appropriately. Please note that only a subset of the requirements listed above are tested by these tools. It is important to ensure that the firewall rules listed above are followed, even if these tests pass. Failing to follow the firewall configuration requirements may cause issues such as intermittent bad call quality or dropped calls.

Outbound Connections

VSee services may occasionally need to connect with your systems for webhooks and callbacks, or to securely transfer patient / encounter data through SFTP, etc. Here are the lists of IP addresses that should be whitelisted.

Messenger Service

13.52.171.113 52.9.150.124 184.72.21.195 184.72.47.83 54.241.101.173

Clinic Service

13.52.7.6 13.56.46.159 52.52.174.230 54.177.111.163 13.52.58.237 18.144.134.162 54.241.243.156 54.176.136.131 13.56.219.50 13.56.202.120 13.56.70.155 50.18.137.251 13.52.25.116

Updates

Update on October 15, 2026New
  • Video Bridge TCP: 443 is now needed only by VSee Messenger 4.25.x or older and Clinic Meet 9111.x or older (see Legacy clients). Current versions use UDP: 10000 for call media and bridge messages.
  • TURN and Video Bridge ports are now marked Required or Optional.
  • UDP: 1853, 6000, 6001, 6256 moved to Legacy clients. Current VSee Messenger and Clinic Meet do not use them. TCP: 3478 stays on the TURN servers as an optional fallback when UDP is blocked.
Update on September 29, 2026
  • Retired 7 US TURN servers that no longer relay calls: cl-coturn-use06.vsee.com, cl-coturn-use07.vsee.com, cl-coturn-use08.vsee.com, cl-coturn-usw05.vsee.com, cl-coturn-usw06.vsee.com, cl-coturn-usw07.vsee.com and cl-coturn-ohio02.vsee.com (44.198.130.26, 3.216.83.102, 18.213.46.117, 54.151.95.19, 54.215.118.248, 52.9.100.25, 3.14.225.49). Removing them from your allow list does not affect VSee calls.
  • These names will stop resolving on November 2, 2026. Please remove the names and IP addresses from your firewall rules.
Update on February 10, 2026
  • Add in EU coturn and video bridge information
Update on February 26, 2025
  • Remove *.pubnub.com from allow list