The IPL final. 50+ MILLION people streaming the same match at the same second - a real world record set on Hotstar. 🏏

#architecture #infrastructure #performance #systemdesign

Hotstar once streamed the Cricket World Cup final to ~59 MILLION people at the same second.

That's not a typo. ~59,000,000 concurrent viewers - a world record.

How does a system survive that? A few things Hotstar actually does:

→ Plan for the "tsunami," not the average. The scary moment isn't steady load — it's a wicket falling, when millions refresh and rejoin in the same few seconds. They design for that spike, not the baseline.

→ Pre-provision capacity. Reactive autoscaling is too slow — servers take minutes to boot, spikes happen in seconds. So Hotstar predicts concurrency and scales up BEFORE the match, keeping warm capacity ready.

→ Segment + multi-CDN fan-out. The live feed is chopped into tiny 2–6s chunks pushed to CDN edges across multiple providers. Millions pull from the nearest edge, not the origin. One encode, served to millions.

→ Graceful degradation ("panic mode"). Under extreme load, Hotstar sheds non-essential features and lowers quality to keep the core stream alive. A slightly lower-res match beats a crashed one.

→ Trade latency for stability. Live runs ~10–30s behind real-time on purpose — that buffer absorbs the spikes.

The big lesson: at this scale you don't fight the load head-on. You predict it, pre-provision for it, push everything to the edge, and degrade gracefully instead of failing.

You can build a live streaming design — origin, transcoding, CDN edge — and push traffic through it to watch where it strains 👇 (free, no signup)
prepgrind.xyz

What would you reach for first to handle 50M+ concurrent viewers?