I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there: Having trouble reaching some sites. Handle DDC1-SIXXS tunnel usdal01 here are some tracert Tracing route to ipv6.l.google.com [2001:4860:0:2001::68] from 2001:4830:1200:152::2 over a maximum of 30 hops: 1 * * * Request timed out. 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. Tracing route to news.ipv6.eweka.nl [2001:4de0:1::1:1] from 2001:4830:1200:152::2 over a maximum of 30 hops: 1 * * * Request timed out. 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. Tracing route to sixxs.net [2001:838:1:1:210:dcff:fe20:7c7c] from 2001:1938:80:52::2 over a maximum of 30 hops: 1 * * * Request timed out. 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 239 ms 235 ms 225 ms noc.sixxs.net [2001:838:1:1:210:dcff:fe20:7c7c] Trace complete. AICCU test ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.100) ### This should return so called 'echo replies' ### If it doesn't then check your firewall settings ### Your local endpoint should always be pingable ### It could also indicate problems with your IPv4 stack Pinging 192.168.1.100 with 32 bytes of data: Reply from 192.168.1.100: bytes=32 time<1ms TTL=128 Reply from 192.168.1.100: bytes=32 time<1ms TTL=128 Reply from 192.168.1.100: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.1.100: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms ###### Did this work? [Y/n] y ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (209.197.16.66) ### These pings should reach the PoP and come back to you ### In case there are problems along the route between your ### host and the PoP this could not return replies ### Check your firewall settings if problems occur Pinging 209.197.16.66 with 32 bytes of data: Reply from 209.197.16.66: bytes=32 time=109ms TTL=54 Reply from 209.197.16.66: bytes=32 time=96ms TTL=54 Reply from 209.197.16.66: bytes=32 time=70ms TTL=54 Ping statistics for 209.197.16.66: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 70ms, Maximum = 109ms, Average = 91ms ###### Did this work? [Y/n] y ####### [3/8] Traceroute to the PoP (209.197.16.66) over IPv4 ### This traceroute should reach the PoP ### In case this traceroute fails then you have no connectivity ### to the PoP and this is most probably the problem Tracing route to 209.197.16.66 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 105 ms 97 ms 57 ms 10.7.112.1 3 29 ms 29 ms 23 ms ge-2-2-0-0.CORE-RTR1.PHIL.verizon-gni.net [130.81.8.9] 4 53 ms 35 ms 41 ms so-7-1-0-0.BB-RTR1.PHIL.verizon-gni.net [130.81.20.136] 5 86 ms 98 ms 122 ms 0.so-6-0-0.XL1.PHL6.ALTER.NET [152.63.3.77] 6 59 ms 53 ms 38 ms 0.so-5-2-0.XL3.IAD8.ALTER.NET [152.63.36.25] 7 127 ms 112 ms 85 ms 0.ge-6-0-0.BR2.IAD8.ALTER.NET [152.63.41.149] 8 34 ms 40 ms 57 ms 204.255.169.202 9 52 ms 29 ms 38 ms 67.17.199.2 10 30 ms 60 ms 75 ms 2-3.r2.dc.hwng.net [69.16.190.26] 11 75 ms 73 ms 73 ms 1-1.r2.da.hwng.net [209.197.1.130] 12 66 ms 109 ms 95 ms 1-3.r1.da.hwng.net [209.197.8.9] 13 166 ms 136 ms 177 ms 209.197.16.66 Trace complete. ###### Did this work? [Y/n] y ###### [4/8] Checking if we can ping IPv6 localhost (::1) ### This confirms if your IPv6 is working ### If ::1 doesn't reply then something is wrong with your IPv6 stack Pinging ::1 with 32 bytes of data: Reply from ::1: time<1ms Reply from ::1: time<1ms Reply from ::1: time<1ms Ping statistics for ::1: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms ###### Did this work? [Y/n] y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1938:80:52::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables Pinging 2001:1938:80:52::2 with 32 bytes of data: Reply from 2001:1938:80:52::2: time<1ms Reply from 2001:1938:80:52::2: time<1ms Reply from 2001:1938:80:52::2: time<1ms Ping statistics for 2001:1938:80:52::2: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms ###### Did this work? [Y/n] y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1938:80:52::1) ### This confirms the reachability of the other side of the tunnel ### If it doesn't reply then check your interface and routing tables ### Don't forget to check your firewall (both IPv4 and IPv6) of course ### If the previous test was succesful then this could be both ### a firewalling and a routing/interface problem Pinging 2001:1938:80:52::1 with 32 bytes of data: Reply from 2001:1938:80:52::1: time=112ms Reply from 2001:1938:80:52::1: time=84ms Reply from 2001:1938:80:52::1: time=87ms Ping statistics for 2001:1938:80:52::1: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 84ms, Maximum = 112ms, Average = 94ms ###### Did this work? [Y/n] y ###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net) ### This confirms that you can reach the central machine of SixXS ### If that one is reachable you should be able to reach most IPv6 destinations ### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection ### If your browser supports IPv6 and uses it of course. Tracing route to noc.sixxs.net [2001:838:1:1:210:dcff:fe20:7c7c] from 2001:1938:80:52::2 over a maximum of 30 hops: 1 93 ms 84 ms 73 ms gw-83.dal-01.us.sixxs.net [2001:1938:80:52::1] 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 234 ms 218 ms 217 ms noc.sixxs.net [2001:838:1:1:210:dcff:fe20:7c7c] Trace complete. ###### Did this work? [Y/n] y ###### [8/8] Traceroute6 to (www.kame.net) ### This confirms that you can reach a Japanese IPv6 destination ### If that one is reachable you should be able to reach most IPv6 destinations ### You should also check http://www.kame.net which should display ### a animated kame (turtle), of course only when your browser supports and uses IPv6 Tracing route to www.kame.net [2001:200:0:8002:203:47ff:fea5:3085] from 2001:1938:80:52::2 over a maximum of 30 hops: 1 * * * Request timed out. 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * 437 ms 407 ms orange.kame.net [2001:200:0:8002:203:47ff:fea5:3085] Trace complete. ###### Did this work? [Y/n] y ###### ACCU Quick Connectivity Test (done)