MTNL Delhi High ping, loads of disconnects.

[Ekaansh Arora]

Hello, I was highly satisfied with the no FUP plans from MTNL 1K for 1Mb/S. I used to have 80-100 ping on SEA DotA2 servers. My connection was very stable but now I have started getting super high pings (300-400) and my connections disconnects nearly every 10 minutes. I am guessing a wiring problem. Below is the SNR, Traceroute to the server and modem log. Any kind of help would be largely appreciated. Should I shift to Reliance thunder 1099 plan? 4Mb/S no FUP.

Modem log
10/20/2014 16:40:57> SNMP TRAP 2: link down
10/20/2014 16:40:57> MPOA Link Down
10/20/2014 16:40:57> mpoaChannDown: ch<0> null iface
10/20/2014 16:40:57> SNMP TRAP 2: link down
10/20/2014 16:40:57> SNMP TRAP 2: link down
10/20/2014 16:40:57> netMakeChannDial: err=-3001 rn_p=804d4790
10/20/2014 16:41:29> Last errorlog repeat 299 Times
10/20/2014 16:41:29> MPOA Link Up
10/20/2014 16:41:29> Quick bridge not allow multi-channel
10/20/2014 16:41:29> bridge only stop
10/20/2014 16:41:29> SNMP TRAP 3: link up
10/20/2014 16:41:29> Quick bridge not allow multi-channel
10/20/2014 16:41:29> bridge only stop
10/20/2014 16:41:29> SNMP TRAP 3: link up
10/20/2014 16:41:32> ppp_ready: ch:8051e930, iface:804690c4
10/20/2014 16:41:32> SNMP TRAP 3: link up
10/20/2014 16:41:32> Accept() fail
10/20/2014 16:41:32> Accept() fail

SNR
Downstream | Upstream
SNR Margin:
20.0 | 28.0 db
Line Attenuation:
33.0 | 20.7 db


Tracing route to sgp-1.valve.net [103.28.54.1]
over a maximum of 30 hops:

1 <1 ms <1 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 * 16 ms 16 ms triband-del-59.180.210.201.bol.net.in [59.180.21
0.201]
4 * * 15 ms triband-del-59.180.210.202.bol.net.in [59.180.21
0.202]
5 * 22 ms 16 ms 115.254.111.150
6 * * * Request timed out.
7 62 ms 61 ms 62 ms so-2-0-1.0.cjr03.ldn001.flagtel.com [62.216.144.
77]
8 * * 125 ms so-7-0-0.0.ejr03.sin001.flagtel.com [62.216.128.
73]
9 128 ms 122 ms 125 ms 80.81.64.102
10 126 ms 129 ms 124 ms global.hgc.com.hk [218.189.12.234]
11 129 ms 126 ms 125 ms sgp-1.valve.net [103.28.54.1]

Trace complete.

 

[Rachit]

This is my Traceroot.In short its reliance problem since you can see this (
8 * 123 ms 123 ms so-7-0-0.0.ejr03.sin001.flagtel.com [62.216.128.
73] ===> this is the problem when i traced it.... it is reliance singapore from which mtnl buy international bandwidth.last 2 days randomly i got 87 - 97 ping when this ping gave 90ms instead of 123.i was very happy since i didnt play last 22 days due to high ping.but it seems the problem is back Don't worry the problem is still there and i am planning to make a facebook page and invite every mtnl/bsnl/reliance user facing the issue.frankly we can only hope it will work with 87 ping again.

Additionally i have got new router issued from MTNL,Drop wire completely changed,lan wire also changed.i cann confirm its routing issue by reliance.if you need any additional help let me know i will help you troubleshoot the issue.

C:\Users\Rachit>tracert 103.28.54.1

Tracing route to sgp-1.valve.net [103.28.54.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * 19 ms 19 ms triband-del-59.180.210.193.bol.net.in [59.180.21
0.193]
4 18 ms 18 ms 18 ms triband-del-59.180.210.194.bol.net.in [59.180.21
0.194]
5 18 ms 19 ms 19 ms 115.254.111.158
6 55 ms * * 115.255.252.149
7 61 ms 61 ms 61 ms 62.216.147.249
8 * 123 ms 123 ms so-7-0-0.0.ejr03.sin001.flagtel.com [62.216.128.
73]
9 121 ms 121 ms 121 ms 80.81.64.102
10 118 ms 118 ms 119 ms global.hgc.com.hk [218.189.12.234]
11 117 ms 138 ms 116 ms sgp-1.valve.net [103.28.54.1]

Trace complete.

C:\Users\Rachit>

 

[panzer008]

This is not to intrude but...... MTNL Mumbai doesnt seem to be using Reliance Flagtel route to Singapore......

ping 103.28.54.1

Pinging 103.28.54.1 with 32 bytes of data:
Reply from 103.28.54.1: bytes=32 time=67ms TTL=55
Reply from 103.28.54.1: bytes=32 time=66ms TTL=56
Reply from 103.28.54.1: bytes=32 time=65ms TTL=55
Reply from 103.28.54.1: bytes=32 time=66ms TTL=55

Ping statistics for 103.28.54.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 65ms, Maximum = 67ms, Average = 66ms

tracert 103.28.54.1

Tracing route to sgp-1.valve.net [103.28.54.1]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  192.168.1.1
 2     *        *        *     Request timed out.
 3     6 ms     7 ms     7 ms  static-mum-59.185.4.45.mtnl.net.in [59.185.4.45]
 4     7 ms     6 ms     5 ms  static-mum-59.185.211.229.mtnl.net.in [59.185.211.229]
 5     7 ms     8 ms     7 ms  121.244.47.189
 6    25 ms    26 ms    25 ms  172.17.169.202
 7    76 ms    27 ms    26 ms  ix-4-2.tcore1.CXR-Chennai.as6453.net [180.87.36.9]
 8    83 ms    60 ms    60 ms  if-5-2.tcore1.SVW-Singapore.as6453.net [180.87.12.53]
 9    60 ms    60 ms    59 ms  180.87.12.154
10    64 ms    65 ms    64 ms  unknown.hwng.net [173.245.210.222]
11    65 ms    66 ms    66 ms  sgp-1.valve.net [103.28.54.1]

Trace complete.

 

[Jagat]

20db SNR is not very good. have your line checked.