300ms to Google services when using 1.1.1.1

#1

Here’s what happened: recently the FOR location was activated, with that I switched to 1.1.1.1 since I live on the same city and my ISP’s DNS is a bit… Unreliable. Then I started noticing huge slowdowns on Google services like Search, Photos and Drive.

I didn’t use Google’s or Cloudflare’s DNS because the closest location is/was GRU; which is 50ms away, and sometimes Google’s can be as high as 70.

Here’s some data:

ISP DNS

PING google.com (172.217.162.110) 56(84) bytes of data.
64 bytes from gru14s07-in-f14.1e100.net (172.217.162.110): icmp_seq=1 ttl=52 time=46.2 ms
64 bytes from gru14s07-in-f14.1e100.net (172.217.162.110): icmp_seq=2 ttl=52 time=45.5 ms
64 bytes from gru14s07-in-f14.1e100.net (172.217.162.110): icmp_seq=3 ttl=52 time=43.6 ms
64 bytes from gru14s07-in-f14.1e100.net (172.217.162.110): icmp_seq=4 ttl=52 time=46.1 ms
google.com ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 43.636/45.384/46.256/1.054 ms

traceroute to google.com (172.217.162.110), 30 hops max, 60 byte packets
1 192.168.50.1 (192.168.50.1) 0.497 ms 0.478 ms 0.375 ms
2 172.16.254.1 (172.16.254.1) 4.240 ms 4.151 ms 4.024 ms
3 172.16.1.1 (172.16.1.1) 3.955 ms 3.863 ms 3.986 ms
4 172.16.0.1 (172.16.0.1) 3.902 ms 3.817 ms 3.830 ms
5 * * *
6 * * *
7 10.5.3.93 (10.5.3.93) 12.232 ms 5.897 ms 5.590 ms
8 10.5.3.109 (10.5.3.109) 3.820 ms 3.729 ms 3.554 ms
9 * * *
10 10.5.4.58 (10.5.4.58) 44.503 ms 44.379 ms 45.924 ms
11 74.125.32.22 (74.125.32.22) 46.450 ms 46.425 ms 44.950 ms
12 74.125.243.1 (74.125.243.1) 46.544 ms 45.586 ms 45.557 ms
13 216.239.51.225 (216.239.51.225) 44.152 ms 216.239.50.113 (216.239.50.113) 44.123 ms 216.239.51.225 (216.239.51.225) 44.378 ms
14 gru14s07-in-f14.1e100.net (172.217.162.110) 43.837 ms 46.573 ms 44.398 ms

Google’s DNS:

PING google.com (172.217.28.238) 56(84) bytes of data.
64 bytes from gru14s05-in-f14.1e100.net (172.217.28.238): icmp_seq=1 ttl=52 time=45.1 ms
64 bytes from gru14s05-in-f14.1e100.net (172.217.28.238): icmp_seq=2 ttl=52 time=46.3 ms
64 bytes from gru14s05-in-f14.1e100.net (172.217.28.238): icmp_seq=3 ttl=52 time=43.6 ms
64 bytes from gru14s05-in-f14.1e100.net (172.217.28.238): icmp_seq=4 ttl=52 time=45.5 ms
google.com ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 43.606/45.160/46.355/1.000 ms

traceroute to google.com (172.217.28.238), 30 hops max, 60 byte packets
1 192.168.50.1 (192.168.50.1) 0.534 ms 0.459 ms 0.415 ms
2 172.16.254.1 (172.16.254.1) 5.175 ms 5.088 ms 4.999 ms
3 172.16.1.1 (172.16.1.1) 4.927 ms 4.769 ms 4.677 ms
4 172.16.0.1 (172.16.0.1) 4.861 ms 4.777 ms 4.687 ms
5 * * *
6 * * *
7 10.5.3.93 (10.5.3.93) 3.354 ms 13.728 ms 6.681 ms
8 10.5.3.109 (10.5.3.109) 5.383 ms 5.292 ms 5.316 ms
9 10.5.3.110 (10.5.3.110) 7.651 ms * *
10 10.5.4.58 (10.5.4.58) 46.084 ms 45.899 ms 44.832 ms
11 74.125.32.22 (74.125.32.22) 45.197 ms 45.108 ms 44.259 ms
12 74.125.243.65 (74.125.243.65) 45.605 ms 74.125.243.1 (74.125.243.1) 47.205 ms 47.771 ms
13 209.85.246.137 (209.85.246.137) 47.356 ms 209.85.250.51 (209.85.250.51) 47.136 ms 47.109 ms
14 gru14s05-in-f14.1e100.net (172.217.28.238) 45.847 ms 45.792 ms 45.684 ms

Basically the same, right? Here’s 1.1.1.1:

PING google.com (172.217.160.78) 56(84) bytes of data.
64 bytes from tsa01s09-in-f14.1e100.net (172.217.160.78): icmp_seq=1 ttl=46 time=296 ms
64 bytes from tsa01s09-in-f14.1e100.net (172.217.160.78): icmp_seq=2 ttl=46 time=321 ms
64 bytes from tsa01s09-in-f14.1e100.net (172.217.160.78): icmp_seq=3 ttl=46 time=295 ms
64 bytes from tsa01s09-in-f14.1e100.net (172.217.160.78): icmp_seq=4 ttl=46 time=297 ms
google.com ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 295.522/302.704/321.246/10.723 ms

traceroute to google.com (172.217.160.78), 30 hops max, 60 byte packets
1 192.168.50.1 (192.168.50.1) 0.586 ms 0.530 ms 0.497 ms
2 172.16.254.1 (172.16.254.1) 5.215 ms 5.133 ms 5.026 ms
3 172.16.1.1 (172.16.1.1) 4.941 ms 4.824 ms 4.741 ms
4 172.16.0.1 (172.16.0.1) 4.919 ms 4.826 ms 4.744 ms
5 * * *
6 * * *
7 10.5.3.93 (10.5.3.93) 6.290 ms 3.456 ms 3.556 ms
8 10.5.3.109 (10.5.3.109) 2.153 ms 2.148 ms 2.048 ms
9 10.5.3.110 (10.5.3.110) 4.245 ms 4.729 ms 4.008 ms
10 10.5.4.58 (10.5.4.58) 43.211 ms 43.075 ms 43.109 ms
11 74.125.32.22 (74.125.32.22) 44.042 ms 43.855 ms 43.159 ms
12 108.170.245.162 (108.170.245.162) 43.558 ms 108.170.245.130 (108.170.245.130) 46.722 ms 46.708 ms
13 172.253.51.197 (172.253.51.197) 121.109 ms 121.075 ms 120.905 ms
14 108.170.230.224 (108.170.230.224) 147.064 ms 146.699 ms 146.887 ms
15 209.85.143.134 (209.85.143.134) 148.236 ms 152.183 ms 149.579 ms
16 * * *
17 209.85.249.63 (209.85.249.63) 292.807 ms 292.712 ms 293.287 ms
18 * 74.125.37.143 (74.125.37.143) 301.336 ms *
19 72.14.239.100 (72.14.239.100) 300.161 ms 300.206 ms 300.122 ms
20 108.170.244.33 (108.170.244.33) 298.937 ms 298.754 ms 298.763 ms
21 209.85.245.65 (209.85.245.65) 299.551 ms 299.469 ms 209.85.243.197 (209.85.243.197) 300.051 ms
22 tsa01s09-in-f14.1e100.net (172.217.160.78) 297.370 ms 297.941 ms 297.323 ms

TSA is in Taiwan, which is over 15000 KM from me.

0 Likes