FYI, HTTPv6 access to www.bt.com was down for me from 3:46 to 4:51 pm U.S. Central today. While that FQDN resolves to 2a00:2381:ffff::1 for me, it's possible our issues were related.
I will now start monitoring www.ipv6.bt.com, too. Frank -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Thomas Schäfer Sent: Saturday, January 03, 2015 4:44 PM To: IPv6 Ops list Subject: www.ipv6.bt.com -- DTAG, question to the routing experts Hi, I can't reach www.ipv6.bt.com from DTAG (2003:63:242d:2c00:beae:c5ff:feb5:2088 and 2a01:598:ffff:815b:da31:a7bc:667e:1438) from here: http://ipv6-test.com/validate.php it works also from DFN/LRZ. If I look here http://lg.he.net/ I see /32 networks. Is it the /32-/48-filter-problem again, or is it something different? ping6 www.ipv6.bt.com PING www.ipv6.bt.com(2a00:1a48:10a1::538a:9648) 56 data bytes >From 2003:0:1803:8268::2 icmp_seq=6 Destination unreachable: No route ^C --- www.ipv6.bt.com ping statistics --- 8 packets transmitted, 0 received, +1 errors, 100% packet loss, time 7000ms /usr/sbin/traceroute6 www.ipv6.bt.com traceroute to www.ipv6.bt.com (2a00:1a48:10a1::538a:9648), 30 hops max, 80 byte packets 1 fritz.box (2003:63:242d:2c00:2665:11ff:fe8f:181f) 0.684 ms 1.037 ms 1.018 ms 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * 2003:0:1803:8268::2 (2003:0:1803:8268::2) 29.451 ms !N * Regards, Thomas
