Evidence of throttling, sans foil...
More recently: http://www.hypebot.com/hypebot/2013/02/major-us-isps-launch-anti-piracy-system-6-strikes-and-well-throttle-you-.html
My personal testimony includes several instances whereby my internet connection dropped to a crawl after having spent enough time utilizing a particular service (about 3-4 hours playing World of Warcraft, roughly the same playing League of Legends, and the speeds will be similarly reduced when playing just one hour on both LoL and Spotify). These conditions are not new to me, and have been occurring at regular rates (discounting random disconnects because, well, that just happens at times for no reason) since I've had my Brighthouse service (about three years, now), and always resumes normal speeds within a few minutes of disconnecting from said programs. It also doesn't seem to matter what time of day, as these drop offs have occurred at various times during the day and late night (seriously, 2AM, 4-5AM, 10AM, 1PM, and of course evening hours as well). I've had techs come out, replaced the modem, and contacted customer service and listen over and over that it must be something on my end, just to offer to send more techs out (a not-so-cheap option, mind you).
In order to avoid it, we just don't play games for very long. It rarely happens during Twitch.tv or Justin.tv streaming anymore (I guess that YT video explains why), and I only get on Spotify for about 20-30 minutes. This method of avoiding prolonged use of these peer-to-peer programs has successfully kept our internet consistent and active. Yes, it's annoying, but it's better than getting our internet speeds dropped...and confirms some form of speed limitation being utilized by Brighthouse.
How about tests gathered from tools here: http://measurementlab.net/measurement-lab-tools
ShaperProbe (7 tests resulted in either test aborted due to too many packets lost, or an average of about this).
DiffProbe release. January 2012. Build 1008.
Shaper Detection Module.
Connected to server 184.108.40.206.
Upstream: 2282 Kbps.
Downstream: 32063 Kbps.
The measurement will take upto 2.5 minutes. Please wait.
Checking for traffic shapers:
Upstream: No shaper detected.
Median received rate: 2240 Kbps.
Downstream: Burst size: 5748-6410 KB;
Shaping rate: 23314 Kbps.
For more information, visit: http://www.cc.gatech.edu/~partha/diffprobe
NDT (keep in mind the above estimate for downstream):
The theoretical network limit is 6.32 Mbps The NDT server has a 82.0 KByte buffer which limits the throughput to 22.49 Mbps Your PC/Workstation has a 63.0 KByte buffer which limits the throughput to 8.73 Mbps The network based flow control limits the throughput to 8.75 Mbps
Your system: Windows XP version 5.2
Java version: 1.7.0_25 (x86)
TCP receive window: 65535 current, 65535 maximum
9.46432E-4 packets lost during test
Round trip time: 45 msec (minimum), 90 msec (maximum), 57.26 msec (average)
Jitter: 45 msec
0 seconds spend waiting following a timeout
TCP time-out counter: 254
61 selective acknowledgement packets received
No duplex mismatch condition was detected.
The test did not detect a cable fault.
No network congestion was detected.
No network address translation appliance was detected.
0.9498% of the time was not spent in a receiver limited or sender limited state.
4.33% of the time the connection is limited by the client machine's receive buffer.
Optimal receive buffer: 67107840 bytes
0 duplicate ACKs set
tl;dr "Currently there are no land based USA providers that engage in throttling of traffic such as P2P" is evidently false, even at the time of original posting.
Was this reply helpful? (1) (0)