Trace to 1.1.1.1

Hi,

I have big latency to 1.1.1.1.
My IP: 95.215.30.226

traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
 1  192.168.200.1 (192.168.200.1)  0.288 ms  0.255 ms  0.254 ms
 2  cho216-r0.systel.pl (195.177.64.60)  2.937 ms  3.002 ms  2.903 ms
 3  ae4-338.cr1-waw1.ip4.gtt.net (46.33.92.249)  14.537 ms  14.522 ms *
 4  ae15.cr6-ams1.ip4.gtt.net (213.200.117.58)  34.940 ms  33.385 ms  33.366 ms
 5  87.119.94.210 (87.119.94.210)  33.865 ms  31.812 ms  32.041 ms
 6  172.71.180.2 (172.71.180.2)  32.783 ms 172.70.44.2 (172.70.44.2)  32.703 ms 172.71.96.2 (172.71.96.2)  32.651 ms
 7  one.one.one.one (1.1.1.1)  32.618 ms  32.631 ms  32.745 ms

in your diagnostic tools I have random two AS names, links:

https://one.one.one.one/help/#eyJpc0NmIjoiTm8iLCJpc0RvdCI6Ik5vIiwiaXNEb2giOiJObyIsInJlc29sdmVySXAtMS4xLjEuMSI6IlllcyIsInJlc29sdmVySXAtMS4wLjAuMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjExMTEiOiJObyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjEwMDEiOiJObyIsImRhdGFjZW50ZXJMb2NhdGlvbiI6IkFNUyIsImlzV2FycCI6Ik5vIiwiaXNwTmFtZSI6IlN5c3RlbCBTeXN0ZW15IFRlbGVpbmZvcm1hdHljem5lIE0uIExpbnNjaGVpZCBTcC4iLCJpc3BBc24iOiIzNDM5MyJ9
https://one.one.one.one/help/#eyJpc0NmIjoiTm8iLCJpc0RvdCI6Ik5vIiwiaXNEb2giOiJObyIsInJlc29sdmVySXAtMS4xLjEuMSI6IlllcyIsInJlc29sdmVySXAtMS4wLjAuMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjExMTEiOiJObyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjEwMDEiOiJObyIsImRhdGFjZW50ZXJMb2NhdGlvbiI6IkFNUyIsImlzV2FycCI6Ik5vIiwiaXNwTmFtZSI6Ikdvb2dsZSIsImlzcEFzbiI6IjE1MTY5In0=

I am from poland and AMS Cloudflare datacenter is wrong for me.
I thing correct datacenter for me is WAW (Warsaw).

AS34393 (Adam Wolk-Jankowski trading as Systel Systemy Teleinformatyczne M. Linscheid Sp. J.), or Systel for short, seems indeed to be taking you to Amsterdam, according to that traceroute.

AS34393 does not peer with Cloudflare, and as such, AS34393 / Systel sends their traffic to their upstream provider, AS3257 / GTT Communications Inc., which then is taking the traffic to the Netherlands, where they pass it over to Cloudflare.

Cloudflare cannot force AS34393 / Systel to peer with them, if AS34393 / Systel are unwilling to do so.

I therefore suggest you to contact your provider, AS34393 / Systel, and request them to establish a peering with Cloudflare, and to do that peering(s) within Poland, as that would be your only opportunity for better routing.

2 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.