How to check live stream is being cached?

Caching your live-streams effectively.

This part applies only if you're delivering already encoded HLS / Dash output through the CDN. If you're using our streaming server to package your RTMP into HLS/Dash, all caching is already enabled.

First of all, we need to make sure your stream is being properly cached. Let's suppose you have an HLS stream. It consists of the manifest ".m3u8" and small chunks ".ts".

These small chunks carrying approximately 3 seconds worth of video are supposed to be cached, while the manifest should not.
Same applies to MPEG-dash, where you're caching ".m4v" chunks, but not the manifest ".mpd".

Your chunks should not have the following header values, as our servers will never be able to cache your content:
Cache-Control: no-cache or Cache-Control: max-age=0

To start caching, you should modify the Cache-control to "public" or increase the "max-age" value. The recommended value for live-streams is 300 seconds.

To confirm your stream is being properly cached you'll need a specific link of a single chunk. You can get it from the Network section in Google Chromes's developer console.
Once you get the link, you can follow this tutorial to check caching:

You can always contact our support via the live-chat or an email, where we'll assist you with the setup or to confirm everything is configured properly.