* Max Grobecker <[email protected]> > my IPv6 pool server [1] is marked unreachable since more ore less > exactly midnight - and I can't figure out why. The server is > reachable via IPv6, tested from different networks and the service is > also up and running. Via IPv4 the exactly same machine is reachable > and has score +20, so I'm sure it is a problem with the IPv6 > monitoring.
Hi, Is Level 3 involved by any chance? I'm having massive problems with IPv6 through Level3/AS3356 since 2016-03-22 23:56:42 UTC. I'm currently escalating a trouble ticket through their customer portal as fast and high as the system will let me. Basically they're advertising routes to me normally, but blackholing all the traffic. I'm not getting any replies from their eBGP neighbour address even. The issue is even reproducable from their own looking glass at http://lookingglass.level3.net/. 1) Ping to 2a02:26f0:ac:189::1bd8 (Akamai) from Oslo: No responses. 2) Traceroute to same address from same PoP: "No route to destination". 3) BGP lookup to 2a02:26f0:ac::/48 from same PoP: 4 routes shown. Problems occur from other sites too, not just Oslo. It varies a bit what works from where, which is why I suspect this might be the problem for you even though your server responds fine here from Oslo. Anyway, the results from test #2 directly contradicts results from #3. The address responds fine from ping from various other sources on the Internet (whose paths do not traverse Level 3). It's not just Akamai, that's just an example - I could list dozens more destinations impacted. Tore _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
