Precision Blacklisting Logic

To optimize traffic when performance issues occur, Precision reallocates traffic from a primary resource to the assigned backup resources. When performance on the primary resource improves, Precision reallocates traffic back to the previously blacklisted Content Delivery Network (CDN) resources. The traffic balancing goal is to maintain the assigned primary resource percentage targets by the end of the day. This logic ensures optimal traffic balance remains a priority, while also assigning backup resources during traffic distributions. Traffic allocation adjustments update dynamically to balance performance utilization while maintaining the configure the primary resource targets, maximizing efficiency and meeting the established traffic goals.

Precision logic is as follows:

• Precision recommends the Primary and Backup resources based on the assigned Share percentages.

• After the player receives the Primary andBackup resource assignments, it is up to the player to implement a mid-stream switch from Primary to Backup1 to Backup 2 (in the order it receives) when it encounters issues, such as too much buffering, buffered falling below a threshold, connection failure, etc.

• Precision does not use data from the back up CDN to make any resoucing decisions.

Backup Distribution Use Cases

• If Akamai is blacklisted with two backup resources, the assigned Akamai traffic is distributed across the resources, Limelight and CloudFront. Approximately 80% of the traffic distributed to Limelight and 9% of the traffic is distributed to CloudFront.

• If Akamai is blacklisted with one backup resource, the assigned Akamai traffic is distributed across the resources, Limelight and CloudFront. Approximately 80% of the traffic distributed to Limelight and 9% of the traffic is distributed to CloudFront.

• If Akamai is blacklisted with without a backup resource, the assigned Akamai traffic is distributed across any other primary resource, Limelight.