AT&T IPv6 latency in Bay Area: Local IPv6 around San Jose?
I’m on AT&T’s IPv6 network in San Jose, CA, and I’m trying to find the best edge nodes latency-wise. Here’s what I have so far, California-wise.
% alias traceroute6 traceroute6 -w2 -l % traceroute6 ipv6.akamai.com traceroute6 to a152.i6g1.akamai.net (2600:5:3700:2::c703:730b) from 2602:306:37cY:YYY0::1, 30 hops max, 12 byte packets 1 2602:300:c533:1510::5 (2602:300:c533:1510::5) 1.863 ms 1.149 ms 1.304 ms 2 sfcca01jt.ip.att.net (2001:1890:ff:ffff:12:122:126:241) 8.013 ms 3.031 ms 3.605 ms 3 2001:1890:1fff:404:192:205:35:18 (2001:1890:1fff:404:192:205:35:18) 5.989 ms 21.109 ms * 4 2600:5:3700:2::c703:730b (2600:5:3700:2::c703:730b) 5.248 ms 7.884 ms 5.317 ms % alias postcmd date % traceroute6 ipv6.akamai.com Fri 17 Feb 2012 12:13:45 PST traceroute6 to a152.i6g1.akamai.net (2001:559:0:301::6011:6d48) from 2602:306:37cY:YYY0::1, 30 hops max, 12 byte packets 1 2602:300:c533:1510::5 (2602:300:c533:1510::5) 1.701 ms 1.306 ms 1.336 ms 2 sfcca03jt.ip.att.net (2001:1890:ff:ffff:12:122:126:243) 3.134 ms 2.941 ms 3.006 ms 3 2001:1890:1fff:400:192:205:37:2 (2001:1890:1fff:400:192:205:37:2) 9.998 ms 7.029 ms 7.734 ms 4 pos-2-2-0-0-cr01.sanjose.ca.ibone.comcast.net (2001:558:0:f58d::1) 10.499 ms 12.967 ms 10.206 ms 5 pos-0-4-0-0-pe01.529bryant.ca.ibone.comcast.net (2001:558:0:f5e4::2) 9.635 ms 8.965 ms 8.941 ms 6 2001:559::16 (2001:559::16) 11.532 ms 8.532 ms 8.35 ms 7 2001:559:0:301::6011:6d48 (2001:559:0:301::6011:6d48) 8.428 ms 8.403 ms 8.437 ms % traceroute6 www.limelight.com Fri 17 Feb 2012 12:14:09 PST traceroute6 to llnw.vo.llnwd.net (2607:f4e8:110:104:230:48ff:fe87:3054) from 2602:306:37cY:YYY0::1, 30 hops max, 12 byte packets 1 2602:300:c533:1510::5 (2602:300:c533:1510::5) 1.613 ms 1.336 ms 1.281 ms 2 sfcca01jt.ip.att.net (2001:1890:ff:ffff:12:122:126:241) 2.917 ms 3.037 ms 2.898 ms 3 2001:450:2008:100::109 (2001:450:2008:100::109) 70.089 ms 70.23 ms 70.255 ms 4 2001:450:2002:2c6::2 (2001:450:2002:2c6::2) 16.898 ms 24.493 ms 13.562 ms 5 ve4.fr3.snv1.ipv6.llnw.net (2607:f4e8:1:a4::2) 14.659 ms 20.964 ms 14.185 ms 6 cds205.sjc.llnw.net (2607:f4e8:110:104:230:48ff:fe87:3054) 15.343 ms 15.902 ms 16.278 ms % traceroute6 ipv6.google.com Fri 17 Feb 2012 12:14:35 PST traceroute6 to ipv6.l.google.com (2001:4860:4001:800::1011) from 2602:306:37cY:YYY0::1, 30 hops max, 12 byte packets 1 2602:300:c533:1510::5 (2602:300:c533:1510::5) 1.749 ms 1.173 ms 1.346 ms 2 sj2ca404me3.ip.att.net (2001:1890:ff:ffff:12:122:119:192) 4.048 ms 3.999 ms 4.059 ms 3 2001:1890:c00:8c02::1116:e9cb (2001:1890:c00:8c02::1116:e9cb) 50.029 ms 48.965 ms 47.51 ms 4 2001:4860::1:0:21 (2001:4860::1:0:21) 5.225 ms 5.96 ms 5.481 ms 5 2001:4860:0:1::1ab (2001:4860:0:1::1ab) 5.381 ms 5.204 ms 5.305 ms 6 2001:4860:4001:800::17 (2001:4860:4001:800::17) 54.298 ms 53.502 ms 53.744 ms % traceroute6 ns2.he.net Fri 17 Feb 2012 12:15:46 PST traceroute6 to ns2.he.net (2001:470:200::2) from 2602:306:37cY:YYY0::1, 30 hops max, 12 byte packets 1 2602:300:c533:1510::5 (2602:300:c533:1510::5) 1.601 ms 1.266 ms 1.283 ms 2 la2ca02jt.ip.att.net (2001:1890:ff:ffff:12:122:127:43) 13.73 ms 13.632 ms 13.996 ms 3 10gigabitethernet5-2.core1.lax2.he.net (2001:470:0:1e6::1) 18.977 ms 13.617 ms 13.708 ms 4 10gigabitethernet7-3.core1.sjc2.he.net (2001:470:0:16a::1) 22.056 ms 24.109 ms 24.928 ms 5 ns2.he.net (2001:470:200::2) 22.112 ms 22.085 ms 21.968 ms % traceroute6 www.ixsystems.com Fri 17 Feb 2012 12:16:38 PST traceroute6 to web.ixsystems.com (2607:fca8:2636:8001::4) from 2602:306:37cY:YYY0::1, 30 hops max, 12 byte packets 1 2602:300:c533:1510::5 (2602:300:c533:1510::5) 1.629 ms 1.233 ms 1.183 ms 2 la2ca02jt.ip.att.net (2001:1890:ff:ffff:12:122:127:43) 14.812 ms 13.473 ms 13.863 ms 3 10gigabitethernet5-2.core1.lax2.he.net (2001:470:0:1e6::1) 14.281 ms 15.176 ms 13.682 ms 4 10gigabitethernet2-1.core1.lax1.he.net (2001:470:0:72::1) 13.531 ms 18.466 ms 20.744 ms 5 2607:fca8:1530::1 (2607:fca8:1530::1) 13.688 ms 13.865 ms 13.782 ms 6 2607:fca8:2636:8001::4 (2607:fca8:2636:8001::4) 14.136 ms 14.481 ms 14.672 ms % traceroute6 www.arpnetworks.com Fri 17 Feb 2012 12:17:02 PST traceroute6 to www.arpnetworks.com (2607:f2f8:0:102::3) from 2602:306:37cY:YYY0::1, 30 hops max, 12 byte packets 1 2602:300:c533:1510::5 (2602:300:c533:1510::5) 1.74 ms 1.222 ms 1.182 ms 2 sfcca01jt.ip.att.net (2001:1890:ff:ffff:12:122:126:241) 113.136 ms 3.134 ms 2.922 ms 3 2001:450:2008:100::109 (2001:450:2008:100::109) 150.088 ms 2001:450:2008:100::c5 (2001:450:2008:100::c5) 69.797 ms 70.066 ms 4 * * * 5 2607:f2f8:100:105::1 (2607:f2f8:100:105::1) 14.123 ms 14.058 ms 14.096 ms 6 www.arpnetworks.com (2607:f2f8:0:102::3) 14.616 ms 14.429 ms 14.47 ms % traceroute6 obsd.isc.org Fri 17 Feb 2012 12:20:22 PST traceroute6 to obsd.isc.org (2001:4f8:3:36::217) from 2602:306:37cY:YYY0::1, 30 hops max, 12 byte packets 1 2602:300:c533:1510::5 (2602:300:c533:1510::5) 1.753 ms 1.213 ms 1.905 ms 2 sfcca01jt.ip.att.net (2001:1890:ff:ffff:12:122:126:241) 2.957 ms 4.544 ms 3.373 ms 3 2001:1890:1fff:40d:192:205:33:50 (2001:1890:1fff:40d:192:205:33:50) 4.895 ms * 5.069 ms 4 chi-bb1-v6.telia.net (2001:2000:3018:2c::1) 55.734 ms 55.583 ms 55.652 ms 5 isc-ic-117366-chi-bb1.c.telia.net (2001:2000:3080:138::2) 55.852 ms 56.083 ms 56.078 ms 6 int-0-0-1-8.r1.pao1.isc.org (2001:4f8:0:1::4a:1) 108.838 ms 108.864 ms 110.633 ms 7 int-0-1-0-0.r1.sql1.isc.org (2001:4f8:1b:1::8:2) 112.205 ms 108.617 ms 109.507 ms 8 2001:4f8:3:36::217 (2001:4f8:3:36::217) 108.234 ms 107.538 ms 108.512 ms
So far, the now-disappeared DNS resolution of ipv6.akamai.com over at Sprint seemed to have had the best latency earlier this morning, of only 5.3ms.
IPv4-wise, I can still get 3.7ms to some CDN host at nlayer.net (see http://www.dslreports.com/forum/remark,26669632 and the traceroute below), so, I’m thinking that something around 4ms should be entirely possible with IPv6, too.
% traceroute -I 69.22.162.122 Fri 17 Feb 2012 12:41:33 PST traceroute to 69.22.162.122 (69.22.162.122), 32 hops max, 60 byte packets 5 12.83.39.145 (12.83.39.145) 16.198 ms 2.141 ms 1.800 ms 6 ppp-151-164-52-233.rcsntx.swbell.net (151.164.52.233) 99.646 ms 207.202 ms 5.913 ms 7 asn4436-nlayer.pxpaca.sbcglobal.net (151.164.46.70) 5.041 ms 4.636 ms 4.421 ms 8 69.22.162.122 (69.22.162.122) 3.802 ms 3.792 ms 3.710 ms
Any ideas what other IPv6 hosts are in the Bay Area that could have good latency with AT&T’s IPv6 network?
written for, and discussion at, http://www.dslreports.com/forum/r26907835-IPv6-latency-BayArea-Local-IPv6-around-San-Jose-
