Latency Brazil

The latency of your DNS service is bigger if compared with Google Public DNS and OpenDNS in Brazil.

tracert 1.1.1.1

1 * * * Esgotado o tempo limite do pedido.
2 22 ms 19 ms 19 ms 187-100-189-26.dsl.telesp.net.br [187.100.189.26]
3 21 ms 53 ms 20 ms 187-100-86-46.dsl.telesp.net.br [187.100.86.46]
4 31 ms 27 ms 27 ms 187-100-81-178.dsl.telesp.net.br [187.100.81.178]
5 35 ms 36 ms 35 ms 84.16.9.65
6 128 ms 126 ms 128 ms 5.53.3.152
7 126 ms 126 ms 127 ms 176.52.253.23
8 127 ms 126 ms 126 ms 1dot1dot1dot1.Cloudflare-dns.com [1.1.1.1]

tracert 1.0.0.1

1 * * * Esgotado o tempo limite do pedido.
2 19 ms 19 ms 22 ms 187-100-189-98.dsl.telesp.net.br [187.100.189.98]
3 20 ms 21 ms 20 ms 187-100-86-50.dsl.telesp.net.br [187.100.86.50]
4 26 ms 25 ms 27 ms 187-100-81-178.dsl.telesp.net.br [187.100.81.178]
5 37 ms 37 ms 37 ms 84.16.10.216
6 128 ms 127 ms 127 ms 5.53.3.152
7 126 ms 127 ms 126 ms 176.52.253.23
8 126 ms 126 ms 126 ms 1dot1dot1dot1.Cloudflare-dns.com [1.0.0.1]

The latency of your DNS service is bigger if compared with Google Public DNS and OpenDNS in Brazil.

tracert 1.1.1.1

1 * * * Esgotado o tempo limite do pedido.
2 22 ms 19 ms 19 ms 187-100-189-26.dsl.telesp.net.br [187.100.189.26]
3 21 ms 53 ms 20 ms 187-100-86-46.dsl.telesp.net.br [187.100.86.46]
4 31 ms 27 ms 27 ms 187-100-81-178.dsl.telesp.net.br [187.100.81.178]
5 35 ms 36 ms 35 ms 84.16.9.65
6 128 ms 126 ms 128 ms 5.53.3.152
7 126 ms 126 ms 127 ms 176.52.253.23
8 127 ms 126 ms 126 ms 1dot1dot1dot1.Cloudflare-dns.com [1.1.1.1]

tracert 1.0.0.1

1 * * * Esgotado o tempo limite do pedido.
2 19 ms 19 ms 22 ms 187-100-189-98.dsl.telesp.net.br [187.100.189.98]
3 20 ms 21 ms 20 ms 187-100-86-50.dsl.telesp.net.br [187.100.86.50]
4 26 ms 25 ms 27 ms 187-100-81-178.dsl.telesp.net.br [187.100.81.178]
5 37 ms 37 ms 37 ms 84.16.10.216
6 128 ms 127 ms 127 ms 5.53.3.152
7 126 ms 127 ms 126 ms 176.52.253.23
8 126 ms 126 ms 126 ms 1dot1dot1dot1.Cloudflare-dns.com [1.0.0.1]

tracert 8.8.8.8

1 * * * Esgotado o tempo limite do pedido.
2 20 ms 20 ms 20 ms 187-100-189-92.dsl.telesp.net.br [187.100.189.92]
3 20 ms 19 ms 20 ms 187-100-86-50.dsl.telesp.net.br [187.100.86.50]
4 30 ms 27 ms 28 ms 187-100-81-176.dsl.telesp.net.br [187.100.81.176]
5 * 29 ms 29 ms 209.85.172.178
6 27 ms 28 ms 28 ms 108.170.245.161
7 27 ms 27 ms 27 ms 216.239.56.57
8 28 ms 29 ms 27 ms google-public-dns-a.google.com [8.8.8.8]

tracert 8.8.4.4

1 * * * Esgotado o tempo limite do pedido.
2 21 ms 20 ms 19 ms 187-100-189-100.dsl.telesp.net.br [187.100.189.100]
3 21 ms 20 ms 22 ms 187-100-86-50.dsl.telesp.net.br [187.100.86.50]
4 29 ms 27 ms 29 ms 187-100-81-176.dsl.telesp.net.br [187.100.81.176]
5 28 ms 28 ms 38 ms 209.85.172.178
6 * 28 ms 35 ms 108.170.245.161
7 29 ms 29 ms 27 ms 66.249.94.255
8 28 ms 28 ms 28 ms google-public-dns-b.google.com [8.8.4.4]

I moved your duplicate posts to this thread. Feel free to delete any duplicates.

Try the ‘dig’ command to see how fast the responses are.

Im using same ISP and have the same problem - Vivo Fibra

tracert 1.0.0.1
1 <1 ms <1 ms <1 ms Broadcom.Home [192.168.15.1]
2 * * * Esgotado o tempo limite do pedido.
3 11 ms 10 ms 10 ms 187-100-181-232.dsl.telesp.net.br [187.100
32]
4 10 ms 10 ms 10 ms 187-100-194-134.dsl.telesp.net.br [187.100
34]
5 16 ms 14 ms 14 ms 187-100-81-178.dsl.telesp.net.br [187.100.
]
6 30 ms 29 ms 29 ms 84.16.9.65
7 109 ms 111 ms 111 ms 5.53.3.152
8 111 ms 112 ms 111 ms 176.52.253.23
9 112 ms 112 ms 112 ms 1dot1dot1dot1.Cloudflare-dns.com [1.0.0.1]

I’m not able to use 1.1.1.1 because the modem uses 1.1.1.1 to go through modem web page

tracert 208.67.222.222

1 * * * Esgotado o tempo limite do pedido.
2 25 ms 20 ms 61 ms 187-100-189-98.dsl.telesp.net.br [187.100.189.98]
3 21 ms 20 ms 21 ms 187-100-86-50.dsl.telesp.net.br [187.100.86.50]
4 28 ms 27 ms 27 ms 187-100-81-176.dsl.telesp.net.br [187.100.81.176]
5 27 ms 30 ms 27 ms 84.16.9.120
6 56 ms 69 ms 54 ms ntt-ae5-grasaotm1.net.telefonicaglobalsolutions.com [213.140.53.51]
7 27 ms 28 ms 30 ms xe-0-0-0-1-4.r01.saplbr01.br.ce.gin.ntt.net [200.15.2.66]
8 28 ms 26 ms 25 ms resolver1.opendns.com [208.67.222.222]

tracert 208.67.220.220

1 * * * Esgotado o tempo limite do pedido.
2 20 ms 20 ms 19 ms 187-100-189-92.dsl.telesp.net.br [187.100.189.92]
3 27 ms 25 ms 24 ms 187-100-86-52.dsl.telesp.net.br [187.100.86.52]
4 27 ms 27 ms 27 ms 187-100-83-0.dsl.telesp.net.br [187.100.83.0]
5 27 ms 28 ms 27 ms 176.52.253.163
6 57 ms 56 ms 53 ms ntt-ae5-grasaotm1.net.telefonicaglobalsolutions.com [213.140.53.51]
7 28 ms 28 ms 28 ms xe-0-0-0-1-4.r01.saplbr01.br.ce.gin.ntt.net [200.15.2.66]
8 28 ms 27 ms 29 ms resolver2.opendns.com [208.67.220.220]

Try this:
dig cnn.com @1.1.1.1

dig cnn.com @8.8.8.8

And the others, also.

C:>dig www.microsoft.com.br @1.1.1.1

; <<>> DiG 9.10.4-P2 <<>> www.microsoft.com.br @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46591
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1536
;; QUESTION SECTION:
;www.microsoft.com.br. IN A

;; ANSWER SECTION:
www.microsoft.com.br. 3600 IN CNAME microsoft.com.br.
microsoft.com.br. 3600 IN A 23.101.184.206
microsoft.com.br. 3600 IN A 104.40.191.237
microsoft.com.br. 3600 IN A 104.43.142.34
microsoft.com.br. 3600 IN A 191.235.218.166
microsoft.com.br. 3600 IN A 191.237.78.58

;; Query time: 469 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon Apr 02 11:11:49 Hora oficial do Brasil 2018
;; MSG SIZE rcvd: 143

C:>dig www.microsoft.com.br @1.0.0.1

; <<>> DiG 9.10.4-P2 <<>> www.microsoft.com.br @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5990
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1536
;; QUESTION SECTION:
;www.microsoft.com.br. IN A

;; ANSWER SECTION:
www.microsoft.com.br. 3512 IN CNAME microsoft.com.br.
microsoft.com.br. 3512 IN A 23.101.184.206
microsoft.com.br. 3512 IN A 104.40.191.237
microsoft.com.br. 3512 IN A 104.43.142.34
microsoft.com.br. 3512 IN A 191.235.218.166
microsoft.com.br. 3512 IN A 191.237.78.58

;; Query time: 125 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Mon Apr 02 11:13:17 Hora oficial do Brasil 2018
;; MSG SIZE rcvd: 143

C:>dig www.microsoft.com.br @8.8.8.8

; <<>> DiG 9.10.4-P2 <<>> www.microsoft.com.br @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24655
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
www.microsoft.com.br. 2762 IN CNAME microsoft.com.br.
microsoft.com.br. 2762 IN A 104.43.142.34
microsoft.com.br. 2762 IN A 23.101.184.206
microsoft.com.br. 2762 IN A 191.237.78.58
microsoft.com.br. 2762 IN A 191.235.218.166
microsoft.com.br. 2762 IN A 104.40.191.237

;; Query time: 78 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Apr 02 11:12:09 Hora oficial do Brasil 2018
;; MSG SIZE rcvd: 143

C:>dig www.microsoft.com.br @8.8.4.4

; <<>> DiG 9.10.4-P2 <<>> www.microsoft.com.br @8.8.4.4
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 65506
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
www.microsoft.com.br. 3541 IN CNAME microsoft.com.br.
microsoft.com.br. 3541 IN A 104.40.191.237
microsoft.com.br. 3541 IN A 104.43.142.34
microsoft.com.br. 3541 IN A 23.101.184.206
microsoft.com.br. 3541 IN A 191.237.78.58
microsoft.com.br. 3541 IN A 191.235.218.166

;; Query time: 78 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: Mon Apr 02 11:13:54 Hora oficial do Brasil 2018
;; MSG SIZE rcvd: 143

C:>dig www.microsoft.com.br @208.67.222.222

; <<>> DiG 9.10.4-P2 <<>> www.microsoft.com.br @208.67.222.222
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41680
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.microsoft.com.br. IN A

;; ANSWER SECTION:
www.microsoft.com.br. 198 IN CNAME microsoft.com.br.
microsoft.com.br. 198 IN A 104.43.142.34
microsoft.com.br. 198 IN A 23.101.184.206
microsoft.com.br. 198 IN A 191.237.78.58
microsoft.com.br. 198 IN A 191.235.218.166
microsoft.com.br. 198 IN A 104.40.191.237

;; Query time: 31 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Mon Apr 02 11:15:18 Hora oficial do Brasil 2018
;; MSG SIZE rcvd: 143

C:>dig www.microsoft.com.br @208.67.220.220

; <<>> DiG 9.10.4-P2 <<>> www.microsoft.com.br @208.67.220.220
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2370
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.microsoft.com.br. IN A

;; ANSWER SECTION:
www.microsoft.com.br. 2179 IN CNAME microsoft.com.br.
microsoft.com.br. 161 IN A 191.235.218.166
microsoft.com.br. 161 IN A 104.40.191.237
microsoft.com.br. 161 IN A 104.43.142.34
microsoft.com.br. 161 IN A 23.101.184.206
microsoft.com.br. 161 IN A 191.237.78.58

;; Query time: 141 msec
;; SERVER: 208.67.220.220#53(208.67.220.220)
;; WHEN: Mon Apr 02 11:15:29 Hora oficial do Brasil 2018
;; MSG SIZE rcvd: 143

I’m waiting an answer.

Thanks for the report!

Hi,

I was very happy in getting the news about your new DNS Servers service. I am a user of your product for quile a while now (personal and company use).

We were doing some tests from our connection and unfortunately got a longer response time from Cloudflare than other DNS services. Is there any route we could use to make it better.

Follow tests (simple PING).

Cloudflare
C:>ping 1.1.1.1
Disparando 1.1.1.1 com 32 bytes de dados:
Resposta de 1.1.1.1: bytes=32 tempo=108ms TTL=54
Resposta de 1.1.1.1: bytes=32 tempo=109ms TTL=54
Resposta de 1.1.1.1: bytes=32 tempo=110ms TTL=54
Resposta de 1.1.1.1: bytes=32 tempo=108ms TTL=54

GOOGLE
C:>ping 8.8.8.8
Disparando 8.8.8.8 com 32 bytes de dados:
Resposta de 8.8.8.8: bytes=32 tempo=26ms TTL=53
Resposta de 8.8.8.8: bytes=32 tempo=24ms TTL=53
Resposta de 8.8.8.8: bytes=32 tempo=25ms TTL=53
Resposta de 8.8.8.8: bytes=32 tempo=24ms TTL=53

OpenDNS
C:>ping 208.67.222.222
Disparando 208.67.222.222 com 32 bytes de dados:
Resposta de 208.67.222.222: bytes=32 tempo=15ms TTL=55
Resposta de 208.67.222.222: bytes=32 tempo=18ms TTL=55
Resposta de 208.67.222.222: bytes=32 tempo=16ms TTL=55
Resposta de 208.67.222.222: bytes=32 tempo=18ms TTL=55

Thanks a lot.

Others are having the same problem. A search here for “Brazil 1.1.1.1” shows the other threads. Cloudflare is looking into it.

Just a heads-up: costumers of this ISP are unlikely to get 1.1.1.1 working – most of their costumer-premises equipment takes the address for themselves.

Here’s another tracert to 1.0.0.1 from my home machine, using the same ISP:
$ traceroute 1.0.0.1
traceroute to 1.0.0.1 (1.0.0.1), 30 hops max, 60 byte packets
[
1 [redacted]
2 * * *
3 187-100-38-185.dsl.telesp.net.br (187.100.38.185) 4.658 ms 4.654 ms 187-100-189-36.dsl.telesp.net.br (187.100.189.36) 4.623 ms
4 187-100-78-105.dsl.telesp.net.br (187.100.78.105) 8.767 ms 187-100-40-225.dsl.telesp.net.br (187.100.40.225) 5.093 ms 187-100-84-68.dsl.telesp.net.br (187.100.84.68) 6.274 ms
5 187-100-81-178.dsl.telesp.net.br (187.100.81.178) 14.039 ms 187-100-83-2.dsl.telesp.net.br (187.100.83.2) 10.814 ms 187-100-81-178.dsl.telesp.net.br (187.100.81.178) 14.740 ms
6 84.16.9.61 (84.16.9.61) 28.425 ms 84.16.10.216 (84.16.10.216) 22.839 ms 84.16.10.30 (84.16.10.30) 26.079 ms
7 5.53.3.152 (5.53.3.152) 108.341 ms 105.949 ms 107.143 ms
8 176.52.253.23 (176.52.253.23) 106.719 ms 107.162 ms 105.989 ms
9 1dot1dot1dot1.Cloudflare-dns.com (1.0.0.1) 103.060 ms 103.101 ms 106.538 ms

Hops 2 to 6 are under AS27699, 7 to 8 under AS12956.

without resolution in moment?

Is it still the same?

Have you tried: dig @1.1.1.1 id.server ch txt
This should show you which data center you are reaching.

dig @1.1.1.1 id.server ch txt

; <<>> DiG 9.10.4-P2 <<>> @1.1.1.1 id.server ch txt
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43804
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1536
;; QUESTION SECTION:
;id.server. CH TXT

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

;; Query time: 156 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon Apr 09 21:06:29 Hora oficial do Brasil 2018
;; MSG SIZE rcvd: 56

dig @1.0.0.1 id.server ch txt

; <<>> DiG 9.10.4-P2 <<>> @1.0.0.1 id.server ch txt
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34399
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1536
;; QUESTION SECTION:
;id.server. CH TXT

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

;; Query time: 156 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Mon Apr 09 21:07:58 Hora oficial do Brasil 2018
;; MSG SIZE rcvd: 56

So…it’s going to Lima, Peru. Maybe Cloudflare can figure out why.

To push more, I’d send the Traceroutes and the Dig from your last post to: noc AT Cloudflare DOT com

Thanks Cloudflare!

Looks like AS12956 made some changes, and now RTT to 1.0.0.1 is something between 30ms and 40ms. But still not faster than the 8-addressed DNS solver :frowning:

$ ping -c 4 1.0.0.1
PING 1.0.0.1 (1.0.0.1) 56(84) bytes of data.
64 bytes from 1.0.0.1: icmp_seq=1 ttl=57 time=37.5 ms
64 bytes from 1.0.0.1: icmp_seq=2 ttl=57 time=37.5 ms
64 bytes from 1.0.0.1: icmp_seq=3 ttl=57 time=37.6 ms
64 bytes from 1.0.0.1: icmp_seq=4 ttl=57 time=37.5 ms

— 1.0.0.1 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 37.512/37.581/37.680/0.061 ms

$ ping -c 4 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=58 time=10.9 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=58 time=10.7 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=58 time=10.7 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=58 time=10.7 ms

— 8.8.8.8 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 10.704/10.788/10.922/0.081 ms

$ dig @1.0.0.1 id.server ch txt

; <<>> DiG 9.10.3-P4-Ubuntu <<>> @1.0.0.1 id.server ch txt
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52037
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1536
;; QUESTION SECTION:
;id.server. CH TXT

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

;; Query time: 34 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Thu Apr 12 04:58:43 UTC 2018
;; MSG SIZE rcvd: 5