←back to thread

Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

(www.sportingnews.com)
492 points storf45 | 3 comments | 16 Nov 24 03:42 UTC | HN request time: 0s | source
Show context
softwaredoug ◴[16 Nov 24 17:53 UTC] No.42157774[source]▶
The way to deal with this is to constantly do live events, and actually build organizational muscle. Not these massive one off events in an area the tech team has no experience in.
replies(9): >>42158542 #>>42158774 #>>42158782 #>>42158854 #>>42158930 #>>42159942 #>>42160430 #>>42160978 #>>42168444 #
geor9e ◴[16 Nov 24 20:07 UTC] No.42158854[source]▶
They've been doing live events since 2023. But it's hard to be prepared for something that's never been done by anyone before — a superbowl scale event, entirely viewed over the internet. The superbowl gets to offload to cable and over the air. Interestingly, I didn't have any problems with my stream. So it sounds like the bandwidth problems might be localized, perhaps by data center or ISP.
replies(7): >>42159567 #>>42159816 #>>42160225 #>>42161436 #>>42161557 #>>42164734 #>>42165472 #
burntalmonds ◴[16 Nov 24 21:36 UTC] No.42159567[source]▶
Yeah, I think people are incorrectly assuming that everyone had the same experience with the stream. I watched the whole thing and only had a few instances of buffering and quality degradation. Not more than 30 seconds total during the stream.
replies(1): >>42159760 #
1. DharmaPolice ◴[16 Nov 24 22:04 UTC] No.42159760[source]▶
Even if it was only 30% of people had a problem that's still millions of unhappy users. Not great for a time sensitive event.

Also, from lurking in various threads on the topic Netflix's in app messages added to people's irritation by suggesting that they check their WiFi/internet was working. Presumably that's the default error message but perhaps that could have been adjusted in advance somehow.

replies(2): >>42161566 #>>42163798 #
2. positr0n ◴[17 Nov 24 02:43 UTC] No.42161566[source]▶
One of the times I reloaded the page I got a raw envoy error message!
3. ta1243 ◴[17 Nov 24 12:17 UTC] No.42163798[source]▶
The point is that if the problem was different depending on the user, it will be in a distribution layer, not in the encoding or production layer

That eliminates a whole raft of problems.