I have BSNL and Airtel DSL lines terminating on the same host in Gurgaon. If you ping/trace one from the other, packets are routed through Chennai! Airtel does not peer with BSNL or NIXI! Instead it hands over traffic to VSNL (TATA), which hauls them all the way to Chennai and then hands them over to BSNL. I have an ugly feeling that Bangalore also figures on this journey. BSNL's retail broadband operations are headquartered in Bangalore. It is quite possible that they route all their broadband traffic through some core switch in Bangalore, for billing/monitoring/big-brother purposes.
$ tracepath 117.198.121.150
1: localhost 0.297ms pmtu 1500
1: airtel 0.903ms
1: airtel 0.891ms
2: airtel 1.050ms pmtu 1400
2: abts-north-static-072.220.160.122.airtelbroadband.in 40.439ms asymm 3
3: no reply
4: aes-static-005.68.144.59.airtel.in 33.364ms asymm 7
5: 14.141.116.89.static-Delhi.vsnl.net.in 32.105ms asymm 6
6: 172.31.17.5 84.003ms asymm 7
7: 14.141.139.146.static-chennai.vsnl.net.in 115.703ms asymm 8
8: 218.248.235.141 117.483ms asymm 9
9: 218.248.169.41 113.957ms
10: 218.248.169.41 118.894ms asymm 9
11: 117.198.121.150 150.196ms asymm 10
12: 117.198.121.150 154.696ms !H
Average RTT 118ms
Oh wait! Before we jump to the above conclusions, let's try the reverse journey, BSNL to Airtel:
# ip netns exec bsnl tracepath airtel-global
1: localhost 0.186ms pmtu 1500
1: bsnl 5.377ms
1: bsnl 5.675ms
2: bsnl 5.784ms pmtu 1400
2: 117.198.120.1 47.735ms
3: 218.248.169.38 68.787ms
4: 218.248.235.130 46.593ms asymm 5
5: 218.100.48.20 57.748ms asymm 6
6: 182.79.255.101 186.722ms asymm 8
7: no reply
8: no reply
9: no reply
10: abts-north-dynamic-007.3.68.182.airtelbroadband.in 155.566ms asymm 11
11: abts-north-dynamic-007.3.68.182.airtelbroadband.in 156.832ms !H
Number 5 is NIXI Delhi! Hurrah! Average RTT is 123ms for this path. What? More than when we were using TATA? I suspect something is amiss in the handover from NIXI Delhi to Airtel.
$ tracepath 117.198.121.150
1: localhost 0.297ms pmtu 1500
1: airtel 0.903ms
1: airtel 0.891ms
2: airtel 1.050ms pmtu 1400
2: abts-north-static-072.220.160.122.airtelbroadband.in 40.439ms asymm 3
3: no reply
4: aes-static-005.68.144.59.airtel.in 33.364ms asymm 7
5: 14.141.116.89.static-Delhi.vsnl.net.in 32.105ms asymm 6
6: 172.31.17.5 84.003ms asymm 7
7: 14.141.139.146.static-chennai.vsnl.net.in 115.703ms asymm 8
8: 218.248.235.141 117.483ms asymm 9
9: 218.248.169.41 113.957ms
10: 218.248.169.41 118.894ms asymm 9
11: 117.198.121.150 150.196ms asymm 10
12: 117.198.121.150 154.696ms !H
Average RTT 118ms
Oh wait! Before we jump to the above conclusions, let's try the reverse journey, BSNL to Airtel:
# ip netns exec bsnl tracepath airtel-global
1: localhost 0.186ms pmtu 1500
1: bsnl 5.377ms
1: bsnl 5.675ms
2: bsnl 5.784ms pmtu 1400
2: 117.198.120.1 47.735ms
3: 218.248.169.38 68.787ms
4: 218.248.235.130 46.593ms asymm 5
5: 218.100.48.20 57.748ms asymm 6
6: 182.79.255.101 186.722ms asymm 8
7: no reply
8: no reply
9: no reply
10: abts-north-dynamic-007.3.68.182.airtelbroadband.in 155.566ms asymm 11
11: abts-north-dynamic-007.3.68.182.airtelbroadband.in 156.832ms !H
Number 5 is NIXI Delhi! Hurrah! Average RTT is 123ms for this path. What? More than when we were using TATA? I suspect something is amiss in the handover from NIXI Delhi to Airtel.