Reply to comment:

Anonymous
We are in the process of upgrading RIPE Atlas probes to a firmware that can do many more measurements, both more simultaneous measurements and more kinds of measurements. Some of the probes that were upgraded early did record answers from F in Beijing over IPv6. One of the is at my house and uses a DSL connection from xs4all with native IPV6 where this started at Sat Oct 1 18:01:08 UTC and ended at Sun Oct 2 19:01:11 UTC. <br /><br />Here are also two traceroutes from that probe. Before<br /><br />RESULT 6004 ongoing 1317491366 traceroute to 2001:500:2f::f (2001:500:2f::f), 32 hops max, 16 byte packets <br />&nbsp;1 2001:980:3500:1:224:feff:fe19:b61c 1.526 ms 1.614 ms 1.669 ms <br />&nbsp;&nbsp;2 2001:888:0:4601::1 10.604 ms 10.119 ms 10.064 ms <br />&nbsp;&nbsp;3 2001:888:0:4603::2 9.436 ms 9.405 ms 9.325 ms <br />&nbsp;&nbsp;4 2001:888:1:4005::1 9.723 ms 10.076 ms 10.270 ms <br />&nbsp;&nbsp;5 2001:7f8:1::a500:6939:1 10.061 ms 18.985 ms 9.942 ms <br />&nbsp;&nbsp;6 2001:470:0:3f::1 18.148 ms 18.081 ms 20.498 ms <br />&nbsp;&nbsp;7 2001:470:0:3e::1 88.401 ms 94.233 ms 85.504 ms <br />&nbsp;&nbsp;8 2001:470:0:1c6::2 103.191 ms 109.736 ms 102.862 ms <br />&nbsp;&nbsp;9 2001:470:1:34::2 123.513 ms 123.706 ms 123.376 ms <br />&nbsp;10 2001:500:2f::f 123.175 ms 123.076 ms 123.218 ms <br /><br />and during:<br /><br />RESULT 6004 ongoing 1317493151 traceroute to 2001:500:2f::f (2001:500:2f::f), 32 hops max, 16 byte packets<br />&nbsp;1 2001:980:3500:1:224:feff:fe19:b61c 1.517 ms 1.442 ms 1.679 ms <br />&nbsp;&nbsp;2 2001:888:0:4601::1 10.495 ms 10.041 ms 14.487 ms<br />&nbsp;&nbsp;3 2001:888:0:4603::2 10.117 ms 9.625 ms 9.507 ms<br />&nbsp;&nbsp;4 2001:888:1:4005::1 10.919 ms 10.569 ms 9.855 ms<br />&nbsp;&nbsp;5 2001:7f8:1::a500:6939:1 10.429 ms 10.547 ms 18.925 ms <br />&nbsp;&nbsp;6 2001:470:0:3f::1 28.205 ms 19.843 ms 23.405 ms<br />&nbsp;&nbsp;7 2001:470:0:3e::1 91.845 ms 94.497 ms 96.812 ms<br />&nbsp;&nbsp;8 2001:470:0:10e::1 147.166 ms 146.861 ms 146.905 ms<br />&nbsp;&nbsp;9 2001:470:0:16b::2 306.184 ms 305.656 ms 305.636 ms<br />&nbsp;10 2001:7fa:0:1::ca28:a1be 314.605 ms 307.503 ms 309.400 ms<br />&nbsp;11 2001:252:0:101::1 356.118 ms 366.003 ms 356.810 ms<br />&nbsp;12 2001:252:0:1::4 352.575 ms 353.977 ms 352.047 ms<br />&nbsp;13 2001:e18:10cc:101:102::1 358.226 ms 353.353 ms 361.451 ms<br />&nbsp;14 2001:e18:10cc:101:106::2 359.442 ms 361.659 ms 361.094 ms<br />&nbsp;15 2001:cc0:1fff::2 358.191 ms 362.187 ms 367.455 ms<br />&nbsp;16 2001:dc7:ff:1005::1:6 361.919 ms 355.630 ms 394.090 ms<br />&nbsp;17 2001:500:2f::f 356.187 ms 358.515 ms 352.517 ms <br /><br /><br />So once all RIPE Atlas Probes are upgraded to the new firmware (4.260) we will have even more vantage points to monitor this from. You can follow the firware upgrade process here:<br /><a href="http://atlas.ripe.net/dynamic/stats/stats.probe_versions.png" rel="nofollow">http://atlas.ripe.net/[&hellip;]/stats.probe_versions.png</a>