MTNL Ping suddenly high to Counter Strike servers

[x720]

Run a ping -t command and post the results. Check for packet loss.

At this point, given you're using your own modem, I'd put it down to Line issues. Any parallel lines installed? Which modem?

 

[Smith1212]

Myself using opendns dns server is it ok ?? if not then what shoud be the stable dns server for mtnl mumbai ?

i live in suburbs n my line is too good

 

[x720]

I use MTNL's own DNS servers and they work well for me. Use whatever works best.

 

[Smith1212]

what are the stable dns of mtnl mumbai ?/

 

[x720]

Have set it to auto. Connects to these always:
59.185.3.12
59.185.3.11

 

[PrateekS92]

Run a ping -t command and post the results. Check for packet loss.

At this point, given you're using your own modem, I'd put it down to Line issues. Any parallel lines installed? Which modem?

I tried with my backup modem and bought a new one.Not an issue at my end.

Used Digisol DG-BG1000,D-Link 2750u,TP-Link 8817.

No parallel lines.New wiring done a in june and port changed at june end..after MTNL made me waste money on new wiring saying line is at fault.

1 port change and everything is back to normal...seems ill have to beg for a port change again...should become a full time beggar, and live in a tent outside the MTNL exchange...

and just as i typed this post...had a disconnection...

i keep 3 cmd tabs open with ping -t commands to 3 MTNL dns servers at all times...the response from the MTNL dns servers are fine...the routing is shit...150-250 ping to singapore ? seriously -.-

 

---

[panzer008]

@PrateekS92

Its line problem.... like x720 pointed out....... ur SNR is fluctuating heavily..... which indicates line problems......

Need to get it fixed...... probably due to the rains.... tell the lines man to chg line DP too if possible.....

I had line noise problem 2 weeks back...... dc every 10mins...... turns out there was moisture in the box leading up to the splitter..... spent 4 days trying to find the problem..... even the lines man chked all the external wiring.... then I found out this problem...... SNR had dropped to 13-17dB...... since last week back to 26dB...... zero dc.... so chk for rain problems.....

 

[© Blackday]

Doesn't look to me the rain problem. How could everyone be facing the same problem. I've like 3 friends using MTNL and all of them are having the same issues

 

[x720]

^You're on Mtnl Delhi. Delhi and Mumbai have entirely different gateways. My latency, for example, is excellent currently.

Could be an issue affecting both cities, but I find that unlikely.

 

[PrateekS92]

@PrateekS92

Its line problem.... like x720 pointed out....... ur SNR is fluctuating heavily..... which indicates line problems......

Need to get it fixed...... probably due to the rains.... tell the lines man to chg line DP too if possible.....

I had line noise problem 2 weeks back...... dc every 10mins...... turns out there was moisture in the box leading up to the splitter..... spent 4 days trying to find the problem..... even the lines man chked all the external wiring.... then I found out this problem...... SNR had dropped to 13-17dB...... since last week back to 26dB...... zero dc.... so chk for rain problems.....

Its fine since yesterday afternoon..no disconnections yet..

 

[PrateekS92]

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>

 

[PrateekS92]

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.

 

[© Blackday]

I have the same ping today

 

[panzer008]

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.....

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

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.

 

[PrateekS92]

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? -.-