Use these configuration details if you are on a corporate, institutional, or restricted network and need to manually whitelist Riverside domains or IPs for recording and media streaming to work correctly.
Riverside Functionality
Using Riverside requires allowing the following traffic:
- Outbound TCP traffic to the specified IP addresses and FQDNs below using destination port 443
- Inbound TCP established traffic in response to the outbound connections above (this will use an ephemeral port on the client side)
- Outbound UDP traffic to the specified IP addresses and FQDNs, using destination port range 6000-8000
- Inbound UDP traffic from the specified IP addresses to any random port on the client side
FQDNs
t0-prod-aps1.lc.riverside.com
t0-prod-aps2.lc.riverside.com
t0-prod-euc1.lc.riverside.com
t0-prod-sae1.lc.riverside.com
t0-prod-use1.lc.riverside.com
t0-prod-usw2.lc.riverside.com
t1-prod-aps1.lc.riverside.com
t1-prod-aps2.lc.riverside.com
t1-prod-euc1.lc.riverside.com
t1-prod-sae1.lc.riverside.com
t1-prod-use1.lc.riverside.com
t1-prod-usw2.lc.riverside.com signals.riverside.com
signals-prod.tools.riverside.com
signals.riverside.fm
signals-prod.tools.riverside.fm
riverside-pro-recordings.s3-accelerate.amazonaws.com
riverside-prod-webrtc-recordings.s3-accelerate.amazonaws.com
*.launchdarkly.com
server-time-sync.keyson.workers.dev
fonts.googleapis.comStatic IPs
34.199.210.92
44.195.64.242
52.1.194.23
52.20.253.239
52.206.212.176
52.45.23.39
52.70.16.34
54.144.167.69
54.196.195.134
100.20.242.208
34.218.98.155
35.161.88.126
44.224.124.241
44.228.153.161
52.27.113.199
52.41.0.116
52.43.253.153
54.185.101.42
18.153.110.13
18.153.88.126
18.194.134.119
18.199.39.98
3.120.119.136
3.73.175.201
3.73.61.254
35.158.232.50
52.59.52.143
13.200.170.159
3.109.149.183
65.0.249.206
18.228.207.168
18.229.151.140
54.232.21.237
52.62.193.220
54.253.162.207
54.66.63.69
52.3.166.122
44.218.237.89
34.230.157.195
44.218.117.149
54.172.191.159
99.83.211.173
15.197.190.62Static IPs details
These IPs support Riverside's regional media relay servers, which carry the direct media path for your recording. They're grouped across the same 6 regions as the FQDNs above: US East (Virginia), US West (Oregon), EU Central (Frankfurt), AP South (Mumbai), SA East (São Paulo), and AP Southeast (Sydney).
Within each region, some of these IPs are the fixed entry points that the t0-prod- and t1-prod- FQDNs resolve to. These handle your TLS connection on port 443, along with relay traffic used as a fallback when a direct media path isn't available. That fallback traffic still falls within the UDP 6000-8000 range described above, so it doesn't require any separate firewall rule.
The remaining IPs in each region are assigned to individual media relay servers as they come online, and carry your session's direct media traffic over that same UDP/TCP 6000-8000 range. Because this assignment can change, allow the entire list rather than a subset of it.
Additional notes on network behavior
You may notice connection attempts to IP addresses outside of those listed above. This is expected behavior.
Riverside will first attempt to establish the best possible connection path. If those attempts are not successful, it will fall back to using the IP addresses and FQDNs included in the lists above.
For this fallback to work correctly, your firewall must be configured exactly according to this guide.