Screwed up routes in BSNL

  • Thread starter Thread starter elepton
  • Start date Start date
  • Replies Replies 43
  • Views Views 8,032
here u go cooper


icrosoft Windows [Version 6.1.7600]
opyright (c) 2009 Microsoft Corporation. All rights reserved.

:\Users\HOME>tracert server.ip.att.net

racing route to server.ip.att.net [67.215.65.132]
ver a maximum of 30 hops:

1 9 ms 1 ms 1 ms 192.168.1.1
2 25 ms 24 ms 25 ms @@@@@@@@@
3 25 ms 24 ms 24 ms 218.248.160.70
4 25 ms 25 ms 23 ms 218.248.255.42
5 32 ms 31 ms 32 ms 59.163.201.153.static.chennai.vsnl.net.in [59.16
.201.153]
6 181 ms 181 ms 213 ms ix-4-2.tcore2.CXR-Chennai.as6453.net [180.87.37.
]
7 212 ms 212 ms 212 ms if-5-2.tcore2.SVW-Singapore.as6453.net [180.87.1
.69]
8 217 ms 212 ms 212 ms Vlan1807.icore1.SVQ-Singapore.as6453.net [120.29
215.29]
9 277 ms 277 ms 278 ms 203.208.186.101
10 276 ms 275 ms 276 ms so-7-0-0-0.sngtp-ar6.ix.singtel.com [203.208.152
34]
11 282 ms 282 ms 281 ms 203.208.190.166
12 273 ms 273 ms 274 ms hit-nxdomain.opendns.com [67.215.65.132]

race complete.

----------

i m in touch with one of the NOC in bangalore
he keeps asking traceroute through email when there is a problem.....i see no difference in connection when he ask for it. .
He might have done a work later.

i don keep checking all this all day..
I do it when i have nothing to do
 
here u go cooper

I'm sure you're trying to be funny, but it's not really working. While I have a sense of humour, nobody likes to be insulted. I'm trying to help people out here, and you're not really making this a place I'll want to continue doing that.

1 9 ms 1 ms 1 ms 192.168.1.1
2 25 ms 24 ms 25 ms @@@@@@@@@
3 25 ms 24 ms 24 ms 218.248.160.70
4 25 ms 25 ms 23 ms 218.248.255.42
5 32 ms 31 ms 32 ms 59.163.201.153.static.chennai.vsnl.net.in [59.16
.201.153]
6 181 ms 181 ms 213 ms ix-4-2.tcore2.CXR-Chennai.as6453.net [180.87.37.
]
7 212 ms 212 ms 212 ms if-5-2.tcore2.SVW-Singapore.as6453.net [180.87.1
.69]
8 217 ms 212 ms 212 ms Vlan1807.icore1.SVQ-Singapore.as6453.net [120.29
215.29]
9 277 ms 277 ms 278 ms 203.208.186.101
10 276 ms 275 ms 276 ms so-7-0-0-0.sngtp-ar6.ix.singtel.com [203.208.152
34]
11 282 ms 282 ms 281 ms 203.208.190.166
12 273 ms 273 ms 274 ms hit-nxdomain.opendns.com [67.215.65.132]


That's not right either - server.ip.att.net doesn't exist, it has to be "route-server.ip.att.net" or to make it easier, the IP address should be 12.0.1.28

i m in touch with one of the NOC in bangalore
he keeps asking traceroute through email when there is a problem.....i see no difference in connection when he ask for it. .
He might have done a work later.


Traceroutes are fine for diagnosing, but now not only has the problem seemingly been identified, the solution has been identified as well. Sadly, it's not possible to just magic up some more bandwidth or new routers/servers/switches, there will be a bureaucracy, and unfortunately, I doubt the NOC guys have the authority to purchase anything.
 
Caught up with some work. Will post the tracerts in a while. Google (goes to Chennai) around 25-30ms.

Chin, your ping to the gateway takes 24ms. Isnt that too much ?

- - - Updated - - -

Code: 
  1     1 ms     1 ms     1 ms   DD-WRT [10.0.0.1]  2     2 ms     2 ms     2 ms   117.198.128.1  3     6 ms     5 ms     4  ms  218.248.169.42  4    21 ms   21 ms    22 ms  115.114.59.169.static-Mumbai.vsnl.net.in [115.114.59.169]  5    24 ms   22 ms    23 ms  115.113.165.98.static-mumbai.vsnl.net.in [115.113.165.98]  6    28 ms   27 ms    27 ms  72.14.232.202  7    28 ms   28 ms    26 ms  72.14.232.93  8    26 ms   29 ms    28 ms  209.85.240.147  9    28 ms   27 ms    29 ms  maa03s17-in-f16.1e100.net [74.125.236.208]Trace complete.
Code: 
Tracing route to rcom.co.in [220.226.182.128]over a maximum of 30 hops:  1     1 ms    1 ms    1 ms  DD-WRT [10.0.0.1]  2     2 ms    3 ms    3 ms  117.198.128.1  3     4 ms     5 ms     3 ms  218.248.169.46  4     4 ms     4 ms     6 ms  115.248.24.238  5    13 ms    17 ms    15 ms  115.255.239.45  6    16 ms    15 ms    15 ms  202.138.117.210  7    19 ms    19 ms    18 ms  202.138.113.246  8    13 ms    18 ms    16 ms  202.138.113.113  9    18 ms    17 ms    17 ms  202.138.112.241 10    19 ms    19 ms    19 ms  220.226.192.58 11     *        *        *     Request timed out.
EDIT

If ip2location is to be believed, 115.248.24.238, is in Bombay, and I'm getting 6ms to it ?

Code: 
Tracing route to a118-215.225-145.deploy.akamaitechnologies.com [118.215.225.145]over a maximum of 30 hops:  1     1 ms     1 ms     1 ms    DD-WRT [10.0.0.1]  2     3 ms     2 ms     3 ms    117.198.128.1  3     4 ms      4 ms    3 ms    218.248.169.42  4    22 ms    21 ms    23 ms  115.114.59.169.static-Mumbai.vsnl.net.in [115.114.59.169]  5    25 ms    23 ms    24 ms  121.240.1.234  6    23 ms    22 ms    24 ms  59.163.52.29.static.vsnl.net.in [59.163.52.29]  7    88 ms    88 ms    88 ms  ge-4-0-0-0.sngc3-cr1.ix.singtel.com [203.208.172.153]  8    89 ms    89 ms    91 ms  ge-3-0-0-0.sngtp-dr2.ix.singtel.com [203.208.151.157]  9    90 ms    90 ms    90 ms  a118-215.225-145.deploy.akamaitechnologies.com [118.215.225.145]Trace complete.
 
Caught up with some work. Will post the tracerts in a while. Google (goes to Chennai) around 25-30ms.

Chin, your ping to the gateway takes 24ms. Isnt that too much ?

- - - Updated - - -

Code: 
  1     1 ms     1 ms     1 ms   DD-WRT [10.0.0.1]  2     2 ms     2 ms     2 ms   117.198.128.1  3     6 ms     5 ms     4  ms  218.248.169.42  4    21 ms   21 ms    22 ms  115.114.59.169.static-Mumbai.vsnl.net.in [115.114.59.169]  5    24 ms   22 ms    23 ms  115.113.165.98.static-mumbai.vsnl.net.in [115.113.165.98]  6    28 ms   27 ms    27 ms  72.14.232.202  7    28 ms   28 ms    26 ms  72.14.232.93  8    26 ms   29 ms    28 ms  209.85.240.147  9    28 ms   27 ms    29 ms  maa03s17-in-f16.1e100.net [74.125.236.208]Trace complete.
Code: 
Tracing route to rcom.co.in [220.226.182.128]over a maximum of 30 hops:  1     1 ms    1 ms    1 ms  DD-WRT [10.0.0.1]  2     2 ms    3 ms    3 ms  117.198.128.1  3     4 ms     5 ms     3 ms  218.248.169.46  4     4 ms     4 ms     6 ms  115.248.24.238  5    13 ms    17 ms    15 ms  115.255.239.45  6    16 ms    15 ms    15 ms  202.138.117.210  7    19 ms    19 ms    18 ms  202.138.113.246  8    13 ms    18 ms    16 ms  202.138.113.113  9    18 ms    17 ms    17 ms  202.138.112.241 10    19 ms    19 ms    19 ms  220.226.192.58 11     *        *        *     Request timed out.
EDIT

If ip2location is to be believed, 115.248.24.238, is in Bombay, and I'm getting 6ms to it ?

Code: 
Tracing route to a118-215.225-145.deploy.akamaitechnologies.com [118.215.225.145]over a maximum of 30 hops:  1     1 ms     1 ms     1 ms    DD-WRT [10.0.0.1]  2     3 ms     2 ms     3 ms    117.198.128.1  3     4 ms      4 ms    3 ms    218.248.169.42  4    22 ms    21 ms    23 ms  115.114.59.169.static-Mumbai.vsnl.net.in [115.114.59.169]  5    25 ms    23 ms    24 ms  121.240.1.234  6    23 ms    22 ms    24 ms  59.163.52.29.static.vsnl.net.in [59.163.52.29]  7    88 ms    88 ms    88 ms  ge-4-0-0-0.sngc3-cr1.ix.singtel.com [203.208.172.153]  8    89 ms    89 ms    91 ms  ge-3-0-0-0.sngtp-dr2.ix.singtel.com [203.208.151.157]  9    90 ms    90 ms    90 ms  a118-215.225-145.deploy.akamaitechnologies.com [118.215.225.145]Trace complete.

there s few cable faults.
bbmp screwed it few months ago.
may be because of that.

But best results i have seen in the morning. .
don know about the gateway but final ping to google will be from 25 ~30ms

- - - Updated - - -

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\HOME>traert www.google.com
'traert' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\HOME>tracert www.google.com

Tracing route to www.l.google.com [74.125.236.82]
over a maximum of 30 hops:

1 6 ms 1 ms 1 ms 192.168.1.1
2 25 ms 23 ms 23 ms
3 44 ms 23 ms 23 ms 218.248.160.74
4 25 ms 24 ms 23 ms 218.248.255.42
5 42 ms 42 ms 41 ms 218.248.246.130
6 49 ms 48 ms 48 ms 115.113.128.17.static-mumbai.vsnl.net.in [115.11
3.128.17]
7 78 ms 49 ms 50 ms 115.113.165.98.static-mumbai.vsnl.net.in [115.11
3.165.98]
8 51 ms 49 ms 51 ms 72.14.232.202
9 51 ms 49 ms 49 ms 72.14.232.93
10 49 ms 49 ms 51 ms 209.85.249.235
11 49 ms 50 ms 50 ms maa03s05-in-f18.1e100.net [74.125.236.82]

Trace complete.

C:\Users\HOME>tracert rcom.co.in

Tracing route to rcom.co.in [220.226.182.128]
over a maximum of 30 hops:

1 9 ms 1 ms 1 ms 192.168.1.1
2 23 ms 24 ms 37 ms
3 23 ms 25 ms 24 ms 218.248.160.70
4 22 ms 24 ms 24 ms 218.248.255.2
5 58 ms 58 ms 58 ms 115.254.59.42
6 53 ms 52 ms 53 ms 115.255.239.45
7 59 ms 59 ms 59 ms 202.138.117.210
8 81 ms 84 ms 65 ms 202.138.113.246
9 50 ms 51 ms 49 ms 202.138.113.113
10 50 ms 49 ms 51 ms 202.138.112.241
11 51 ms 50 ms 48 ms 220.226.192.58
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * ^C
C:\Users\HOME>

C:\Users\HOME>

C:\Users\HOME>

- - - Updated - - -

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\HOME>tracert 12.0.1.28

Tracing route to route-server.cbbtier3.att.net [12.0.1.28]
over a maximum of 30 hops:

1 9 ms 1 ms 1 ms 192.168.1.1
2 23 ms 26 ms 23 ms
3 25 ms 23 ms 24 ms 218.248.160.74
4 26 ms 23 ms 23 ms 218.248.255.42
5 41 ms 41 ms 42 ms 218.248.246.130
6 237 ms 234 ms 233 ms 12.89.56.25
7 237 ms 237 ms 236 ms cr84.n54ny.ip.att.net [12.122.105.126]
8 238 ms 234 ms 239 ms cr2.n54ny.ip.att.net [12.122.115.93]
9 233 ms 233 ms 233 ms n54ny401me3.ip.att.net [12.123.2.129]
10 238 ms 239 ms 239 ms whitedwarf-t640.cbbtier3.att.net [12.89.5.14]
11 236 ms 235 ms 236 ms route-server.cbbtier3.att.net [12.0.1.28]

Trace complete
 
If ip2location is to be believed, 115.248.24.238, is in Bombay, and I'm getting 6ms to it ?


Probably *registered* in Bombay, as it's Tata, but unlikely you'd get 6ms ping at a 1,200km distance. Granted, not entirely out of the question since I've seen 31ms to London from Tbilisi (about 3500km) but still not likely.

Code: 
Tracing route to a118-215.225-145.deploy.akamaitechnologies.com [118.215.225.145]over a maximum of 30 hops:  1     1 ms     1 ms     1 ms    DD-WRT [10.0.0.1]  2     3 ms     2 ms     3 ms    117.198.128.1  3     4 ms      4 ms    3 ms    218.248.169.42  4    22 ms    21 ms    23 ms  115.114.59.169.static-Mumbai.vsnl.net.in [115.114.59.169]  5    25 ms    23 ms    24 ms  121.240.1.234  6    23 ms    22 ms    24 ms  59.163.52.29.static.vsnl.net.in [59.163.52.29]  7    88 ms    88 ms    88 ms  ge-4-0-0-0.sngc3-cr1.ix.singtel.com [203.208.172.153]  8    89 ms    89 ms    91 ms  ge-3-0-0-0.sngtp-dr2.ix.singtel.com [203.208.151.157]  9    90 ms    90 ms    90 ms  a118-215.225-145.deploy.akamaitechnologies.com [118.215.225.145]Trace complete.

Is this att.com? Sadly, the Akamai factor doesn't make it useful - can you trace to the same IP that chin has as below?

there s few cable faults.
bbmp screwed it few months ago.
may be because of that.

According to industry sources, there are about 10,000 cable cuts a year in India - I'm not entirely sure it would be relevant?

C:\Users\HOME>tracert rcom.co.in

Tracing route to rcom.co.in [220.226.182.128]
over a maximum of 30 hops:

1 9 ms 1 ms 1 ms 192.168.1.1
2 23 ms 24 ms 37 ms
3 23 ms 25 ms 24 ms 218.248.160.70
4 22 ms 24 ms 24 ms 218.248.255.2
5 58 ms 58 ms 58 ms 115.254.59.42
6 53 ms 52 ms 53 ms 115.255.239.45
7 59 ms 59 ms 59 ms 202.138.117.210
8 81 ms 84 ms 65 ms 202.138.113.246
9 50 ms 51 ms 49 ms 202.138.113.113
10 50 ms 49 ms 51 ms 202.138.112.241
11 51 ms 50 ms 48 ms 220.226.192.58
12 * * * Request timed out.


C:\Users\HOME>tracert 12.0.1.28

Tracing route to route-server.cbbtier3.att.net [12.0.1.28]
over a maximum of 30 hops:

1 9 ms 1 ms 1 ms 192.168.1.1
2 23 ms 26 ms 23 ms
3 25 ms 23 ms 24 ms 218.248.160.74
4 26 ms 23 ms 23 ms 218.248.255.42
5 41 ms 41 ms 42 ms 218.248.246.130
6 237 ms 234 ms 233 ms 12.89.56.25
7 237 ms 237 ms 236 ms cr84.n54ny.ip.att.net [12.122.105.126]
8 238 ms 234 ms 239 ms cr2.n54ny.ip.att.net [12.122.115.93]
9 233 ms 233 ms 233 ms n54ny401me3.ip.att.net [12.123.2.129]
10 238 ms 239 ms 239 ms whitedwarf-t640.cbbtier3.att.net [12.89.5.14]
11 236 ms 235 ms 236 ms route-server.cbbtier3.att.net [12.0.1.28]


These are pretty good results. It seems that, unlike the links to Tata, the peering or wholesales links with Reliance and AT&T respectively are not congested, so I guess it's the luck of the draw as to what kind of results you'll get depending on which websites you visit/where you download from etc. In my case, I see worse pings when my traffic goes through Bharti but very good pings when my traffic goes through Tata and so on. YMMV.
 
Is VSNL a govt org??I know now TATA is holding it. . . why was it given to TATA??
 

For BSNL, your traces to Google are great. Can we see something from x720 or elepton or probuddha or someone in Kolkata or something?

I'll try to post a tracert when routes get congested later on today. Ignore the 2 morons in this thread; this is a very serious problem in Kolkata - and yes it's probably on BSNL's end. Diablo 3 came out last week and the latency/packet loss on BSNL is so horrendous, it's basically unplayable. I've been using Airtel for the most part and both latencies, jitter and connection quality (no packet loss) has been tons better. Airtel rarely has congestion issues at least although prices are fairly high and there's nasty FUP.

Again, the problem in kolkata/easter/NE india is other than Airtel and BSNL there aren't any alternatives.

I wonder if there's a way to escalate this issue, but there seems to be any kind of high level tech support anywhere in India. Perhaps so few people actually use internet in a way where connection quality is required; BSNL/Airtel doesn't care.

- - - Updated - - -

ok.

pings to www.google.com -

Code: 
Reply from 74.125.236.178: bytes=32 time=44ms TTL=56Reply from 74.125.236.178: bytes=32 time=54ms TTL=56Reply from 74.125.236.178: bytes=32 time=46ms TTL=56Reply from 74.125.236.178: bytes=32 time=46ms TTL=56Reply from 74.125.236.178: bytes=32 time=46ms TTL=56Reply from 74.125.236.178: bytes=32 time=46ms TTL=56Reply from 74.125.236.178: bytes=32 time=46ms TTL=56Reply from 74.125.236.178: bytes=32 time=46ms TTL=56Reply from 74.125.236.178: bytes=32 time=48ms TTL=56Reply from 74.125.236.178: bytes=32 time=47ms TTL=56Reply from 74.125.236.178: bytes=32 time=47ms TTL=56Reply from 74.125.236.178: bytes=32 time=45ms TTL=56Reply from 74.125.236.178: bytes=32 time=55ms TTL=56Reply from 74.125.236.178: bytes=32 time=48ms TTL=56Reply from 74.125.236.178: bytes=32 time=45ms TTL=56Request timed out.Request timed out.Reply from 74.125.236.178: bytes=32 time=386ms TTL=48Reply from 74.125.236.178: bytes=32 time=386ms TTL=48Reply from 74.125.236.178: bytes=32 time=385ms TTL=48Reply from 74.125.236.178: bytes=32 time=386ms TTL=48Reply from 74.125.236.178: bytes=32 time=385ms TTL=48Request timed out.Reply from 74.125.236.178: bytes=32 time=321ms TTL=45Reply from 74.125.236.178: bytes=32 time=320ms TTL=45Reply from 74.125.236.178: bytes=32 time=316ms TTL=45Reply from 74.125.236.178: bytes=32 time=317ms TTL=45Reply from 74.125.236.178: bytes=32 time=317ms TTL=45Reply from 74.125.236.178: bytes=32 time=314ms TTL=45Reply from 74.125.236.178: bytes=32 time=317ms TTL=45Reply from 74.125.236.178: bytes=32 time=317ms TTL=45Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=348ms TTL=42Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=356ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=362ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=42Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=361ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=42Request timed out.Reply from 74.125.236.178: bytes=32 time=375ms TTL=42Reply from 74.125.236.178: bytes=32 time=375ms TTL=44Reply from 74.125.236.178: bytes=32 time=373ms TTL=42Reply from 74.125.236.178: bytes=32 time=375ms TTL=44Reply from 74.125.236.178: bytes=32 time=375ms TTL=44Reply from 74.125.236.178: bytes=32 time=374ms TTL=44Reply from 74.125.236.178: bytes=32 time=373ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=365ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=42Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Request timed out.Request timed out.Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Request timed out.Request timed out.Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=42Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Request timed out.Request timed out.Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=42Request timed out.Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=361ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=358ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=362ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=42Reply from 74.125.236.178: bytes=32 time=360ms TTL=42Reply from 74.125.236.178: bytes=32 time=402ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=42Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=42Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Reply from 74.125.236.178: bytes=32 time=360ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Request timed out.Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44Reply from 74.125.236.178: bytes=32 time=359ms TTL=44
Route statistics to the same server:

Code: 
|------------------------------------------------------------------------------------------||                                      WinMTR statistics                                   ||                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last ||------------------------------------------------|------|------|------|------|------|------||                             59.93.192.1 -    0 |  271 |  271 |    8 |   12 |  171 |    9 ||                         218.248.255.118 -    0 |  270 |  270 |   42 |   45 |   86 |   46 ||115.114.131.141.static-mumbai.vsnl.net.in -    0 |  271 |  271 |  261 |  264 |  409 |  264 ||115.113.165.98.static-mumbai.vsnl.net.in -   12 |  185 |  163 |  358 |  366 |  457 |  361 ||                           209.85.241.52 -   13 |  178 |  155 |  358 |  363 |  425 |  363 ||                           209.85.251.95 -   14 |  176 |  152 |  359 |  362 |  385 |  360 ||                          209.85.240.145 -   12 |  185 |  163 |  359 |  362 |  376 |  359 ||               maa03s16-in-f18.1e100.net -   16 |  164 |  138 |    0 |  360 |  459 |  358 ||________________________________________________|______|______|______|______|______|______|   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
graphical representation of what's going on in d3tr -


green = low latency (sub 100) orange and red is higher.
gaps in the graph are lost packets.
 
For BSNL, your traces to Google are great. Can we see something from x720 or elepton or probuddha or someone in Kolkata or something?

First of all, I really appreciate the help and insights you're providing us in this forum..much appreciated. And yes, as rsen mentioned, this is a very serious problem at least in this part of the country. I have lodged several complaints and have even escalated the matter to the national public grievance cell, things got normal for a while but now it's back.

So I'd request all who are facing the same problem to kindly lodge complaints at :: Grievance Redress Mechanism in Government :: Maybe the BSNL guys will take this matter seriously once they receive a large number of complaints.

Here are the traces you'd asked for

C:\>tracert rcom.co.in


Tracing route to rcom.co.in [220.226.182.128] over a maximum of 30 hops:


1 2 ms 2 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 42 ms 33 ms 117.194.64.1
4 12 ms 13 ms 9 ms 218.248.162.70
5 12 ms 11 ms 9 ms 218.248.255.10
6 62 ms 62 ms 63 ms 218.248.246.130
7 380 ms 377 ms 377 ms 115.254.106.154
8 382 ms 380 ms 387 ms 115.255.239.45
9 373 ms 374 ms 373 ms 202.138.117.210
10 366 ms 366 ms 365 ms 202.138.113.246
11 380 ms 379 ms 381 ms 202.138.113.113
12 374 ms 371 ms 374 ms 202.138.112.66
13 379 ms 382 ms 379 ms 220.226.192.58
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 ^C



C:\>tracert att.com


Tracing route to att.com [144.160.155.43] over a maximum of 30 hops:


1 2 ms 1 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 11 ms 9 ms 117.194.64.1
4 12 ms 9 ms 11 ms 218.248.162.70
5 12 ms 9 ms 11 ms 218.248.255.22
6 415 ms 349 ms 349 ms 59.163.207.81.static.chennai.vsnl.net.in [59.163.207.81]
7 368 ms 368 ms 369 ms ix-4-2.tcore1.CXR-Chennai.as6453.net [180.87.36.9]
8 349 ms 349 ms 397 ms if-5-2.tcore1.SVW-Singapore.as6453.net [180.87.12.53]
9 356 ms 358 ms 361 ms if-2-2.tcore2.SVW-Singapore.as6453.net [180.87.12.2]
10 354 ms 353 ms 353 ms if-7-2.tcore2.LVW-LosAngeles.as6453.net [180.87.15.26]
11 354 ms 359 ms 353 ms if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1]
12 421 ms 421 ms 421 ms 192.205.35.129
13 432 ms 429 ms 431 ms cr1.la2ca.ip.att.net [12.122.84.202]
14 435 ms 435 ms 431 ms cr1.sffca.ip.att.net [12.122.3.121]
15 432 ms 431 ms 431 ms 12.123.155.117
16 * 429 ms 431 ms 151.164.54.98
17 427 ms 429 ms 432 ms ded-p10-0.pltn13.sbcglobal.net [151.164.191.243]


18 429 ms 431 ms 431 ms 71.140.37.98
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.


Trace complete.


C:\>tracert cw.com


Tracing route to cw.com [195.59.115.40] over a maximum of 30 hops:


1 2 ms 2 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 11 ms 11 ms 117.194.64.1
4 10 ms 11 ms 13 ms 218.248.162.74
5 11 ms 9 ms 9 ms 218.248.255.10
6 54 ms 53 ms 51 ms 218.248.250.174
7 382 ms 382 ms 393 ms so-9-2-0-xcr1.nyk.cw.net [195.89.21.65]
8 382 ms 379 ms 393 ms xe-1-3-0-xcr1.bkl.cw.net [195.2.25.25]
9 386 ms 385 ms 385 ms vdc-gw.bkl.cw.net [195.59.8.22]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 ^C



C:\>tracert inteliquent.com


Tracing route to inteliquent.com [64.202.189.170] over a maximum of 30 hops:


1 2 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 11 ms 9 ms 117.194.64.1
4 10 ms 13 ms 11 ms 218.248.162.74
5 11 ms 11 ms 9 ms 218.248.255.22
6 250 ms 249 ms 249 ms 59.163.207.81.static.chennai.vsnl.net.in [59.163.207.81]
7 * * * Request timed out.
8 * * * Request timed out.
9 249 ms 248 ms 247 ms 59.163.25.46.static.vsnl.net.in [59.163.25.46]
10 250 ms 251 ms 249 ms if-0-1-9-0.tcore1.CXR-Chennai.as6453.net [180.87.36.53]
11 272 ms 245 ms 267 ms if-5-2.tcore1.SVW-Singapore.as6453.net [180.87.12.53]
12 264 ms 261 ms 275 ms if-6-2.tcore2.TV2-Tokyo.as6453.net [180.87.12.110]
13 265 ms 265 ms 277 ms if-2-2.tcore1.TV2-Tokyo.as6453.net [180.87.180.1]
14 261 ms 267 ms 263 ms if-9-2.tcore2.PDI-PaloAlto.as6453.net [180.87.180.17]
15 * * 261 ms Vlan3254.icore1.SQN-SanJose.as6453.net [66.198.144.6]
16 449 ms 439 ms 431 ms te2-5.ccr02.sjc03.atlas.cogentco.com [154.54.12.21]
17 268 ms 265 ms 263 ms te0-2-0-1.ccr22.lax01.atlas.cogentco.com [154.54.5.70]
18 384 ms 441 ms 447 ms te9-8.ccr02.lax05.atlas.cogentco.com [154.54.44.134]
19 356 ms 405 ms 263 ms te4-2.mag03.lax05.atlas.cogentco.com [154.54.80.38]
20 263 ms 267 ms 263 ms 38.104.84.86
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.


Trace complete.


Let me know if you'd need any further info

Thanks
 
All I can say is "whoa".

Rcom: Looks like the links to Reliance get just as saturated as the ones to VSNL.
ATT/Inteliquent: These links go through Tata, so that's the behaviour we're seeing elsewhere as well.
CW is roughly as I'd expect given the distances and all.

In short, it seems simply to be saturation at the gateways. I can ping 59.163.207.81 (Sixth hop for you) in 27 or 28ms, you are seeing 250+ and with 115.254.106.154 I can see that in 17 or 18ms whereas you can see it in 350+ only. BSNL needs to either upgrade it's core and/or edge routers, buy more bandwidth or maybe even both.
 
So I'd request all who are facing the same problem to kindly lodge complaints at :: Grievance Redress Mechanism in Government :: Maybe the BSNL guys will take this matter seriously once they receive a large number of complaints.



Department of telecommunication right ? What exactly should the complaint talk about ?
Typically anything about latency gets completely ignored by the call center or the online BSNL complaint thingy.
 
Department of telecommunication right ? What exactly should the complaint talk about ?
Typically anything about latency gets completely ignored by the call center or the online BSNL complaint thingy.

Yes, dept of telecom

My complaint was regarding extreme slow speeds and high latencies even to local Indian servers. I had also sent them snapshots taken from speedtest and also traceroutes to some popular websites stressing on the poor routing issue.

I'd also suggest you send written complaints to the Nodal Officer, the NWO of your circle and also to the Appellate authority (GM Broadband)

Let me know if you'd need any help
 
Got some time right now so here it goes. This is during non-peak time and pings to google chennai are ~60 ms.

Code: 
$ date; traceroute google.comTue May 29 01:31:37 IST 2012traceroute to google.com (74.125.236.197), 30 hops max, 60 byte packets 1  117.205.xxx.1 (117.205.xxx.1)  5.590 ms  7.013 ms  8.456 ms 2  218.248.175.246 (218.248.175.246)  13.889 ms  14.319 ms  15.542 ms 3  115.114.130.5.STATIC-Chennai.vsnl.net.in (115.114.130.5)  62.827 ms  64.616 ms  65.264 ms 4  121.240.1.46 (121.240.1.46)  65.764 ms  67.207 ms  68.664 ms 5  72.14.232.110 (72.14.232.110)  70.166 ms  72.080 ms  72.804 ms 6  209.85.240.147 (209.85.240.147)  73.771 ms  69.526 ms  70.550 ms 7  maa03s17-in-f5.1e100.net (74.125.236.197)  70.485 ms  66.511 ms  67.874 ms$ date; mtr --report --report-wide --mpls google.comTue May 29 01:33:32 IST 2012                                                Loss%   Snt   Last   Avg  Best  Wrst StDev  1.|-- 117.205.xxx.1                              0.0%    10    5.4   6.0   5.1   9.9   1.4  2.|-- 218.248.175.246                            0.0%    10    9.5  10.4   9.2  11.5   0.7  3.|-- 59.163.206.161.static.chennai.vsnl.net.in 10.0%    10   53.8  55.0  53.6  57.0   1.2  4.|-- 121.240.1.46                               0.0%    10   51.2  53.9  49.9  76.8   8.1  5.|-- 72.14.232.110                              0.0%    10   52.0  51.3  49.3  53.2   1.3  6.|-- 209.85.240.147                             0.0%    10   52.2  52.0  50.2  53.9   1.4  7.|-- maa03s17-in-f4.1e100.net                   0.0%    10   50.1  51.1  49.7  53.8   1.3$ date; traceroute rcom.co.inTue May 29 01:38:38 IST 2012traceroute to rcom.co.in (220.226.182.128), 30 hops max, 60 byte packets 1  117.205.xxx.1 (117.205.xxx.1)  5.557 ms  6.707 ms  8.407 ms 2  218.248.175.246 (218.248.175.246)  14.823 ms  14.804 ms  15.745 ms 3  218.248.246.130 (218.248.246.130)  63.056 ms  65.451 ms  66.692 ms 4  115.254.106.154 (115.254.106.154)  62.972 ms  64.313 ms  65.948 ms 5  115.255.239.45 (115.255.239.45)  69.318 ms  70.262 ms  71.953 ms 6  202.138.117.210 (202.138.117.210)  73.409 ms  69.516 ms * 7  202.138.113.246 (202.138.113.246)  68.528 ms  63.349 ms  64.562 ms 8  202.138.113.113 (202.138.113.113)  64.545 ms  53.587 ms  54.484 ms 9  202.138.112.66 (202.138.112.66)  55.444 ms  54.816 ms  54.461 ms10  220.226.192.58 (220.226.192.58)  73.578 ms  57.087 ms  58.255 ms11  * * *12  * * *13  * * *14  * * *15  * * *16  * * *17  * * *18  * * *19  * * *20  * * *21  * * *22  * * *23  * * *24  * * *25  * * *26  * * *27  * * *28  * * *29  * * *30  * * *$ date; mtr --report --report-wide --mpls rcom.co.inTue May 29 01:40:02 IST 2012                      Loss%   Snt   Last   Avg  Best  Wrst StDev  1.|-- 117.205.xxx.1    0.0%    10    5.2   6.1   5.1  11.6   2.0  2.|-- 218.248.175.246  0.0%    10    9.8  11.1   9.3  14.7   1.9  3.|-- 218.248.246.130  0.0%    10   57.1  59.4  54.9  73.0   6.2  4.|-- 115.254.106.154 10.0%    10   50.5  52.2  50.2  57.4   2.2  5.|-- 115.255.239.45  10.0%    10   52.4  53.6  52.3  54.9   0.9  6.|-- 202.138.117.210  0.0%    10   52.7  52.9  50.8  54.4   1.2  7.|-- 202.138.113.246  0.0%    10   51.3  53.2  51.3  55.1   1.5  8.|-- 202.138.113.113 10.0%    10   51.6  52.5  51.6  53.7   0.8  9.|-- 202.138.112.66   0.0%    10   52.5  52.6  50.7  55.4   1.6 10.|-- 220.226.192.58  20.0%    10   56.6  57.3  56.2  59.1   0.9 11.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0$ date; traceroute route-server.ip.att.netTue May 29 01:34:43 IST 2012traceroute to route-server.ip.att.net (12.0.1.28), 30 hops max, 60 byte packets 1  117.205.xxx.1 (117.205.xxx.1)  5.580 ms  6.597 ms  7.435 ms 2  218.248.175.246 (218.248.175.246)  15.616 ms  17.571 ms  17.557 ms 3  218.248.246.130 (218.248.246.130)  63.277 ms  63.960 ms  64.458 ms 4  12.89.56.25 (12.89.56.25)  304.453 ms  305.457 ms  306.595 ms 5  cr83.n54ny.ip.att.net (12.122.115.6)  309.544 ms  310.258 ms  310.842 ms 6  cr1.n54ny.ip.att.net (12.122.105.49)  316.638 ms  315.281 ms  314.646 ms 7  n54ny401me3.ip.att.net (12.123.2.5)  369.388 ms  360.561 ms  359.471 ms 8  whitedwarf-t640.cbbtier3.att.net (12.89.5.14)  314.597 ms  297.161 ms  297.276 ms 9  route-server.cbbtier3.att.net (12.0.1.28)  301.229 ms * *$ date; mtr --report --report-wide --mpls route-server.ip.att.netTue May 29 01:35:01 IST 2012                                       Loss%   Snt   Last   Avg  Best  Wrst StDev  1.|-- 117.205.xxx.1                     0.0%    10    5.0   5.4   5.0   5.8   0.3  2.|-- 218.248.175.246                   0.0%    10    9.3  10.7   9.3  13.1   1.3  3.|-- 218.248.246.130                   0.0%    10   55.6  55.6  54.3  56.6   0.9  4.|-- 12.89.56.25                       0.0%    10  294.3 294.3 292.3 295.7   1.1  5.|-- cr83.n54ny.ip.att.net             0.0%    10  294.5 295.2 293.6 297.5   1.3    |   +-- [MPLS: Lbl 16025 Exp 0 S 1 TTL 255]  6.|-- cr1.n54ny.ip.att.net              0.0%    10  300.8 301.8 298.6 303.5   1.5    |   +-- [MPLS: Lbl 0 Exp 1 S 0 TTL 255]    |   +-- [MPLS: Lbl 16535 Exp 1 S 1 TTL 255]  7.|-- n54ny401me3.ip.att.net            0.0%    10  298.4 305.3 297.1 367.3  21.8  8.|-- whitedwarf-t640.cbbtier3.att.net 20.0%    10  298.3 367.6 297.9 848.2 194.2  9.|-- route-server.cbbtier3.att.net    20.0%    10  300.5 300.3 299.0 302.0   1.1$ date; traceroute cw.com; date; mtr --report --report-wide --mpls cw.comTue May 29 01:41:53 IST 2012traceroute to cw.com (195.59.115.40), 30 hops max, 60 byte packets 1  117.205.xxx.1 (117.205.xxx.1)  5.624 ms  6.301 ms  9.563 ms 2  218.248.175.246 (218.248.175.246)  13.404 ms  13.838 ms  16.087 ms 3  so-9-2-0-xcr1.nyk.cw.net (195.89.21.65)  315.430 ms  316.885 ms  317.461 ms 4  xe-1-3-0-xcr1.bkl.cw.net (195.2.25.25)  401.593 ms  402.273 ms xe-0-1-0-xcr1.lnd.cw.net (195.2.25.21)  409.255 ms 5  vdc-gw.bkl.cw.net (195.59.8.22)  417.795 ms *  418.832 ms 6  * * * 7  * * * 8  * * * 9  * * *10  * * *11  * * *12  * * *13  * * *14  * * *15  * * *16  * * *17  * * *18  * * *19  * * *20  * * *21  * * *22  * * *23  * * *24  * * *25  * * *26  * * *27  * * *28  * * *29  * * *30  * * *Tue May 29 01:42:18 IST 2012                               Loss%   Snt   Last   Avg  Best  Wrst StDev  1.|-- 117.205.xxx.1             0.0%    10    5.4   5.4   5.1   5.6   0.2  2.|-- 218.248.175.246           0.0%    10    9.9  17.2   8.6  73.8  20.0  3.|-- so-9-2-0-xcr1.nyk.cw.net  0.0%    10  312.7 308.8 307.2 312.7   1.6  4.|-- xe-0-1-0-xcr1.lnd.cw.net  0.0%    10  395.1 403.8 393.8 441.5  19.2  5.|-- vdc-gw.bkl.cw.net         0.0%    10  408.2 405.8 399.9 415.1   5.4  6.|-- ???                      100.0    10    0.0   0.0   0.0   0.0   0.0$ date; traceroute intelliquent.com; date; mtr --report --report-wide --mpls intelliquent.comTue May 29 01:49:39 IST 2012traceroute to intelliquent.com (64.202.189.170), 30 hops max, 60 byte packets 1  117.205.xxx.1 (117.205.xxx.1)  5.355 ms  6.510 ms  7.735 ms 2  218.248.175.246 (218.248.175.246)  13.627 ms  15.073 ms  16.568 ms 3  59.163.206.157.static.chennai.vsnl.net.in (59.163.206.157)  60.868 ms  62.069 ms  63.540 ms 4  172.31.35.198 (172.31.35.198)  65.005 ms  66.953 ms  67.661 ms 5  * * * 6  59.163.25.46.static.vsnl.net.in (59.163.25.46)  68.601 ms  64.679 ms  65.378 ms 7  if-0-1-9-0.tcore1.CXR-Chennai.as6453.net (180.87.36.53)  103.330 ms  96.790 ms  95.977 ms 8  if-5-2.tcore1.SVW-Singapore.as6453.net (180.87.12.53)  271.342 ms  261.084 ms  261.285 ms 9  if-6-2.tcore2.TV2-Tokyo.as6453.net (180.87.12.110)  280.769 ms  280.574 ms  272.640 ms10  if-2-2.tcore1.TV2-Tokyo.as6453.net (180.87.180.1)  279.557 ms  278.803 ms  277.129 ms11  if-9-2.tcore2.PDI-PaloAlto.as6453.net (180.87.180.17)  267.216 ms  259.513 ms  259.756 ms12  Vlan3254.icore1.SQN-SanJose.as6453.net (66.198.144.6)  282.593 ms  302.624 ms  289.130 ms13  te2-5.ccr02.sjc03.atlas.cogentco.com (154.54.12.21)  274.115 ms  274.388 ms  258.041 ms14  te0-2-0-1.mpd22.lax01.atlas.cogentco.com (154.54.5.182)  270.373 ms  287.668 ms te0-2-0-1.ccr22.lax01.atlas.cogentco.com (154.54.5.70)  269.393 ms15  te7-8.ccr02.lax05.atlas.cogentco.com (154.54.30.198)  272.213 ms te3-4.ccr02.lax05.atlas.cogentco.com (154.54.3.10)  272.190 ms te7-8.ccr02.lax05.atlas.cogentco.com (154.54.30.198)  269.723 ms16  te3-2.mag03.lax05.atlas.cogentco.com (154.54.80.34)  275.372 ms te4-2.mag03.lax05.atlas.cogentco.com (154.54.80.38)  272.631 ms te3-2.mag03.lax05.atlas.cogentco.com (154.54.80.34)  272.623 ms17  38.104.84.94 (38.104.84.94)  280.018 ms 38.104.84.82 (38.104.84.82)  283.734 ms 38.104.84.90 (38.104.84.90)  270.462 ms18  * * *19  * * *20  * * *21  * * *22  * * *23  * * *24  * * *25  * * *26  * * *27  * * *28  * * *29  * * *30  * * *Tue May 29 01:49:57 IST 2012                                                Loss%   Snt   Last   Avg  Best  Wrst StDev  1.|-- 117.205.xxx.1                              0.0%    10    5.1   5.8   5.1   8.7   1.0  2.|-- 218.248.175.246                            0.0%    10    9.2  10.3   9.2  12.1   1.0  3.|-- 59.163.206.157.static.chennai.vsnl.net.in  0.0%    10   56.0  54.9  53.5  56.8   1.1  4.|-- 172.31.35.198                              0.0%    10   55.2  55.4  53.8  56.6   1.0  5.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0  6.|-- 59.163.25.46.static.vsnl.net.in            0.0%    10   53.0  52.9  51.0  59.4   2.4  7.|-- if-0-1-9-0.tcore1.CXR-Chennai.as6453.net   0.0%    10   54.4  58.7  53.6  91.5  11.6  8.|-- if-5-2.tcore1.SVW-Singapore.as6453.net     0.0%    10  278.1 263.7 260.3 278.1   5.2    |   +-- [MPLS: Lbl 756032 Exp 0 S 1 TTL 1]  9.|-- if-6-2.tcore2.TV2-Tokyo.as6453.net        20.0%    10  268.3 272.5 265.8 303.4  12.7    |   +-- [MPLS: Lbl 300608 Exp 0 S 1 TTL 1] 10.|-- if-2-2.tcore1.TV2-Tokyo.as6453.net        30.0%    10  256.1 253.5 252.3 256.1   1.3    |   +-- [MPLS: Lbl 299776 Exp 0 S 1 TTL 1] 11.|-- if-9-2.tcore2.PDI-PaloAlto.as6453.net      0.0%    10  263.3 262.6 261.6 264.0   0.8 12.|-- Vlan3254.icore1.SQN-SanJose.as6453.net    30.0%    10  288.1 282.8 276.6 288.1   4.8 13.|-- te2-5.ccr02.sjc03.atlas.cogentco.com       0.0%    10  260.5 279.6 259.8 363.9  39.1 14.|-- te0-2-0-1.mpd22.lax01.atlas.cogentco.com  10.0%    10  275.6 274.3 273.1 275.6   0.8 15.|-- te7-8.ccr02.lax05.atlas.cogentco.com       0.0%    10  267.4 289.0 267.0 475.1  65.4 16.|-- te4-2.mag03.lax05.atlas.cogentco.com       0.0%    10  266.8 266.9 266.2 267.8   0.6 17.|-- 38.104.84.94                               0.0%    10  267.5 267.1 265.8 269.9   1.2 18.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
Also, let us all date the traceroutes when we do them. Traceroutes can vary a lot depending on the time of day; so a traceroute with a date and time is more useful than a traceroute without one.
 
Yes, dept of telecom

My complaint was regarding extreme slow speeds and high latencies even to local Indian servers. I had also sent them snapshots taken from speedtest and also traceroutes to some popular websites stressing on the poor routing issue.

I'd also suggest you send written complaints to the Nodal Officer, the NWO of your circle and also to the Appellate authority (GM Broadband)

Let me know if you'd need any help



Do u think your problem will be solved complaining there???????
i have lodged a complaint that my landline is almost dead no incoming and outgoing
still no call from them. . .
ONLY BROADBAND WORKS.THEY CLAIM IT S A CABLE FAULT.
landline works only during night after 12. . with crappy noise.

Department of telecom will just forward u r case to delhi sanchar bhavan and they will forward it to your city pgm(principle g.m)
NO USE DUDE
i m very much sure about it...
DOT will no wr interfere to solve u.r case.

I have seen airtel responding to these complaints very quickly..when it goes to DOT.

- - - Updated - - -

Yes, dept of telecom

My complaint was regarding extreme slow speeds and high latencies even to local Indian servers. I had also sent them snapshots taken from speedtest and also traceroutes to some popular websites stressing on the poor routing issue.

I'd also suggest you send written complaints to the Nodal Officer, the NWO of your circle and also to the Appellate authority (GM Broadband)

Let me know if you'd need any help



Do u think your problem will be solved complaining there???????
i have lodged a complaint that my landline is almost dead no incoming and outgoing
still no call from them. . .
ONLY BROADBAND WORKS.THEY CLAIM IT S A CABLE FAULT.
landline works only during night after 12. . with crappy noise.

Department of telecom will just forward u r case to delhi sanchar bhavan and they will forward it to your city pgm(principle g.m)
NO USE DUDE
i m very much sure about it...
DOT will no wr interfere to solve u.r case.

I have seen airtel responding to these complaints very quickly..when it goes to DOT.

- - - Updated - - -

All I can say is "whoa".

Rcom: Looks like the links to Reliance get just as saturated as the ones to VSNL.
ATT/Inteliquent: These links go through Tata, so that's the behaviour we're seeing elsewhere as well.
CW is roughly as I'd expect given the distances and all.

In short, it seems simply to be saturation at the gateways. I can ping 59.163.207.81 (Sixth hop for you) in 27 or 28ms, you are seeing 250+ and with 115.254.106.154 I can see that in 17 or 18ms whereas you can see it in 350+ only. BSNL needs to either upgrade it's core and/or edge routers, buy more bandwidth or maybe even both.


mg u can just give suggestions.
you cannot do much.

But e over there are sleeping...BULL Sh** company.
all of them who are working there should be given a retirement @ the age of 45
For the better service of the customers and to avoid loss in their company

I m just waiting some indian private company to take over BSNL.. or I might be dreaming about it.

This f****** isp will no where progress .
or must be given license to serve only village areas.
 

Similar threads

P
  • Featured
Looks like BSNL enabled IPv6 in Telangana!
Replies
8
Views
738
!!..PD..!!
P
  • Solved
Exposing application on IPV6 Airtel Xstream for self hosting purpose
2
Replies
22
Views
2,254
panic0
P
Experiencing Packet Loss with One Broadband
Replies
8
Views
1,063
Powerful84tiger
Lolita_Magnum
Not able to Reverse Traceroute/MTR.
Replies
3
Views
1,573
Lolita_Magnum
Top