Traceroute to 1.1.1.1 completes successfully, with the following:
tracert 1.1.1.1
Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms Router.home [10.29.0.1]
2 2 ms 2 ms 2 ms 202.163.100.245
3 4 ms * * 202.163.100.105
4 2 ms 1 ms 4 ms 202.163.100.66
5 3 ms 2 ms 2 ms 119.159.240.53
6 5 ms 2 ms 3 ms khi275.p01.pie.net.pk [221.120.251.201]
7 3 ms 2 ms 2 ms rwp44.pie.net.pk [221.120.248.54]
8 21 ms 19 ms 20 ms 10.253.4.17
9 20 ms 19 ms 20 ms 10.253.8.13
10 18 ms 18 ms 19 ms one.one.one.one [1.1.1.1]
Trace complete.
Ping works fine too.
Finally, on my mobile data, 1.1.1.1 loads just fine, so it seems an ISP issue.
I’m facing this issue not only at home, but also at work. My ISP at home and work are same. StormFiber they are owned by Cybernet.
I’m thinking of writing to my ISP, any assistance in what to provide would be quite helpful.
Would also be helpful is someone from Cloudflare writes to them at [email protected] and [email protected]
Thank you for the response. Here’s a little update, I emailed my ISP
Dear Sir/Madam
I have problems connecting to my DNS provider, Cloudflare, at their IP Address https://1.1.1.1
Their other IP address at 1.0.0.1 works just fine though.
I can confirm that this issue does not occur when on mobile data and the DNS resolver and the webpage at the IP Address 1.1.1.1 work just fine. The same used to work fine on StormFiber up until a week ago.
Kindly look into the issue and fix it at the earliest.
Yours sincerely
I got a call back from them in a couple of minutes (even though it was quite late in the evening). They requested access to my PC, which I gave them, and the guy downloaded a couple of utilities and ran them through command prompt, a number of ports for 1.1.1.1 were blocked, while the same were open for 1.0.0.1
Consequently, the guy insisted that the problem was at Cloudflare’s end.
I told him to open 1.1.1.1 on his own mobile phone using his data network, and it loaded for him as well.
He apologized and told me that he’ll escalate the matter. I got this email later:
Dear Customer,
With reference to our verbal discussion, this is to inform you that your concern has been noted and forwarded to Network Operations Team (NOC) for initial assessment. We will update you once we will receive any update from them.
Name
Engineer
tracert 1.0.0.1
Tracing route to one.one.one.one [1.0.0.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Router.home [10.29.0.1]
2 3 ms 7 ms 1 ms 202.163.100.245
3 * 8 ms * 202.163.100.105
4 3 ms 2 ms 2 ms 202.163.100.66
5 3 ms 3 ms 2 ms 119.159.240.53
6 6 ms 3 ms 7 ms khi77.pie.net.pk [221.120.251.205]
7 3 ms 3 ms 3 ms rwp44.pie.net.pk [221.120.251.101]
8 3 ms 3 ms 3 ms static.khi77.pie.net.pk [221.120.200.3]
9 3 ms 2 ms 4 ms one.one.one.one [1.0.0.1]
Trace complete.
also:
tracert 1.1.1.1
Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:
1 <1 ms <1 ms 1 ms Router.home [10.29.0.1]
2 2 ms 3 ms 1 ms 202.163.100.245
3 9 ms 4 ms 4 ms 202.163.100.105
4 2 ms 1 ms 2 ms 202.163.100.66
5 2 ms 2 ms 2 ms 119.159.240.53
6 6 ms 3 ms 3 ms khi275.p01.pie.net.pk [221.120.251.201]
7 3 ms 2 ms 2 ms rwp44.pie.net.pk [221.120.248.54]
8 20 ms 19 ms 20 ms 10.253.4.17
9 21 ms 19 ms 19 ms 10.253.8.13
10 18 ms 19 ms 18 ms one.one.one.one [1.1.1.1]
It appears to be some ISP related issue. After writing to my ISP personally, and getting other customers to do the same, including some corporate ones, the matter was fixed.