All MTNL users, please run a ping test on these popular servers and post the result. Also, don't forget to mention what plan you are on. This is to test how MTNL performs in Asian gaming servers. Since most ISPs lag like turtle in US/UK servers, I didn't even consider including them in the testHere are the server list:203.116.28.29:19567 (Singapore)110.50.241.134:19573 (Japan)111.92.239.20:19567 (Hong Kong) 60.251.74.101:11020 (Taiwan)Regards,
-
Amazon Deals - ToS - Like us?
MTNL Broadband: Ping issues
- Thread starter bubuthemonkeyprince
- Start date
- Replies 68
- Views 23,166
MTNL Delhi TriB UL data-1Mbps Eco
Download: 2Mbps
Upload: 512 Kbps
Pinging 203.116.28.29 with 32 bytes of data:
Reply from 203.116.28.29: bytes=32 time=106ms TTL=54
Reply from 203.116.28.29: bytes=32 time=104ms TTL=54
Reply from 203.116.28.29: bytes=32 time=105ms TTL=54
Reply from 203.116.28.29: bytes=32 time=104ms TTL=54
Ping statistics for 203.116.28.29:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 106ms, Average = 104ms
Pinging 110.50.241.134. [110.50.241.134] with 32 bytes of data:
Reply from 110.50.241.134: bytes=32 time=268ms TTL=108
Reply from 110.50.241.134: bytes=32 time=269ms TTL=108
Reply from 110.50.241.134: bytes=32 time=269ms TTL=108
Reply from 110.50.241.134: bytes=32 time=268ms TTL=108
Ping statistics for 110.50.241.134:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 268ms, Maximum = 269ms, Average = 268ms
Pinging 111.92.239.20 with 32 bytes of data:
Reply from 111.92.239.20: bytes=32 time=121ms TTL=113
Reply from 111.92.239.20: bytes=32 time=121ms TTL=113
Reply from 111.92.239.20: bytes=32 time=121ms TTL=113
Reply from 111.92.239.20: bytes=32 time=121ms TTL=113
Ping statistics for 111.92.239.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 121ms, Maximum = 121ms, Average = 121ms
Pinging 60.251.74.101 with 32 bytes of data:
Reply from 60.251.74.101: bytes=32 time=142ms TTL=115
Reply from 60.251.74.101: bytes=32 time=146ms TTL=115
Reply from 60.251.74.101: bytes=32 time=145ms TTL=115
Reply from 60.251.74.101: bytes=32 time=145ms TTL=115
Ping statistics for 60.251.74.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 142ms, Maximum = 146ms, Average = 144ms
Download: 2Mbps
Upload: 512 Kbps
Pinging 203.116.28.29 with 32 bytes of data:
Reply from 203.116.28.29: bytes=32 time=106ms TTL=54
Reply from 203.116.28.29: bytes=32 time=104ms TTL=54
Reply from 203.116.28.29: bytes=32 time=105ms TTL=54
Reply from 203.116.28.29: bytes=32 time=104ms TTL=54
Ping statistics for 203.116.28.29:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 106ms, Average = 104ms
Pinging 110.50.241.134. [110.50.241.134] with 32 bytes of data:
Reply from 110.50.241.134: bytes=32 time=268ms TTL=108
Reply from 110.50.241.134: bytes=32 time=269ms TTL=108
Reply from 110.50.241.134: bytes=32 time=269ms TTL=108
Reply from 110.50.241.134: bytes=32 time=268ms TTL=108
Ping statistics for 110.50.241.134:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 268ms, Maximum = 269ms, Average = 268ms
Pinging 111.92.239.20 with 32 bytes of data:
Reply from 111.92.239.20: bytes=32 time=121ms TTL=113
Reply from 111.92.239.20: bytes=32 time=121ms TTL=113
Reply from 111.92.239.20: bytes=32 time=121ms TTL=113
Reply from 111.92.239.20: bytes=32 time=121ms TTL=113
Ping statistics for 111.92.239.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 121ms, Maximum = 121ms, Average = 121ms
Pinging 60.251.74.101 with 32 bytes of data:
Reply from 60.251.74.101: bytes=32 time=142ms TTL=115
Reply from 60.251.74.101: bytes=32 time=146ms TTL=115
Reply from 60.251.74.101: bytes=32 time=145ms TTL=115
Reply from 60.251.74.101: bytes=32 time=145ms TTL=115
Ping statistics for 60.251.74.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 142ms, Maximum = 146ms, Average = 144ms
mtnlpacked
Back to NoS on Mtnl
C:\>ping 203.116.28.29Pinging 203.116.28.29 with 32 bytes of data:Reply from 203.116.28.29: bytes=32 time=75ms TTL=51Reply from 203.116.28.29: bytes=32 time=76ms TTL=51Reply from 203.116.28.29: bytes=32 time=75ms TTL=51Reply from 203.116.28.29: bytes=32 time=75ms TTL=51Ping statistics for 203.116.28.29: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 75ms, Maximum = 76ms, Average = 75msC:>ping 110.50.241.134Pinging 110.50.241.134 with 32 bytes of data:Reply from 110.50.241.134: bytes=32 time=157ms TTL=108Reply from 110.50.241.134: bytes=32 time=157ms TTL=108Reply from 110.50.241.134: bytes=32 time=157ms TTL=108Reply from 110.50.241.134: bytes=32 time=157ms TTL=108Ping statistics for 110.50.241.134: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 157ms, Maximum = 157ms, Average = 157msC:\>ping 111.92.239.20Pinging 111.92.239.20 with 32 bytes of data:Reply from 111.92.239.20: bytes=32 time=262ms TTL=110Reply from 111.92.239.20: bytes=32 time=266ms TTL=110Reply from 111.92.239.20: bytes=32 time=263ms TTL=110Reply from 111.92.239.20: bytes=32 time=263ms TTL=110Ping statistics for 111.92.239.20: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 262ms, Maximum = 266ms, Average = 263msC:\>ping 60.251.74.101Pinging 60.251.74.101 with 32 bytes of data:Reply from 60.251.74.101: bytes=32 time=253ms TTL=108Reply from 60.251.74.101: bytes=32 time=253ms TTL=108Reply from 60.251.74.101: bytes=32 time=253ms TTL=108Reply from 60.251.74.101: bytes=32 time=254ms TTL=108Ping statistics for 60.251.74.101: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 253ms, Maximum = 254ms, Average = 253ms
Since mid September i have been facing ping issue's with Mtnl broadband service.Primarily i used to get around 170-180ms to Europe(Netherlands).After that ping spiked to 200-220ms and now is 260-320ms which is a pain affected my gaming cod4.This is usual for MTNL though around the year the generally spike the ping it get back to normal anywhere between 2-6 months.This time around i got tired of waiting and having time in my hands,i went to the Darpan exchange(Andheri east)to sort the problem out.(Before this i have contacted the customer care service countless times who didn't understand what was ping.After going there i was directed to a Mister Sandip who was a engineer.He only understood that ping measured in ms and there is no problem with the net if the speed and the net was constant.He asked us to change the DNS to a given number:ishock
ping to a server and DNS are not related).I tried hard to explain to him that the problem was not at my end but it was routing problem to which he advised me to go to Prabhadevi exchange,and to call a Noc there.The call was answered by jaiyant/vaidyant some one who primarily told me that they werent related to ping and the problem was at the local exchange.After that i went to the Vile Parle exchange(i was with a friend who has connection from Parle exchange).The engineer there actually understood our problem to my amazement told us that he himself had the ping problem and when he called to inquire regarding it he ended up no-where.From there i called guy at the NOC prabhadevi again who told us that mtnl are not responsible for the way the packet the transferred.I told him that packet from my router after jumping 4 times in mumbai was transferred to New Delhi bharti (Airtel)and then to europe.Why does MTNL route me to Delhi to airtel when there is a working gateway in Mumbai.I will keep this updated.I will be visiting the Prabhadevi office shortly.If anyone else has any problem post away that way i can inquire there regarding it.
ping to a server and DNS are not related).I tried hard to explain to him that the problem was not at my end but it was routing problem to which he advised me to go to Prabhadevi exchange,and to call a Noc there.The call was answered by jaiyant/vaidyant some one who primarily told me that they werent related to ping and the problem was at the local exchange.After that i went to the Vile Parle exchange(i was with a friend who has connection from Parle exchange).The engineer there actually understood our problem to my amazement told us that he himself had the ping problem and when he called to inquire regarding it he ended up no-where.From there i called guy at the NOC prabhadevi again who told us that mtnl are not responsible for the way the packet the transferred.I told him that packet from my router after jumping 4 times in mumbai was transferred to New Delhi bharti (Airtel)and then to europe.Why does MTNL route me to Delhi to airtel when there is a working gateway in Mumbai.I will keep this updated.I will be visiting the Prabhadevi office shortly.If anyone else has any problem post away that way i can inquire there regarding it.