Thread: MTNL Pings just went up quite a bit??

I remember last year when i took this mtnl connnection 256k unlimited i had 30-50 ms to vstreet in mumbai

and now check this out
E:\Documents and Settings\Raja>ping 202.63.160.44

Pinging 202.63.160.44 with 32 bytes of data:

Reply from 202.63.160.44: bytes=32 time=266ms TTL=120
Reply from 202.63.160.44: bytes=32 time=267ms TTL=120
Reply from 202.63.160.44: bytes=32 time=269ms TTL=120
Reply from 202.63.160.44: bytes=32 time=273ms TTL=120

Ping statistics for 202.63.160.44:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 266ms, Maximum = 273ms, Average = 268ms

Taken at 12-1 pm

This is obviously too high!!
These days I am getting 65-80 ms on the lower side and 150-350 ms on the upper side to mumbai.

Even within delhi I used to ping 30-50 ms just a few days back
These days the pings are spiking to 80-100-300ms just within delhi!!

I did a traceroute.
Tracing route to 202-63-160-44.static.exatt.net [202.63.160.44]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 13 ms 11 ms 11 ms triband-del-59.178.191.254.bol.net.in [59.178.19
1.254]
3 11 ms 12 ms 12 ms triband-del-59.179.0.61.bol.net.in [59.179.0.61]

4 271 ms 274 ms 271 ms 121.241.106.26.static-delhi.vsnl.net.in [121.241
.106.26]

Problem seems to begin very early.
And its this 4th hop which contributes the max to my ping.

Any1 having mtnl broadband and good pings , i.e sub 50ms???
What kind of pings is everyone getting
a) within delhi
and
b) to mumbai/vstreet servers

When posting please post
a) your location
b) your plan
c) Ping the following server and leave a ping/traceroute copy/paste in this thread
202.63.160.44

hey im also having the same problem

im from delhi and have mtnl 256kbps UNLMTD
my ping is around 160-200 during offpeaks i.e morning and nights and 250-500 during peak times on the vstreets servers..my friends wid same plan from delhi get around 70!

I was kinda upset today.
Posted here and also mailed mtnl.
Waise sarkari offices mein sab kuch dheere hota hai
lekin kamaal ho gaya bhai log!!

My pings are back to the way they used to be last year!!
WOW!!! 35-50 ms!!
If it stays this way then DAMN!!

One in a million chance that mtnl people actually listened to me.
I had sent the traceroute to them and the route was messed up. pings were spiking at some vsnl point..
Now check the pings and traceroute

E:\Documents and Settings\Raja>ping 202.63.160.44

Pinging 202.63.160.44 with 32 bytes of data:

Reply from 202.63.160.44: bytes=32 time=36ms TTL=113
Reply from 202.63.160.44: bytes=32 time=38ms TTL=113
Reply from 202.63.160.44: bytes=32 time=36ms TTL=113
Reply from 202.63.160.44: bytes=32 time=37ms TTL=113

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



Tracing route to 202-63-160-44.static.exatt.net [202.63.160.44]
over a maximum of 30 hops:

1 3 ms 1 ms 2 ms 192.168.1.1
2 13 ms 11 ms 13 ms triband-del-59.178.191.254.bol.net.in [59.178.19
1.254]
3 12 ms 12 ms 12 ms triband-del-59.179.0.62.bol.net.in [59.179.0.62]

4 34 ms 35 ms 35 ms 125.21.187.73
5 34 ms 35 ms 36 ms 203.101.100.70
6 34 ms 36 ms 34 ms 125.18.13.138
7 36 ms 36 ms 37 ms DSL-mum-Static-ILP-078.120.170.122.airtelbroadba
nd.in [122.170.120.78]
8 35 ms 37 ms * 202-63-189-10.static.exatt.net [202.63.189.10]
9 36 ms 37 ms 36 ms 202-63-160-44.static.exatt.net [202.63.160.44]

Just for comparison this is the old traceroute
Tracing route to 202-63-160-44.static.exatt.net [202.63.160.44]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 13 ms 11 ms 11 ms triband-del-59.178.191.254.bol.net.in [59.178.19
1.254]
3 11 ms 12 ms 12 ms triband-del-59.179.0.61.bol.net.in [59.179.0.61]

4 271 ms 274 ms 271 ms 121.241.106.26.static-delhi.vsnl.net.in [121.241
.106.26]
5 288 ms 283 ms 286 ms 59.163.55.149.static.vsnl.net.in [59.163.55.149]

6 278 ms 279 ms 274 ms 59.163.55.149.static.vsnl.net.in [59.163.55.149]

7 298 ms 298 ms 293 ms 59.163.55.209.static.vsnl.net.in [59.163.55.209]

8 294 ms 284 ms 286 ms 59.163.16.229.static.vsnl.net.in [59.163.16.229]

9 286 ms 295 ms 298 ms 125.21.167.98
10 305 ms 307 ms 303 ms 203.101.100.86
11 305 ms 313 ms 304 ms 125.18.13.138
12 1667 ms 294 ms 283 ms DSL-mum-Static-ILP-078.120.170.122.airtelbroadba
nd.in [122.170.120.78]
13 273 ms 290 ms 278 ms 202-63-189-10.static.exatt.net [202.63.189.10]
14 282 ms 285 ms 288 ms 202-63-160-44.static.exatt.net [202.63.160.44]

Trace complete.

I am being routed thru airtel now
and not vsnl.
Fantastic is all i can say.

I guess I should enjoy the low pings while they last

Tracing route to ns2.mtnl.net.in [203.94.243.70]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 24 ms 27 ms 27 ms triband-del-59.180.225.134.bol.net.in [59.180.22
5.134]
4 24 ms 27 ms 85 ms triband-del-59.180.225.133.bol.net.in [59.180.22
5.133]
5 25 ms 27 ms 26 ms 202.159.212.161
6 24 ms 26 ms 27 ms ns2.mtnl.net.in [203.94.243.70]

Trace complete.

In my case, its timing out at 2nd place...and moreover my download speeds have dropped. Earlier it hovered around 200KBps and now its not even touching 130KBps...!