Drastic change in BSNL routing

[probuddha]

C:>tracert google.com

Tracing route to google.com [173.194.36.2] over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 9 ms 11 ms 117.194.64.1
4 12 ms 10 ms 10 ms 218.248.162.70
5 11 ms 11 ms 12 ms 218.248.255.10
6 96 ms 97 ms 100 ms bom04s01-in-f2.1e100.net [173.194.36.2]

I mean...

Anyone else experiencing this?

 

[rj27]

Looks like they are upto something :question:
Pings are high but the number of hops never used to be less than 9 or 10 :tongue_2:

 

[x720]

They finally have peering with Google?!

 

[iChaitanya]

Same here. Google is now 4 hops away, but what's the use? Latency has now increased from the usual ~42ms to 132ms.

 

[kickass]

mtnl does peer with google. thats why we on vdsl get low pings
Tracing route to www.google.com [74.125.236.148]over a maximum of 30 hops: 1

 

[x720]

^doesnt go via tata anymore, so pretty sure they're peering.

 

[probuddha]

Back to being shitty again
C:>tracert google.com

Tracing route to google.com [173.194.38.133] over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 10 ms 11 ms 11 ms 117.194.64.1
4 8 ms 9 ms 8 ms 218.248.162.70
5 11 ms 11 ms 9 ms 218.248.255.22
6 134 ms 131 ms 133 ms 115.114.130.17.STATIC-Chennai.vsnl.net.in [115.114.130.17]
7 * 149 ms 151 ms 172.29.251.34
8 * * * Request timed out.
9 181 ms 185 ms 183 ms 115.114.142.137.static-Chennai.vsnl.net.in [115.114.142.137]
10 714 ms 707 ms 709 ms 121.240.1.50
11 701 ms * 712 ms 72.14.233.204
12 735 ms 737 ms 751 ms 72.14.239.20
13 84 ms 83 ms 83 ms 72.14.233.79
14 745 ms 743 ms 730 ms sin04s01-in-f5.1e100.net [173.194.38.133]

Trace complete.

For a moment I had thought that BSNL was improving...whew!

 

[bajechele]

Is mine ok?

 

[kickass]

pretty decent !

 

[probuddha]

Is mine ok?

Yours is not BSNL - anything apart from BSNL is good