Ingest Rate Limiting

Configure your encoder to adhere to ingest rate limit guidelines.

When you publish MSL 4 streams to the shared infrastructure, your encoder needs to adhere to these rate limit guidelines:

Attribute Limit
Maximum number of hits per second for a stream rendition 10 hits/second
Maximum number of hits per second for a streamID 100 hits/second
Maximum bitrate per rendition 45 Mbps
Aggregate maximum bitrate per streamID publishing either primary OR backup stream 75 Mbps
Aggregate maximum bitrate per streamID publishing both primary AND backup streams 150 Mbps
Minimum duration of a media segment 2 seconds
Maximum duration of a media segment 10 seconds
Maximum segment size 100 MB

If you exceed these limitations, a 429 response code will be sent to the encoder.

  • ERROR_EXCEED_RL_MAX_SEGMENT_SIZE_LIMIT
  • ERROR_EXCEED_RL_RENDITION_HITS_LIMIT
  • ERROR_EXCEED_RL_RENDITION_BITS_LIMIT
  • ERROR_EXCEED_RL_STREAM_HITS_LIMIT
  • ERROR_EXCEED_RL_STREAM_BITS_LIMIT
This can cause disruption to the stream delivery for your viewers, so you should configure your encoder to adhere to these guidelines.
Warning: To prevent overloading the shared infrastructure, there are limits to the number of events allowed per streamID. The .m3u8 file and the video segment are counted individually as events, therefore every request for a video would be the equivalent of two events. When you have a master variant playlist, that also adds to the event count. If your stream exceeds the event threshold limit, a 429 response code will be sent to the encoder. To avoid a 429 error, create a new streamID for each channel that serves your streaming media content.
These limits also apply to Ingest Accelerated streams. You’ll see a warning in the IAS client UI when the limits are exceeded.
In this case, 429 responses are not sent back to the encoder to avoid disrupting the entire stream. Check the email that is set up to receive alert notifications to understand the ingest limits violated.