at&t U-verse 6rd in Santa Clara County
http://www.dslreports.com/forum/remark,26841639 Is at&t for real?
printf "%02x%02x:%02x%02x\n" 76 220 xx xx ; printf "%02x%02x:%02x%02x\n" 99 124 xxx xxx 4cdc:20yy 637c:YYYYFrom MSK.
# traceroute6 2602:304:cdc2:0yy0::1 ; traceroute6 2602:306:37cY:YYY0::1 traceroute6 to 2602:304:cdc2:0yy0::1 (2602:304:cdc2:yy0::1) from Z, 16 hops max, 12 byte packets Skipping 2 intermediate hops 3 xe012-438.RT.MR.MSK.RU.retn.net 1.320 ms 1.191 ms 1.248 ms 4 RT.TLX.NYC.US.retn.net 124.866 ms 124.400 ms 125.080 ms 5 as7018-att.10gigabitethernet2-3.core1.nyc4.he.net 137.598 ms 179.680 ms 150.144 ms 6 * * * 7 * * * 8 2001:1890:ff:ffff:12:122:99:125 139.270 ms 138.714 ms 138.885 ms 9 2602:300:c533:1510::4 138.903 ms 138.695 ms 138.780 ms 10 2602:300:c533:1510::5 189.738 ms 189.757 ms 190.096 ms 11 * * * 12 * * * 13 * * * 14 2602:300:c533:1510::5 190.810 ms 190.647 ms 190.884 ms traceroute6 to 2602:306:37cY:YYY0::1 (2602:306:37cY:YYY0::1) from Z, 16 hops max, 12 byte packets Skipping 2 intermediate hops 3 xe012-438.RT.MR.MSK.RU.retn.net 1.245 ms 1.090 ms 1.112 ms 4 RT.TLX.NYC.US.retn.net 124.698 ms 124.320 ms 124.783 ms 5 as7018-att.10gigabitethernet2-3.core1.nyc4.he.net 137.132 ms 137.704 ms 138.025 ms 6 * * * 7 * * * 8 2001:1890:ff:ffff:12:122:99:125 139.692 ms 140.326 ms 139.774 ms 9 2602:300:c533:1510::4 138.898 ms 139.584 ms 145.563 ms 10 2602:300:c533:1510::5 189.704 ms 190.298 ms 190.905 ms 11 * * * 12 2602:300:c533:1510::5 194.267 ms 192.703 ms 191.208 ms 13 * * * 14 * * * 15 2602:300:c533:1510::5 191.379 ms * 190.522 ms 16 * * *From FMT (at&t has a crappy route, but the routing definitely gets full trip to LA and safely back to the Bay Area).
# traceroute6 2602:304:cdc2:0yy0::1 ; traceroute6 2602:306:37cY:YYY0::1 traceroute to 2602:304:cdc2:0yy0::1 (2602:304:cdc2:yy0::1), 16 hops max, 80 byte packets 2 10gigabitethernet2-3.core1.fmt1.he.net (2001:470:1:1db::1) 8.677 ms 8.680 ms 8.721 ms 3 gige-g4-8.core1.fmt2.he.net (2001:470:0:2d::2) 0.376 ms 0.427 ms 0.416 ms 4 10gigabitethernet6-4.core1.lax1.he.net (2001:470:0:18d::2) 8.487 ms 8.496 ms 8.669 ms 5 10gigabitethernet1-3.core1.lax2.he.net (2001:470:0:72::2) 12.416 ms 12.880 ms 13.510 ms 6 att-internet4-as7018.10gigabitethernet5-2.core1.lax2.he.net (2001:470:0:1e6::2) 9.267 ms 9.335 ms 9.417 ms 7 * * * 8 * * * 9 2001:1890:ff:ffff:12:122:114:41 (2001:1890:ff:ffff:12:122:114:41) 21.074 ms 21.109 ms 21.086 ms 10 2602:300:c533:1510::5 (2602:300:c533:1510::5) 20.761 ms 20.756 ms 20.812 ms 11 2602:300:c533:1510::5 (2602:300:c533:1510::5) 22.213 ms 21.943 ms 22.371 ms traceroute to 2602:306:37cY:YYY0::1 (2602:306:37cY:YYY0::1), 16 hops max, 80 byte packets 2 10gigabitethernet2-3.core1.fmt1.he.net (2001:470:1:1db::1) 0.536 ms 0.499 ms 0.443 ms 3 gige-g4-8.core1.fmt2.he.net (2001:470:0:2d::2) 4.335 ms 4.997 ms 4.995 ms 4 10gigabitethernet6-4.core1.lax1.he.net (2001:470:0:18d::2) 8.663 ms 8.649 ms 8.635 ms 5 10gigabitethernet1-3.core1.lax2.he.net (2001:470:0:72::2) 9.270 ms 9.617 ms 9.201 ms 6 att-internet4-as7018.10gigabitethernet5-2.core1.lax2.he.net (2001:470:0:1e6::2) 9.574 ms 9.549 ms 9.511 ms 7 * * * 8 * * * 9 2001:1890:ff:ffff:12:122:114:41 (2001:1890:ff:ffff:12:122:114:41) 21.208 ms 21.135 ms 21.165 ms 10 2602:300:c533:1510::5 (2602:300:c533:1510::5) 20.762 ms 20.773 ms 20.798 ms 11 * * * 12 * * * 13 * * * 14 * * * 15 2602:300:c533:1510::5 (2602:300:c533:1510::5) 22.326 ms 23.112 ms 22.765 ms 16 * * *Wow… … What’s next? Finally the 40/10 HSI for BPON subscribers? :-) Or 200/100 HSI with a GPON upgrade? (-: