|
Cogestion between Occaid and TATA?
![[us]](/s/countries/us.gif) Shadow Hawkins on Friday, 22 February 2013 00:14:03
tracert ipv6.speedtest.comcast.net
Tracing route to ipv6.speedtest.g.comcast.net [2001:558:1010:5:68:87:73:52]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 2001:4830:1621::2
2 26 ms 26 ms 26 ms gw-60.qas-01.us.sixxs.net [2001:4830:1600:3b::1]
3 27 ms 27 ms 26 ms sixxs-asbnva-gw.customer.occaid.net [2001:4830:e6:7::2]
4 27 ms 28 ms 26 ms sixxs-gw.hotnic.us.occaid.net [2001:4830:e6:7::1]
5 27 ms 29 ms 28 ms ibr01-ve96.asbn01.occaid.net [2001:504:0:2:0:3:71:1]
6 35 ms 34 ms 33 ms bbr01-p2-1.nwrk01.occaid.net [2001:4830:ff:f150::1]
7 43 ms 41 ms 42 ms tata.nwrk01.occaid.net [2001:4830:e2:a::2]
8 175 ms 179 ms 194 ms if-ge-11-2-8.0.tcore1.NYY-NewYork.ipv6.as6453.net [2001:5a0:400:500::15]
9 175 ms 175 ms 174 ms if-ae5.5.tcore1.NTO-NewYork.ipv6.as6453.net [2001:5a0:400:200::e]
10 205 ms 182 ms 185 ms if-4-0-0.15.core3.NTO-NewYork.ipv6.as6453.net [2001:5a0:a00::21]
11 250 ms 194 ms 187 ms 2001:5a0:a00:200::e
12 192 ms 181 ms 179 ms pos-1-7-0-0-cr01.newyork.ny.ibone.comcast.net [2001:558:0:f5ea::1]
13 184 ms 249 ms 184 ms te-0-15-0-4-ar01.crosstown.mn.minn.comcast.net [2001:558:0:f6ed::2]
14 183 ms 235 ms 184 ms te-2-1-ur04-d.manassascc.va.bad.comcast.net [2001:558:340:c::1]
15 187 ms 184 ms 184 ms 2001:558:1010:5:68:87:73:52
Trace complete.
Cogestion between Occaid and TATA?
While that traceroute shows latency rising quite a bit after hop 7, latency != congestion. Also it seems that it is all happening inside the TATA/comcast network.
What is your exact concern, can you provide more details?
From Switzerland I can't even reach that site:
traceroute6 to ipv6.speedtest.g.comcast.net (2001:558:1010:5:68:87:73:52) from 2a02:2528:[..], 64 hops max, 12 byte packets
[..]
4 ge0-1.gv1.ip-max.sixxs.net 31.784 ms 31.219 ms 31.163 ms
5 ge3-14.ar01.gva253.ip-max.net 33.269 ms 31.344 ms 32.504 ms
6 ge3-8.cr01.gva253.ip-max.net 31.296 ms 34.388 ms 31.432 ms
7 ge3-2.br01.gva252.ip-max.net 47.355 ms 31.841 ms 33.517 ms
8 2001:450:2002:24d::1 49.462 ms 43.664 ms 43.556 ms
9 * * *
10 2001:450:2002:4c::2 141.030 ms 132.541 ms 131.888 ms
11 2001:450:2002:4c::2 131.738 ms 131.841 ms 131.738 ms
12 so-1-0-0-0-ar04.whitemarsh.md.bad.comcast.net 135.843 ms 133.857 ms 135.354 ms
13 te-2-1-ur04-d.manassascc.va.bad.comcast.net 140.055 ms 139.034 ms 138.484 ms
14 * * *
15 * * *
16 *^C
almost a similar latency though... and that is from Europe ;)
From the Netherlands:
traceroute to ipv6.speedtest.comcast.net (2001:558:1010:5:68:87:73:52), 30 hops max, 80 byte packets
[..]
3 gi2-11.nikhef.ipv6.concepts-ict.net (2001:838:5:a::1) 1.933 ms 1.978 ms 2.039 ms
4 a3820.conceptsict.atom86.net (2a00:1188:4::3102) 5.735 ms 5.732 ms 5.735 ms
5 xe-4-2-0.ams12.ip6.tinet.net (2001:668:0:3::6000:1a1) 5.969 ms 5.997 ms 6.055 ms
6 xe-10-2-0.nyc32.ip6.tinet.net (2001:668:0:2::1:2321) 82.888 ms xe-8-3-0.nyc30.ip6.tinet.net (2001:668:0:2::1:1a32) 78.824 ms xe-0-2-0.nyc30.ip6.tinet.net (2001:668:0:2::142) 78.902 ms
7 te-1-11-0-4-pe01.111eighthave.ny.ibone.comcast.net (2001:558:0:f750::1) 80.246 ms te-1-11-0-5-pe01.111eighthave.ny.ibone.comcast.net (2001:558:0:f751::1) 80.139 ms 80.109 ms
8 pos-1-11-0-0-cr01.newyork.ny.ibone.comcast.net (2001:558:0:f5af::1) 80.933 ms 84.142 ms 80.875 ms
9 2001:558:0:f78f::2 (2001:558:0:f78f::2) 87.228 ms 87.823 ms 88.656 ms
10 te-2-1-ur04-d.manassascc.va.bad.comcast.net (2001:558:340:c::1) 89.045 ms 89.452 ms 89.321 ms
11 * * *
12 * * *
Also unreachable. Almost looks like it is a Comcast only service
From Chicago over Level3:
traceroute to ipv6.speedtest.g.comcast.net (2001:558:1010:5:68:87:73:52) from 2620:0:6b0:[..], 30 hops max, 16 byte packets
[..]
4 COMCAST-IP.edge1.Chicago2.Level3.net (2001:1900:2100::3de) 18.522 ms 15.579 ms 15.07 ms
5 he-1-3-0-0-cr01.350ecermak.il.ibone.comcast.net (2001:558:0:f607::2) 13.823 ms 17.129 ms 11.906 ms
6 he-4-5-0-0-cr01.newyork.ny.ibone.comcast.net (2001:558:0:f625::1) 75.734 ms 74.14 ms 71.9 ms
7 so-4-0-0-0-ar03.seattle.wa.seattle.comcast.net (2001:558:0:f6b4::2) 72.257 ms 73.271 ms 73.139 ms
8 te-2-1-ur04-d.manassascc.va.bad.comcast.net (2001:558:340:c::1) 77.477 ms 76.413 ms 73.532 ms
9 * * *
Another traceroute that does not finish
And from San Francisco area:
traceroute to ipv6.speedtest.comcast.net (2001:558:1010:5:68:87:73:52), 30 hops max, 80 byte packets
[..]
3 int-0-1-0-0.r2.pao1.isc.org (2001:4f8:0:1::4:2) 1.332 ms 1.852 ms int-0-1-0-1.r2.pao1.isc.org (2001:4f8:0:1::5:2) 1.886 ms
4 2001:559::14d (2001:559::14d) 1.311 ms 1.302 ms 1.800 ms
5 pos-1-11-0-0-cr01.sanjose.ca.ibone.comcast.net (2001:558:0:f5c1::1) 2.831 ms 2.839 ms 2.823 ms
6 he-0-7-0-0-cr01.denverqwest.co.ibone.comcast.net (2001:558:0:f65f::2) 60.887 ms 59.957 ms 59.926 ms
7 he-3-13-0-0-cr01.denver.co.ibone.comcast.net (2001:558:0:f652::1) 63.361 ms 63.347 ms 63.320 ms
8 he-5-9-0-0-cr01.350ecermak.il.ibone.comcast.net (2001:558:0:f64a::1) 59.138 ms 58.982 ms 59.028 ms
9 he-4-2-0-0-cr01.newyork.ny.ibone.comcast.net (2001:558:0:f622::1) 74.345 ms 73.599 ms 73.611 ms
10 so-9-1-0-0-ar04.whitemarsh.md.bad.comcast.net (2001:558:0:f756::2) 75.639 ms 75.565 ms 75.539 ms
11 te-2-1-ur04-d.manassascc.va.bad.comcast.net (2001:558:340:c::1) 79.927 ms 80.031 ms 80.131 ms
12 * * *
None of these traceroutes finish, thus I guess that that service is either down or is filtering ICMPv6, which would be silly for something that sounds like a speedtest.
Cogestion between Occaid and TATA?
Shadow Hawkins on Thursday, 28 March 2013 11:44:07
I have been observing this for awhile. I cannot seem to get more than 6mbit/s. As it looks to be an inbound to OCCAID from TATA. I am not sure OCCAID has the power to do much about this since it is inbound.
From my Comcast FTTH circuit to my SixXS/OCCAID aiccu tunnel on a Verizon FTTH circuit.
traceroute6 to 2001:4830:1600:401::2 (2001:4830:1600:401::2) from 2001:559:800c:1005:6012:2daf:df1a:c6ad, 64 hops max, 12 byte packets
1 2001:559:800c:1005::1 0.327 ms 0.319 ms 0.231 ms
2 2001:559:0:84::1 0.592 ms 0.591 ms 0.594 ms
3 ae-19-0-ar04.capitolhghts.md.bad.comcast.net 0.830 ms 0.855 ms 0.842 ms
4 pos-5-4-0-0-cr01.ashburn.va.ibone.comcast.net 5.337 ms
pos-4-3-0-0-cr01.ashburn.va.ibone.comcast.net 6.322 ms 6.263 ms
5 pos-0-4-0-0-pe01.ashburn.va.ibone.comcast.net 3.328 ms 3.253 ms 3.090 ms
6 2001:559::322 2.468 ms 2.528 ms 2.476 ms
7 if-ae8.1508.tcore2.lvw-losangeles.ipv6.as6453.net 72.320 ms 67.301 ms 84.910 ms
8 if-ae2.2.tcore1.lvw-losangeles.ipv6.as6453.net 67.289 ms
if-9-0-0.14.mcore3.laa-losangeles.ipv6.as6453.net 108.961 ms
if-12-0-0.15.mcore3.laa-losangeles.ipv6.as6453.net 133.367 ms
9 if-10-0-0.12.mcore3.laa-losangeles.ipv6.as6453.net 182.363 ms
if-15-0-0.13.mcore3.laa-losangeles.ipv6.as6453.net 241.792 ms
if-10-0-0.12.mcore3.laa-losangeles.ipv6.as6453.net 117.875 ms
10 if-2-14.mse1.sv1-santaclara.ipv6.as6453.net 80.074 ms 84.841 ms 97.462 ms
11 if-2-14.mse1.sv1-santaclara.ipv6.as6453.net 84.983 ms 75.622 ms
2001:5a0:2400::1e 78.113 ms
12 2001:5a0:2400::1e 82.050 ms
bbr01-v442.lsan01.occaid.net 93.301 ms 89.027 ms
13 bbr01-p1-2.dlls01.occaid.net 104.393 ms 96.068 ms 104.685 ms
14 bbr01-p1-0.atln01.occaid.net 104.834 ms
bbr01-p1-2.dlls01.occaid.net 107.385 ms
bbr01-p1-0.atln01.occaid.net 104.740 ms
15 bbr01-p1-0.atln01.occaid.net 96.458 ms
bbr01-g0-1.asbn01.occaid.net 100.107 ms 96.098 ms
16 equi6ix.dc.hotnic.net 95.404 ms
bbr01-g0-1.asbn01.occaid.net 100.261 ms 95.347 ms
17 equi6ix.dc.hotnic.net 96.373 ms 99.989 ms 111.724 ms
18 gw-1026.qas-01.us.sixxs.net 105.539 ms 100.467 ms 120.382 ms
19 cl-1026.qas-01.us.sixxs.net 115.850 ms 124.584 ms 103.768 ms
From SixXS/OCCAID PoP to Comcast:
traceroute6 to 2001:559:800c:1005:223:32ff:fea1:11b1 (2001:559:800c:1005:223:32ff:fea1:11b1) from 2001:4830:1600:401::2, 64 hops max, 12 byte packets
1 gw-1026.qas-01.us.sixxs.net 11.924 ms 6.620 ms 6.666 ms
2 sixxs-asbnva-gw.customer.occaid.net 6.714 ms 6.654 ms 9.662 ms
3 sixxs-gw.hotnic.us.occaid.net 7.422 ms 7.443 ms 7.475 ms
4 ibr01-ve96.asbn01.occaid.net 7.051 ms 11.512 ms 7.310 ms
5 bbr01-p2-1.nwrk01.occaid.net 17.192 ms 18.309 ms 13.445 ms
6 tata.nwrk01.occaid.net 23.562 ms 19.939 ms 23.454 ms
7 if-5-0-4.mcore4.nyy-newyork.ipv6.as6453.net 102.579 ms 107.032 ms 102.418 ms
8 if-ae5.5.tcore1.nto-newyork.ipv6.as6453.net 111.703 ms 110.043 ms 116.685 ms
9 2001:5a0:a00:200::e 103.700 ms
2001:5a0:a00:200::16 106.174 ms
2001:5a0:a00:200::32 106.242 ms
10 pos-1-14-0-0-cr01.newyork.ny.ibone.comcast.net 105.147 ms 107.521 ms 103.104 ms
11 so-1-1-0-0-ar04.whitemarsh.md.bad.comcast.net 115.073 ms 115.793 ms 115.225 ms
12 so-15-1-0-0-ar04.howardcounty.md.bad.comcast.net 107.743 ms
so-15-0-0-0-ar04.howardcounty.md.bad.comcast.net 107.109 ms
so-10-1-0-0-ar04.howardcounty.md.bad.comcast.net 106.822 ms
13 ae-1-0-sur01.michiganave.dc.bad.comcast.net 102.733 ms 104.144 ms 109.718 ms
14 2001:559:0:84::2 108.313 ms 104.132 ms 103.098 ms
15 2001:559:800c:1005:223:32ff:fea1:11b1 103.151 ms 103.523 ms 105.294 ms
If I were to guess where the congestion was occurring, it would be at that peering point between TATA and OCCAID in the LAX area.
Outbound traffic via the tunnel to TATA does not seem to exhibit the slowness.
|
![[ch]](/s/countries/ch.gif)
on Friday, 22 February 2013 01:10:07
Posting is only allowed when you are