Reliability of 1.1.1.1 and 1.0.0.1


#1

First I wanted to say thank you for setting up Cloudflare DNS. Your service allows me to securely browse an internet as intended by the authors of websites, rather than another created by those that hijack queries and redirect traffic.

Through regular mis-configuration or otherwise, I find myself frequently unable to reach 1.0.0.1 / 1.1.1.1.

Are you able to assist in making this service more reliable for my ISP?

Example traceroute below:

traceroute to 1.0.0.1 (1.0.0.1), 30 hops max, 60 byte packets
1 58.32.4.1 (58.32.4.1) 2.722 ms 2.471 ms 2.536 ms
2 101.95.91.81 (101.95.91.81) 2.923 ms 101.95.91.77 (101.95.91.77) 2.792 ms 101.95.91.85 (101.95.91.85) 2.629 ms
3 59.43.77.153 (59.43.77.153) 3.135 ms 3.025 ms 101.95.88.61 (101.95.88.61) 3.010 ms
4 * * *
5 * * *
6 * * *


#2

Who is your ISP?

What do you see here?


#3

% Information related to ‘58.32.0.0/16AS4809’

route: 58.32.0.0/16
descr: China Telecom
descr: ShangHai province
origin: AS4809
mnt-by: MAINT-CHINANET
last-modified: 2008-09-04T07:54:55Z
source: APNIC

I don’t want to be cruel, but… does 1.1.1.1 generally work from the CT backbone? :thinking:


#4

I doubt it works from Mainland China… Especially reliably…


#5

The details you asked for are:

Connected to 1.1.1.1 Yes
Using DNS over HTTPS (DoH) No
Using DNS over TLS (DoT) Yes
AS Name Cloudflare
AS Number 13335
Cloudflare Data Center HKG

#6

1.1.1.1 is unreliable from Verizon FiOS in Massachusetts hitting EWR. I wouldn’t expect it to ever work well from mainland China, but I’m a bit surprised I’ve had so many issues in the US. At bad times, ~5% of queries will fail; at good times, it’ll be 1-2%. That might not seem like a lot, but it’s enough to be pretty annoying while browsing the web.

(Yes, I know I’m using 8.8.8.8 at the moment.)