Update 04/17/14 2:47pm Eastern
Alright guys, I messed up – I never ran the other test I was working on, and I apologize for dropping the ball there. Sounds like the issue was with an interconnect, and it also sounds like Netflix is setting up deals with ISP’s to avoid this type of problem.
Update 02/13/14 9:25am Eastern
Just a quick update for you all – I’m still working out a testing solution that standardizes as many variables as possible. Just for fun (and for the sake of actionable data) I’ve been running the original test periodically both on AWS and Akamai content. Neither has reached anything approaching the speeds my connection is capable of, however, in most cases the speeds have been usable (more like 1 – 2mb/s instead of 60kb/s). It does seem like something is consistently interfering with the data rate, though it’s still impossible to say with certainty whether it’s throttling, a dodgy backbone or node, or something all together different. I’ll update with more info when I can.
Update 02/11/14 9:24pm Eastern
As some of you have pointed out, it’s hard to say anything definitive about whether Fios is throttling without traceroute information. Additionally, it’s come to my attention that the file I was testing on today is hosted on Akamai, not AWS. Turns out I had some outdated info – sorry about that. It does, hwoever, look like Akamai is subject to the same slowdown based on what I found. I’m going to look into testing Akami further, and I’ll be running more tests on AWS in the coming days.
Articles and tweets have been popping up over the past couple of days accusing Verizon of throttling content hosted by AWS, Amazon’s cloud-based content storage solution. Today, I decided to spend a couple of hours running tests on my Fios internet connection to see if I could find signs of throttling, and the results were shocking.