MTNL Ping suddenly high to Counter Strike servers

  • Thread starter Thread starter Rehan
  • Start date Start date
  • Replies Replies 94
  • Views Views 22,231
AHPbloH.png


Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\System32>tracert 91.227.221.173:
Unable to resolve target system name 91.227.221.173:.

C:\Windows\System32>tracert 91.227.221.173

Tracing route to 91.227.221.173 over a maximum of 30 hops

1 3 ms 1 ms 1 ms WR-841N [192.168.2.1]
2 3 ms 9 ms 2 ms 192.168.1.1
3 * * * Request timed out.
4 26 ms 23 ms 8 ms static-mum-59.185.211.221.mtnl.net.in [59.185.21
1.221]
5 26 ms 15 ms 8 ms static-mum-59.185.211.222.mtnl.net.in [59.185.21
1.222]
6 * * * Request timed out.
7 40 ms 254 ms * 62.216.147.73
8 145 ms 142 ms 149 ms xe-0-0-0.0.pjr03.ldn001.flagtel.com [85.95.26.23
8]
9 143 ms 143 ms 143 ms ge-3-1-0.0.cjr03.ldn004.flagtel.com [62.216.129.
138]
10 158 ms 144 ms 145 ms po20.edge1.the.lon.uk.as31715.net [195.66.237.18
]
11 207 ms 204 ms 201 ms te3-3.edge1.thn.lon.uk.as31715.net [84.234.19.14
2]
12 167 ms 208 ms 148 ms rtr-peer-04.thn.v4.custdc.net [84.234.19.178]
13 143 ms 159 ms 145 ms rtr-23.cdc.custdc.net [109.74.255.189]
14 204 ms 150 ms 157 ms rtr-01.cdc.custdc.net [109.74.255.171]
15 177 ms 143 ms 143 ms mai-core-rou1.vooservers.com [109.74.246.107]
16 142 ms 294 ms 353 ms 91.227.221.173

Trace complete.

C:\Windows\System32>
 






Even if its a line problem..mtnl guys dont give a f*ck...13 complaints open,13 complaints instantly closed.According to them,if internet works for 10 minutes a day..its deemed working.
 
I dont think MTNL Mumbai is having problems to tht server.... Its more related to ur line instability @PrateekS92

MTNL Delhi has their routing messed up........

Below frm MTNL Mumbai...... No timeouts...... Reasonable ping to UK server.....

Code: 
ping 91.227.221.173 -t

Pinging 91.227.221.173 with 32 bytes of data:
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51
Reply from 91.227.221.173: bytes=32 time=134ms TTL=51
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51
Reply from 91.227.221.173: bytes=32 time=132ms TTL=51
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51
Reply from 91.227.221.173: bytes=32 time=132ms TTL=51
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51

Ping statistics for 91.227.221.173:
    Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 132ms, Maximum = 134ms, Average = 132ms
Control-C


Code: 
tracert 91.227.221.173

Tracing route to 91.227.221.173 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     6 ms     6 ms     6 ms  static-mum-59.185.4.45.mtnl.net.in [59.185.4.45]
  4     *        *        *     Request timed out.
  5    67 ms    67 ms    66 ms  62.216.147.45
  6   224 ms   223 ms   223 ms  xe-0-1-1.0.pjr03.ldn001.flagtel.com [85.95.26.233]
  7   310 ms   315 ms   316 ms  xe-5-2-0.0.cji01.ldn004.flagtel.com [62.216.128.114]
  8     *        *        *     Request timed out.
  9   131 ms   131 ms   131 ms  te3-3.edge1.thn.lon.uk.as31715.net [84.234.19.142]
 10   136 ms   135 ms   135 ms  rtr-peer-04.thn.v4.custdc.net [84.234.19.178]
 11   135 ms   135 ms   136 ms  rtr-23.cdc.custdc.net [109.74.255.189]
 12   133 ms   133 ms   133 ms  rtr-01.cdc.custdc.net [109.74.255.171]
 13   133 ms   133 ms   134 ms  mai-core-rou1.vooservers.com [109.74.246.107]
 14   133 ms   132 ms   133 ms  91.227.221.173

Trace complete.
 
Got line checked..turned out to be fine...definitely server problem....coz around 10-15 of my friends facing same issue in different places in mumbai...

Everyone whose connection and line was fine until last week...

SO how do we get this fixed? -.-
 
No idea :D

Switch to 8mbps, if you want awesome latency. But I don't think your line would be able to handle it.
 

ping 91.227.221.173 -t

Pinging 91.227.221.173 with 32 bytes of data:
Reply from 91.227.221.173: bytes=32 time=233ms TTL=51
Reply from 91.227.221.173: bytes=32 time=233ms TTL=51
Reply from 91.227.221.173: bytes=32 time=134ms TTL=51
Reply from 91.227.221.173: bytes=32 time=153ms TTL=51
Reply from 91.227.221.173: bytes=32 time=162ms TTL=51
Reply from 91.227.221.173: bytes=32 time=123ms TTL=51
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51
Reply from 91.227.221.173: bytes=32 time=233ms TTL=51
Reply from 91.227.221.173: bytes=32 time=122ms TTL=51
Reply from 91.227.221.173: bytes=32 time=222ms TTL=51
Reply from 91.227.221.173: bytes=32 time=167ms TTL=51
Reply from 91.227.221.173: bytes=32 time=156ms TTL=51
Reply from 91.227.221.173: bytes=32 time=189ms TTL=51
Reply from 91.227.221.173: bytes=32 time=145ms TTL=51
Reply from 91.227.221.173: bytes=32 time=133ms TTL=51
Reply from 91.227.221.173: bytes=32 time=122ms TTL=51
Reply from 91.227.221.173: bytes=32 time=233ms TTL=51
Reply from 91.227.221.173: bytes=32 time=144ms TTL=51

Ping statistics for 91.227.221.173:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 122ms, Maximum = 233ms, Average = 133ms
 
DownstreamUpstream
SNR Margin (0.1dB):251129
Attenuation (0.1dB):10085
Output Power (dBm):0.07.0
Attainable Rate (Kbps):260562529
Rate (Kbps):81912045
D (interleave depth):11
Delay (msec):0.220.24
Data Counter:
155295
24103
HEC Errors:00
OCD Errors:00
LCD Errors:00
CRC Errors:00
FEC Errors:00
Total ES12400
 

Similar threads

S
Counter-Strike servers being blocked ??
Replies
1
Views
1,769
WizZ
H
MTNL Delhi PLS tell about ping of sify on counter strike server
Replies
0
Views
1,152
harmandedar
H
PLS tell about ping of sify on counter strike server
Replies
0
Views
7,418
harmandedar
P
250ms+ Ping on Indian Servers (Counter Strike 1.6)
Replies
4
Views
6,907
PsyGeek
Back