1.1.1.1 on Indian ISP Jio Gigafiber - routing to MRS, France?!

I just started using 1.1.1.1 here in India, in the Delhi area, and it seems something is really wrong with the routing to 1.1.1.1; I’m using Jio Gigafiber as my ISP.

Is this the ISP’s fault or something?

ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=52 time=127.480 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=52 time=135.022 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=52 time=129.374 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=52 time=128.393 ms

traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
1 router.asus.com (192.168.1.1) 2.101 ms 1.157 ms 1.044 ms
2 192.168.29.1 (192.168.29.1) 1.447 ms 2.170 ms 1.784 ms
3 100.103.164.1 (100.103.164.1) 5.262 ms 3.951 ms 2.925 ms
4 172.16.18.33 (172.16.18.33) 3.642 ms 5.833 ms 5.372 ms
5 172.16.18.33 (172.16.18.33) 5.397 ms
172.25.115.24 (172.25.115.24) 4.488 ms 4.425 ms
6 172.17.115.230 (172.17.115.230) 5.085 ms 4.203 ms 5.710 ms
7 172.17.115.225 (172.17.115.225) 5.976 ms
172.17.115.229 (172.17.115.229) 5.195 ms 6.353 ms
8 172.16.16.11 (172.16.16.11) 31.422 ms
172.26.40.64 (172.26.40.64) 32.174 ms
172.16.16.11 (172.16.16.11) 28.969 ms
9 172.16.16.11 (172.16.16.11) 31.281 ms
172.16.18.32 (172.16.18.32) 33.427 ms
172.16.16.11 (172.16.16.11) 30.110 ms
10 172.16.1.207 (172.16.1.207) 32.643 ms 31.780 ms
172.16.2.113 (172.16.2.113) 28.844 ms
11 10.70.14.97 (10.70.14.97) 36.698 ms 30.128 ms
172.16.1.218 (172.16.1.218) 29.539 ms
12 103.198.140.60 (103.198.140.60) 30.580 ms 29.521 ms
103.198.140.164 (103.198.140.164) 28.187 ms
13 103.198.140.107 (103.198.140.107) 138.135 ms
103.198.140.29 (103.198.140.29) 136.616 ms 140.499 ms
14 103.198.140.54 (103.198.140.54) 134.515 ms
103.198.140.29 (103.198.140.29) 145.024 ms
103.198.140.27 (103.198.140.27) 133.675 ms
15 103.198.140.107 (103.198.140.107) 133.007 ms 143.236 ms 129.929 ms
16 one.one.one.one (1.1.1.1) 132.699 ms 132.309 ms
162.158.20.254 (162.158.20.254) 140.473 ms

The 1.1.1.1/help page confirms that the Cloudflare Datacenter being used is MRS.

Is this something I can fix at my router/machine level or unfortunately I have to bend over to the ISP?

A quick look through that route shows mostly private IP blocks (192., 172., 10.) The final two are an IP block originating in Singapore (103.) and an IP belonging to CloudFlare (162.). Did this just begin happening with the most recent firmware update from ASUS? If so, it may be partially to blame as I too have noticed an increase in routing IP to IP within my own ASUS router. I suspect this as a possibility due to that Singapore based IP.

Actually, this is a new router that I got yesterday, and while setting up figured might as well setup DNS properly this time, so I don’t have pre-Asus data to compare. That being said, the 172 blocks are most likely the ISP; the Asus router on the 192.168.1.x blocks connects on DHCP to my ISP’s modem (which is actually a router too) on the 192.168.29.x chain, and beyond that it’s the ISP. I’m not sure how Asus can influence that routing. :S

Due to the Terms set for Privacy / Data collection when the built in Trend Micro services are used or the remote connection is setup for connections from WAN (generally used when you’re outside of your LAN and need or want to fiddle with the router’s settings), ASUS collects information such as DNS queries, times when they’re performed, the connecting IPs etc. ASUS can very easily manipulate traffic routing - it’s not called a router for no reason. If you’ve not turned off the info page that appears when the WAN isn’t working, ASUS is manipulating your routing. As for the 172. addresses, they are private LAN addresses, not public IPs. You’ve got a Singapore public IP and a CloudFlare public IP (London based). I’m not sure how many routers you’ve set up in your residence, but multi-NAT setups would return your results. Private to private to private to public.

@intr0 - I know, but I don’t have any of these ASUS services turned on in my router. I only have two routers (192.168.29.1 is the second), so it’s multi-NAT, yes, but I don’t use the 172 range on my network. Also, the 172. addresses are probably in my ISP’s internal network -> JioFiber is notorious for more multi-NAT internally (for example, my public IP may or may not be shared with other people at a time).

Interestingly, things are now different (without me making changes); I am now pinging Chennai’s 1.1.1.1 server, which is in my country and much better at around 45ms. Looks like something is constantly going on at my ISP’s end.

traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
1 router.asus.com (192.168.1.1) 103.263 ms 1.190 ms 0.995 ms
2 192.168.29.1 (192.168.29.1) 1.709 ms 2.035 ms 7.917 ms
3 100.103.164.1 (100.103.164.1) 132.855 ms 3.925 ms 4.886 ms
4 172.16.18.33 (172.16.18.33) 6.480 ms 5.867 ms 146.801 ms
5 172.16.18.33 (172.16.18.33) 4.409 ms
172.25.115.24 (172.25.115.24) 5.285 ms 5.669 ms
6 172.17.115.226 (172.17.115.226) 5.626 ms 4.135 ms
172.17.115.230 (172.17.115.230) 5.431 ms
7 172.17.115.229 (172.17.115.229) 5.183 ms
172.17.115.225 (172.17.115.225) 6.179 ms 6.014 ms
8 172.26.40.64 (172.26.40.64) 142.924 ms 30.186 ms
172.16.16.11 (172.16.16.11) 148.737 ms
9 172.25.115.25 (172.25.115.25) 31.506 ms
172.25.115.27 (172.25.115.27) 30.660 ms
172.25.115.25 (172.25.115.25) 143.749 ms
10 * 172.16.1.207 (172.16.1.207) 37.629 ms
49.44.18.38 (49.44.18.38) 29.483 ms
11 10.70.14.97 (10.70.14.97) 33.948 ms 32.026 ms
172.16.1.220 (172.16.1.220) 29.363 ms
12 * * *
13 172.69.104.254 (172.69.104.254) 51.679 ms 50.251 ms 57.557 ms
14 one.one.one.one (1.1.1.1) 45.995 ms 43.931 ms 49.041 ms

This is better, but still not the best, given https://www.cloudflarestatus.com/ does state there is a data center in my own city, New Delhi. oh well. :frowning:

Unfortunately, ISPs are, IMO, malicious entities that exist to drain one’s money in exchange for a shabby product. I wish you the best.