I got:
C:\
Windows\system32>tracert google.com
Tracing route to google.com [74.125.236.81]
over a maximum of 30 hops:
1 1 ms 1 ms 3 ms 192.168.0.1
2 2 ms 1 ms 2 ms 192.168.1.1
3 24 ms 24 ms 26 ms 117.192.160.1
4 24 ms 23 ms 24 ms 218.248.160.170
5 25 ms 24 ms 25 ms 218.248.255.74
6 33 ms 31 ms 31 ms 218.248.255.70
7 34 ms 32 ms 32 ms 59.163.206.45.static.chennai.vsnl.net.in [59.163
.206.45]
8 33 ms 34 ms 33 ms 121.240.1.46
9 34 ms 92 ms 34 ms 72.14.232.110
10 33 ms 33 ms 35 ms 209.85.249.235
11 34 ms 33 ms 33 ms maa03s05-in-f17.1e100.net [74.125.236.81]
Trace complete.
I think there is a problem, my line is pretty god nowadays with SNR in excess of 30 on BSNL & hence get this.
P.S: First 2 hops are from my internal network, i'm using a Access Point/Range Extender to amplify the signal to the second floor.
----------
But u may try using
Google or Open
DNS to see if it makes a difference, that is if you already haven't but looks like the issue lies in the 1st hop itself & hence something that needs to be checked by ISP like Chaitanya said. Results above were on BSNL's own DNS servers from what i know.
