Solutions · Quality & rebuffering

CMCD-driven routing.

Per-viewer, not per-region.

The signal

The player is the instrument.

Quality routing is only as good as the thing it measures. We measure the stream itself — the same session the viewer is watching, while it plays.

CMCD (CTA-5004)

The player annotates its own segment requests: buffer level, encoded bitrate, buffer starvation, object type. Telemetry of the actual stream, per session, in-band — from hls.js, Shaka, dash.js and players you built yourself. No page tag, no separate beacon, no sampling.

What that buys the decision

A number that belongs to one viewer, not to an average. The brain knows this session’s buffer is draining on this network right now — so it can move the source of the next segment for this viewer, and leave everyone else where they are.

The resolution

A score per viewer and network.

The brain scores every CDN per viewer and access network, continuously. Two viewers on the same street, on different networks, can need different CDNs — a regional average erases exactly the difference that matters. Per-viewer scoring is what turns “rebuffering you cannot explain” into a network you can name.

Per session

Each session gets its own answer, recomputed as its own signals change — not a weight shared with a million strangers.

Continuous

Scoring runs all stream long, so a CDN that decays slowly is caught slowly decaying — before the buffer empties, not after.

Per network

Problems live in one access network, in one city, on one CDN. The score keeps that resolution instead of averaging it away.

Read more about the vidNT brain — how it learns and why nothing leaves your servers →

The audit

Every decision shows its reasons.

Chosen CDN, the score, each component of the score, and why a switch was held back — readable in the console and over the API. A routing decision you cannot interrogate is a routing decision you cannot trust, and “the algorithm did it” is not an incident review.

The analytics behind the decisions →

Watch the decisions run against your stream.

Point a player at the system and read the reasons next to the routing.