# CDN Analytics for Video Streaming | Vodlix **Source:** https://vodlix.com/features/cdn-analytics **Summary:** CDN analytics for video in your admin: bandwidth and requests served, cache hit rate, origin traffic and response time, data-centre traffic and failed requests. **Publisher:** Vodlix --- ## CDN Analytics for Video Delivery See the bandwidth and requests your CDN serves, how fast your origin answers, which data centres carry your traffic and how many requests fail. - **Feature Plan:** 2 - core-platform - back-end ## CDN Analytics for Video, Built Into Your Admin Track the bandwidth and requests your CDN serves, your cache hit rate, origin traffic and response time, data-centre distribution and failed requests, in one admin screen. ### What CDN Analytics Shows About Your Video Delivery CDN analytics for video tells you how well your content delivery network is getting your streams to viewers. In Vodlix it is a screen in your admin, under Stats & Report, so there is no separate CDN console to log in to. It shows the bandwidth and requests your CDN served, how much of that came from cache, how much traffic went back to your origin storage and how quickly the origin answered, which data centres carried the load, and how many requests failed. Operations teams use it to spot delivery problems early, finance teams to see what drives bandwidth, and engineering leads to check that the cache is doing its job. #### Bandwidth and requests Served, cached and uncached. #### Origin health Origin traffic and response time. #### Regions and errors Data centres and failed requests. ### What Your CDN Numbers Mean for Viewers Every number on the CDN analytics screen is about one thing: whether a viewer who presses play gets a fast start and smooth playback. A high cache hit rate means video segments come from a data centre near the viewer instead of travelling back to your storage. A low origin response time means the first seconds of a new title load quickly. Few failed requests mean fewer stalls and error screens. Every quality the player offers, from 360p up to 4K, travels through the same network, so these figures cover all of it. When they are healthy, viewers simply see the video start and keep playing. - mx-auto ### Track the Video Bandwidth Your CDN Serves The Bandwidth Served chart shows how much video data your CDN delivered, day by day or hour by hour, over the last 7, 15 or 30 days, this week, this month or last month. Above the chart you see the total, the cached share, the uncached share and the daily average, so a premiere weekend or a viral title stands out at once. Finance teams can match the curve to the bandwidth allowance on their plan, and operations teams can see when demand peaks. Compare it with your plan's allowance on [Space & Bandwidth Details](/features/space-bandwidth-details). - mx-auto ### See Requests Served and Your CDN Cache Hit Rate Requests Served counts how many times pieces of your video were fetched from the CDN, split into cached and uncached requests. One play is many requests, because a stream is delivered in short segments, so this is a delivery figure rather than a view count. Your cache hit rate is a headline figure at the top of the screen: the share of traffic answered from copies already near viewers. A high rate means faster starts and lower delivery cost, and a short dip after you publish new titles is normal while the cache warms up. - mx-auto ### Monitor Origin Traffic and Origin Response Time Origin traffic is the video your CDN had to fetch from your main storage because no nearby copy existed yet, and origin response time is how quickly that storage answered, in milliseconds. The two charts sit side by side, each with its average for the period. Rising origin traffic usually means a lot of new or rarely watched content is being played, and a slower response time means the first seconds of those plays take longer to load. Watching the two together tells engineering leads whether a slow start is a cache problem or a storage problem. - mx-auto ### See Which CDN Data Centres Serve Your Viewers The data-centre traffic distribution shows how much of your video was delivered from each CDN location, such as Frankfurt, New York or Singapore, with its share of the total. It is a quick picture of where your audience really watches, without opening your viewer reports. A growing share in a new region shows a market taking off, and it helps you plan launches, pricing and support hours around the places your viewers actually are. For what your platform delivers from, see [Global CDN](/features/global-cdn). - mx-auto ### Catch Failed Video Requests Before Viewers Complain The Non 2xx Requests Served chart counts every request your CDN did not answer with a normal success response, split by type: 3xx redirects, 4xx requests for files that are missing or not allowed, and 5xx server errors. The Errors figure at the top of the screen adds up the 4xx and 5xx requests, the ones that really failed. A few are normal on any busy service. A growing 4xx or 5xx count usually means missing files or an origin that is struggling, and viewers feel it as videos that will not start. Check it for the same dates as bandwidth and origin response time to see whether errors rose with traffic or on their own. - mx-auto ### CDN Analytics Alongside Your Other Streaming Reports CDN analytics tells you how well the network served your viewers; your viewing reports tell you what those viewers watched. Use [Reports & Analytics](/features/reports-and-analytics) for views, watch time and top titles, and keep CDN analytics for delivery volume, speed and errors. [Space & Bandwidth Details](/features/space-bandwidth-details) shows the bandwidth and storage allowance on your plan, and [Global CDN](/features/global-cdn) explains the delivery network behind every number on this screen. **Q: What is CDN analytics for video?** CDN analytics for video reports how your content delivery network delivers your streams: how much bandwidth and how many requests it served, how much came from cache, how your origin storage performed, where the traffic was served from and how many requests failed. In Vodlix it is a screen in your admin under Stats & Report. **Q: Is CDN analytics the same as viewer analytics?** No. CDN analytics shows how well the network delivered your video, while viewer analytics shows what people watched. Requests are not views, because one play is delivered as many small segments. Use Reports & Analytics for views and watch time. **Q: What is a good cache hit rate for video streaming?** The higher the better, because cached requests are answered from a data centre near the viewer. A falling rate means more traffic is going back to your origin, which makes playback slower and delivery more expensive. A short dip after publishing new titles is normal and recovers as the cache warms up. **Q: Can I see CDN bandwidth by day or by hour?** Yes. Choose daily or hourly figures and a date range such as the last 7, 15 or 30 days, this week, this month or last month, then apply the filter. Every chart on the screen updates for the same period, and you can switch between your streaming, storage and thumbnail, and static file traffic. **Q: Why did my CDN bandwidth go up when my viewer numbers did not?** Usually because viewers are watching at a higher quality, or because more content is coming from your origin rather than the cache. Compare bandwidth with the cache hit rate and origin traffic for the same dates to see which one it is. **Q: Who on my team can open CDN analytics?** Any admin whose role includes the Stats report access permission. The same permission also opens the dashboard, Insights and Reporting, so you can give operations and finance staff the reports without giving them content or billing settings.