 Anonymous_AnonymousPremium
join:2004-06-21
127.0.0.1
kudos:2
 ·RoadRunner Cable
4 edits | Preview of Twc torrent Throttling? (some areas)
Looks like TWC is Throttling connection due to torrent usage
by punishing users with HIGH ping time and slower throttled connections. usually restores it self with in 8 to 10 hours.
I tested this a few times to make sure what they were doing
tried 3 days in a row to make sure.
Rebooting DOES NOTHING!
CALL IN ASK FOR CREDIT!! I am sure after issuing enough credits they will disable it. Got to hit them were it hurts their pocket book.
I'll just have to switch back to direct downloads even though they are a little slower |
|
 hobgoblinSortof AgoblinPremium
join:2001-11-25
Orchard Park, NY
kudos:8 | Re: Preview of Twc torrent Throttling , now BEING ENFORCED "Looks like TWC is Throttling connection due to torrent usage"
And your proof is exactly what?
A speedtest from a third party site.
Good job.
Hob
--
"A foolish consistency is the hobgoblin of little minds."
- Ralph Waldo Emerson
|
|
Anonymous_AnonymousPremium
join:2004-06-21
127.0.0.1
kudos:2 Reviews:
·RoadRunner Cable
3 edits | said by hobgoblin:"Looks like TWC is Throttling connection due to torrent usage"
And your proof is exactly what?
A speedtest from a third party site.
Good job.
Hob
done more then that plus it starts happening on all devices(that dismisses connection limit issue) after starting a torrent so that is proof enough and does it for hours and hours after.
changed ip's to terminate all connections. (that dismisses echo connections issue as well)
signals are ideal
Locked QAM256 85 687000000 Hz 0.3 dBmV 39.0 dB 0 0
2 Locked QAM256 86 693000000 Hz 0.2 dBmV 39.2 dB 0 0
3 Locked QAM256 87 699000000 Hz 0.1 dBmV 39.0 dB 0 0
4 Locked QAM256 88 705000000 Hz -0.1 dBmV 38.7 dB 0 0
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 8 ms 11 ms 12 ms cpe-75-83-224-1.socal.res.rr.com [75.83.224.1]
2 9 ms 7 ms 23 ms cpe-24-24-194-157.socal.rr.com [24.24.194.157]
3 219 ms 218 ms 229 ms tge8-1.pldlcabl-cer02.socal.rr.com [72.129.26.17
7]
4 222 ms 219 ms 217 ms 72.129.26.174
5 260 ms 256 ms 260 ms agg24.tustcaft-ccr01.socal.rr.com [72.129.25.2]
6 267 ms 263 ms 247 ms 107.14.19.30
7 197 ms 195 ms 209 ms ae-1-0.pr0.lax00.tbone.rr.com [66.109.6.129]
8 189 ms 188 ms 197 ms xe-8-2-0.edge1.LosAngeles6.Level3.net [4.26.0.13
]
9 230 ms 226 ms 220 ms vlan70.csw2.LosAngeles1.Level3.net [4.69.144.126
]
10 211 ms 209 ms 213 ms ae-73-73.ebr3.LosAngeles1.Level3.net [4.69.137.3
7]
11 277 ms 276 ms 288 ms 4.69.132.82
12 263 ms 247 ms 256 ms ae-61-61.csw1.Washington1.Level3.net [4.69.134.1
30]
13 282 ms 296 ms 285 ms ae-62-62.ebr2.Washington1.Level3.net [4.69.134.1
45]
14 283 ms 279 ms 278 ms ae-4-4.ebr2.Newark1.Level3.net [4.69.132.102]
15 276 ms 277 ms 290 ms ae-21-52.car1.Newark1.Level3.net [4.69.156.37]
16 293 ms 309 ms 297 ms NETCCESS.car1.Newark1.Level3.net [4.26.16.186]
17 317 ms 324 ms 325 ms 0.e3-3.tbr2.mmu.nac.net [209.123.11.77]
18 321 ms 319 ms 308 ms 0.e1-1.tbr2.oct.nac.net [209.123.10.21]
19 283 ms 291 ms 288 ms vlan808.esd1.oct.nac.net [209.123.10.42]
20 285 ms 277 ms 283 ms www.dslreports.com [209.123.109.175]
Trace complete. |
|
Reviews:
·RoadRunner Cable
| reply to Anonymous_
No throttling here. I went to »broadband.mpi-sws.org/transparen···test.php and ran the BitTorrent test, then immediately went to speedtest.net after. Results:
Is your upload traffic rate limited?
There is no indication that your ISP rate limits your uploads.
However, some of the measurements were affected by noise, which limits Glasnost ability to detect rate limiting.
Details:
There is no indication that your ISP rate limits your BitTorrent uploads. In our tests, uploads using control flows achieved up to 3176 Kbps while uploads using BitTorrent achieved up to 3706 Kbps.
There is no indication that your ISP rate limits uploads on port 6881 or 47809. In our tests, uploads on port 6881 achieved up to 3148 Kbps while uploads on port 47809 achieved up to 3706 Kbps.
Is your download traffic rate limited?
There is no indication that your ISP rate limits your downloads.
However, some of the measurements were affected by noise, which limits Glasnost ability to detect rate limiting.
Details:
There is no indication that your ISP rate limits your BitTorrent downloads. In our tests, downloads using control flows achieved up to 19343 Kbps while downloads using BitTorrent achieved up to 19337 Kbps.
There is no indication that your ISP rate limits downloads on port 6881 or 47809. In our tests, downloads on port 6881 achieved up to 19343 Kbps while downloads on port 47809 achieved up to 19326 Kbps.
Based on your speed test you seem to be in SoCal as well. Maybe it's some other issue that you're having? Have you tried putting your modem into bridge mode and using another router? |
|
| reply to Anonymous_
You should learn how to read a traceroute.
High ping times start at the 3rd hop from you. If you were being throttled at your modem, the high ping times would show up at the first hop, between your modem and the CMTS you are connected to.
That traceroute shows me that some kind of congestion problem is causing the high ping times starting at the 3rd hop. |
|
Reviews:
·RoadRunner Cable
| reply to Anonymous_
By having high ping times don't mean TWC is throttling you. Just look like some congestion problem might be going on.
You can't blame TWC for throttling you. Cause TWC does not do any throttling on anything that I know of.
If they did we would have seen it on the front page here. Cause it would be big news here I would think. |
|
| reply to Anonymous_
Re: Preview of Twc torrent Throttling? Another throttling thread...FAIL!  |
|
DelmarPip
join:2011-10-15
South Padre Island, TX | reply to Anonymous_
i suspected this for a while they always slow me down alot an i have the fastest speed they got they should gimmy more speed not slow me down |
|
iansltx
join:2007-02-19
Golden, CO
kudos:2 Reviews:
 ·Verizon Online DSL
·RoadRunner Cable
·Comcast
| reply to Anonymous_
Reporting NO THROTTLING here in Austin (sorry for the caps; just making a tl;dr).
I've downloaded 10GB torrents before...then turned around and downloaded another 10GB torrent...all without seeing speeds drop below 40 Mbps of so (I have 50/5...40 Mbps only because the torrents I download aren't particularly well-seeded at times). It has been awhile since I've done this (a month or so) however recently I've pulled down a gigabyte or two at full speed, then 45 minutes later done the same thing, except around 4GB, without any ill effects.
I've also downloaded torrents, then turned around and gamed on the connection, with ~60ms ping to LA (just like normal). And this is on a not-particularly-high-capacity node (4x1 bonding...there may be additional channels available but I'm not seeing them...and sometimes my speeds won't quite make it to 50 Mbps during congested times, but they won't go below 40 Mbps iehter).
As such, I'm treating all reports of TWC throttling of torrents (or anything else) as anecdotal until I see more of them, with similar behavior, spread over multiple people, with connections that aren't naturally congested (some areas have serious congestion issues during peak times on TWC). |
|
 NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:9
·SONIC.NET
·Pacific Bell - SBC
| reply to Anonymous_
Re: Preview of Twc torrent Throttling , now BEING ENFORCED said by Anonymous_: done more then that plus it starts happening on all devices(that dismisses connection limit issue) after starting a torrent so that is proof enough and does it for hours and hours after.
I once had torrent speed problems on an SBC ADSL connection. It appeared to be "throttling", but that was not normal for SBC. So I did some local troubleshooting. Turns out that an upgrade of the uTorrent client had changed some of my custom settings back to defaults, and I was essentially throttling myself.
If you really suspect your ISP is throttling, there are better tests than tracert for finding evidence of throttling.
You could search the Comcast forum; one of their users proved that they were forging TCP "RST" flags using Wireshark.
Or Google "glasnost throttling test", and pick a site.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
|
|
 Suit Up
join:2003-07-21
Los Angeles, CA
·Time Warner Cable
| reply to motoracer
Re: Preview of Twc torrent Throttling? said by motoracer:Another throttling thread...FAIL!
Well it's been a couple weeks since the last one. We were due for another sooner or later... |
|
 DrDrewSo that others may surf.
join:2009-01-28
SoCal
kudos:8 | reply to Anonymous_
Seems you're throwing things at the wall to see what sticks:
»High Lantcy after IP block change
BTW, why would TWC give a customer credit for something they were purposely doing? If TWC didn't think it was a problem, they wouldn't give you credit. If it were really a TWC policy, they'd tell you to stop torrenting, not give you credit.
--
If it's important, back it up... twice. Even 99.999% availability isn't enough sometimes. |
|
 Elyria
join:2011-10-12
Elyria, OH | reply to Anonymous_
Another caps and throttling thread
 |
|
 SeleniaI love DebianPremium
join:2006-09-22
Lanesboro, MA
kudos:2 | reply to mind21_98
Re: Preview of Twc torrent Throttling , now BEING ENFORCED My glasnost test says I am throttled, but I get full speeds on torrents. Wonder if TWC simply gives them low priority if there is congestion and such traffic management(which would be reasonable) shows up as throttling. Anyways, no real world trouble here. |
|
Anonymous_AnonymousPremium
join:2004-06-21
127.0.0.1
kudos:2 Reviews:
·RoadRunner Cable
1 edit | reply to Lowtarget
said by Lowtarget:By having high ping times don't mean TWC is throttling you. Just look like some congestion problem might be going on.
You can't blame TWC for throttling you. Cause TWC does not do any throttling on anything that I know of.
If they did we would have seen it on the front page here. Cause it would be big news here I would think.
still doing it every time I try it.. getting 300 to 1000 to the east cost currently .
120ms locally
problem can be reproduced with ease on a continues basis.
2.9Mbps while downloads on port 43473 achieved up to 3.1 Mbps.
10% of 30mbps download
68% of 5 upload |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:9 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| said by Anonymous_: still doing it every time I try it.. getting 300 to 1000 to the east cost currently .
120ms locally
problem can be reproduced with ease on a continues basis.
You need to run Wireshark and capture some packets.
Some reading material:
»Comcast is using Sandvine to manage P2P Connections
Buried in that mess should be a post by funchords  on how to capture the packets needed to prove throttling.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
Anonymous_AnonymousPremium
join:2004-06-21
127.0.0.1
kudos:2 | still 400ms+ daily at the same time every day. (does it on all devices ) |
|
| said by Anonymous_: still 400ms+ daily at the same time every day. (does it on all devices )
400ms you say? Same time every day you say? All devices you say?
Then it sounds like a congestion problem at the time most people are using the service. (The "same time every day" thing would clue you in on that.) Call TWC. Don't just come here and make conspiracies about throttling when you have no idea how it works in the first place. |
|
DrDrewSo that others may surf.
join:2009-01-28
SoCal
kudos:8 | reply to Anonymous_
said by Anonymous_: still 400ms+ daily at the same time every day. (does it on all devices )
If it's the link between hops 2 and 3 in the trace above that is hitting 400ms... then it's between the CMTS and the main router in the Palmdale headend. Not throttling at all.
--
If it's important, back it up... twice. Even 99.999% availability isn't enough sometimes. |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:9 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| reply to Anonymous_
said by Anonymous_: still 400ms+ daily at the same time every day. (does it on all devices )
Wireshark will also show evidence of congestion, as well as throttling. Capture some packets, already!
Although it was ADSL, not DOCSIS, I know I have never been throttled, but I have been congested.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
