Wrong PoPS in Bogota Colombia

Here in Colombia we have two CloudFlare datacenters, one in Bogota and one in Medellin.
However I started to see a big latency to CloudFlare resolver. Google is about 20ms, 1.1.1.1 is 80ms.

I review my websites using cdn-cgi/trace and see the colo property accessing to data centers in USA (CLT, TPA, etc). I also ask multiple friends and all of them get datacenters in USA. I think this is hapenning for CloudFlare typical web site protection and Cloudflare Resolver.

What could we do? We expect less latency having local datacenters here.

Routing issues come up from time to time, and here is some information on that:

The sad thing is i am seeing this for months

I’ll add this:
cloudflare.com goes to the BOG datacenter

But 1.1.1.1 goes to USA datacenter

hi
im having the same issue

Hi @ricardo.polo. Can you help us debug this issue by doing the following things?

  1. go to 1.1.1.1/help/ and then paste the link here.
  2. go to cloudflare-dns.com/help/ and then paste the link here.
  3. run “dig +trace @1.1.1.1 example.com” and paste the results here.
  4. run “dig +trace @1.0.0.1 example.com” and paste the results here.

Thanks! :v::v:

Hello @irtefa
I have the same issue reported by @ricardo.polo. Allow me to provide also the debug information you requested. Im also including tracerts


1.1.1.1
https://1.1.1.1/help/#eyJpc0NmIjoiTm8iLCJpc0RvdCI6Ik5vIiwiaXNEb2giOiJObyIsInJlc29sdmVySXAtMS4xLjEuMSI6IlllcyIsInJlc29sdmVySXAtMS4wLjAuMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjExMTEiOiJObyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjEwMDEiOiJObyIsImRhdGFjZW50ZXJMb2NhdGlvbiI6IkFUTCIsImlzcE5hbWUiOiJDbG91ZGZsYXJlIiwiaXNwQXNuIjoiMTMzMzUifQ==


cloudflare-dns
https://cloudflare-dns.com/help/#eyJpc0NmIjoiTm8iLCJpc0RvdCI6Ik5vIiwiaXNEb2giOiJObyIsInJlc29sdmVySXAtMS4xLjEuMSI6IlllcyIsInJlc29sdmVySXAtMS4wLjAuMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjExMTEiOiJObyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjEwMDEiOiJObyIsImRhdGFjZW50ZXJMb2NhdGlvbiI6IkJPRyIsImlzcE5hbWUiOiJDbG91ZGZsYXJlIiwiaXNwQXNuIjoiMTMzMzUifQ==


dig +trace @1.1.1.1 wsopen.com

; <<>> DiG 9.14.4 <<>> +trace @1.1.1.1 wsopen.com
; (1 server found)
;; global options: +cmd
.                       9143    IN      NS      f.root-servers.net.
.                       9143    IN      NS      g.root-servers.net.
.                       9143    IN      NS      h.root-servers.net.
.                       9143    IN      NS      i.root-servers.net.
.                       9143    IN      NS      j.root-servers.net.
.                       9143    IN      NS      k.root-servers.net.
.                       9143    IN      NS      l.root-servers.net.
.                       9143    IN      NS      m.root-servers.net.
.                       9143    IN      NS      a.root-servers.net.
.                       9143    IN      NS      b.root-servers.net.
.                       9143    IN      NS      c.root-servers.net.
.                       9143    IN      NS      d.root-servers.net.
.                       9143    IN      NS      e.root-servers.net.
.                       9143    IN      RRSIG   NS 8 0 518400 20190828170000 20190815160000 59944 . lwEmWodaVZFzkk/GJfELkgMSTdbrXpeFbLwnMqsqh5wFmQQHEmnuBC2Q 3eqEc7xocWpdCHKVUbnrjfqHfL5kqSX0/3VZe9fQeCCnuoXCASNYjWYJ NzgFxuXVLdteBhr4g5v/qWMkaW3T6rUr4zuWgKCOit2MTBDq0woN/oN1 imVUwrtbqZfCWRMsqgbmSAGopNHCQgJNSfI3C4d3lV1QOw/wv8c1gAzE 7xCje/4WnksSvC9MDVZRPBK6JgGIHMtdaUH4m9KJT2WBT3AC+qx28myH ogq907fkyq9fk1Ld97s8dfMOxiS5Sjwqtf2nsvPDTbC9Xmmqj5xdFIxL zJ8UJg==
;; Received 717 bytes from 1.1.1.1#53(1.1.1.1) in 180 ms

;; Received 28 bytes from 202.12.27.33#53(m.root-servers.net) in 80 ms

dig +trace @1.0.0.1 wsopen.com

; <<>> DiG 9.14.4 <<>> +trace @1.0.0.1 wsopen.com
; (1 server found)
;; global options: +cmd
.                       7364    IN      NS      c.root-servers.net.
.                       7364    IN      NS      d.root-servers.net.
.                       7364    IN      NS      e.root-servers.net.
.                       7364    IN      NS      f.root-servers.net.
.                       7364    IN      NS      g.root-servers.net.
.                       7364    IN      NS      h.root-servers.net.
.                       7364    IN      NS      i.root-servers.net.
.                       7364    IN      NS      j.root-servers.net.
.                       7364    IN      NS      k.root-servers.net.
.                       7364    IN      NS      l.root-servers.net.
.                       7364    IN      NS      m.root-servers.net.
.                       7364    IN      NS      a.root-servers.net.
.                       7364    IN      NS      b.root-servers.net.
.                       7364    IN      RRSIG   NS 8 0 518400 20190828170000 20190815160000 59944 . lwEmWodaVZFzkk/GJfELkgMSTdbrXpeFbLwnMqsqh5wFmQQHEmnuBC2Q 3eqEc7xocWpdCHKVUbnrjfqHfL5kqSX0/3VZe9fQeCCnuoXCASNYjWYJ NzgFxuXVLdteBhr4g5v/qWMkaW3T6rUr4zuWgKCOit2MTBDq0woN/oN1 imVUwrtbqZfCWRMsqgbmSAGopNHCQgJNSfI3C4d3lV1QOw/wv8c1gAzE 7xCje/4WnksSvC9MDVZRPBK6JgGIHMtdaUH4m9KJT2WBT3AC+qx28myH ogq907fkyq9fk1Ld97s8dfMOxiS5Sjwqtf2nsvPDTbC9Xmmqj5xdFIxL zJ8UJg==
;; Received 717 bytes from 1.0.0.1#53(1.0.0.1) in 130 ms

;; Received 28 bytes from 198.41.0.4#53(a.root-servers.net) in 170 ms

tracert 1.1.1.1
Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

  1   113 ms     6 ms     2 ms  router.asus.com [10.0.0.1]
  2     *        *        *     Request timed out.
  3    31 ms    11 ms    15 ms  172.21.114.126
  4    17 ms    18 ms    22 ms  190.85.254.145
  5    38 ms    37 ms    36 ms  10.14.16.18
  6    53 ms    57 ms    33 ms  10.14.18.41
  7    73 ms    74 ms    77 ms  ix-et-2-0-2-0.tcore2.a56-atlanta.as6453.net [64.86.8.37]
  8    85 ms   106 ms    78 ms  64.86.9.103
  9    75 ms    79 ms    74 ms  one.one.one.one [1.1.1.1]

Trace complete.

tracert cloudflare-dns.com

Tracing route to cloudflare-dns.com [104.16.249.249]
over a maximum of 30 hops:

  1     3 ms     1 ms     2 ms  router.asus.com [10.0.0.1]
  2     *        *        *     Request timed out.
  3    14 ms    13 ms    12 ms  172.21.114.126
  4    16 ms    23 ms    14 ms  190.85.254.145
  5    53 ms    57 ms    56 ms  10.14.15.181
  6   269 ms   139 ms   159 ms  internexa1-nap.ccit.org.co [206.223.124.154]
  7    49 ms    49 ms    51 ms  179.1.92.18
  8    58 ms    59 ms    61 ms  179.1.92.19
  9    61 ms    60 ms    60 ms  104.16.249.249

Trace complete.

This seems like an issue with the ISP internexa.

Our network team will reach out to them to fix it.

Thanks for your help @andresmorago!

1 Like

thanks so much!
can you please keep us posted in case of any updates?

1 Like

Will do.

1 Like