Hi all. I have NTP servers in Europe that are choosing Tata (6453) to get to 0.freebsd.pool.ntp.org which lives on 197.224.66.40: traceroute -I 0.freebsd.pool.ntp.org traceroute to 0.freebsd.pool.ntp.org (197.224.66.40), 64 hops max, 48 byte packets 1 ae-2-24.er-01-ams.nl.seacomnet.com (105.26.64.13) 0.300 ms 0.301 ms 0.215 ms 2 ce-0-0-11.cr-01-mrs.fr.seacomnet.com (105.16.8.201) 22.163 ms 22.370 ms 22.084 ms 3 ce-0-0-3.br-01-mrs.fr.seacomnet.com (105.16.32.254) 20.230 ms 20.243 ms 20.139 ms 4 ix-hge-0-0-0-28.ecore3.emrs2-marseille.as6453.net (80.231.165.52) 21.875 ms 21.679 ms 21.762 ms 5 * if-be-3-2.ecore2.emrs2-marseille.as6453.net (195.219.175.0) 42.751 ms * 6 if-ae-25-2.tcore1.ldn-london.as6453.net (195.219.175.5) 43.509 ms 43.280 ms 43.353 ms 7 195.219.83.158 (195.219.83.158) 203.310 ms 203.452 ms 203.209 ms 8 196.20.225.84 (196.20.225.84) 208.289 ms 208.637 ms 208.374 ms 9 197.226.230.13 (197.226.230.13) 209.657 ms 209.658 ms 209.830 ms 10 197.224.66.40 (197.224.66.40) 208.638 ms 208.632 ms 208.712 ms NTP is not sync'ing to that address, and sessions stay in an Init state. Other NTP servers I have in Africa are reaching the same address via local Anycast hosters, and sync'ing just fine. Anyone else seeing this particular issue across Tata in Europe? Mark.