High Pings To Some Servers

ravi_thegreat1

Newbie
[OP]
Dec 5, 2005
11
0
Hi !I am a MTNL delhi user and I am getting very high pings to V street gaming servers for over a week( 200+ ms) .It used to be about 50 ms before.I though it would be a network problem but today i came to know that one friend of mine on MTNL is getting 50+ ping to VS servers.Please post any solutions to the above problem or atleast post your ping times to the VS servers.Their ip is 202.63.160.44 .I do fiddle a lot with my poor router(its status light has lived beyond its lifetime).Its kinda urgent.Thanks.
 

cyberwiz

Senior Member
Regulars
Mar 11, 2005
2,482
46
Delhi
Pinging 202.63.160.44 with 32 bytes of data:Reply from 202.63.160.44: bytes=32 time=39ms TTL=123Reply from 202.63.160.44: bytes=32 time=39ms TTL=123Reply from 202.63.160.44: bytes=32 time=38ms TTL=123Reply from 202.63.160.44: bytes=32 time=40ms TTL=123Ping statistics for 202.63.160.44: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 38ms, Maximum = 40ms, Average = 39ms
 


alluring_bat

Newbie
Jan 22, 2007
2
0
hi ravi,even im getting bad pings on some servers like fragshack(about 400) since 2-3 weeks.but my pings on vstreet and cybergames servers are ok most of the times...maybe your prob will get rectified automatically as pings on cs servers depend on the routing and not on router or any other stuff...it just depend on the routing that is done by your exchange or isp company...so chill out maybe its gona get ok within few days.even experience same sort of problem sometimes though my friends get good pings.cheers
 

ravi_thegreat1

Newbie
[OP]
Dec 5, 2005
11
0
@sushu (intended :) )
Does my ping to an IP address(not to a web address) depend on my DNS server also ?

@ alluring bat
me getting 50 ping of fragshack but about 200+ ms on all others.

I know i can't do much about my pings but the thing is my friends on the same MTNL network are getting good pings but not me.

Trace route report : I cant get any info from this.Experts please help.

Code:
C:\Documents and Settings\Ravi>tracert 202.63.160.44Tracing route to 202-63-160-44.static.exatt.net [202.63.160.44]over a maximum of 30 hops:  1     *        *        *     Request timed out.  2    16 ms    14 ms    16 ms  triband-del-59.176.31.254.bol.net.in [59.176.31.254]  3    15 ms    15 ms    14 ms  triband-del-59.179.0.5.bol.net.in [59.179.0.5]  4     *      294 ms   295 ms  220.227.69.78  5     *        *        *     Request timed out.  6   193 ms   193 ms   194 ms  220.227.211.105  7   195 ms   193 ms   194 ms  202-63-160-44.static.exatt.net [202.63.160.44]Trace complete.
 


leomax

FraudBand
Regulars
Oct 26, 2005
312
0
Looks like a peering issue,between node 3 and 4,thats between mtnl and reliance..If your friends trace is simliar to vs?
 

sanke1

Well-Known Member
Aug 1, 2005
3,907
519
Mumbai
Code:
Microsoft Windows XP [Version 5.1.2600]© Copyright 1985-2001 Microsoft Corp.C:\Documents and Settings\Administrator>tracert 202.63.160.44Tracing route to 202-63-160-44.static.exatt.net [202.63.160.44]over a maximum of 30 hops:  1     *        *        *     Request timed out.  2    30 ms    22 ms    19 ms  triband-mum-59.183.63.254.mtnl.net.in [59.183.63.254]  3     *        *        *     Request timed out.  4    27 ms    26 ms    26 ms  203.197.72.162.static.vsnl.net.in [203.197.72.162]  5    25 ms    21 ms    19 ms  203.197.72.17.static.vsnl.net.in [203.197.72.17]  6    20 ms    17 ms    18 ms  unknown.net.reach.com [202.41.226.14]  7    21 ms    18 ms    17 ms  202-63-162-222.static.exatt.net [202.63.162.222]  8    26 ms    23 ms    27 ms  202-63-182-149.static.exatt.net [202.63.182.149]  9    30 ms    29 ms     *     202-63-160-44.static.exatt.net [202.63.160.44] 10    29 ms    31 ms    31 ms  202-63-160-44.static.exatt.net [202.63.160.44]Trace complete.
seems fine here frm Mumbai
 

ravi_thegreat1

Newbie
[OP]
Dec 5, 2005
11
0
Thanks to all for replying.
By the grace of St. Isidore of Seville (saint of internet) the pings have returned to 50 ms without me doing anything.
Maybe giving 10 hours of rest to the router did the trick.

The new tracert report ::

Code:
Microsoft Windows XP [Version 5.1.2600]© Copyright 1985-2001 Microsoft Corp.C:\Documents and Settings\Ravi>tracert 202.63.160.44Tracing route to 202-63-160-44.static.exatt.net [202.63.160.44]over a maximum of 30 hops:  1     *        *        *     Request timed out.  2    18 ms    14 ms    16 ms  triband-del-59.176.31.254.bol.net.in [59.176.31.254]  3    15 ms    16 ms    14 ms  202.159.220.33  4   275 ms   276 ms   275 ms  delhi-203.197.228-245.vsnl.net.in [203.197.228.245]  5    35 ms    33 ms    35 ms  59.163.16.1.static.vsnl.net.in [59.163.16.1]  6    34 ms    35 ms    35 ms  59.163.16.1.static.vsnl.net.in [59.163.16.1]  7    36 ms    33 ms    35 ms  203.197.33.162.static.vsnl.net.in [203.197.33.162]  8    49 ms    39 ms    38 ms  203.197.72.17.static.vsnl.net.in [203.197.72.17]  9    41 ms    38 ms    42 ms  unknown.net.reach.com [202.41.226.14] 10    41 ms    42 ms    37 ms  202-63-162-222.static.exatt.net [202.63.162.222] 11    36 ms    36 ms    36 ms  202-63-182-149.static.exatt.net [202.63.182.149] 12    40 ms    39 ms    38 ms  202-63-160-44.static.exatt.net [202.63.160.44]Trace complete.C:\Documents and Settings\Ravi>
 

mystery_inc18

Regulars
Regulars
Feb 6, 2006
1,038
4
Code:
Microsoft Windows XP [Version 5.1.2600](C) Copyright 1985-2001 Microsoft Corp.D:\Documents and Settings\Vishal.COMPAQ-PRESARIO>ping 4.2.2.1Pinging 4.2.2.1 with 32 bytes of data:Reply from 4.2.2.1: bytes=32 time=361ms TTL=240Reply from 4.2.2.1: bytes=32 time=356ms TTL=240Reply from 4.2.2.1: bytes=32 time=358ms TTL=240Reply from 4.2.2.1: bytes=32 time=357ms TTL=240Ping statistics for 4.2.2.1:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 356ms, Maximum = 361ms, Average = 358msD:\Documents and Settings\Vishal.COMPAQ-PRESARIO>ping 202.63.160.44Pinging 202.63.160.44 with 32 bytes of data:Reply from 202.63.160.44: bytes=32 time=121ms TTL=114Reply from 202.63.160.44: bytes=32 time=119ms TTL=114Reply from 202.63.160.44: bytes=32 time=121ms TTL=114Reply from 202.63.160.44: bytes=32 time=127ms TTL=114Ping statistics for 202.63.160.44:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 119ms, Maximum = 127ms, Average = 122ms
ping's no good in airtel either :( even on hamachi we get a min of 80ms (airtel to airtel) while my friends on mtnl get min of 35-40ms (mtnl to mtnl) :angry: