nanoStream Analytics Release – October 2026

nanoStream Analytics API v2.36.3 · Dashboard v2.34.0

MOQ playback now has its own place in nanoStream Analytics. A new MOQ tab in the Analytics Dashboard and new MOQ routes in the Analytics API show how your viewers experience MOQ playback, on its own. Your H5Live numbers get cleaner too, because they no longer mix both playback paths.

New: A Dedicated MOQ Tab in the Analytics Dashboard

The new MOQ tab, right below H5Live, gives this audience its own view in the Analytics Dashboard. The nanoStream Player plays over MOQ wherever the viewer’s browser supports it, and falls back to H5Live where it doesn’t. With MOQ support in the nanoStream Player, more of your viewers are watching over Media over QUIC. The new MOQ tab, right below H5Live, gives this audience its own view in the Analytics Dashboard.

Check latency, startup time and buffering for MOQ playbacks on their own, and see which browsers and player versions your MOQ audience uses.
It shows the playback metrics of MOQ playbacks with the same widgets you know from the H5Live tab:

playback count and playtime per OS and per browser
average and median playing time
play buffering ratio
player loading count per country
used player versions
average and median player latency
median play startup time
status/error codes and stop reasons

Every widget supports Zoom and Get CSV.

New: MOQ Metrics in the Analytics API

The Analytics API has 14 new GET routes under /v2/moq/*: views and playing time by OS and browser, plus timeseries for playing time, latency, startup time, buffering ratio, error codes and stop reasons. Playing time, latency, startup time and buffering ratio are also available for a single stream.

If you pull Analytics data into your own monitoring or reporting, you can now track MOQ playback separately. The routes follow the same structure as the existing /v2/h5live/* routes, so extending an integration is mostly a matter of swapping the path.

H5Live Metrics No Longer Include MOQ Playbacks

The H5Live tab and the /v2/h5live/* API routes no longer count MOQ playbacks. Those playbacks now appear only on the MOQ tab and under /v2/moq/*.

From this release on, your H5Live numbers will be lower than before. Nothing is lost: the difference is your MOQ traffic, which now has its own view. Keep this in mind when you compare H5Live figures from before and after the release, or when reports are built on H5Live totals.

Changelog

1) Dashboard v2.34.0 – MOQ playback statistics

MOQ

added a new MOQ tab (/moq) below H5Live with these widgets, each with zoom and CSV export: playback count per OS and per browser, playtime per OS and per browser, average and median playing time in seconds, play buffering ratio in percent, player loading count per country, used player versions, average and median player latency in seconds, median play startup time in seconds, status/error codes, stop reasons.

H5Live

the H5Live tab no longer includes MOQ playbacks; they are shown on the MOQ tab.

2) API v2.36.3 – MOQ playback statistics

MOQ playback metrics

added GET routes under /v2/moq/*:
views/os,
views/browser,
playtime/os,
playtime/browser,
playtime/timeseries,
playtime/streams/timeseries,
latency/timeseries,
latency/streams/timeseries,
startuptime/timeseries,
startuptime/streams/timeseries,
bufferingratio/timeseries,
bufferingratio/streams/timeseries,
errorcodes/timeseries,
stopReasons/timeseries