[TriLUG] time warner business class
Tim Jowers
timjowers at gmail.com
Thu Nov 29 09:00:59 EST 2007
Below are some traceroutes. The first three are good and what one
would want. The later is several months back but shows the random
delays. Maybe these are fixed. I'll try to look for the test tool
mentioned or write something to run tests over a 24 hour period.
The current time is: 8:50:02.19
Through a VPN:
tracert www.trilug.org
Tracing route to pilot.trilug.org [64.244.27.136]
over a maximum of 30 hops:
1 29 ms 30 ms 30 ms asqvpn2.mci.com [166.44.240.2]
2 29 ms 29 ms 29 ms asqer1-vlan111.mcilink.com [166.44.243.27]
3 28 ms 30 ms 31 ms asqir2-vlan41.mcilink.com [199.249.28.193]
4 30 ms 28 ms 30 ms asqir1-vlan22.mcilink.com [192.135.72.201]
5 28 ms 28 ms 27 ms GigabitEthernet1-0.GW2.IAD5.ALTER.NET
[137.39.253.177]
6 29 ms 30 ms 31 ms 0.so-3-0-0.CL1.IAD5.ALTER.NET [152.63.34.186]
7 39 ms 39 ms 38 ms 0.so-4-0-2.XL1.RDU1.ALTER.NET [152.63.27.57]
8 43 ms 49 ms 39 ms 123.ATM7-0.GW7.RDU1.ALTER.NET [152.63.37.133]
9 40 ms 38 ms 39 ms sungard-gw.customer.alter.net [63.65.185.70]
10 39 ms 50 ms 41 ms dhmir1-vl-2.sgns.net [64.244.31.43]
11 38 ms 38 ms 39 ms pilot.trilug.org [64.244.27.136]
Trace complete.
Through the residential network:
tracert www.trilug.org
Tracing route to pilot.trilug.org [64.244.27.136]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 12 ms 12 ms 8 ms cpe-075-189-144-001.nc.res.rr.com [75.189.144.1]
3 10 ms 8 ms 7 ms gig2-0-2.rlghncj-rtr4.nc.rr.com [24.25.2.42]
4 11 ms 10 ms 12 ms pos1-2.rlghnca-rtr1.nc.rr.com [24.25.0.94]
5 9 ms 12 ms 10 ms
gig2-3-0.rlghncrdc-pop1.southeast.rr.com [24.93.64.164]
6 18 ms 17 ms 18 ms
ge-0-3-0.chrlncsa-rtr6.southeast.rr.com [24.93.64.173]
7 17 ms 18 ms 15 ms pop1-cha-P1-0.atdn.net [66.185.132.33]
8 14 ms 17 ms 17 ms bb1-cha-P3-0.atdn.net [66.185.138.64]
9 20 ms 21 ms 20 ms bb1-atm-P6-0.atdn.net [66.185.152.182]
10 20 ms 20 ms 22 ms pop2-atm-P1-0.atdn.net [66.185.147.209]
11 82 ms 145 ms 113 ms 0.so-2-0-0.BR1.ATL4.ALTER.NET [204.255.169.77]
12 22 ms 22 ms 21 ms 0.so-1-1-0.XT2.ATL4.ALTER.NET [152.63.86.174]
13 35 ms 35 ms 34 ms 0.so-4-0-3.XL2.RDU1.ALTER.NET [152.63.0.94]
14 36 ms 35 ms 37 ms 124.ATM7-0.GW7.RDU1.ALTER.NET [152.63.37.145]
15 36 ms 47 ms 36 ms sungard-gw.customer.alter.net [63.65.185.70]
16 34 ms 34 ms 35 ms dhmir1-vl-2.sgns.net [64.244.31.43]
17 34 ms 33 ms 35 ms pilot.trilug.org [64.244.27.136]
Trace complete.
Through residential network:
]# traceroute www.trilug.org
traceroute to pilot.trilug.org (64.244.27.136), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.456 ms 0.578 ms 0.355 ms
2 cpe-075-189-144-001.nc.res.rr.com (75.189.144.1) 9.397 ms 9.758
ms 9.362 ms
3 gig2-0-2.rlghncj-rtr4.nc.rr.com (24.25.2.42) 8.123 ms 9.114 ms 8.303 ms
4 pos1-2.rlghnca-rtr1.nc.rr.com (24.25.0.94) 8.919 ms 11.065 ms 8.189 ms
5 gig2-3-0.rlghncrdc-pop1.southeast.rr.com (24.93.64.164) 9.321 ms
12.139 ms 22.828 ms
6 ge-0-3-0.chrlncsa-rtr6.southeast.rr.com (24.93.64.173) 14.060 ms
ge-1-3-0.chrlncpop-rtr1.southeast.rr.com (24.93.64.169) 16.901 ms
16.721 ms
7 pop1-cha-P1-0.atdn.net (66.185.132.33) 18.019 ms 17.868 ms
pop1-cha-P7-0.atdn.net (66.185.138.69) 15.990 ms
8 bb1-cha-P3-0.atdn.net (66.185.138.64) 17.929 ms 17.564 ms 18.114 ms
MPLS Label=301 CoS=5 TTL=1 S=0
9 bb1-atm-P6-0.atdn.net (66.185.152.182) 21.082 ms 21.877 ms 22.934 ms
MPLS Label=171 CoS=5 TTL=1 S=0
10 pop2-atm-P1-0.atdn.net (66.185.147.209) 32.649 ms 21.655 ms 21.758 ms
11 0.so-2-0-0.BR1.ATL4.ALTER.NET (204.255.169.77) 23.718 ms 21.071
ms 22.327 ms
12 0.so-1-1-0.XT1.ATL4.ALTER.NET (152.63.86.170) 22.445 ms
0.so-1-1-0.XT2.ATL4.ALTER.NET (152.63.86.174) 21.206 ms
0.so-1-1-0.XT1.ATL4.ALTER.NET (152.63.86.170) 20.666 ms
13 0.so-4-0-2.XL1.RDU1.ALTER.NET (152.63.27.57) 36.561 ms 35.086 ms
34.614 ms
14 124.ATM6-0.GW7.RDU1.ALTER.NET (152.63.37.137) 34.346 ms
123.ATM6-0.GW7.RDU1.ALTER.NET (152.63.37.141) 37.758 ms 37.341 ms
15 sungard-gw.customer.alter.net (63.65.185.70) 35.209 ms 37.034 ms
36.155 ms
16 dhmir1-vl-2.sgns.net (64.244.31.43) 45.474 ms 34.633 ms 34.585 ms
Bad performance seen in the past. Am I missing something? Where's the
bottelneck?
traceroute to www.kernel.org (204.152.191.37), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 1.642 ms 1.700 ms *
2 * * *
3 * * *
4 * * *
5 * * *
6 * pos14-0.rlghncrdc-rtr1.nc.rr.com ( 24.25.0.5) 634.242 ms 634.387 ms
7 son0-0-3.rlghncrdc-rtr3.nc.rr.com (24.93.64.34) 634.546 ms
634.650 ms 634.801 ms
8 te-1-3.car1.Raleigh1.Level3.net (4.71.160.5) 635.320 ms
te-1-4.car1.Raleigh1.Level3.net (4.71.160.1) 635.447 ms 635.564 ms
9 ae-11-11.car2.Raleigh1.Level3.net (4.69.132.174) 643.455 ms
643.597 ms 643.712 ms
10 ae-6-6.ebr2.Washington1.Level3.net (4.69.132.178) 649.176 ms
648.898 ms 649.050 ms
11 * * ae-2.ebr2.Chicago1.Level3.net (4.69.132.69) 254.990 ms
12 ae-1-100.ebr1.Chicago1.Level3.net (4.69.132.41) 248.797 ms * *
13 ae-3.ebr2.Denver1.Level3.net (4.69.132.61) 234.408 ms 423.459 ms
533.733 ms
14 ae-1-100.ebr1.Denver1.Level3.net (4.69.132.37) 520.128 ms
622.826 ms 623.019 ms
15 ae-3.ebr2.SanJose1.Level3.net (4.69.132.57) 651.141 ms 651.347
ms 651.529 ms
16 ae-2-56.bbr2.SanJose1.Level3.net ( 4.68.123.161) 747.479 ms
747.158 ms 747.371 ms
17 so-13-0.hsa3.SanJose1.Level3.net (4.68.121.234) 750.664 ms
750.859 ms 751.089 ms
18 isc-level3-ge.SanJose1.Level3.net (4.68.111.59) 751.637 ms
703.822 ms 703.706 ms
19 zeus-pub2.kernel.org (204.152.191.37) 742.215 ms 741.886 ms 741.545 ms
[root at localhost ~]#
1 second latency!
Looks like zeus is on Level3's network. (Level3 bought ACSI from what
I remember.)
[root at localhost ~]# tracert www.microsoft.com
traceroute to www.microsoft.com (207.46.19.60), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 1.714 ms 1.771 ms 1.844 ms
2 10.127.0.1 (10.127.0.1 ) 480.874 ms 481.037 ms 481.109 ms
3 gig2-1.rlghncj-rtr3.nc.rr.com (24.25.1.18) 481.181 ms 481.323 ms
481.395 ms
4 srp5-0.rlghncg-rtr2.nc.rr.com (24.25.2.147) 482.724 ms 482.796
ms 482.869 ms
5 pos1-1.rlghnca-rtr2.nc.rr.com ( 24.25.20.25) 482.940 ms 483.014
ms 483.086 ms
6 pos14-0.rlghncrdc-rtr2.nc.rr.com (24.25.0.9) 490.783 ms 368.689
ms 368.823 ms
7 son0-1-1.chrlncsa-rtr6.carolina.rr.com (24.93.64.57) 373.686 ms
317.454 ms 317.552 ms
8 te-1-3.car1.Charlotte1.Level3.net (4.71.124.1) 336.068 ms
364.222 ms te-1-4.car1.Charlotte1.Level3.net ( 4.71.124.5) 364.848 ms
9 ae-4-4.ebr1.Atlanta2.Level3.net (4.69.132.162) 405.642 ms
369.521 ms 370.828 ms
10 ae-3.ebr1.Dallas1.Level3.net (4.69.132.81) 397.114 ms 404.205 ms
404.345 ms
11 ae-1-100.ebr2.Dallas1.Level3.net ( 4.69.132.46) 392.582 ms
426.240 ms 426.348 ms
12 ae-3.ebr2.LosAngeles1.Level3.net (4.69.132.77) 450.449 ms
446.432 ms 446.546 ms
13 ae-1-100.ebr1.LosAngeles1.Level3.net (4.69.132.5) 447.036 ms
515.681 ms 515.840 ms
14 ae-2.ebr1.SanJose1.Level3.net (4.69.132.9) 413.698 ms 280.643 ms
280.442 ms
15 ge-2-0-0-53.gar1.SanJose1.Level3.net ( 4.68.123.66) 287.572 ms
302.898 ms 303.002 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
On Nov 28, 2007 10:46 PM, Nick Goldwater <trilug at dogstar1.com> wrote:
> Yes but I need to look at the logs at work to be exact but 6 weeks ago is a guess. The Co-Lo actually cut TW out of their routing for a time. I was told that this is an ongoing effort so it may be hard to pin-point a specific cause and effect without TW's help.
> Nick
>
>
>
> ----- "Ron Joffe" <rjoffe at yahoo.com> wrote:
> | On Wednesday 28 November 2007 17:48, Nick Goldwater wrote:
> | > I know TW has been upgrading their infrastructure because we took
> | some
> | > heavy hits at one of our data centers due to Time Warner. Could be
> | related
> | > to that and the associated peering/routing issues.
> |
> | Do you have a time frame ?
> |
> | --
> | TriLUG mailing list :
> | http://www.trilug.org/mailman/listinfo/trilug
> | TriLUG Organizational FAQ : http://trilug.org/faq/
> | TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
>
> --
> TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ : http://trilug.org/faq/
> TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
>
More information about the TriLUG
mailing list