Help bad routeo isp to cloudflare services

[german.garciadoego]

Good Morning!!!
I am having routing problems with the isp of one of my clients …
The ISP in question is TELECOM FIBERTEL (ARGENINA - BUENOS AIRES).
There are Cloudflare servers located locally on the IXP CABASE, and the ISP is routing some Cloudflare services (1.1.1.1, 1.1.1.2, 1.1.1.3) to ROME -ITALY and other services like Cloudflare Gateway (172.64.36.1 and 2) CORDOBA-ARGENTINA.
For my part, I already spoke to the first level support this morning and explained the problem, but since it is a residential service, they indicated that they could not do anything about it … Yes … Here the ISPs are handled in this way bad way…
Does Cloudflare have any way to contact said ISP to solve the problem? Could you give me a hand with this topic ???
Attached screenshots of the routes:

CLOUDFLARE DNS (COMMON AND FAMILY)

CLOUDFLARE GATEWAY

Thank you in advance !!!

Cheers!!!

[mvavrusa]

Hi, it seems like you’re ~9ms away from 1.1.1.1. Can you capture debug information as per Have problems with 1.1.1.1? *Read Me First* ?

[german.garciadoego]

Hi @mvavrusa, thanks for replying !!!
Yes, according to the ping, the latency is low, but the final destination in 1.1.1.1 is ROMA and 172.64.36.1 is CORDOBA …
TELECOM is one of the companies that have international output cable here, maybe that’s why it sees little latency …
Anyway, now I am going to talk to my client and I am going to verify what he is asking me on a pc there.

I write to you later with the results.

Greetings and thanks again for your help!!!

[german.garciadoego]

@mvavrusa Here is the data… there is something strange here…

Cloudflare HELP

1.1.1.1 — the Internet’s Fastest, Privacy-First DNS Resolver

nslookup example.com 1.1.1.1
Servidor: one.one.one.one
Address: 1.1.1.1

Respuesta no autoritativa:
Nombre: example.com
Addresses: 2606:2800:220:1:248:1893:25c8:1946
93.184.216.34

nslookup example.com 1.0.0.1
Servidor: one.one.one.one
Address: 1.0.0.1

Respuesta no autoritativa:
Nombre: example.com
Addresses: 2606:2800:220:1:248:1893:25c8:1946
93.184.216.34

nslookup example.com 8.8.8.8
Servidor: dns.google
Address: 8.8.8.8

Respuesta no autoritativa:
Nombre: example.com
Addresses: 2606:2800:220:1:248:1893:25c8:1946
93.184.216.34

nslookup -class=chaos -type=txt id.server 1.1.1.1
Servidor: one.one.one.one
Address: 1.1.1.1

Respuesta no autoritativa:
id.server text =

    "EZE"

nslookup -class=chaos -type=txt id.server 1.0.0.1
Servidor: one.one.one.one
Address: 1.0.0.1

Respuesta no autoritativa:
id.server text =

    "EZE"

nslookup -type=txt whoami.Cloudflare.com ns3.Cloudflare.com
Servidor: ns3.cloudflare.com
Address: 162.159.0.33

whoami.Cloudflare.com text =

    "201.213.72.XXX"

tracert 1.1.1.1

Traza a la dirección one.one.one.one [1.1.1.1]
sobre un máximo de 30 saltos:

1 2 ms 2 ms 1 ms XXX_XXXX [192.168.1.1]
2 * * * Tiempo de espera agotado para esta solicitud.
3 * * * Tiempo de espera agotado para esta solicitud.
4 * * * Tiempo de espera agotado para esta solicitud.
5 * * * Tiempo de espera agotado para esta solicitud.
6 31 ms 14 ms 16 ms host119.181-89-2.telecom.net.ar [181.89.2.119]
7 15 ms 14 ms 15 ms ae6.baires3.bai.seabone.net [185.70.203.22]
8 17 ms 11 ms 21 ms cloudflare.baires3.bai.seabone.net [185.70.203.71]
9 12 ms 12 ms 12 ms one.one.one.one [1.1.1.1]

Traza completa.

tracert 1.0.0.1

Traza a la dirección one.one.one.one [1.0.0.1]
sobre un máximo de 30 saltos:

1 2 ms 2 ms 2 ms XXX_XXXX [192.168.1.1]
2 * * * Tiempo de espera agotado para esta solicitud.
3 * * * Tiempo de espera agotado para esta solicitud.
4 * * * Tiempo de espera agotado para esta solicitud.
5 * * * Tiempo de espera agotado para esta solicitud.
6 15 ms 14 ms 15 ms host119.181-89-2.telecom.net.ar [181.89.2.119]
7 17 ms 34 ms 30 ms ae6.baires3.bai.seabone.net [185.70.203.22]
8 16 ms 23 ms 28 ms cloudflare.baires3.bai.seabone.net [185.70.203.71]
9 16 ms 12 ms 13 ms one.one.one.one [1.0.0.1]

Traza completa.

nslookup example.com 172.64.36.1
Servidor: UnKnown
Address: 172.64.36.1

Respuesta no autoritativa:
Nombre: example.com
Addresses: 2606:2800:220:1:248:1893:25c8:1946
93.184.216.34

nslookup example.com 172.64.36.2
Servidor: UnKnown
Address: 172.64.36.2

Respuesta no autoritativa:
Nombre: example.com
Addresses: 2606:2800:220:1:248:1893:25c8:1946
93.184.216.34

nslookup -class=chaos -type=txt id.server 172.64.36.1
Servidor: UnKnown
Address: 172.64.36.1

Respuesta no autoritativa:
id.server text =

    "EZE"

nslookup -class=chaos -type=txt id.server 172.64.36.2
Servidor: UnKnown
Address: 172.64.36.2

Respuesta no autoritativa:
id.server text =

    "EZE"

tracert 172.64.36.1

Traza a 172.64.36.1 sobre caminos de 30 saltos como máximo.

1 2 ms 2 ms 1 ms XXX_XXXX [192.168.1.1]
2 * * * Tiempo de espera agotado para esta solicitud.
3 * * * Tiempo de espera agotado para esta solicitud.
4 * * * Tiempo de espera agotado para esta solicitud.
5 * * * Tiempo de espera agotado para esta solicitud.
6 19 ms 25 ms 20 ms host119.181-89-2.telecom.net.ar [181.89.2.119]
7 13 ms 18 ms 14 ms host246.181-13-127.telecom.net.ar [181.13.127.246]
8 54 ms 18 ms 13 ms 172.64.36.1

Traza completa.

tracert 172.64.36.2

Traza a 172.64.36.2 sobre caminos de 30 saltos como máximo.

1 5 ms 2 ms 2 ms XXX_XXXX [192.168.1.1]
2 * * * Tiempo de espera agotado para esta solicitud.
3 * * * Tiempo de espera agotado para esta solicitud.
4 * * * Tiempo de espera agotado para esta solicitud.
5 * * * Tiempo de espera agotado para esta solicitud.
6 20 ms 14 ms 22 ms host119.181-89-2.telecom.net.ar [181.89.2.119]
7 14 ms 14 ms 14 ms host246.181-13-127.telecom.net.ar [181.13.127.246]
8 13 ms 13 ms 11 ms 172.64.36.2

Traza completa.

[german.garciadoego]

Here I have another client with the same ISP, it appears that it is connected to 1.1.1.1 but that it has no connectivity to either 1.1.1.1 or 1.0.0.1.

1.1.1.1 — the Internet’s Fastest, Privacy-First DNS Resolver

However I can ping and tracert it and it doesn’t matter the other client…

[german.garciadoego]

@mvavrusa Good Morning!!!
Could you see something? Can Telecom Fibertel be contacted to solve the route to IXP CABASE where their servers are located? Is it useful to copy other ISP screens with their correct routing?

Cheers!!!

[mvavrusa]

Hi! I’m not sure what can be improved. Based on the logs you’re connected to Buenos Aires which is 9ms away. Why do you think you’re routed to Rome?

[german.garciadoego]

Hello @mvavrusa , thanks for answering!!!
I say they are routing to ROME because if you check the ip just before reaching 1.1.1.1, it gives this result:

The routes that are good should be like this:

ISP IPLAN NETWORKS

ISP TELECENTRO

As you can see, in these 2 ISPs the routing is optimal, reaching ip 200.0.17.181 (IXP CABASE) where the CLOUDFLARE BUENOS AIRES EZE servers are hosted.

[alejandro]

This is for anycast. That IP may be registered in Rome, but it is reported around the world to resolve in the cloudflare network, in the closest data center. You can read more about anycast on the web, it is like “a virtual address”, and here the phrase comes from wonders “all roads lead to cloudflare”. It may seem that there are different or confusing routes, it depends on many factors, but you will always give the best one.

Esto es por anycast. puede que esa ip esté registrada en Roma, pero es informada en rededor del mundo para resolver en la red de cloudflare, en el centro de datos más cercano. Puedes leer más sobre anycast en la web, es como “un domicilio virtual”, y aquí la frase viene de maravillas “todos los caminos conducen a cloudflare”. Puede parecer que hay rutas distintas o confusas, depende de muchos factores, pero siempre dará la mejor.