Can't reach 1.1.1.1 from Argentina - ISP: Claro Argentina

I can’t reach 1.1.1.1.

Details:

Diagnostic tool report: https://cloudflare-dns.com/help/#eyJpc0NmIjoiTm8iLCJpc0RvdCI6Ik5vIiwiaXNEb2giOiJObyIsInJlc29sdmVySXAtMS4xLjEuMSI6Ik5vIiwicmVzb2x2ZXJJcC0xLjAuMC4xIjoiWWVzIiwicmVzb2x2ZXJJcC0yNjA2OjQ3MDA6NDcwMDo6MTExMSI6Ik5vIiwicmVzb2x2ZXJJcC0yNjA2OjQ3MDA6NDcwMDo6MTAwMSI6Ik5vIiwiZGF0YWNlbnRlckxvY2F0aW9uIjoiRVpFIiwiaXNXYXJwIjoiTm8iLCJpc3BOYW1lIjoiQ2xhcm8gQXJnZW50aW5hIiwiaXNwQXNuIjoiMTkwMzcifQ==

traceroute 1.1.1.1 (it never ends)
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
1 192.168.100.1 (192.168.100.1) 2.218 ms 1.190 ms 2.582 ms
2 host2.186-12-144.telmex.net.ar (186.12.144.2) 5.373 ms 5.394 ms 4.924 ms
3 10.2.200.190 (10.2.200.190) 6.677 ms
10.2.200.194 (10.2.200.194) 6.781 ms
10.2.200.190 (10.2.200.190) 17.969 ms
4 10.2.201.117 (10.2.201.117) 7.201 ms
10.2.201.125 (10.2.201.125) 9.144 ms 6.919 ms
5 10.2.186.117 (10.2.186.117) 6.427 ms
10.2.186.121 (10.2.186.121) 6.473 ms
10.2.186.117 (10.2.186.117) 6.288 ms
6 be4-2-cf223-br-04-bsas.claro.com.ar (131.100.186.102) 8.984 ms 7.368 ms 5.969 ms
7 be4-1-cf223-igw-01-bsas.claro.com.ar (131.100.186.97) 6.628 ms 6.251 ms 6.644 ms
8 * * *
9 * * *
10 10.2.200.189 (10.2.200.189) 8.903 ms 7.832 ms
10.2.200.193 (10.2.200.193) 7.200 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *

traceroute 1.0.0.1
traceroute to 1.0.0.1 (1.0.0.1), 64 hops max, 52 byte packets
1 192.168.100.1 (192.168.100.1) 2.512 ms 1.878 ms 1.387 ms
2 host2.186-12-144.telmex.net.ar (186.12.144.2) 5.250 ms 5.039 ms 4.936 ms
3 10.2.200.190 (10.2.200.190) 6.682 ms 6.985 ms
10.2.200.194 (10.2.200.194) 7.035 ms
4 10.2.201.125 (10.2.201.125) 6.712 ms 7.138 ms 6.684 ms
5 10.2.186.121 (10.2.186.121) 5.944 ms
10.2.186.117 (10.2.186.117) 6.654 ms 6.630 ms
6 be4-2-cf223-br-04-bsas.claro.com.ar (131.100.186.102) 12.895 ms 6.752 ms 6.475 ms
7 200.0.17.181 (200.0.17.181) 7.699 ms 7.542 ms 7.323 ms
8 one.one.one.one (1.0.0.1) 6.685 ms 6.933 ms 7.167 ms

dig +short CHAOS TXT id.server @1.0.0.1
“EZE”

dig +tcp @1.0.0.1 id.server CH TXT
; <<>> DiG 9.10.6 <<>> +tcp @1.0.0.1 id.server CH TXT
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13881
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;id.server. CH TXT

;; ANSWER SECTION:
id.server. 0 CH TXT “EZE”

;; Query time: 8 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Fri Oct 16 12:10:09 -03 2020
;; MSG SIZE rcvd: 43

Hi, sorry about that. We’ll try to email Claro. If you can email them as a customer that would be probably even better.

@elmatyf Hi, we got a response from Claro that there’s no issue at the moment. Does it work for you now?

Hi, I just checked again and it seems now it’s working. I’m going to switch my DNS settings back to 1.1.1.1

Thanks!