Hi, that seems to be the key - thank you! The problem was not incoming traffic, but outgoing traffic from my machine to the rest of the world. My carrier disabled Level3 for now and the problem is gone :-)
Traceroute to 2a02:a00:1009:6202::123 1 (2607:f238:2::1) 0.631 0.790 0.782 2 (2607:f238:0:8::1) 1.001 0.994 1.240 3 * * * 4 ae-3.r00.lsanca07.us.bb.gin.ntt.net (2001:418:0:2000::161) 0.729 0.729 0.935 5 (2003:3c0:1103:4002::1) 73.604 73.606 73.597 6 (2003:0:1206::1) 156.303 156.264 156.463 7 (2003:0:1206:4::2274:5) 155.157 155.160 155.154 8 r1.wup.tal.de (2a01:170:0:1:11::1) 158.010 157.979 157.988 9 (2a01:170:0:2:3::c18) 156.198 154.856 154.611 10 ntp2.301-moved.de (2a02:a00:1009:6202::123) 158.661 158.634 159.248 Thanks to all! Greetings from Wuppertal Max Am 23.03.2016 um 12:25 schrieb Tore Anderson: > > 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. _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
