29 Jan

Amazon India peering check

And here goes first blog post of 2018. Last few months went busy with some major changes in personal life. ūüôā

I looked into Amazon’s India connectivity with various ASNs tonight. Here’s how it looks like. (Note: Jump to bottom most to skip traces and look at the summary data).

 

Amazon India to Vodafone India

traceroute to 118.185.107.1 (118.185.107.1), 30 hops max, 60 byte packets
 1 ec2-52-66-0-128.ap-south-1.compute.amazonaws.com (52.66.0.128) 21.861 ms ec2-52-66-0-134.ap-south-1.compute.amazonaws.com (52.66.0.134) 19.244 ms 19.233 ms
 2 100.64.2.200 (100.64.2.200) 14.789 ms 100.64.0.200 (100.64.0.200) 20.731 ms 100.64.3.12 (100.64.3.12) 13.187 ms
 3 100.64.0.193 (100.64.0.193) 14.418 ms 100.64.3.69 (100.64.3.69) 15.469 ms 100.64.3.67 (100.64.3.67) 15.946 ms
 4 100.64.16.67 (100.64.16.67) 0.343 ms 100.64.17.165 (100.64.17.165) 0.312 ms 100.64.17.199 (100.64.17.199) 0.313 ms
 5 52.95.67.213 (52.95.67.213) 1.942 ms 52.95.67.209 (52.95.67.209) 1.967 ms 52.95.67.213 (52.95.67.213) 1.935 ms
 6 52.95.66.218 (52.95.66.218) 4.998 ms 4.694 ms 52.95.66.130 (52.95.66.130) 4.650 ms
 7 52.95.66.67 (52.95.66.67) 1.752 ms 52.95.66.89 (52.95.66.89) 1.850 ms 1.806 ms
 8 52.95.217.183 (52.95.217.183) 3.111 ms 3.102 ms 3.088 ms <- Amazon India
 9 182.19.106.204 (182.19.106.204) 3.426 ms 4.547 ms 4.537 ms <- Vodafone India
10 118.185.107.1 (118.185.107.1) 2.035 ms 2.059 ms 2.039 ms

 

Amazon India to IDEA

traceroute to 223.196.83.1 (223.196.83.1), 30 hops max, 60 byte packets
 1 ec2-52-66-0-128.ap-south-1.compute.amazonaws.com (52.66.0.128) 16.133 ms ec2-52-66-0-132.ap-south-1.compute.amazonaws.com (52.66.0.132) 14.232 ms ec2-52-66-0-130.ap-south-1.compute.amazonaws.com (52.66.0.130) 21.267 ms
 2 100.64.3.10 (100.64.3.10) 16.418 ms 100.64.1.76 (100.64.1.76) 20.674 ms 100.64.1.206 (100.64.1.206) 26.416 ms
 3 100.64.3.129 (100.64.3.129) 18.727 ms 100.64.3.135 (100.64.3.135) 13.790 ms 100.64.3.133 (100.64.3.133) 20.787 ms
 4 100.64.16.101 (100.64.16.101) 0.323 ms 100.64.16.195 (100.64.16.195) 0.296 ms 100.64.16.135 (100.64.16.135) 2.358 ms
 5 52.95.67.213 (52.95.67.213) 1.879 ms 2.452 ms 2.465 ms
 6 52.95.66.174 (52.95.66.174) 2.717 ms 52.95.66.130 (52.95.66.130) 8.568 ms 52.95.66.64 (52.95.66.64) 6.004 ms
 7 52.95.66.183 (52.95.66.183) 4.361 ms 52.95.66.73 (52.95.66.73) 11.474 ms 52.95.66.51 (52.95.66.51) 11.414 ms
 8 52.95.217.201 (52.95.217.201) 3.585 ms 3.627 ms 3.420 ms
 9 223.196.6.237 (223.196.6.237) 3.704 ms 3.832 ms 3.826 ms
10 223.196.15.26 (223.196.15.26) 6.155 ms 223.196.2.141 (223.196.2.141) 8.472 ms *

 

Amazon India to Reliance Communications

traceroute to 115.252.64.1 (115.252.64.1), 30 hops max, 60 byte packets
 1 ec2-52-66-0-132.ap-south-1.compute.amazonaws.com (52.66.0.132) 18.567 ms ec2-52-66-0-134.ap-south-1.compute.amazonaws.com (52.66.0.134) 19.024 ms 19.020 ms
 2 100.64.0.72 (100.64.0.72) 22.429 ms 100.64.0.200 (100.64.0.200) 19.483 ms 100.64.2.142 (100.64.2.142) 18.679 ms
 3 100.64.1.67 (100.64.1.67) 11.717 ms 100.64.0.7 (100.64.0.7) 30.194 ms 100.64.2.195 (100.64.2.195) 11.700 ms
 4 100.64.16.195 (100.64.16.195) 0.353 ms 100.64.16.67 (100.64.16.67) 0.398 ms 100.64.17.163 (100.64.17.163) 0.400 ms
 5 52.95.67.209 (52.95.67.209) 1.847 ms 1.879 ms 1.891 ms
 6 52.95.66.108 (52.95.66.108) 5.567 ms 52.95.67.108 (52.95.67.108) 11.119 ms 52.95.66.174 (52.95.66.174) 9.029 ms
 7 52.95.66.141 (52.95.66.141) 2.938 ms 52.95.67.99 (52.95.67.99) 1.755 ms 52.95.67.165 (52.95.67.165) 1.755 ms
 8 54.239.43.171 (54.239.43.171) 18.605 ms 54.239.44.63 (54.239.44.63) 18.034 ms 54.239.43.171 (54.239.43.171) 18.522 ms
 9 52.93.19.126 (52.93.19.126) 63.893 ms 52.93.19.82 (52.93.19.82) 23.508 ms 52.93.19.62 (52.93.19.62) 20.812 ms
10 52.93.19.139 (52.93.19.139) 19.302 ms 52.93.19.133 (52.93.19.133) 18.600 ms 52.93.19.25 (52.93.19.25) 18.365 ms
11 115.110.161.61.static.vsnl.net.in (115.110.161.61) 17.966 ms 18.201 ms 115.110.161.65.static.vsnl.net.in (115.110.161.65) 17.948 ms
12 121.244.23.6.STATIC.Chennai.vsnl.net.in (121.244.23.6) 18.391 ms * *
13 115.255.253.69 (115.255.253.69) 27.234 ms 27.455 ms 27.652 ms
14 115.255.28.129 (115.255.28.129) 27.836 ms 121.244.23.6.STATIC.Chennai.vsnl.net.in (121.244.23.6) 18.906 ms 18.809 ms
15 115.255.232.1 (115.255.232.1) 27.524 ms 115.255.253.69 (115.255.253.69) 27.971 ms 115.255.232.1 (115.255.232.1) 27.777 ms
16 220.227.241.217 (220.227.241.217) 27.841 ms * 27.886 ms
17 115.255.232.1 (115.255.232.1) 27.628 ms 27.920 ms 27.965 ms
18 220.227.241.217 (220.227.241.217) 29.835 ms 220.224.230.177 (220.224.230.177) 28.402 ms *

 

Amazon India to Powergrid Corp

traceroute to 43.227.132.1 (43.227.132.1), 30 hops max, 60 byte packets
 1 ec2-52-66-0-132.ap-south-1.compute.amazonaws.com (52.66.0.132) 15.971 ms ec2-52-66-0-128.ap-south-1.compute.amazonaws.com (52.66.0.128) 11.558 ms ec2-52-66-0-134.ap-south-1.compute.amazonaws.com (52.66.0.134) 19.813 ms
 2 100.64.0.14 (100.64.0.14) 18.356 ms 100.64.2.200 (100.64.2.200) 15.390 ms 15.390 ms
 3 100.64.2.1 (100.64.2.1) 21.122 ms 100.64.3.3 (100.64.3.3) 19.208 ms 100.64.1.1 (100.64.1.1) 21.094 ms
 4 100.64.17.165 (100.64.17.165) 0.283 ms 100.64.16.39 (100.64.16.39) 0.323 ms 100.64.17.103 (100.64.17.103) 0.341 ms
 5 52.95.67.215 (52.95.67.215) 1.638 ms 52.95.67.211 (52.95.67.211) 0.702 ms 52.95.67.215 (52.95.67.215) 0.749 ms
 6 52.95.67.64 (52.95.67.64) 1.103 ms 52.95.67.86 (52.95.67.86) 4.012 ms 3.986 ms
 7 52.95.67.51 (52.95.67.51) 0.599 ms 52.95.67.29 (52.95.67.29) 0.662 ms 52.95.67.51 (52.95.67.51) 0.651 ms
 8 52.95.219.49 (52.95.219.49) 7.935 ms 8.111 ms 8.675 ms
 9 kalwa-edge-177.230.218.103.powergrid.in (103.218.230.177) 1.452 ms 1.641 ms 1.169 ms
10 43.227.132.65 (43.227.132.65) 49.309 ms 49.233 ms 49.296 ms
11 43.227.132.1 (43.227.132.1) 58.909 ms 58.975 ms 58.893 ms

 

Amazon India to BSNL

traceroute to 218.248.235.130 (218.248.235.130), 30 hops max, 60 byte packets
 1 ec2-52-66-0-128.ap-south-1.compute.amazonaws.com (52.66.0.128) 15.199 ms 15.173 ms ec2-52-66-0-130.ap-south-1.compute.amazonaws.com (52.66.0.130) 16.306 ms
 2 100.64.2.140 (100.64.2.140) 18.831 ms 100.64.2.202 (100.64.2.202) 18.159 ms 100.64.2.78 (100.64.2.78) 15.493 ms
 3 100.64.1.1 (100.64.1.1) 16.829 ms 100.64.1.129 (100.64.1.129) 16.823 ms 100.64.2.193 (100.64.2.193) 16.813 ms
 4 100.64.16.193 (100.64.16.193) 0.403 ms 100.64.17.133 (100.64.17.133) 0.290 ms 100.64.17.99 (100.64.17.99) 0.289 ms
 5 52.95.67.215 (52.95.67.215) 0.803 ms 52.95.67.211 (52.95.67.211) 0.672 ms 0.702 ms
 6 52.95.66.130 (52.95.66.130) 7.382 ms 7.107 ms 52.95.67.174 (52.95.67.174) 2.292 ms
 7 52.95.66.179 (52.95.66.179) 1.819 ms 52.95.67.91 (52.95.67.91) 0.658 ms 52.95.66.91 (52.95.66.91) 1.798 ms
 8 52.95.217.42 (52.95.217.42) 0.534 ms 0.505 ms 52.95.217.38 (52.95.217.38) 2.010 ms
 9 182.79.178.199 (182.79.178.199) 1.938 ms 182.79.178.63 (182.79.178.63) 1.936 ms 182.79.178.201 (182.79.178.201) 1.926 ms
10 * * aes-static-042.105.144.59.airtel.in (59.144.105.42) 3.179 ms
11 218.248.235.157 (218.248.235.157) 3.106 ms 3.230 ms *
12 218.248.235.129 (218.248.235.129) 40.928 ms 40.433 ms 40.853 ms
13 218.248.235.130 (218.248.235.130) 40.307 ms 40.384 ms 40.280 ms

 

Trace from Amazon India to Google’s anycasted 8.8.8.8:

traceroute -A 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 ec2-52-66-0-134.ap-south-1.compute.amazonaws.com (52.66.0.134) [AS38895/AS16509] 12.662 ms ec2-52-66-0-130.ap-south-1.compute.amazonaws.com (52.66.0.130) [AS38895/AS16509] 20.008 ms ec2-52-66-0-128.ap-south-1.compute.amazonaws.com (52.66.0.128) [AS38895/AS16509] 21.983 ms
2 100.64.0.142 (100.64.0.142) [AS22773] 15.525 ms 100.64.0.204 (100.64.0.204) [AS22773] 16.081 ms 100.64.1.206 (100.64.1.206) [AS22773] 19.696 ms
3 100.64.0.131 (100.64.0.131) [AS22773] 12.944 ms 12.893 ms 100.64.2.5 (100.64.2.5) [AS22773] 15.071 ms
4 100.64.16.103 (100.64.16.103) [AS22773] 0.318 ms 100.64.17.39 (100.64.17.39) [AS22773] 0.325 ms 100.64.17.69 (100.64.17.69) [AS22773] 0.291 ms
5 52.95.67.215 (52.95.67.215) [AS16509] 1.374 ms 5.725 ms 4.294 ms
6 52.95.67.130 (52.95.67.130) [AS16509] 4.896 ms 52.95.67.86 (52.95.67.86) [AS16509] 2.021 ms 52.95.67.108 (52.95.67.108) [AS16509] 5.735 ms
7 52.95.67.111 (52.95.67.111) [AS16509] 0.705 ms 0.672 ms 0.670 ms
8 52.95.218.225 (52.95.218.225) [*] 0.542 ms 0.570 ms 0.505 ms
9 108.170.248.161 (108.170.248.161) [AS15169] 0.853 ms 108.170.248.193 (108.170.248.193) [AS15169] 0.804 ms 108.170.248.177 (108.170.248.177) [AS15169] 0.770 ms
10 108.170.234.9 (108.170.234.9) [AS15169] 1.449 ms 209.85.248.147 (209.85.248.147) [AS15169] 1.725 ms 1.728 ms
11 google-public-dns-a.google.com (8.8.8.8) [AS15169] 0.460 ms 0.744 ms 0.449 ms

 

Amazon India to Microsoft Azure India

traceroute to 52.172.52.79 (52.172.52.79), 30 hops max, 60 byte packets
 1 ec2-52-66-0-132.ap-south-1.compute.amazonaws.com (52.66.0.132) 11.434 ms ec2-52-66-0-134.ap-south-1.compute.amazonaws.com (52.66.0.134) 14.968 ms ec2-52-66-0-128.ap-south-1.compute.amazonaws.com (52.66.0.128) 14.694 ms
 2 100.64.2.8 (100.64.2.8) 15.301 ms 100.64.3.14 (100.64.3.14) 14.541 ms 100.64.2.10 (100.64.2.10) 15.289 ms
 3 100.64.0.131 (100.64.0.131) 19.954 ms 100.64.2.199 (100.64.2.199) 20.491 ms 100.64.1.135 (100.64.1.135) 20.473 ms
 4 100.64.16.67 (100.64.16.67) 6.650 ms 100.64.16.65 (100.64.16.65) 0.306 ms 100.64.16.133 (100.64.16.133) 0.307 ms
 5 52.95.67.213 (52.95.67.213) 1.917 ms 52.95.67.209 (52.95.67.209) 1.931 ms 1.980 ms
 6 52.95.66.130 (52.95.66.130) 3.015 ms 52.95.66.196 (52.95.66.196) 10.939 ms 52.95.66.86 (52.95.66.86) 11.644 ms
 7 52.95.66.91 (52.95.66.91) 1.802 ms 52.95.66.177 (52.95.66.177) 7.303 ms 52.95.66.199 (52.95.66.199) 3.435 ms
 8 52.95.218.61 (52.95.218.61) 16.785 ms 52.95.218.63 (52.95.218.63) 1.700 ms 1.674 ms
 9 ae0-0.bom02-96cbe-1b.ntwk.msn.net (104.44.226.17) 1.952 ms 1.897 ms ae14-0.bom30-96cbe-1b.ntwk.msn.net (198.206.164.159) 2.238 ms
10 ae14-0.bom30-96cbe-1b.ntwk.msn.net (198.206.164.159) 2.150 ms 2.172 ms ae5-0.maa30-96cbe-1a.ntwk.msn.net (104.44.226.241) 26.009 ms
11 ae5-0.maa30-96cbe-1a.ntwk.msn.net (104.44.226.241) 25.940 ms ae10-0.maa01-96cbe-1b.ntwk.msn.net (104.44.226.243) 27.591 ms 27.587 ms
12 ae10-0.maa01-96cbe-1b.ntwk.msn.net (104.44.226.243) 27.698 ms ae0-0.maa01-96cbe-1a.ntwk.msn.net (104.44.227.208) 28.090 ms *
13 * ae0-0.maa01-96cbe-1a.ntwk.msn.net (104.44.227.208) 27.682 ms *
14 * * *
15 * * *
16 * * *
17 * * *
18 *^C

 

Amazon India to Cloudflare India PoP

traceroute to amy.ns.cloudflare.com (173.245.58.101), 30 hops max, 60 byte packets
 1 ec2-52-66-0-130.ap-south-1.compute.amazonaws.com (52.66.0.130) [AS38895/AS16509] 13.912 ms ec2-52-66-0-134.ap-south-1.compute.amazonaws.com (52.66.0.134) [AS38895/AS16509] 15.167 ms 15.159 ms
 2 100.64.0.142 (100.64.0.142) [AS22773] 21.393 ms 100.64.3.72 (100.64.3.72) [AS22773] 16.098 ms 100.64.3.14 (100.64.3.14) [AS22773] 11.766 ms
 3 100.64.2.67 (100.64.2.67) [AS22773] 27.118 ms 100.64.2.131 (100.64.2.131) [AS22773] 27.097 ms 100.64.2.133 (100.64.2.133) [AS22773] 21.532 ms
 4 100.64.16.39 (100.64.16.39) [AS22773] 0.253 ms 100.64.17.193 (100.64.17.193) [AS22773] 0.256 ms 100.64.16.195 (100.64.16.195) [AS22773] 0.260 ms
 5 52.95.67.209 (52.95.67.209) [AS16509] 1.850 ms 1.846 ms 52.95.67.213 (52.95.67.213) [AS16509] 1.808 ms
 6 52.95.66.108 (52.95.66.108) [AS16509] 3.007 ms 52.95.66.174 (52.95.66.174) [AS16509] 13.312 ms 13.285 ms
 7 52.95.66.201 (52.95.66.201) [AS16509] 1.890 ms 52.95.66.135 (52.95.66.135) [AS16509] 2.571 ms 52.95.66.71 (52.95.66.71) [AS16509] 1.867 ms
 8 115.114.89.209.static-Mumbai.vsnl.net.in (115.114.89.209) [AS4755] 2.448 ms 115.114.89.189.static-Mumbai.vsnl.net.in (115.114.89.189) [AS4755] 1.984 ms 1.888 ms
 9 * * *
10 * 182.79.203.36 (182.79.203.36) [*] 2.459 ms *
11 182.79.223.54 (182.79.223.54) [*] 2.357 ms 2.368 ms 14.142.21.18.static-vsnl.net.in (14.142.21.18) [AS4755] 2.008 ms
12 amy.ns.cloudflare.com (173.245.58.101) [AS13335] 2.467 ms 182.79.203.44 (182.79.203.44) [*] 2.777 ms amy.ns.cloudflare.com (173.245.58.101) [AS13335] 2.445 ms

 

 

Some traces where traffic going from Amazon India is getting routed to Indian networks from outside:

traceroute to 125.18.237.1 (125.18.237.1), 30 hops max, 60 byte packets
 1 ec2-52-66-0-134.ap-south-1.compute.amazonaws.com (52.66.0.134) 18.252 ms ec2-52-66-0-130.ap-south-1.compute.amazonaws.com (52.66.0.130) 17.868 ms ec2-52-66-0-132.ap-south-1.compute.amazonaws.com (52.66.0.132) 20.634 ms
 2 100.64.3.76 (100.64.3.76) 15.640 ms 100.64.2.202 (100.64.2.202) 13.602 ms 100.64.0.74 (100.64.0.74) 14.663 ms
 3 100.64.3.197 (100.64.3.197) 2.152 ms 100.64.2.69 (100.64.2.69) 2.128 ms 100.64.3.69 (100.64.3.69) 2.134 ms
 4 100.64.17.37 (100.64.17.37) 0.337 ms 100.64.16.37 (100.64.16.37) 0.354 ms 100.64.17.129 (100.64.17.129) 0.293 ms
 5 52.95.67.213 (52.95.67.213) 1.902 ms 1.861 ms 52.95.67.209 (52.95.67.209) 1.867 ms
 6 52.95.66.64 (52.95.66.64) 5.317 ms 52.95.66.218 (52.95.66.218) 6.883 ms 52.95.66.196 (52.95.66.196) 9.687 ms
 7 52.95.66.203 (52.95.66.203) 1.817 ms 52.95.66.69 (52.95.66.69) 1.844 ms 52.95.66.137 (52.95.66.137) 1.792 ms
 8 115.114.89.121.static-Mumbai.vsnl.net.in (115.114.89.121) 1.745 ms 115.114.89.209.static-Mumbai.vsnl.net.in (115.114.89.209) 1.799 ms 115.114.89.121.static-Mumbai.vsnl.net.in (115.114.89.121) 2.034 ms
 9 * * *
10 ix-ae-4-2.tcore1.CXR-Chennai.as6453.net (180.87.36.9) 54.804 ms * *
11 if-ae-3-3.tcore2.CXR-Chennai.as6453.net (180.87.36.6) 228.066 ms ix-ae-4-2.tcore1.CXR-Chennai.as6453.net (180.87.36.9) 56.587 ms 53.271 ms
12 if-ae-3-3.tcore2.CXR-Chennai.as6453.net (180.87.36.6) 225.894 ms 226.883 ms 227.007 ms
13 if-ae-6-2.tcore2.SVW-Singapore.as6453.net (180.87.37.14) 226.616 ms 227.081 ms if-ae-10-2.tcore2.SVW-Singapore.as6453.net (180.87.37.65) 226.699 ms
14 if-ae-7-2.tcore2.LVW-Los-Angeles.as6453.net (180.87.15.26) 227.935 ms 225.266 ms 235.497 ms
15 xe-4-1-0.edge1.SanJose3.level3.net (4.68.62.105) 247.387 ms 257.588 ms 249.384 ms
16 ae-116-3502.edge3.London15.Level3.net (4.69.167.78) 241.053 ms 241.539 ms ae-115-3501.edge3.London15.Level3.net (4.69.167.74) 242.991 ms
17 ae-116-3502.edge3.London15.Level3.net (4.69.167.78) 240.407 ms ae-225-3601.edge3.London15.Level3.net (4.69.167.90) 243.525 ms ae-226-3602.edge3.London15.Level3.net (4.69.167.94) 241.484 ms
18 BHARTI-AIRT.edge3.London15.Level3.net (212.187.139.82) 244.356 ms 244.610 ms *
19 * * *
20 * * *
21 * * *
22 *^C

 

Summary of results

Network Name Network ASN Domestic Connectivity
Tata Communications 4755 Yes*
Airtel 9498 Yes*
Idea Cellular 55644 Yes
Reliance Communucations 18101 No
Aircel 10201 No
Powergrid Telecom 132215 Yes
Railtel 24186 Yes
BSNL 9829 No
NKN 55824 No
CtrlS 18229 No
Syscon Infoway 45194 No
Intech Online 58678 Yes
Charotar Broadband 132933 Yes
Ishan Tech 45117 Yes
Webwerks 33480 No
Blazenet 17625 Yes
Spectra 10029 Yes
Excitel Broadband 133982 Yes
Google 15169 Yes
Cloudflare 13335 No
Microsoft 8075 Yes

 

Misc points:

  1. *TCL and *Airtel seem to be IP transit provider of Amazon. For certain routes going outside India traffic seem to be going via Tata VSNL AS4755.
  2. Connectivity checked for certain random pools only and not for all announced routes for a large telco network.
25 Nov

Peering with content networks in India

peering

One of frequent email and contact form message I get my blog is about available content networks in India and where one can peer. There are certain content networks in India and of course most of the content networks have open peering policy and are usually happy with direct inter-connection (we call as “peering“) with the ISP networks (often referred to as “eyeball networks”). Some of these networks have a backbone which connects back to their key datacenter locations on their own circuits via Singapore/Europe, some other have simply placed their caching server where cache fill happens over IP transit.

 

Based on publically known information across community and of course peeringdb, following content players are available in India and known to be open for peering:

  1. Google
  2. Microsoft
  3. Amazon
  4. Limelight

 

A quick list of these with datacenter names and locations as taken from Peeringdb record of these networks.

Organisation ASN City Datacenter Location
Amazon 16509 Mumbai GPX Mumbai Unit A-001, Boomerang Chandivali Farm Road, Near Chandivali Studio, Andheri East Mumbai, Mumbai, 400 051
Amazon 16509 Noida Sify Greenfort – Noida B7, Block A, Sector 132, Noida Expressway, Noida , UP 201304
Amazon 16509 Mumbai Tata Mumbai IDC LVSB, Opposite Kirti College
6th floor, Prabahdevi
Mumbai, MH, 400 028
Google 15169 Chennai Bharti Airtel Santhome Bharti Towers, 101 Santhome High Road, Chennai, 600 028
Google 15169 Mumbai GPX Mumbai Unit A-001, Boomerang Chandivali Farm Road, Near Chandivali Studio, Andheri East Mumbai, Mumbai, 400 051
Google 15169 Noida Sify Greenfort – Noida B7, Block A, Sector 132, Noida Expressway, Noida , UP 201304
Google 15169 Chennai TATA Communications Ltd 14th floor, 2nd block
4, Swami Sivanand Salai, Chennai, TN 600 002
Google 15169 Delhi Tata Delhi VSB, Bangla Sahib Road, New Delhi 110001
Google 15169 Mumbai Tata Mumbai IDC LVSB, Opposite Kirti College
6th floor, Prabhadevi
Mumbai, MH, 400 028
Limelight 55439 / 22822 Chennai Bharti Airtel Santhome Bharti Towers, 101 Santhome High Road, Chennai, 600 028
Limelight 55439 / 22822 Mumbai Netmagic Vikhroli Mehra Industrial Estate
LBS Marg, Vikhroli
Mumbai, 400 079
Microsoft 8075 Mumbai Bharti Airtel Mumbai Plot No, TPS-2, 14/3, 2nd floor
Dattatray Road, Linking Road Extension
Mumbai, 400054
Microsoft 8075 Chennai Bharti Airtel Santhome Bharti Towers, 101 Santhome High Road, Chennai, 600 028
Microsoft 8075 Chennai TATA Communications Ltd 14th floor, 2nd block
4, Swami Sivanand Salai, Chennai, TN 600 002
Microsoft 8075 Delhi Tata Communications Ltd – GK1 Greater Kailash-1
New Delhi, 110048
Microsoft 8075 Mumbai Tata Mumbai IDC LVSB, Opposite Kirti College
6th floor, Prabhadevi
Mumbai, MH, 400 028

 

Besides these Google also has an option of GGC, Akamai has an option of Akamai Caching server, Facebook has the option for caching server which is hosted inside ISP’s network and Netflix has an option for OCAs. Besides these networks there are known nodes of Verizon’s Edgecast in Delhi, Mumbai &¬†Chennai (as per this map), Cloudflare has nodes in Delhi, Mumbai & Chennai (as per this map), PCH & K-root server have a node with Web Werks available on MCH peering fabric and Dyn has a node in Mumbai (as per this map).

Go ahead and peer as after all it all starts with a handshake. ūüôā

28 Sep

Good bye BSNL (AS9829) | New link at home!

A blog post dedicated to BSNL AS9829. It just¬†tried so hard to become as irrelevant as it can¬†from everyone’s life (and that doesn’t excludes me now).

 

So what really is BSNL btw?

  • A Govt of India telco sitting at a extensive fiber of over 600,000 Kms across the country (staying just¬†unused¬†and unavailable for anyone’s use!)
  • A telco which has an extensive¬†last mile copper (which is very poorly maintained and barely works!)
  • A backbone with over¬†200Gbps of IP transit capacity (which completely sucks due to¬†rotten routing)
  • An integrated telecom provider offering services from landline to DSL broadband, from leased line to datacenter services! (out of which everything fails miserably from product line to technical ground level operations)
  • An extensive manpower (which is terribly arrogant and from top to ground level staff anyone barely works!)
  • Although telecom industry just boomed, it¬†went from 10,000 crore profits in 2004 to 8000 crore losses in 2015. And still politics goes around it!
  • While private sector was busy with focus on 4G LTE deployment, BSNL’s market share dropped below 10% in 2014
  • While private sector firms like Sterlite, Radius Infratel focused on FTTH rollouts, BSNL rolled out FTTH plans for 4000 INR/month for 50GB cap and FUP speed of (amazing) 512Kbps to ensure no one uses it
  • While Reliance Jio is about to come, Airtel is extensively launching 4G LTE, cool companies like ACT¬†are getting¬†more investment, BSNL is putting 6000 crore in public wifi infrastructure to give few mins of free wifi and with hop of users paying it afterwards. (Wow?!)

 

All above tells nothing but ways in which BSNL is 100% screwed up for now. I don’t expect it to ever pick up again. Politically, technically, and fundamentally it’s a mess.

I became BSNL broadband user in 2008 and it has been over 7 years of (painful and terrible) experience with them. As a company which put so much of infrastructure to connect India worked extremely hard to do as many stupid things as possible. For me trouble remained that in my city they were only wired telecom provider for retail services.

 

Last month¬†I got a long haul circuit from Airtel (provisioned on fiber) between my city and a friend’s ISP PoP for 10Mbps bandwidth. Circuit is delivered at a Airtel¬†BTS site location (slightly¬†away from my home) and I have installed Microtik SXT Lite 5’s shooting link from there to my home (around 1km link with clear LoS). This is a usual long range fixed wireless RF link over un-licensed 5.8Ghz band. (Thankyou govt. of India for delicensing¬†it in 2007 and making available for public use). Thanks to companies like Microtik and Ubiquiti for opening up world of good fixed wireless radios and antennas which really work great and are available for quite good prices. I got pair of SXT Lite5’s from Amazon.in at 7700 INR (~$116).

Fortunately BTS site has a private WISP tower and the owner of tower agreed to let me use his tower for my radio for reasonable price.

 

 

Some statistics about my new link

 

Airtel BTS site

Airtel BTS Site

 

 

 

LoS of tower (from home)

tower

 

 

Radio at my rooftop

Radio on rooftop

 

 

(Water tanks pipes were tall enough that I didn’t had to mount any pole and used those pipes)

 

Closer look

Radio at home

 

Link quality checks

Radio link stats

 

I am getting end to end bandwidth of around 35Mbps between radios (while provisioned bandwidth is 10Mbps on backend). I am using 5Mhz of channel bandwidth with 802.11 protocol and usual WPA2-PSK works to have encryption between radios.

End to end latency between Rasberry Pi (connected via wired to my home router) to other end radio:

PING 10.10.10.101 (10.10.10.101) 56(84) bytes of data.
64 bytes from 10.10.10.101: icmp_req=1 ttl=63 time=1.57 ms
64 bytes from 10.10.10.101: icmp_req=2 ttl=63 time=1.03 ms
64 bytes from 10.10.10.101: icmp_req=3 ttl=63 time=1.02 ms
64 bytes from 10.10.10.101: icmp_req=4 ttl=63 time=1.02 ms
64 bytes from 10.10.10.101: icmp_req=5 ttl=63 time=1.24 ms
^C
--- 10.10.10.101 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 1.023/1.179/1.570/0.214 ms

 

And lastly speedtest from a server far away from here:

speedtest

 

(Note: Hided ISP name to avoid un-needed DDoS attack on them which are hitting my blog from few weeks)

 

 

Some thoughts on fixed wireless links

  1. Work great if LOS and free channels are there. India does has serious problem of very low unlicensed open spectrum permitted for outside use.
  2. Hard to predict capacity for large country like India – may work somewhere, may not somewhere.
  3. WISP stupidly use 20Mhz and HT beams of 40Mhz when even 5Mhz can do job for many of their links. (More “bandwidth” usage = reducing channels for others + more potential chances of interference).
  4. Links work well given 1st Fresnel zone is cleared. Special thanks to my friend Brough Turner for pointing this out. He runs an ISP based on this technology in Boston & surrounding areas. (Checkout netblzr)
  5. Fixed wireless is NOT mobile wireless (understand the difference!).
  6. Some other successful ISPs using this technology – MonkeyBrains in San Francisco (on unlicensed spectrum) and Webpass (using microwave links).
  7. Tikona in India used it a bit but with mesh to increase coverage and eventually got a network with latency & packet loss issues. Wireless links work well but for point to point and very little point to multi-point. Not good choice for a large network with wireless nodes acting as transport in between. Indian media as usual stupidly took technology as swiss knife solution to broadband issues. (checkout NDTV review of Tikona).
  8. Tech and NOG community across India have to support for more un-licensed spectrum for use in India. (Excellent article on this here)
  9. I am overall motivated by excellent paper – America’s Broadband Heros which gave very detailed understanding of technology and limitations
  10. I am overall happy with 2.5x increase in download speed but a whopping 20x increase in upload speeds. Fixed wireless has a good edge over upload speeds when compared to DSL

 

Ending this blog post with Cacti graph of my home broadband connection for last one month.¬†There’s high amount of systematic transfers of routing table data and some other stuff. I do keep a Rasberry Pi running all the time as home server. ūüôā

 

Home Broadband Graph