TVHEADEND.IO
Order channels
JOURNAL NETWORK

Why we run six core sites instead of one headend

· NOC

A single headend is simple to run and terrible to deliver from. Every kilometre between the encoder and the receiver adds latency, and every hop adds a place for the signal to break. So the hub is six core sites, not one.

Each core site captures, transcodes, encrypts, packages and records. That means a channel leaving Singapore has been processed in Singapore — not in Luxembourg and then dragged across the planet. Delivery edges home to whichever core is closest, so a viewer in Auckland is served from Singapore and a viewer in Bogotá from Dallas.

Every channel runs from two cores. If a site drops, its edges re-home to the next closest one and the picture stays up. That is the whole reason for the shape of the network: not marketing geography, but the number of hops between the satellite dish and the screen.

ORDER CHANNELS ONLINE

SRT from EUR 115 per channel per month. Volume discounts apply automatically.

Open the catalogue Free 3-day trial
MORE FROM THE JOURNAL
Reading the looking glass: what RTT actually tells you The number on the page is an estimate from distance and our routing table. Here is what it predicts well, what it does not, and when to ask for a real probe. What is actually inside our EPG data Artwork, cast and crew, categories, series structure and synopses in twelve languages — and why a guide without images costs you engagement. Turning SRT into UDP multicast on site Most hotel and campus receivers still expect multicast MPEG-TS. Our player software and appliance bridge the gap without a headend on site.