As you can see, am getting almost 600ms(?) with packet drops or timeouts on a BROADBAND VSNL(512 kbps) connection. Sounds dicey as Im in INDIA. I dont think I should be getting more than 150-200ms especially since im on broadband. I think the number of hops is a culprit or a bad vsnl gateway could be the problem :see the drastic jump in servers between (7) and ( 8 ) . But MOST IMPORTANTLY, the BIGGEST jump in LATENCY is in SIFY's local LAN - SifyLimited.demarc.cogentco.com to lan-202-144-2-237.maa.sify.net!!!! I think something IS fixable @ ur end!!!!One bottleneck is right there. A two fold jump in ping!!!!
Hope this gets a jump start gms.
To sum it up, if these two congestions are cleared, the latency will automatically fall to around 220-280ms which would be perfect.!!!
Guys, BSNL and hathway users..plz post ur tracert info here! Might help to research especially for the lagging users.
~Alador Level 61 HK
The following shows three separate TRACERT runs. Two from my machine @ home and third one from a friend's office(all three running on VSNL). U can see there exist common latency points in ALL THREE!!! Imagine, 550ms latency on a T1 Line(Basically implies doesnt matter what type of connection exist..the problem is universal for VSNL->Radyan connectivity)???? Please see the statistics below:-
Tracert run #1(My Machine, 512 ADSL Line)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
C:\>tracert 210.210.67.138
Tracing route to 210-210-67-138.lan.sify.net [210.210.67.138]
over a maximum of 30 hops:
1 30 ms 29 ms 30 ms 210.211.194.1.bb-dynamic.vsnl.net.in [210.211.19
4.1]
2 * * * Request timed out.
3 33 ms 32 ms 32 ms 202.54.84.124.ill-bgl.static.vsnl.net.in [202.54
.84.124]
4 44 ms 44 ms 45 ms ekm-bgl-2nd-stm1.Bbone.vsnl.net.in [202.54.2.169
]
5 151 ms 150 ms 152 ms unknown.net.reach.com [134.159.129.61]
6 149 ms 150 ms 149 ms i-5-2.hht-dist02.net.reach.com [202.84.154.98]
7 111 ms 111 ms 110 ms i-11-0.hhtstcbr01.net.reach.com [202.84.154.65]
8 286 ms 285 ms 284 ms i-6-3.wil-core02.net.reach.com [202.84.249.41]
9 268 ms 269 ms 268 ms unknown.net.reach.com [202.84.251.166]
10 313 ms 313 ms 314 ms unassign.net.reach.com [134.159.63.66]
11 274 ms 275 ms 274 ms p9-2.core01.lax01.atlas.cogentco.com [154.54.1.3
3]
12 313 ms 314 ms 314 ms p14-0.core01.sjc01.atlas.cogentco.com [66.28.4.7
4]
13 315 ms 314 ms 315 ms g8.ba21.b001848-1.sjc01.atlas.cogentco.com [38.1
12.36.166]
14 285 ms 284 ms 285 ms SifyLimited.demarc.cogentco.com [38.112.1.46]
15 517 ms 517 ms 518 ms lan-202-144-2-237.maa.sify.net [202.144.2.237]
16 557 ms 559 ms 557 ms lan-202-144-74-161.sify.net [202.144.74.161]
17 * * * Request timed out.
Tracert run #2(My Machine, second run, 512 ADSL Line)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
C:\>tracert 210.210.67.138
Tracing route to 210-210-67-138.lan.sify.net [210.210.67.138]
over a maximum of 30 hops:
1 30 ms 30 ms 30 ms 210.211.194.1.bb-dynamic.vsnl.net.in [210.211.19
4.1]
2 30 ms 31 ms 31 ms 202.54.84.70.ill-bgl.static.vsnl.net.in [202.54.
84.70]
3 32 ms 30 ms 31 ms 202.54.84.124.ill-bgl.static.vsnl.net.in [202.54
.84.124]
4 44 ms 44 ms 44 ms ekm-bgl-2nd-stm1.Bbone.vsnl.net.in [202.54.2.169
]
5 150 ms 150 ms 151 ms unknown.net.reach.com [134.159.129.61]
6 150 ms 151 ms 152 ms i-5-2.hht-dist02.net.reach.com [202.84.154.98]
7 112 ms 110 ms 111 ms i-11-0.hhtstcbr01.net.reach.com [202.84.154.65]
8 284 ms 284 ms 284 ms i-6-3.wil-core02.net.reach.com [202.84.249.41]
9 267 ms 267 ms 268 ms unknown.net.reach.com [202.84.251.166]
10 313 ms 313 ms 313 ms unassign.net.reach.com [134.159.63.66]
11 275 ms 275 ms 275 ms p9-2.core01.lax01.atlas.cogentco.com [154.54.1.3
3]
12 314 ms 314 ms 314 ms p14-0.core01.sjc01.atlas.cogentco.com [66.28.4.7
4]
13 316 ms 314 ms 315 ms g8.ba21.b001848-1.sjc01.atlas.cogentco.com [38.1
12.36.166]
14 285 ms 284 ms 285 ms SifyLimited.demarc.cogentco.com [38.112.1.46]
15 519 ms 518 ms 518 ms lan-202-144-2-237.maa.sify.net [202.144.2.237]
16 559 ms 558 ms 571 ms lan-202-144-74-161.sify.net [202.144.74.161]
17 * * * Request timed out.
18 * * * Request timed out.
Tracert run#3(Office Machine, 10Mbps T1 LINE)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
C:\Documents and Settings\bh>tracert 210.210.67.138
Tracing route to 210-210-67-138.lan.sify.net [210.210.67.138]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms 192.168.130.1
2 <10 ms <10 ms <10 ms 192.168.1.1
3 2 ms 2 ms 2 ms
203.200.19.161.ill-bgl.static.vsnl.net.in [203.2
00.19.161]
4 3 ms 3 ms 3 ms 202.54.87.222.ill-bgl.static.vsnl.net.in
[202.54
.87.222]
5 3 ms 4 ms 3 ms 202.54.84.124 [202.54.84.124]
6 16 ms 19 ms 16 ms ekm-bgl-2nd-stm1.Bbone.vsnl.net.in
[202.54.2.169
]
7 253 ms 254 ms 253 ms unknown.net.reach.com [134.159.129.61]
8 270 ms 270 ms 270 ms i-5-2.hht-dist02.net.reach.com
[202.84.154.98]
9 275 ms 274 ms 274 ms i-11-0.hhtstcbr01.net.reach.com
[202.84.154.65]
10 257 ms 257 ms 257 ms i-6-3.wil-core02.net.reach.com
[202.84.249.41]
11 256 ms 256 ms 256 ms i-1-2.wil03.net.reach.com
[202.84.251.202]
12 262 ms 263 ms 261 ms unassign.net.reach.com [134.159.63.66]
13 276 ms 275 ms 276 ms p9-1.core01.lax01.atlas.cogentco.com
[154.54.2.1
01]
14 247 ms 247 ms 247 ms p14-0.core01.sjc01.atlas.cogentco.com
[66.28.4.7
4]
15 271 ms 271 ms 271 ms
g8.ba21.b001848-1.sjc01.atlas.cogentco.com [38.1
12.36.166]
16 271 ms 272 ms 271 ms SifyLimited.demarc.cogentco.com
[38.112.1.46]
17 516 ms 520 ms 514 ms lan-202-144-2-237.maa.sify.net
[202.144.2.237]
18 516 ms 516 ms 517 ms lan-202-144-74-161.sify.net
[202.144.74.161]
To close, I'm quoting a text from an Everquest user:
"I've always used cable (2 to 6 Mb) when playing. I have no idea how it plays on other connections. My ping in Everquest is typically 80 to 130 ms."
U can see how BAD the situation is in A3 if broadband is also delivering such high ping rates
.Im not expecting 80-130ms here in india, but 200-250 would be a decent estimate wouldnt u think??
