Another Case Of Bad Routing: Vi and Airtel

[albonycal]

Another Case Of Bad Routing: Vi and Airtel | Shrirang Kahale

Abysmal routing between Airtel and Vi

blog.shrirangkahale.com

 

[nishantt6969]

not only with you, I am also facing this issue, using warp+ helps in most of the cases.

 

[albonycal]

Vi seems to have horrible routes everywhere, even their routes to cloudflare are abysmal

 

[Lolita_Magnum]

There seems to be some internal conflicts, but except with Jio.
Vi is peering with Airtel only at Delhi and Bangalore. Which causes extreme performance penalty and latency hike. This also seems to be true with Tata.
I get about 90-120ms of latency when I try to connect to an Airtel IP in the same geolocation from Vodafone cellular and vice-versa.

The following traceroute is with >> ooklatestshslab01.live.vodafone.in [Vi India Mumbai Test Server]
Tata
1  115.113.165.21  3.230 ms  4.771 ms  *
2  14.142.18.74  67.719 ms  66.096 ms  66.710 ms
3  223.196.6.237  30.095 ms  29.994 ms  *
4  223.196.1.217  35.810 ms  34.148 ms  35.717 ms
5  122.15.65.161  36.584 ms  38.032 ms  36.138 ms
6  *  *  *
7  42.106.166.136  56.958 ms !C  65.278 ms !C  57.161 ms !C

Airtel
1  116.119.33.179  5.726 ms  4.952 ms  5.100 ms
2  125.22.42.238  6.910 ms  6.536 ms  6.312 ms
3  223.196.24.62  6.706 ms  6.322 ms  223.196.24.70  6.789 ms
4  223.196.1.221  33.614 ms  33.853 ms  33.856 ms
5  122.15.65.163  32.459 ms  33.208 ms  32.955 ms
6  *  *  *
7  42.106.166.136  33.336 ms !C  33.509 ms !C  33.646 ms !C

Ignore the ISP; it's not Cloudflare.

 

[albonycal]

Yeah it routes to Delhi for me for the VoWiFi, but through limelight networks for some reason

 

[albonycal]

IPv4 routes seem to be better, maybe the only peer over IPv4? I need to check

This is the speedtest server:

➜ traceroute -A ooklatestshslab01.live.vodafone.in
traceroute to ooklatestshslab01.live.vodafone.in (42.106.166.136), 30 hops max, 60 byte packets
 1  _gateway (10.0.1.1) [*]  0.205 ms  0.158 ms  0.161 ms
 2  * * *
 3  125.18.48.121 (125.18.48.121) [AS9498]  13.873 ms dsl-ncr-dynamic-093.88.16.125.airtelbroadband.in (125.16.88.93) [AS9498]  13.886 ms  13.907 ms
 4  182.79.178.106 (182.79.178.106) [*]  13.973 ms 116.119.49.248 (116.119.49.248) [AS55536]  14.548 ms 116.119.33.179 (116.119.33.179) [AS55536]  14.425 ms
 5  aes-static-238.42.22.125.airtel.in (125.22.42.238) [AS24560/AS9498]  15.303 ms  15.756 ms  15.769 ms
 6  223.196.24.22 (223.196.24.22) [AS55644]  15.873 ms 223.196.20.48 (223.196.20.48) [AS55644]  15.831 ms 223.196.24.70 (223.196.24.70) [AS55644]  15.715 ms
 7  223.196.1.221 (223.196.1.221) [AS55644]  41.585 ms  41.269 ms  41.625 ms
 8  122.15.65.163 (122.15.65.163) [AS55410]  44.161 ms  43.989 ms  43.971 ms
 9  42.106.166.136 (42.106.166.136) [AS38266]  41.920 ms !X  41.903 ms !X  42.331 ms !X

 

[panks21]

Off topic
The prefix in your traceroute output at step 4 (116.119.49.248 and others) belongs to Airtel AS9498 and not AS55536 as mentioned.
Not sure why the trace is showing incorrect AS numbers.

 

[albonycal]

Yeah I have no idea why it does that, also is the latency high across the whole Vi network? like to everything? I was getting 100ms+ to google? The hop to local Vi gateway was ~ 30ms, so that's fine