Estimation: Sizing Peak Network Capacity for YouTube TV's Live Streaming Launch

YouTube TV is about to launch its live TV streaming service. Estimate the network bandwidth it needs. ```hint Pick the moment that matters Think about which moment of the day the network has to survive, and what decides how much data a single viewer pulls at that moment. ``` ### Clarifying Questions - Does "bandwidth" mean the peak throughput the delivery network must serve at the busiest minute, or the total data transferred in a month? - Is the launch nationwide in the US or in a handful of metro areas first, and how many subscribers should I plan for in the first year? - Should I size only delivery to viewers, or also bringing in and encoding the channel feeds? - What picture quality is offered at launch: HD only, or 4K as well? ### What a Strong Answer Covers - A clear definition of the quantity being estimated, and why peak throughput drives capacity - An equation from subscribers to concurrent streams at peak to average bitrate, with every input labeled as an assumption - A device and resolution mix behind the per-stream bitrate, with bits and bytes kept straight - Headroom for live-event spikes and a sanity check of the result from a second angle - What the number means for the launch: edge versus origin capacity, cost levers and a plan for degrading gracefully ### Follow-up Questions - A championship game pushes concurrency far above your prime-time estimate. What do you do before kickoff, and what happens if demand still exceeds capacity? - How does the estimate change if 4K is offered to a share of living-room viewers? - Which assumption is your number most sensitive to, and how would you validate it in the first weeks after launch?