3 ms·
No, your reply is innacurate: https://www.extremetech.com/g00/computing/186576-verizon-caught-throttling-netflix-traffic-even-after-its-pays-for-more-bandwidth?
by peg_leg 9y ago
No, your reply is innacurate: https://www.extremetech.com/g00/computing/186576-verizon-caught-throttling-netflix-traffic-even-after-its-pays-for-more-bandwidth?i10c.encReferrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8%3D&i10c.ua=1 https://www.extremetech.com/g00/computing/186576-verizon-cau...
- wdewind 9y agoEdit: I'm having multiple people reply with basically the same thing which is: look here's what happened in 2014. I'm just going to reply to all of you here: What happened in 2014 was not throttling in the last mile, which is what the 2015 Title II re-classification protects against, so this would've been legal even without the repeal (and more importantly did not meaningfully contribute to Title II classification, like parent is implying). What happened in 2017 probably wasn't either, but could more reasonably be construed that way because it was all happening inside of Verizon's network. The Netflix Verizon case illustrates what makes Net Neutrality law so difficult to describe in technical terms. Verizon was not slowing down netflix packets, netflix was so big that it fully saturated multiple links. You can argue about what this implies for the peering agreements that are setup, but regardless this area is simply not something that net neutrality covers. Net neutrality says the last mile needs to treat all content it receives the same way. If the congestion is further up the network, NN has nothing to do with it.