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 126.96.36.199 / 188.8.131.52.
Are you able to assist in making this service more reliable for my ISP?
Example traceroute below:
traceroute to 184.108.40.206 (220.127.116.11), 30 hops max, 60 byte packets
1 18.104.22.168 (22.214.171.124) 2.722 ms 2.471 ms 2.536 ms
2 126.96.36.199 (188.8.131.52) 2.923 ms 184.108.40.206 (220.127.116.11) 2.792 ms 18.104.22.168 (22.214.171.124) 2.629 ms
3 126.96.36.199 (188.8.131.52) 3.135 ms 3.025 ms 184.108.40.206 (220.127.116.11) 3.010 ms
4 * * *
5 * * *
6 * * *
Who is your ISP?
What do you see here?
% Information related to ‘18.104.22.168/16AS4809’
descr: China Telecom
descr: ShangHai province
I don’t want to be cruel, but… does 22.214.171.124 generally work from the CT backbone?
I doubt it works from Mainland China… Especially reliably…
The details you asked for are:
|Connected to 126.96.36.199
|Using DNS over HTTPS (DoH)
|Using DNS over TLS (DoT)
|Cloudflare Data Center
188.8.131.52 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 184.108.40.206 at the moment.)