Broadcast grade uptime

Redundancy
The Jet-Stream platform is fully redundant. Locations, caches, databases, servers, backbone connections and even power lines are all outfitted at least twice. Historically we have reached 99.999% actual content uptime. By default we allow any of your live channels to be configured redundantly.

Content uptime versus platform uptime
Do you know the difference between platform uptime and content uptime? CDNs, video platforms and clouds claim high uptimes, but this does not guarantee that your content is available. How? They use DNS to (geo) load balance traffic over their locations.

Uptime claims
If regular CDNs need to re-load balance, they change the records in their DNS servers. DNS changes in desktops, browsers, smart TVs and media players can take hours, days (or even a restart) to be effective, due to DNS caching, even though the CDNs use a 1 minute ‘Time To Live”. These CDNs and clouds still claim platform uptime, but viewers experience poor and broken streams: the CDNs don’t even know and cannot do anything about it. Whoops. DNS was never intended to be used as a dynamic load balancing mechanism.

Active request routing
Jet-Stream went beyond DNS and invented active request routing: stream requests are individually analysed and instantly geo load balanced to the best delivery node, for each individual user, for each stream: the analysis, calculation and redirect are performed in less than a millisecond: much faster than a typical DNS request.

Broadcast grade streaming
We actively monitor all edge servers and 3rd party CDNs. If we encounter performance issues or disturbances in individual servers or PoPs, our platform automatically and instantly takes affected resources out of the active pool and re-load balances to alternative servers: guaranteed. This is what we call content uptime: broadcast grade availability.

< go back