Teradek User Guide

Network communication requirements for using On Demand Hyperion servers in Core

Updated on


When an On Demand Hyperion server is used, the server is handled differently by Teradek encoders, decoders, or apps compared to using a dedicated Hyperion server that is hosted by Core, or a self-hosted Hyperion server that is associated with a Core account.

Network port ranges and IP addresses used by the On Demand Hyperion can change between each use of the service. Teradek devices and apps are able to automatically obtain the current IP address and port for the On Demand Hyperion region.

In comparison, a dedicated Hyperion server allows a consistent IP address and range of ports to always be available.


Core Subscription Levels

On Demand Hyperion servers are accessible at any Core subscription level.

Since the IP address and ports used with an On Demand Hyperion server can change, there are some scenarios where it may not be possible to use an On Demand Hyperion server. For example:

  • If there are stringent security requirements on a network -- e.g. a static destination IP address or limited port range must be approved for outbound connections through a business firewall.
  • Another use case which would require a dedicated Hyperion server is the use of 3rd party streaming software like Telestream Wirecast or vMix. Third party products cannot determine the On Demand Hyperion server's address or ports, and are not supported for use with On Demand Hyperion servers.

If you have similar requirements on a network, you would not be able to use the On Demand Hyperion servers and would need to choose a subscription plan that allows a dedicated Hyperion server.


Network Port Requirements

The following port ranges must be allowed for connections to an On Demand Hyperion server:

Inbound Network Connections

No incoming connections are needed from either the Core management system or an On Demand Hyperion server to allow a Teradek encoder, decoder or app to communicate.


Outbound Network Connections


  • 1024-65535 (TCP). This port range is used for the following:
    • Streaming from a Teradek encoder or app to the On Demand Hyperion server using the TCP protocol.
    • Receiving / pulling down MPEG Transport Stream from the On Demand Hyperion server back to a Teradek decoder. This type of pulled MPEG-TS connection always uses the TCP protocol.
  • 1024-65535/UDP : This port range is used in the following scenarios:
    • By Teradek encoders capable of using the UDP protocol for streaming video into an On Demand Hyperion server.
      • Streaming with the UDP protocol is available on a Cube + Bond (original), Bond II, Bond Pro, or 600 / 700 / 800 series encoders, and the streaming protocol is changed from the default TCP to UDP.
      • This does not apply to a standalone Cube (1st or 2nd gen), Slice encoder (1st gen), T-RAX encoder, or apps.
    • By Teradek hardware decoders or Teradek apps (Core TV for iOS or macOS, or VUER for Android, iOS or macOS) capable of using the SRT protocol to receive video from an On Demand Hyperion Server. 

If these outbound port ranges are blocked then it may not be possible for the encoder or decoder to make a connection to the On Demand Hyperion server on that particular network interface (Ethernet, USB modem, or Wi-Fi).

Outbound port blocking may be encountered on shared network connections at public venues (hotels, airports, coffee shops) or at facilities with restrictive security settings such as school, government, or business networks.

Previous Articles Network communication requirements for using Self-hosted and Cloud Hyperion servers with Core
Next Articles Network communication requirements for using Teradek Encoders with Core