On Sun, 2017-05-21 at 21:22 +0000, Tim Lightfoot wrote: > 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
Another datapoint. The IPv6 address of my server ( 2001:4428:0:dc::22 ) has fallen out the pool too. The best path we have towards stuff in Phyber is also via Cogent which we buy transit off in San Jose. Our mtr from NZ towards there looks like: Host Loss% Snt Last Avg Best Wrst StDev 1. ge0-0-1-220.v4wlg0.acsdata.co.nz 0.0% 3 0.3 0.4 0.3 0.5 0.0 2. te0-0-1-3076.v4akl5.acsdata.co.nz 0.0% 3 11.1 10.9 10.8 11.1 0.0 3. ge0-0-0-809.v4sjc9.acsdata.co.nz 0.0% 3 145.8 145.8 145.8 145.9 0.0 4. 2001:550:2:3::11:1 0.0% 3 146.4 146.2 146.2 146.4 0.0 5. be2063.ccr21.sjc01.atlas.cogentco.com 0.0% 3 145.8 145.9 145.8 145.9 0.0 6. be3176.ccr21.lax01.atlas.cogentco.com 0.0% 3 158.5 158.5 158.5 158.6 0.0 7. be2964.ccr41.lax04.atlas.cogentco.com 0.0% 3 158.3 158.1 158.0 158.3 0.0 8. ??? If I shut down our Cogent transit, the same mtr looks like: Host Loss% Snt Last Avg Best Wrst StDev 1. ge0-0-1-220.v4wlg0.acsdata.co.nz 0.0% 22 0.4 0.4 0.3 0.5 0.0 2. te0-0-1-3076.v4akl5.acsdata.co.nz 0.0% 22 10.8 10.8 10.7 10.8 0.0 3. ge0-0-0-809.v4sjc9.acsdata.co.nz 0.0% 22 145.9 147.4 145.7 181.9 7.7 4. ae7-216.cr0-sjc2.ip6.gtt.net 0.0% 22 145.0 147.6 144.9 203.2 12.4 5. et-3-3-0.cr2-lax2.ip6.gtt.net 0.0% 22 156.0 155.5 155.3 156.0 0.0 6. te7-2.r02.lax2.phyber.com 9.5% 22 155.4 155.4 155.2 155.6 0.0 7. 2607:f238:2::1 4.8% 21 154.9 159.6 154.8 248.4 20.9 This looks like to solve the issue. Cheers, -- Lincoln Reid zl1ljr > -----Original Message----- > From: pool [mailto:[email protected] > g] 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 _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
