 dmwagnerQwest DSL -alltel join:2002-04-29 Canton, SD | Lag Lag Lag I am getting so frustrated with the lag I am getting in online gaming for the past month or so.
It's getting worse and worse.
My modem's connection is nearly perfect. The problem I am having is with my 3rd hop, it goes super high latency at 1 to 2 minute intervals. |
|
 | Are you using a UDP traceroute or TCP? If TCP, what port are you using? |
|
 dmwagnerQwest DSL -alltel join:2002-04-29 Canton, SD | said by colorbars:Are you using a UDP traceroute or TCP? If TCP, what port are you using? I am not aware of a UDP or TCP version ping. It's a ICMP ping request that the program uses. |
|
 | Sorry, I meant ICMP not UDP. Using ICMP is your first problem. Routers know it's useless data and often shove it down to lowest priority. That won't necessarily give you an accurate reading. Using a TCP traceroute on the same port that the game uses will give more accurate results. Whether that makes a difference in this case I don't know. Actually finding a Windows traceroute that does TCP is another matter.
In any case if I'm reading the traceroute correctly (and it's accurate) the problem is between the local location where your connection hits the DSLAM/Remote Terminal/whatever and then heads out toward the net. My guess would be that your local point is oversold. Only thing I can think to do is complain. |
|
 BinkVillains... knock off all that evil join:2006-05-14 Denver, CO kudos:4 Reviews:
·VOIPo
| reply to dmwagner While it doesn't mean much and, FWIW, here's my UDP-based traceroute:
$ traceroute 66.135.52.116
traceroute to 66.135.52.116 (66.135.52.116), 64 hops max, 40 byte packets
1 hlrn-dsl-gw51-243.hlrn.qwest.net (207.225.112.243) 30.963 ms 31.102 ms 30.223 ms
2 hlrn-agw1.inet.qwest.net (71.217.189.145) 29.813 ms 30.358 ms 31.95 ms
3 dvr-core-02.inet.qwest.net (67.14.24.29) 31.11 ms 30.928 ms 31.340 ms
4 dvr-brdr-01.inet.qwest.net (205.171.10.10) 111.56 ms 46.249 ms 219.822 ms
5 63.146.26.138 (63.146.26.138) 30.923 ms 31.343 ms 31.784 ms
6 vlan51.ebr1.Denver1.Level3.net (4.69.147.94) 31.777 ms 31.136 ms 31.982 ms
7 ae-2-2.ebr2.Dallas1.Level3.net (4.69.132.106) 49.510 ms 49.656 ms 49.551 ms
8 ae-62-62.csw1.Dallas1.Level3.net (4.69.151.129) 49.121 ms ae-92-92.csw4.Dallas1.Level3.net (4.69.151.165) 49.705 ms ae-82-82.csw3.Dallas1.Level3.net (4.69.151.153) 51.36 ms
9 ae-1-60.edge9.Dallas1.Level3.net (4.69.145.16) 49.359 ms ae-4-90.edge9.Dallas1.Level3.net (4.69.145.208) 49.653 ms ae-1-60.edge9.Dallas1.Level3.net (4.69.145.16) 49.232 ms
10 PEER-1-NETW.edge9.Dallas1.Level3.net (4.59.118.6) 48.57 ms 49.724 ms 50.769 ms
11 10ge-ten1-3.sat-8500v-cor-2.peer1.net (216.187.124.178) 56.897 ms 57.478 ms 57.187 ms
12 216.187.124.110 (216.187.124.110) 56.129 ms 57.206 ms 57.645 ms
13 66.135.52.116 (66.135.52.116) 59.163 ms 57.962 ms 57.9 ms
|
|
 dmwagnerQwest DSL -alltel join:2002-04-29 Canton, SD | reply to dmwagner I am so sick of this lousy peformance. Tonight, I can't even break 1MB/s download.
Modem is trained in perfect. |
|
 dmwagnerQwest DSL -alltel join:2002-04-29 Canton, SD | reply to dmwagner Wow, Qwest fixed me up. Got on the online chat... about an hour later I was good to go. |
|