Backup Publishing Real-time Streaming allows you to set up redundant ingest publishing, as a backup in the event that one of your streams fails and you need to fail-over to another. This feature allows you to have two parallel ingests from the encoder, or from different encoders with same source. If one of them fails, viewers will be switched to the other active published stream.

For true redundancy you would have two encoders receiving the same signal connected to separate networks. However, different levels of redundancy will depend on your event type.

Setting up Backup Publishing

  1. Creating a Publishing Token and create a stream.
  2. Configure your encoders to both publish to the same streams. This works for WebRTC, RTMP, or SRT publishing.
  3. Start streaming with your backup encoder.
  4. Start streaming with your primary encoder.


For backup publishing, streams must be published to the same region/cluster. The feature does not support publishing with the same streamName in different regions.

Viewers will connect to the most recently started stream within the same region, which is why you must start the backup encoder first. In the event that the primary encoder going offline, viewers will automatically be switched over to the backup encoder.

Each ingest feed is billed independently, and viewer data only bills the actual data sent to the viewer, regardless of the number of redundant streams.