Why we run six core sites instead of one headend
Luxembourg, Frankfurt, Helsinki, Dallas, Singapore and Johannesburg. What each site does, and why an edge always homes to the nearest one.
Read: Why we run six core sites instead of one headendHow the network is built, why we deliver the way we do, and what changes for operators when signal distribution is priced on a page instead of in a meeting.
Luxembourg, Frankfurt, Helsinki, Dallas, Singapore and Johannesburg. What each site does, and why an edge always homes to the nearest one.
Read: Why we run six core sites instead of one headendThe 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.
Read: Reading the looking glass: what RTT actually tells youArtwork, cast and crew, categories, series structure and synopses in twelve languages, and why a guide without images costs you engagement.
Read: What is actually inside our EPG dataMost hotel and campus receivers still expect multicast MPEG-TS. Our player software and appliance bridge the gap without a headend on site.
Read: Turning SRT into UDP multicast on siteProgramme-accurate boundaries, restart, start-over and what happens when a broadcaster overruns a live match by twenty minutes.
Read: How the seven-day catch-up window is builtEUR 115 per channel per month, published, with volume discounts applied automatically. What that changes for a small operator.
Read: Why we put the rate card on the websiteWant the technical detail on a specific piece? The NOC answers directly.
Ask an engineer