This article lists the subnets for the following environments:
In addition, ports are listed in this section:
With vidyo.io, the connection will be initiated from the client/endpoint side. This means that in most network environments, Vidyo.io applications will work without requiring the network team to modify the configuration. Keep in mind, however, that in some environments which are more restrictive outbound, the network team may need to make changes that allow vidyo.io to work.
The tables below shows a setup for stateful connections to Vidyo.io.
Production Subnets (Current)
The following table lists the current vidyo.io production subnets.
Added (March 2020)
The following table lists the subnets that were added in March, 2020.
They ARE INCLUDED in the Production Subnets (Current) table at the beginning of this article.
Vidyo.io Staging Subnets (Current)
The following table lists the current vidyo.io staging subnets.
Vidyo.io EU (eu.prod.vidyo.io)
EU Production Subnets (Current)
The following table lists the current vidyo.io EU production subnets.
Added (March 2020)
The following table lists the subnet that was added in March, 2020.
They ARE INCLUDED in the EU Production Subnets (Current) table above.
For All VidyoCloud Environments:
We host clients on AWS CDN which does not guarantee static IPs. AWS subnets can be found here: https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html.
The following table lists the ports, IPs, and ranges.
|60,000-61,000||UDP||Media (WebRTC only)|
- Media ports are negotiated between the endpoint and the vidyo.io servers.
- Some firewalls may misclassify the media traffic and apply a UDP default timeout. In these cases, calls will always drop at exactly the same time. To avoid call timeouts, change the default (0:02:00 – 2 minutes) to a time that is longer than the longest potential call.