In this article:
- What is Vimeo Enterprise eCDN
- What devices & browsers are compatible?
- What happens on incompatible devices/browsers?
- What ports and domains should be whitelisted?
- How do you handle VPN?
- What is Subnet Matching?
- How do I know if it’s working?
- How can I troubleshoot?
What is Vimeo Enterprise eCDN?
Vimeo Enterprise eCDN is a peer-to-peer delivery system that will allow you to stream your event across your network of users with minimal local bandwidth consumption. It’s easy to implement, since it’s browser-based and doesn’t require any plugins, workstation software, or hardware to install. The appeal of the eCDN is the ability to deliver a high-quality live stream within a network, without overusing or bottlenecking bandwidth. Streaming via eCDN is a great solution to ensure high-quality video delivery without impacting the corporate network or risking network health. It works with single sign-on (SSO), and is ideal for a corporate setting, such as an internal broadcast or training. This also means lower bandwidth usage—which leads to cost savings.
Enterprise eCDN is only available for Vimeo Enterprise-level members—if you are not currently affiliated with an Enterprise account, but would like to know more, feel free to reach out here for more information.
Below you’ll find some commonly asked questions about Vimeo Enterprise eCDN.
What devices & browsers are compatible?
- Operating systems: Windows, MacOS, Linux
- Mobile devices: Android (with Chrome)
- Browsers: Chrome, Firefox, Edge 20.1024+, Safari 11+
- For MS Edge and Chrome, additional Whitelisting of URLs can be required.
- Enterprise eCDN is not compatible with Internet Explorer 11.
What happens on incompatible devices/browsers?
Vimeo eCDN is a fully hybrid solution: on workstations that do not support Vimeo eCDN technology, delivery automatically falls back to full server-based delivery (no peer-to-peer is done) without any interruptions to playback or the video experience.
What ports and domains should be whitelisted?
The network your viewers are connected to should have the following ports open:
- All ports between UDP 50000 and 64000 (allows for peer-to-peer connection)
- UDP 19302 (WebRTC stun servers connect via this port)
In addition, their network should whitelist the following domains:
How do you handle VPN?
In most situations, it’s desirable to not have VPN users peering content through the VPN concentrator. In this case the recommendation is to enable subnet matching, and create a site that covers the VPN subnets. Within this site peering can be disabled. Other options may include allowing split-tunneling for video traffic, or handling it operationally by requiring users to disconnect from VPN to consume the video.
What is Subnet Matching?
Subnet matching is a feature of the Vimeo eCDN that gives network operations teams more control over the behavior of how the peer mesh forms. It helps network operators better handle the traffic inside their network.
By defining public and private pairings of IPs and subnets, users are able to define sites within their network, and thus limit peer exchanges to within the desired subnet ranges. This helps optimize the mesh formation, and limits network traffic flowing over WAN links between customer sites.
If you are interested in subnet matching, reach out to your Account Manager.
How do I know if it’s working?
The technology is entirely based on standard web browser technology, and as such, it’s probably already working in your environment. The easiest way to tell what is and isn’t working is to use our test page: https://player.vimeo.com/ecdn-test.
This diagnostic page shows you real-time statistics on the peering as well as a checklist which demonstrates if all services are reachable by the browser and functioning correctly. Please note that if you want to test the peer-to-peer sharing, you have to simulate additional users. You can do this either by testing with other members of your team, or by opening the test page in additional browser tabs.
How can I troubleshoot?
The same diagnostic page can be used to test your specific account and event by modifying the URL. Simply add the stream ID of your live event to the end of the diagnostic URL, and you’ll be able to view all the same peering statistics and capability checklist with your event as the source. For example, if your live event URL is:
You’ll be able to monitor the event through the eCDN diagnostic page if you make the URL:
The origin of the requesting URL needs to be whitelisted. Read more about that here in Google's documentation.