Jio bad routing to Vultr Delhi Servers

[sahshivam]

This is Jio to Vultr Delhi, while I'm like less than 300Km from Delhi

1 <1 ms <1 ms <1 ms reliance.reliance [192.168.29.1]
2 7 ms 7 ms 8 ms 10.241.120.1
3 12 ms 13 ms 13 ms
4 12 ms 12 ms 12 ms
5 12 ms 12 ms 11 ms
6 14 ms 13 ms 13 ms
7 12 ms 13 ms 13 ms
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 16 ms 15 ms 15 ms 115.110.210.37.static-Delhi.vsnl.net.in [115.110.210.37]
12 * * * Request timed out.
13 63 ms 60 ms 61 ms 115.117.120.186
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 54 ms 53 ms 54 ms 139.84.162.104.vultrusercontent.com [139.84.162.104]

And here's to Vultr Mumbai servers

1 <1 ms <1 ms <1 ms reliance.reliance [192.168.29.1]
2 8 ms 7 ms 7 ms
3 11 ms 11 ms 13 ms
4 13 ms 11 ms 18 ms
5 11 ms 11 ms 11 ms
6 12 ms 13 ms 13 ms
7 12 ms 12 ms 13 ms 192.168.41.74
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 16 ms 16 ms 16 ms 115.110.210.37.static-Delhi.vsnl.net.in [115.110.210.37]
12 * * * Request timed out.
13 37 ms 37 ms 38 ms 121.241.56.170
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 44 ms 43 ms 45 ms 65.20.66.100.vultrusercontent.com [65.20.66.100]

Which again is 300Km + whatever distance is between Delhi and Mumbai..

You can find the IP's here "Looking Glass - Vultr.com"

I was wondering if moving to static IP on Jio will make my pings better, as there are a lot of hops involved for now..like I feel lucky if I get under 55ms ping on CS, while it used to be around 35-45ms with BSNL and is at times 47-57ms with AirTel.. Jio is consistent with giving me a lobby with close to 60-70ms ping.

 

[Lolita_Magnum]

There is often more in-between than the distance between the nodes, i.e., you and the Vultr server itself.

Looking through, AS20473 The Constant Company, LLC it seems they (Jio) do not directly peer with Vultr unlike Tata and Bharti, and this deal is likely a transit bought by Vultr itself than an open-peering policy.

Judging from the traceroute you have shared below, Jio has already handed-off your packet to Tata i.e., 115.110.210.37 and there is nothing more Jio could do.
You can try fighting with Tata over this, but I doubt they'd listen from a non-direct consumer.

The reverse trace from Vultr up to the Tata/Jio peering node [115.110.210.37] seems fine, so the likely thing to do would be to do reverse trace yourself with your Public IP for further investigation?

 1  * * *
 2  100.100.100.1 (100.100.100.1)  0.200 ms  0.181 ms  0.218 ms
 3  10.102.0.85 (10.102.0.85)  6.288 ms 10.102.0.89 (10.102.0.89)  0.905 ms 10.102.0.85 (10.102.0.85)  6.246 ms
 4  10.102.0.9 (10.102.0.9)  0.244 ms  0.228 ms 10.102.0.5 (10.102.0.5)  0.194 ms
 5  115.117.120.185 (115.117.120.185)  1.588 ms  1.562 ms  1.554 ms
 6  * * *
 7  * * *
 8  172.23.185.30 (172.23.185.30)  2.987 ms * *

As always, if it is critical, you can also change your ISP. This is Airtel from Mumbai to Delhi DC.

  2.|-- nsg-corporate-9.210.186.122.airtel.in  0.0%     5    9.2   5.2   4.0   9.2   2.3
  3.|-- 182.79.243.60                          0.0%     5   30.8  31.9  28.6  39.5   4.3
  4.|-- 122.184.140.154                        0.0%     5   28.3  28.2  28.2  28.4   0.1
  5.|-- 10.102.0.14                            0.0%     5   29.5  29.9  29.1  32.1   1.3
  6.|-- 10.102.0.86                            0.0%     5   27.6  27.4  27.3  27.6   0.1
  7.|-- ???                                   100.0     5    0.0   0.0   0.0   0.0   0.0
  8.|-- 139.84.162.104.vultrusercontent.com    0.0%     5   28.9  28.9  28.7  29.0   0.1

 

[sahshivam]

I did notice the VSNL one, I was wondering whether having a static IP changes things, with different peering maybe.

As for AirTel I used to get 9-11ms on Delhi servers, but few weeks back it has changed to 17-19ms at minimum on the static IP

 

[Lolita_Magnum]

An IP address should not affect routing unless it is announced in an exceptional way or have routing rules, which is rare.

The above case more seems to be something to be resolved on Tata's end or Vultr itself, depending on how they are routing back.

If you have a service with them, I guess you can request them to re-route via their Airtel Backbone and see if that helps.