I have horrible lag while play quake 3. Here's a tracert, can someone tell me where my problem is.
Thx for help ..Tracing route to q3.quake****.com [216.66.15.138]
over a maximum of 30 hops:
1 26 ms 40 ms 40 ms 24.8.123.1
2 346 ms 19 ms 16 ms r1-fe6-7-100bt.mntp1.il.home.net [24.2.192.1]
3 93 ms 17 ms 18 ms 24.7.77.173
4 82 ms 33 ms 69 ms posip2-1.core2.Chicago1.Level3.net [209.0.227.77
]
5 488 ms 71 ms 34 ms so-6-0-0.mp1.Chicago1.level3.net [209.247.10.165
]
6 211 ms 52 ms 60 ms so-0-0-0.mp1.NewYork1.level3.net [209.247.8.13]
7 68 ms 44 ms 44 ms pos8-0.core1.NewYork1.level3.net [209.247.10.34]
8 135 ms 40 ms 107 ms gigaethernet6-0.ipcolo1.NewYork1.Level3.net [209
.244.12.42]
9 338 ms 60 ms 73 ms fa0-0.br1.nycmny.us.lightning.net [209.244.186.1
0]
10 106 ms 89 ms 79 ms s4-1-0.br1.minlny.us.lightning.net [216.66.0.89]
11 119 ms 59 ms 56 ms q3.quake****.com [216.66.15.138]
Trace complete
I did this one right after the on above..
Tracing route to q3.quake****.com [216.66.15.138]
over a maximum of 30 hops:
1 57 ms 100 ms 119 ms 24.8.123.1
2 148 ms 70 ms 82 ms r1-fe6-7-100bt.mntp1.il.home.net [24.2.192.1]
3 47 ms 112 ms 69 ms 24.7.77.173
4 94 ms 145 ms 87 ms posip2-1.core2.Chicago1.Level3.net [209.0.227.77
]
5 64 ms 74 ms 47 ms so-6-0-0.mp1.Chicago1.level3.net [209.247.10.165
]
6 106 ms 58 ms 143 ms so-0-0-0.mp1.NewYork1.level3.net [209.247.8.13]
7 345 ms 103 ms 68 ms pos8-0.core1.NewYork1.level3.net [209.247.10.34]
8 222 ms 97 ms 53 ms gigaethernet6-0.ipcolo1.NewYork1.Level3.net [209
.244.12.42]
9 111 ms 120 ms 105 ms fa0-0.br1.nycmny.us.lightning.net [209.244.186.1
0]
10 282 ms 108 ms 81 ms s4-1-0.br1.minlny.us.lightning.net [216.66.0.89]
11 108 ms 97 ms 94 ms q3.quake****.com [216.66.15.138]
Trace complete.
Tracert ?
I'm not really good at deciphering this stuff but here's some tracerts to the server. I don't know if this information will help you butv here it is:
I have Road Runner by Time Warner Cable. My caps are 2000/386 up. Here's the 2 tracerts I did:
Tracing route to q3.quake****.com [216.66.15.138]
over a maximum of 30 hops:
1 13 ms <10 ms <10 ms 10.74.88.1
2 <10 ms 13 ms 14 ms msp-hub3-ubr-a-pos-1-0.mn.rr.com [24.26.161.81]
3 13 ms <10 ms 14 ms 24.26.161.86
4 14 ms <10 ms 14 ms msp-hub1-gsr-a-pos1-1.mn.rr.com [24.26.161.9]
5 14 ms 14 ms 13 ms msp-mhe-gsr-a-pos5-0.mn.mediaone.net [24.26.161.65]
6 14 ms 13 ms 14 ms msp-mhe-gsr-b-pos-1-0.mn.mediaone.net [24.31.1.2]
7 14 ms 28 ms 27 ms nic-31-c2-030.mn.mediaone.net [24.31.2.30]
8 13 ms 42 ms 27 ms 12.125.74.29
9 27 ms 28 ms 27 ms gbr5-p80.sl9mo.ip.att.net [12.123.24.234]
10 27 ms 28 ms 27 ms gbr3-p100.sl9mo.ip.att.net [12.122.5.178]
11 69 ms 68 ms 69 ms gbr3-p20.sffca.ip.att.net [12.122.2.74]
12 69 ms 69 ms 68 ms gbr2-p60.sffca.ip.att.net [12.122.5.253]
13 68 ms 69 ms 68 ms nr1-p360.napsf.ip.att.net [192.205.31.38]
14 123 ms 110 ms 110 ms mae-west.lightning.net [198.32.136.156]
15 124 ms 110 ms 110 ms s1-0-0.br1.snvaca.us.lightning.net [216.66.1.9]
16 110 ms 123 ms 110 ms a4-0-0.br1.nycmny2.us.lightning.net [216.66.3.5]
17 110 ms 124 ms 110 ms s4-1-0.br1.minlny.us.lightning.net [216.66.0.89]
18 124 ms 109 ms 124 ms q3.quake****.com [216.66.15.138]
Trace complete.
Here's the seconds one:
Tracing route to q3.quake****.com [216.66.15.138]
over a maximum of 30 hops:
1 14 ms <10 ms <10 ms 10.74.88.1
2 14 ms 14 ms 14 ms msp-hub3-ubr-a-pos-1-0.mn.rr.com [24.26.161.81]
3 14 ms 13 ms <10 ms 24.26.161.86
4 13 ms <10 ms 14 ms msp-hub1-gsr-a-pos1-1.mn.rr.com [24.26.161.9]
5 14 ms 14 ms <10 ms msp-mhe-gsr-a-pos5-0.mn.mediaone.net [24.26.161.65]
6 14 ms 14 ms 13 ms msp-mhe-gsr-b-pos-1-0.mn.mediaone.net [24.31.1.2]
7 27 ms 14 ms 27 ms nic-31-c2-030.mn.mediaone.net [24.31.2.30]
8 27 ms 28 ms 27 ms 12.125.74.29
9 27 ms 28 ms 27 ms gbr5-p80.sl9mo.ip.att.net [12.123.24.234]
10 13 ms 28 ms 27 ms gbr3-p100.sl9mo.ip.att.net [12.122.5.178]
11 69 ms 68 ms 69 ms gbr3-p20.sffca.ip.att.net [12.122.2.74]
12 69 ms 68 ms 69 ms gbr2-p60.sffca.ip.att.net [12.122.5.253]
13 68 ms 69 ms 82 ms nr1-p360.napsf.ip.att.net [192.205.31.38]
14 110 ms 110 ms 110 ms mae-west.lightning.net [198.32.136.156]
15 110 ms 124 ms 110 ms s1-0-0.br1.snvaca.us.lightning.net [216.66.1.9]
16 110 ms 123 ms 110 ms a4-0-0.br1.nycmny2.us.lightning.net [216.66.3.5]
17 110 ms 124 ms 110 ms s4-1-0.br1.minlny.us.lightning.net [216.66.0.89]
18 110 ms 109 ms 110 ms q3.quake****.com [216.66.15.138]
Trace complete.
Here's some pings I did:
Pinging q3.quake****.com [216.66.15.138] with 32 bytes of data:
Reply from 216.66.15.138: bytes=32 time=110ms TTL=238
Reply from 216.66.15.138: bytes=32 time=123ms TTL=238
Reply from 216.66.15.138: bytes=32 time=110ms TTL=238
Reply from 216.66.15.138: bytes=32 time=110ms TTL=238
Reply from 216.66.15.138: bytes=32 time=124ms TTL=238
Reply from 216.66.15.138: bytes=32 time=109ms TTL=238
Reply from 216.66.15.138: bytes=32 time=123ms TTL=238
Reply from 216.66.15.138: bytes=32 time=110ms TTL=238
Reply from 216.66.15.138: bytes=32 time=110ms TTL=238
Reply from 216.66.15.138: bytes=32 time=123ms TTL=238
Ping statistics for 216.66.15.138:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 124ms, Average = 115ms
[ 02-07-2001: Message edited by: Aaladar ]
I have Road Runner by Time Warner Cable. My caps are 2000/386 up. Here's the 2 tracerts I did:
Tracing route to q3.quake****.com [216.66.15.138]
over a maximum of 30 hops:
1 13 ms <10 ms <10 ms 10.74.88.1
2 <10 ms 13 ms 14 ms msp-hub3-ubr-a-pos-1-0.mn.rr.com [24.26.161.81]
3 13 ms <10 ms 14 ms 24.26.161.86
4 14 ms <10 ms 14 ms msp-hub1-gsr-a-pos1-1.mn.rr.com [24.26.161.9]
5 14 ms 14 ms 13 ms msp-mhe-gsr-a-pos5-0.mn.mediaone.net [24.26.161.65]
6 14 ms 13 ms 14 ms msp-mhe-gsr-b-pos-1-0.mn.mediaone.net [24.31.1.2]
7 14 ms 28 ms 27 ms nic-31-c2-030.mn.mediaone.net [24.31.2.30]
8 13 ms 42 ms 27 ms 12.125.74.29
9 27 ms 28 ms 27 ms gbr5-p80.sl9mo.ip.att.net [12.123.24.234]
10 27 ms 28 ms 27 ms gbr3-p100.sl9mo.ip.att.net [12.122.5.178]
11 69 ms 68 ms 69 ms gbr3-p20.sffca.ip.att.net [12.122.2.74]
12 69 ms 69 ms 68 ms gbr2-p60.sffca.ip.att.net [12.122.5.253]
13 68 ms 69 ms 68 ms nr1-p360.napsf.ip.att.net [192.205.31.38]
14 123 ms 110 ms 110 ms mae-west.lightning.net [198.32.136.156]
15 124 ms 110 ms 110 ms s1-0-0.br1.snvaca.us.lightning.net [216.66.1.9]
16 110 ms 123 ms 110 ms a4-0-0.br1.nycmny2.us.lightning.net [216.66.3.5]
17 110 ms 124 ms 110 ms s4-1-0.br1.minlny.us.lightning.net [216.66.0.89]
18 124 ms 109 ms 124 ms q3.quake****.com [216.66.15.138]
Trace complete.
Here's the seconds one:
Tracing route to q3.quake****.com [216.66.15.138]
over a maximum of 30 hops:
1 14 ms <10 ms <10 ms 10.74.88.1
2 14 ms 14 ms 14 ms msp-hub3-ubr-a-pos-1-0.mn.rr.com [24.26.161.81]
3 14 ms 13 ms <10 ms 24.26.161.86
4 13 ms <10 ms 14 ms msp-hub1-gsr-a-pos1-1.mn.rr.com [24.26.161.9]
5 14 ms 14 ms <10 ms msp-mhe-gsr-a-pos5-0.mn.mediaone.net [24.26.161.65]
6 14 ms 14 ms 13 ms msp-mhe-gsr-b-pos-1-0.mn.mediaone.net [24.31.1.2]
7 27 ms 14 ms 27 ms nic-31-c2-030.mn.mediaone.net [24.31.2.30]
8 27 ms 28 ms 27 ms 12.125.74.29
9 27 ms 28 ms 27 ms gbr5-p80.sl9mo.ip.att.net [12.123.24.234]
10 13 ms 28 ms 27 ms gbr3-p100.sl9mo.ip.att.net [12.122.5.178]
11 69 ms 68 ms 69 ms gbr3-p20.sffca.ip.att.net [12.122.2.74]
12 69 ms 68 ms 69 ms gbr2-p60.sffca.ip.att.net [12.122.5.253]
13 68 ms 69 ms 82 ms nr1-p360.napsf.ip.att.net [192.205.31.38]
14 110 ms 110 ms 110 ms mae-west.lightning.net [198.32.136.156]
15 110 ms 124 ms 110 ms s1-0-0.br1.snvaca.us.lightning.net [216.66.1.9]
16 110 ms 123 ms 110 ms a4-0-0.br1.nycmny2.us.lightning.net [216.66.3.5]
17 110 ms 124 ms 110 ms s4-1-0.br1.minlny.us.lightning.net [216.66.0.89]
18 110 ms 109 ms 110 ms q3.quake****.com [216.66.15.138]
Trace complete.
Here's some pings I did:
Pinging q3.quake****.com [216.66.15.138] with 32 bytes of data:
Reply from 216.66.15.138: bytes=32 time=110ms TTL=238
Reply from 216.66.15.138: bytes=32 time=123ms TTL=238
Reply from 216.66.15.138: bytes=32 time=110ms TTL=238
Reply from 216.66.15.138: bytes=32 time=110ms TTL=238
Reply from 216.66.15.138: bytes=32 time=124ms TTL=238
Reply from 216.66.15.138: bytes=32 time=109ms TTL=238
Reply from 216.66.15.138: bytes=32 time=123ms TTL=238
Reply from 216.66.15.138: bytes=32 time=110ms TTL=238
Reply from 216.66.15.138: bytes=32 time=110ms TTL=238
Reply from 216.66.15.138: bytes=32 time=123ms TTL=238
Ping statistics for 216.66.15.138:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 124ms, Average = 115ms
[ 02-07-2001: Message edited by: Aaladar ]
your problem is when you get routed through level3.net in newyork i pings the servers your routed through and 209.247.10.165
would ping as high as 200ms on average
same with 209.247.8.13 i would get a 25% packet loss on 209.244.12.42 i would try to find a server that you didn't route through level3.net
would ping as high as 200ms on average
same with 209.247.8.13 i would get a 25% packet loss on 209.244.12.42 i would try to find a server that you didn't route through level3.net
It's Because Light Travels Faster Then Sound That Some People Appear Bright Until They Speak
-
Kip Patterson
- Senior Member
- Posts: 4438
- Joined: Wed Jun 07, 2000 12:00 pm
- Location: Columbus, Ohio
For phamien:
Your pings are in trouble at the first hop. You need to resolve that before you look further upstream.
Possible causes include electrical interference (ingress), someone in your serving group running a server, intermittent cable or amplifier, low signal level, etc.
Look at Aaladar's popsting for comparison. His times look great, by the way, considering the atrocious routing. The point is, they are consistent. That happens because the cross-country circuits have thousands of simultaneous users, and the propagation times don't change rapidly from one ping to the next. Think of it like inertia. When youo see big circuits with big swings in pings, it probably isn't happening there.
Good luck,
Kip Patterson
Your pings are in trouble at the first hop. You need to resolve that before you look further upstream.
Possible causes include electrical interference (ingress), someone in your serving group running a server, intermittent cable or amplifier, low signal level, etc.
Look at Aaladar's popsting for comparison. His times look great, by the way, considering the atrocious routing. The point is, they are consistent. That happens because the cross-country circuits have thousands of simultaneous users, and the propagation times don't change rapidly from one ping to the next. Think of it like inertia. When youo see big circuits with big swings in pings, it probably isn't happening there.
Good luck,
Kip Patterson
During the day my pings are horrible on every server I try. Between the hours of 2am-7am are the only times when my ping is good 20-50ms.
How would I find out how many people are on my node?
Actually my pings arent horrible, they are usually between 50-125, but the lag spikes are just ridiculous, people cant even see my guy on the screen
I would rather play with a 300 ping without lag.
Even on one server I get a 20 ping normally and when I lag it is around 50, but people complain that I am impossible to hit, grr it's aggravating.
Help me
[ 02-08-2001: Message edited by: phamien ]
How would I find out how many people are on my node?
Actually my pings arent horrible, they are usually between 50-125, but the lag spikes are just ridiculous, people cant even see my guy on the screen
I would rather play with a 300 ping without lag.Even on one server I get a 20 ping normally and when I lag it is around 50, but people complain that I am impossible to hit, grr it's aggravating.
Help me
[ 02-08-2001: Message edited by: phamien ]