I've shutdown our IPv6 BGP session with Cogent (AS174) and can now ping6 to my UK NTP servers from https://lg.as7012.net/cgi-bin/bgplg and trace from https://trace.ntppool.org/traceroute
Previously tracert was not leaving the Phyber network and their looking glass showed the best route to our network via Cogent. However it seems inconsistent as the route to the original reported server (ntp.rail.eu.org) routes via NTT/Telia from the Phyber looking glass and is unreachable, unless the return path involves Cogent? Tim -----Original Message----- From: pool [mailto:[email protected]] On Behalf Of Ask Bjørn Hansen Sent: 21 May 2017 21:49 To: Marco Senft <[email protected]> Cc: [email protected] Subject: Re: [Pool] Problems with IPv6 > On May 21, 2017, at 12:49, Marco Senft <[email protected]> wrote: > > Well, as far as I understand from the conversation so far, nobody blamed the > monitoring node for the problems. I completely agree with you that a > peering/routing issue is most probably the root cause of it. However that's > just an educated guess, the only thing we can tell for sure is that the > monitoring incorrectly states many servers as being unreachable. Yeah, about 25% of the IPv6 servers. :-/ http://www.pool.ntp.org/zone/@ The folks at Phyber (AS7012) are working on debugging it. It’s not terribly obvious what’s going on. You can traceroute from the network here with https://trace.ntppool.org/traceroute/8.8.8.8 Ask _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
