Mid-stream
The switch happens inside the playing session, on a segment boundary, without a restart and without the viewer doing anything.
Built for the night of the match, not the average Tuesday.
A match does not ramp; it detonates at kickoff. Concurrency multiplies faster than any single CDN allocates capacity, and match night is the worst possible time to discover a vendor’s limit. Spreading the load per viewer across the CDNs you already contract means no single vendor’s ceiling becomes the broadcast’s ceiling.
When a CDN strains in the second half, each affected session’s next segment comes from a healthier CDN — behind the playing buffer, per viewer, mid-stream. The goal is not interrupted by the failure, and not by the rescue either. Viewers who joined before the trouble are exactly the ones a DNS answer cannot reach; they are the ones this mechanism exists for.
The switch happens inside the playing session, on a segment boundary, without a restart and without the viewer doing anything.
The sessions that are suffering switch. The stadium’s worth of sessions that are fine stay put. No mass migration, no secondary stampede.
The mechanism is standards in the stream — CMCD up, Content Steering down — spoken by the players you already ship.
SCTE-35 markers drive the insertions the whole rights model rides on. vidNT parses them and holds switching inside no-switch windows around each break, so a rescue never cuts across an ad avail. The switch waits for the break to end; the break never waits for the switch.
Run your own stream through the mechanism on a quiet Tuesday, and read the log.
Leave your details and we open your access. A person comes back to you within one business day.
Open your assistant with a ready prompt — ask it anything about multi-CDN stitching, how vidNT fits your stack, or how to start.
The prompt asks your assistant to read vidnt.com/llms.txt and answer from it.