Cloudflare Peerings in India


#1

Hello Cloudflare Team,

Majority of the local broadband providers uses TATA Communications (AS4755) as their primary ISP and Bharti Airtel (AS9498) / Vodafone (AS55410) as their backup. The reason I can say this is because I am coming from ISP as well as enterprise background and have worked there as Network Engineer.

The problem is, since Cloudflare is peering with TATA Communications (America) (AS6453), all ISP’s send traffic to AS4755 and then AS4755 handsoff traffic to AS6453 and since AS6453 is not present in India, the nearest peering point between Cloudflare and AS6453 is in Singapore. Hence even though Cloudflare is present in India, it traverses all the way to Singapore to reach Cloudflare.

This traceroute explains it:

~$  traceroute cloudflare.com
traceroute: Warning: cloudflare.com has multiple addresses; using 198.41.215.162
traceroute to cloudflare.com (198.41.215.162), 64 hops max, 52 byte packets
 1  192.168.168.1 (192.168.168.1)  2.489 ms  1.153 ms  1.056 ms
 2  10.242.0.1 (10.242.0.1)  2.020 ms  2.140 ms  1.973 ms
 3  broadband.actcorp.in (202.83.20.205)  2.342 ms  2.285 ms  2.148 ms
 4  broadband.actcorp.n (202.83.26.1)  2.391 ms  35.521 ms  2.540 ms
 5  10.139.105.1 (10.139.105.1)  2.074 ms  2.134 ms  1.992 ms
 6  14.141.145.5.static-bangalore.vsnl.net.in (14.141.145.5)  2.832 ms  3.036 ms  2.586 ms
 7  172.31.244.45 (172.31.244.45)  8.449 ms
    172.29.251.34 (172.29.251.34)  10.219 ms
    172.31.244.45 (172.31.244.45)  7.865 ms
 8  ix-ae-4-2.tcore2.cxr-chennai.as6453.net (180.87.37.1)  9.794 ms  9.474 ms  8.756 ms
 9  if-ae-6-2.tcore2.svw-singapore.as645(.net (180.87.37.14)  41.458 ms
    if-ae-10-2.tcore2.svw-singapore.as6453.net (180.87.37.65)  41.736 ms
    if-ae-6-2.tcore2.svw-singapore.as6453.net (180.87.37.14)  40.076 ms
10  if-ae-2-2.tcore1.svw-singapore.as645(.net (180.87.12.1)  40.692 ms  42.684 ms  42.436 ms
11  if-ae-11-2.thar1.svq-singapore.as6453.net (180.87.98.37)  42.552 ms  40.922 ms  42.322 ms
12  120.29.214.90 (120.29.214.90)  40.838 ms  41.303 ms  39.642 ms
13  198.41.215.162 (198.41.215.162)  41.576 ms  41.885 ms  41.212 ms

~$ traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
 1  192.168.168.1 (192.168.168.1)  1.834 ms  1.039 ms  0.991 ms
 2  10.242.0.1 (10.242.0.1)  2.397 ms  3.308 ms  2.339 ms
 3  broadband.actcorp.in (202.83.20.205)  3.006 ms  2.844 ms  2.627 ms
 4  broadband.actcorp.in (202.83.26.1)  2.458 ms  2.453 ms  2.731 ms
 5  10.139.105.1 (10.139.105.1)  19.198 ms  6.255 ms  2.216 ms
 6  14.141.145.5.static-bangalore.vsnl.net.in (14.141.145.5)  3.954 ms  5.035 ms  4.209 ms
 7  172.31.29.245 (172.31.29.245)  21.615 ms  15.498 ms  15.146 ms
 8  172.23.78.234 (172.23.78.234)  18.898 ms  19.063 ms  14.777 ms
 9  * * *
10  115.114.85.237 (115.114.85.237)  18.769 ms  18.873 ms  22.608 ms
11  if-ae-16-2.tcore1.svw-singapore.as6453.net (180.87.12.226)  69.551 ms  67.010 ms  61.327 ms
12  if-ae-11-2.thar1.svq-singapore.as6453.net (180.87.98.37)  61.260 ms  76.293 ms  77.903 ms
13  120.29.214.90 (120.29.214.90)  71.795 ms  60.645 ms  64.661 ms
14  1dot1dot1dot1.cloudflare-dns.com (1.1.1.1)  61.137 ms  61.511 ms  61.614 ms

These traceroutes are from ISP TATA having AS4755. Below is the traceroute from ISP Bharti Airtel with AS9498:

~$ traceroute cloudflare.com
traceroute: Warning: cloudflare.com has multiple addresses; using 198.41.215.162
traceroute to cloudflare.com (198.41.215.162), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  5.610 ms  1.893 ms  2.336 ms
 2  abts-kk-dynamic-1.72.76.171.airtelbroadband.in (171.76.72.1)  14.703 ms  11.735 ms  13.202 ms
 3  125.18.117.241 (125.18.117.241)  19.134 ms
    125.21.0.189 (125.21.0.189)  9.708 ms  14.707 ms
 4  182.79.255.169 (182.79.255.169)  22.622 ms
    182.79.239.161 (182.79.239.161)  21.359 ms
    182.79.176.209 (182.79.176.209)  22.546 ms
 5  125.21.167.7 (125.21.167.7)  21.589 ms
    182.79.205.121 (182.79.205.121)  20.177 ms
    182.79.223.58 (182.79.223.58)  27.502 ms
 6  198.41.215.162 (198.41.215.162)  24.959 ms  31.213 ms
    182.79.237.156 (182.79.237.156)  21.051 ms

~$ traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  1.987 ms  1.881 ms  1.721 ms
 2  abts-kk-dynamic-1.72.76.171.airtelbroadband.in (171.76.72.1)  13.655 ms  13.679 ms  14.432 ms
 3  * 125.21.0.149 (125.21.0.149)  99.590 ms
    125.17.21.53 (125.17.21.53)  13.332 ms
 4  * 182.79.237.158 (182.79.237.158)  33.500 ms
    182.79.208.156 (182.79.208.156)  21.941 ms
 5  182.79.191.125 (182.79.191.125)  71.073 ms
    182.79.223.58 (182.79.223.58)  19.899 ms
    125.21.167.5 (125.21.167.5)  20.797 ms
 6  182.79.237.156 (182.79.237.156)  21.487 ms
    182.79.205.84 (182.79.205.84)  19.695 ms
    1dot1dot1dot1.cloudflare-dns.com (1.1.1.1)  18.918 ms

Here everyone can clearly see the difference of ~20-50ms between 2 major ISP’s in India.

The story with Vodafone is totally different, Vodafone prefers AS1273 which is Cable and Wireless as they have acquired them. Hence, if Vodafone doesn’t find any direct peering with content provider’s, it doesn’t prefers other major ISP’s in India, rather defaults traffic to AS1273 and since AS1273 is not present in India, it again traverses across continent to reach something which was present locally regionwise.

Can Cloudflare Network Engineering team do something about this?

Thanks,
Mayur Patel


#2

Hi @fameroxx,

Sorry if no one got back to you earlier.

As far as I can tell everything works on your end, right? It changes only the latency based on the provider?
The usual cause for this is that some providers do not peer (do not want to, usually) locally with Cloudflare or prefer additional routes that bring everything to Singapore.

The problem is well explained, but would you mind following this guide with the missing command?

Would love to get a reply from the networking team via @cscharff, but I think I would guess it boils down to the previous points…


#3

This topic was automatically closed after 14 days. New replies are no longer allowed.