Can't connect to 1.1.1.1 from Lima, Peru


#1

Hi,

Since 3 days I can’t connect anymore to 1.1.1.1. 1.0.0.1 works well. Here is my dig result. Regards.

dig example.com 21 @1.1.1.1
; <<>> DiG 9.11.3-RedHat-9.11.3-4.fc27 <<>> example.com 21 @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31001
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;exampl e . com. IN A

;; ANSWER SECTION:
example . com. 10197 IN A 93.184.216.34

;; Query time: 191 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: lun. avril 23 12:11:06 -05 2018
;; MSG SIZE rcvd: 56

;; connection timed out; no servers could be reached


#2

Looks like a copy and paste from here

https://community.cloudflare.com/c/reliability/1111

This in an excellent troubleshooting guide. You should follow all steps that apply.

A traceroute to 1.1.1.1 would also be helpful. :slight_smile:


#3

dig example.com 21 @1.1.1.1
; <<>> DiG 9.11.3-RedHat-9.11.3-4.fc27 <<>> example.com 21 @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31001
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;example.com. IN A

;; ANSWER SECTION:
example.com. 10197 IN A 93.184.216.34

;; Query time: 191 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: lun. avril 23 12:11:06 -05 2018
;; MSG SIZE rcvd: 56

;; connection timed out; no servers could be reached

dig example.com 21 @1.0.0.1

; <<>> DiG 9.11.3-RedHat-9.11.3-4.fc27 <<>> example.com 21 @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37869
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;example.com. IN A

;; ANSWER SECTION:
example.com. 10076 IN A 93.184.216.34

;; Query time: 269 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: lun. avril 23 12:11:21 -05 2018
;; MSG SIZE rcvd: 56

;; connection timed out; no servers could be reached

dig example.com 21 @8.8.8.8

; <<>> DiG 9.11.3-RedHat-9.11.3-4.fc27 <<>> example.com 21 @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1129
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;example.com. IN A

;; ANSWER SECTION:
example.com. 10004 IN A 93.184.216.34

;; Query time: 310 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: lun. avril 23 12:12:33 -05 2018
;; MSG SIZE rcvd: 56

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21480
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;21. IN A

;; AUTHORITY SECTION:
. 27643 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2018042201 1800 900 604800 86400

;; Query time: 145 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: lun. avril 23 12:12:33 -05 2018
;; MSG SIZE rcvd: 106

dig +short CHAOS TXT id.server @1.1.1.1
;; connection timed out; no servers could be reached

dig +short CHAOS TXT id.server @1.0.0.1
;; connection timed out; no servers could be reached


#4

Hi,
I tried to send a full log and a traceroute but this blog doesn’t allow me to send more than 2 links (example.com) or a full post :frowning:


#5

traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
1 Modem (192.168.0.100) 0.686 ms 0.913 ms 1.066 ms
2 192.168.1.1 (192.168.1.1) 4.304 ms 4.363 ms 4.614 ms

3 10.214.0.1 (10.214.0.1) 23.282 ms 23.336 ms 37.558 ms
4 10.229.2.57 (10.229.2.57) 32.645 ms 36.704 ms 36.739 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


#6

traceroute 1.0.0.1
traceroute to 1.0.0.1 (1.0.0.1), 30 hops max, 60 byte packets
1 Modem (192.168.0.100) 0.540 ms 0.710 ms 0.896 ms
2 192.168.1.1 (192.168.1.1) 4.099 ms 4.130 ms 4.170 ms
3 10.214.0.1 (10.214.0.1) 17.101 ms 17.198 ms 17.290 ms
4 10.229.2.57 (10.229.2.57) 13.676 ms 14.592 ms 14.649 ms
5 * * *
6 * * *
7 10.112.0.98 (10.112.0.98) 33.585 ms 10.111.65.10 (10.111.65.10) 34.180 ms *
8 10.111.0.246 (10.111.0.246) 27.817 ms 10.111.0.206 (10.111.0.206) 28.788 ms 10.112.128.234 (10.112.128.234) 32.193 ms
9 1dot1dot1dot1.cloudflare-dns.com (1.0.0.1) 31.390 ms 31.112 ms 30.139 ms


#7

Ping to @cscharff :blush:

EDIT: This seems like a case of ISP problems, not router related.


#8

Thanks for the report. We reached out to the ISP directly, haven’t head back from them yet though. :frowning:


#9

Yeah, NOCs can be slow to reply… Tiscali (Italy) hasn’t replied to me in 10 days.


#10

Hello,
It seems that your request to my ISP Telefónica / Movistar worked ! Now 1.1.1.1 is responding again. But it’s f***g slow ! If I remember, the average speed was before ­around 30ms. It’s now at 400ms! Same problem for 1.0.0.1
Regards.

— 1.1.1.1 ping statistics —
101 packets transmitted, 99 received, 1% packet loss, time 100031ms
rtt min/avg/max/mdev = 149.701/393.922/678.215/110.654 ms

— 1.0.0.1 ping statistics —
101 packets transmitted, 97 received, 3% packet loss, time 100079ms
rtt min/avg/max/mdev = 145.383/400.535/655.878/89.167 ms