A Step-by-Step Guide to Enable Communication with InSpace's Cloud
Choppy, hard-to-access InSpace session? Check your firewall configuration.
Your network must communicate with InSpace's cloud in order to function. This guide lists the IP address ranges and protocols used to communicate with InSpace's cloud. Use this information to configure your firewall to enable communication with InSpace if necessary.
Main Connectivity Requirements
- sdkgw.us1.twilio.com (WSS, 443)
- sock.inspace.chat (WSS, 443)
- tsock.us1.twilio.com (WSS, 443)
- global.vss.twilio.com (WSS, 443)
- api.inspace.chat (https, 443)
- login.inspace.chat (https, 443)
- cdn.inspace.chat (https, 443)
- lambda.inspace.chat (https)
- rec.inspace.chat (https)
- sockapi.inspace.chat (https)
- chat.stream-io-api.com (https, wss)
- miro.com (http, wss)
- https://cookie.testnhaedbms.com/ (https)
- https://connect.facebook.snet (https)
- https://accounts.google.com (https)
Signaling Communication
Find your region in this list.
Region ID | Location | Host Name | Port and Protocol |
gll | Global Low Latency (default) | global.vss.twilio.com | 443 WSS |
au1 | Australia | au1.vss.twilio.com | 443 WSS |
br1 | Brazil | br1.vss.twilio.com | 443 WSS |
de1 | Germany | de1.vss.twilio.com | 443 WSS |
ie1 | Ireland | ie1.vss.twilio.com | 443 WSS |
in1 | India | in1.vss.twilio.com | 443 WSS |
jp1 | Japan | jp1.vss.twilio.com | 443 WSS |
sg1 | Singapore | sg1.vss.twilio.com | 443 WSS |
us1 | US East Coast (Virginia) | us1.vss.twilio.com | 443 WSS |
us2 | US West Coast (Oregon) | us2.vss.twilio.com | 443 WSS |
Media Servers
Ports used: 10,000 - 60,000 UDP/SRTP/SRTCP or TLS/443 or UDP/3478
gion ID | Location | Server IPv4 Address Range |
au1 | Australia |
13.210.2.128/27 (13.210.2.128 - 13.210.2.159) 54.252.254.64/26 (54.252.254.64 - 54.252.254.127) 3.25.42.128/25 (3.25.42.128 - 3.25.42.255) |
br1 | Brazil |
18.231.105.32/27 (18.231.105.32 - 18.231.105.63) 177.71.206.192/26 (177.71.206.192 - 177.71.206.255) 18.230.125.0/25 (18.230.125.0 - 18.230.125.127) |
de1 | Germany |
52.59.186.0/27 (52.59.186.0 - 52.59.186.31) 18.195.48.224/27 (18.195.48.224 - 18.195.48.255) 18.156.18.128/25 (18.156.18.128 - 18.156.18.255) |
ie1 | Ireland |
52.215.253.0/26 (52.215.253.0 - 52.215.253.63) 54.171.127.192/26 (54.171.127.192 - 54.171.127.255) 52.215.127.0/24 (52.215.127.0 - 52.215.127.255) 3.249.63.128/25 (3.249.63.128 - 3.249.63.255) |
in1 | India |
52.66.193.96/27 (52.66.193.96 - 52.66.193.127) 52.66.194.0/26 (52.66.194.0 - 52.66.194.63) 3.7.35.128/25 (3.7.35.128 - 3.7.35.255) |
jp1 | Japan |
13.115.244.0/27 (13.115.244.0 - 13.115.244.31) 54.65.63.192/26 (54.65.63.192 - 54.65.63.255) 18.180.220.128/25 (18.180.220.128 - 18.180.220.255) |
sg1 | Singapore |
13.229.255.0/27 (13.229.255.0 - 13.229.255.31) 54.169.127.128/26 (54.169.127.128 - 54.169.127.191) 18.141.157.128/25 (18.141.157.128 - 18.141.157.255) |
us1 | US East Coast (Virginia) |
34.203.254.0/24 (34.203.254.0 - 34.203.254.255) 54.172.60.0/23 (54.172.60.0 - 54.172.61.255) 34.203.250.0/23 (34.203.250.0 - 34.203.251.255) 3.235.111.128/25 (3.235.111.128 - 3.235.111.255) |
us2 | US West Coast (Oregon) |
34.216.110.128/27 (34.216.110.128 - 34.216.110.159) 54.244.51.0/24 (54.244.51.0 - 54.244.51.255) 44.234.69.0/25 (44.234.69.0 - 44.234.69.127) |
How to allowlist and configure dedicated InSpace servers.
Ensuring smooth connectivity by configuring IP addresses for InSpace Cloud Proxy
IP addresses for Cloud Proxy
InSpace deploys dedicated servers to run the cloud proxy service. InSpace owns the IP addresses and fully controls the traffic on these addresses. To use InSpace Cloud Proxy Force UDP or Force TCP modes, you must first configure your firewalls to trust the following IP address and port ranges.
When adding IP addresses:
- If you use a cloud proxy with network geofencing, you can add only the IP addresses dedicated to your specified region.
- If you do not enable network geofencing, you need to add all IP addresses to ensure connectivity.
Force UDP mode
The IP addresses for the different geographical regions are:IP addresses for Cloud Proxy | Agora Documentation
IP addresses for Cloud Proxy (WEB)
Agora deploys dedicated servers to run the cloud proxy service. Agora owns the IP addresses and fully controls the traffic on these addresses. To use Agora Cloud Proxy Force UDP or Force TCP modes, your end users must first configure their firewalls to trust the following IP address and port ranges.
When adding IP addresses:
- If you use cloud proxy with network geofencing, you can add only the IP addresses dedicated to your specified region.
- If you do not enable network geofencing, you need to add all IP addresses to ensure connectivity.
- 128.14.195.192/28
- 128.14.245.16/28
- 128.14.72.80/28
- 128.14.200.208/28
- 47.252.17.251
- 170.106.135.177
- UDP: 443
- TCP: 443
- 104.166.160.208/28
- 23.236.110.32/28
- 148.153.25.148
- 148.153.25.147
- 148.153.25.146
- 148.153.25.184
- 148.153.93.19
- 148.153.93.24
- 148.153.93.25
- 148.153.93.27
- 47.254.149.145
- 162.62.220.8
- UDP: 443
- TCP: 443
- 129.227.217.128/28
- 129.227.108.208/28
- 128.1.105.112/28
- 147.139.34.215
- 129.226.26.104
- 161.117.177.218
- 104.250.52.195
- UDP: 443
- TCP: 443
- 129.227.113.112/28
- 129.227.55.96/28
- 164.52.24.41
- 164.52.24.44
- 164.52.24.43
- 103.101.125.26
- 103.101.125.20
- 103.101.125.22
- 122.10.153.90
- 47.245.7.250
- 43.128.248.97
- UDP: 443
- TCP: 443
- 128.1.186.240/28
- 129.227.73.32/28
- 103.193.127.208/28
- 161.117.177.218
- 104.250.52.195
- UDP: 443
- TCP: 443
- 14.29.38.144/28
- 27.45.161.144/28
- 183.232.200.144/28
- 115.238.206.0/28
- 106.3.209.0/28
- 112.13.216.0/28
- 219.153.111.128/28
- 221.178.42.0/28
- 113.207.12.0/28
- 139.196.42.124
- 123.56.57.206
- UDP: 443