nanog mailing list archives
Re: Soooo..... Netflix
From: Tom Beecher <beecher () beecher cc>
Date: Mon, 18 Nov 2024 00:22:49 -0500
What were your educated observations, preferably with supporting data?
If it was capacity issues, they learned a hard lesson that you should have other CDNs available to shed traffic over to if yours hits a problem that can't be quickly solved in real time. If it was server/software/livestream technical , then /shrug. Fix those. :) On Sun, Nov 17, 2024 at 1:28 PM Mike Hammett <nanog () ics-il net> wrote:
Armchair quarterbacking... Discussions I've seen from operators on Facebook shows some that had PNIs that worked just fine, while others with PNIs and cache boxes didn't fare so well. Some with just cache boxes were fine, while others were not. What were your educated observations, preferably with supporting data? Did we have a problem with congestion where the cache boxes phones home to, and this they just fell over? AWS used to be the data source of last resort. Did anyone notice congestion going from AWS to cache boxes? -----Mike HammettIntelligent Computing SolutionsMidwest Internet ExchangeThe Brothers WISP
Current thread:
- Soooo..... Netflix Mike Hammett (Nov 17)
- Re: Soooo..... Netflix Maurice Brown (Nov 17)
- Re: Soooo..... Netflix Innocent Obi (Nov 17)
- Re: Soooo..... Netflix Livingood, Jason via NANOG (Nov 18)
- Re: [EXTERNAL] Soooo..... Netflix Tebault, Peter H (Nov 17)
- Re: Soooo..... Netflix Tom Beecher (Nov 17)
- RE: Soooo..... Netflix Cooke, David via NANOG (Nov 18)
- Re: Soooo..... Netflix Livingood, Jason via NANOG (Nov 18)
- Re: Soooo..... Netflix Ca By (Nov 18)
- Re: Soooo..... Netflix joel (Nov 18)
- Re: Soooo..... Netflix Innocent Obi (Nov 18)
- Re: Soooo..... Netflix Livingood, Jason via NANOG (Nov 18)
- Re: Soooo..... Netflix Aaron1 (Nov 18)
- RE: Soooo..... Netflix Cooke, David via NANOG (Nov 18)
- Re: Soooo..... Netflix Maurice Brown (Nov 17)
