Old but interesting question. I see it's un-answered since last 4 years.
Your trace link is not visible anymore, so I cannot give exact answer for your case but in general:
BGP routes by default may not reflect actual geography. So imagine route from Delhi to London may have two paths:
1. Delhi > Mumbai > Marseille > London
2. Delhi > Singapore > Los Angeles > London
BGP cannot tell that #1 is better unless special attributes called BGP communities are used. They can in theory ask upstream to announce them routes containing BGP communities. These would tell where the upstream has learnt the route. While it may not be 100% true, but likely valid for 99% cases i.e if Jio's upstream is learning a route in EU, it would for a EU customer (exceptions: Indian routes, African routes can also be tagged as EU customer). They can de-prefer these routes from the American upstream and de-prefer EU routes from Singapore upstream as well. (Same way de-pref Asia routes from EU and US). All this requires config change and at scale of Jio - it would be bit of internal bureaucratic process by engineers to justify why they are tweaking things. When 90% of their traffic terminates within India, many times these things are not the priority list. Often such changes happen when high paying enterprise customers request so.
