US Cable Support > OptimumOnline > [Bresnan] DOCSIS 3.0 + Channel Bonding in Butte

reply to koolkid1563

Re: [Bresnan] DOCSIS 3.0 + Channel Bonding in Butte

Yah tonight really isn't a good test of internet speeds due to super bowl. Tomorrow night, i expect it up into the 160-180 ms range.

reply to koolkid1563
Here's the 3 sites again. Right around 9:00pm

Tracing route to ny-monitor.dslreports.com [74.208.229.54]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms SHYPANDA [192.168.1.1]
2 * * * Request timed out.
3 9 ms 11 ms 11 ms chywy002dr5-GE-3-0-6U0.int.bresnan.net [72.175.110.177]
4 9 ms 8 ms 8 ms chywy001cr5-XE-5-2-0U0.int.bresnan.net [72.175.110.130]
5 13 ms 10 ms 12 ms dencofh1tr5-XE-5-3-0U0.int.bresnan.net [72.175.110.229]
6 12 ms 11 ms 11 ms host-72-175-111-144.blnmt.client.bresnan.net [72.175.111.144]
7 57 ms 258 ms 96 ms te-9-3.car1.Denver1.Level3.net[4.53.10.97]
8 71 ms 75 ms 70 ms vlan52.ebr2.Denver1.Level3.net[4.69.147.126]
9 70 ms 86 ms 120 ms ae-4-4.car2.KansasCity1.Level3.net[4.69.135.237]
10 75 ms 74 ms 60 ms ae-11-11.car1.KansasCity1.Level3.net[4.69.135.233]
11 90 ms 91 ms 92 ms 11-INTERNET.car1.KansasCity1.Level3.net [4.53.32.10]
12 63 ms 62 ms 63 ms te-2-2.bb-d.slr.lxa.us.oneandone.net[74.208.1.77]
13 61 ms 63 ms 71 ms ae-10.gw-distpa.slr.lxa.oneandone.net [74.208.1.101]
14 65 ms 61 ms 62 ms ae-1.gw-prtr-r5a.slr.lxa.oneandone.net [74.208.1.167]
15 61 ms 62 ms 64 ms u15150124.onlinehome-server.com[74.208.229.54]

Trace complete.
**********************************
Tracing route to bismuth.vcn.com [209.193.68.5]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms SHYPANDA [192.168.1.1]
2 * * * Request timed out.
3 13 ms 10 ms 10 ms chywy002dr5-GE-3-0-6U0.int.bresnan.net [72.175.110.177]
4 10 ms 8 ms 8 ms chywy001cr5-XE-5-2-0U0.int.bresnan.net [72.175.110.130]
5 55 ms 11 ms 11 ms dencofh1tr5-XE-5-3-0U0.int.bresnan.net [72.175.110.229]
6 16 ms 13 ms 11 ms host-72-175-111-144.blnmt.client.bresnan.net [72.175.111.144]
7 32 ms 14 ms 11 ms dvr-edge-13.inet.qwest.net[65.124.87.21]
8 * 12 ms * 205.170.77.238
9 19 ms 17 ms 19 ms bismuth.vcn.com [209.193.68.5]
Trace complete.
********************************

Tracing route to vnsc-pri.sys.gtei.net [4.2.2.1]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms SHYPANDA [192.168.1.1]
2 * * * Request timed out.
3 24 ms 10 ms 9 ms chywy002dr5-GE-3-0-6U0.int.bresnan.net [72.175.110.177]
4 10 ms 10 ms 8 ms chywy001cr5-XE-5-2-0U0.int.bresnan.net [72.175.110.130]
5 12 ms 11 ms 12 ms dencofh1tr5-XE-5-3-0U0.int.bresnan.net [72.175.110.229]
6 12 ms 11 ms 12 ms host-72-175-111-144.blnmt.client.bresnan.net [72.175.111.144]
7 56 ms 56 ms 58 ms te-9-3.car1.Denver1.Level3.net[4.53.10.97]
8 84 ms 83 ms 103 ms vlan51.ebr1.Denver1.Level3.net[4.69.147.94]
9 101 ms 89 ms 90 ms ae-2-2.ebr2.Dallas1.Level3.net[4.69.132.106]
10 69 ms 70 ms 68 ms ae-82-82.csw3.Dallas1.Level3.net[4.69.151.153]
11 71 ms 56 ms 57 ms ae-31-80.car1.Dallas1.Level3.net[4.69.145.131]
12 78 ms 78 ms 79 ms vnsc-pri.sys.gtei.net [4.2.2.1]

Trace complete.
*******************************

Here is mine taken shortly after - just getting around to posting.

traceroute to ny-monitor.dslreports.com (74.208.229.54), 64 hops max, 52 byte packets
 1  * * *
 2  butmtfh1hb6-ge-0-0-0-U168.int.bresnan.net (72.175.110.169)  9.558 ms  11.253 ms  9.053  ms
 3  blnmtfh2cr5-GE-3-0-9-U0.int.bresnan.net (72.175.110.34)  55.629 ms  28.107 ms  17.706  ms
 4  blnmtfh1cr5-XE-5-0-0-U0.int.bresnan.net (72.175.110.72)  15.962 ms  17.800 ms  15.381  ms
 5  cspwy001hb1-GE-2-1.int.bresnan.net (72.175.110.93)  23.594 ms  24.310 ms  22.217 ms
 6  72.175.111.20 (72.175.111.20)  36.802 ms  33.595 ms  34.743 ms
 7  blnmtdc3hb6-GE-0-1-3-U0.int.bresnan.net (72.175.110.45)  34.833 ms  38.818 ms  34.531  ms
 8  12.90.77.21 (12.90.77.21)  113.905 ms  111.916 ms
    12.90.77.17 (12.90.77.17)  127.961 ms
 9  cr2.st6wa.ip.att.net (12.123.46.130)  112.562 ms  112.151 ms  111.572 ms
10  cr81.st0wa.ip.att.net (12.122.5.197)  127.954 ms  127.484 ms  127.987 ms
11  12.122.82.9 (12.122.82.9)  110.378 ms  110.470 ms  110.486 ms
12  64.208.110.213 (64.208.110.213)  160.985 ms
    te8-4-10G.ar1.PAO2.gblx.net (64.208.27.81)  47.186 ms
    64.208.110.213 (64.208.110.213)  163.716 ms
13  te2-1-10G.ar5.CHI1.gblx.net (67.17.106.133)  194.282 ms  194.589 ms  192.820 ms
14  64.209.105.234 (64.209.105.234)  193.323 ms  192.612 ms  200.236 ms
15  te-1-4.bb-c.slr.lxa.us.oneandone.net (74.208.6.106)  79.453 ms  78.832 ms  94.375 ms
16  ae-11.gw-distp-a.slr.lxa.oneandone.net (74.208.1.117)  86.000 ms  80.233 ms  79.587 ms
17  ae-1.gw-prtr-r5-a.slr.lxa.oneandone.net (74.208.1.167)  79.740 ms
    ae-10.gw-distp-a.slr.lxa.oneandone.net (74.208.1.101)  166.139 ms  167.432 ms
18  ae-1.gw-prtr-r5-a.slr.lxa.oneandone.net (74.208.1.167)  81.049 ms  81.423 ms
    u15150124.onlinehome-server.com (74.208.229.54)  78.738 ms

traceroute to bismuth.vcn.com (209.193.68.5), 64 hops max, 52 byte packets
 1  * * *
 2  butmtfh1hb6-ge-0-0-0-U168.int.bresnan.net (72.175.110.169)  11.991 ms  11.046 ms  9.07 5 ms
 3  blnmtfh2cr5-GE-3-0-9-U0.int.bresnan.net (72.175.110.34)  16.361 ms  16.481 ms  18.911  ms
 4  blnmtfh1cr5-XE-5-0-0-U0.int.bresnan.net (72.175.110.72)  16.359 ms  16.530 ms  15.996  ms
 5  cspwy001hb1-GE-2-1.int.bresnan.net (72.175.110.93)  26.565 ms  22.145 ms  22.312 ms
 6  72.175.111.20 (72.175.111.20)  32.988 ms  33.038 ms  56.002 ms
 7  blnmtdc3hb6-GE-0-1-3-U0.int.bresnan.net (72.175.110.45)  43.745 ms  39.143 ms  34.899  ms
 8  te7-4.ccr01.sea02.atlas.cogentco.com (38.104.126.53)  136.178 ms  103.676 ms  108.806  ms
 9  te2-4.ccr01.sea01.atlas.cogentco.com (154.54.3.33)  212.515 ms
    te7-8.ccr01.sea01.atlas.cogentco.com (154.54.82.37)  153.740 ms
    te7-1.ccr01.sea01.atlas.cogentco.com (154.54.82.33)  190.758 ms
10  te3-4.ccr01.slc01.atlas.cogentco.com (154.54.5.34)  340.608 ms
    te7-1.ccr01.slc01.atlas.cogentco.com (154.54.5.22)  206.145 ms
    te3-4.ccr01.slc01.atlas.cogentco.com (154.54.5.34)  151.001 ms
11  te3-3.mpd02.den01.atlas.cogentco.com (154.54.3.13)  157.915 ms
    te7-2.mpd02.den01.atlas.cogentco.com (154.54.45.46)  140.540 ms
    te3-3.mpd02.den01.atlas.cogentco.com (154.54.3.13)  155.264 ms
12  te3-1.ccr01.den03.atlas.cogentco.com (154.54.45.186)  157.741 ms  166.309 ms  156.867  ms
13  38.122.114.18 (38.122.114.18)  220.737 ms  242.074 ms  199.444 ms
14  bismuth.vcn.com (209.193.68.5)  145.443 ms  150.831 ms  151.177 ms

traceroute to 4.2.2.1 (4.2.2.1), 64 hops max, 52 byte packets
 1  * * *
 2  butmtfh1hb6-ge-0-0-0-U168.int.bresnan.net (72.175.110.169)  10.832 ms  12.408 ms  9.42 2 ms
 3  blnmtfh2cr5-GE-3-0-9-U0.int.bresnan.net (72.175.110.34)  19.164 ms  17.914 ms  15.772  ms
 4  blnmtaT1cr5-XE-4-0-0-U0.int.bresnan.net (72.175.110.118)  18.860 ms  17.752 ms  19.019  ms
 5  cspwy002cr5-XE-5-1-0-U0.int.bresnan.net (72.175.110.121)  25.462 ms  25.080 ms  21.208  ms
 6  cspwy001cr5-XE-5-0-0-U0.int.bresnan.net (72.175.110.94)  22.167 ms  24.269 ms  41.869  ms
 7  chywyaT1cr5-XE-5-3-0-U0.int.bresnan.net (72.175.110.225)  72.906 ms  47.773 ms  28.426  ms
 8  chywy001cr5-XE-5-1-0-U0.int.bresnan.net (72.175.110.128)  40.482 ms  30.997 ms  29.116  ms
 9  dencofh1tr5-XE-5-3-0-U0.int.bresnan.net (72.175.110.229)  47.228 ms  70.978 ms  45.719  ms
10  host-72-175-111-144.bln-mt.client.bresnan.net (72.175.111.144)  50.718 ms  45.116 ms   54.651 ms
11  te-9-3.car1.Denver1.Level3.net (4.53.10.97)  124.101 ms  155.889 ms
    xe-8-2-3.edge3.Denver1.Level3.net (4.28.20.29)  36.386 ms
12  vlan51.ebr1.Denver1.Level3.net (4.69.147.94)  123.572 ms  123.206 ms  121.802 ms
13  ae-2-2.ebr2.Dallas1.Level3.net (4.69.132.106)  158.114 ms  165.773 ms  165.136 ms
14  ae-62-62.csw1.Dallas1.Level3.net (4.69.151.129)  128.346 ms  138.393 ms
    ae-92-92.csw4.Dallas1.Level3.net (4.69.151.165)  160.953 ms
15  ae-11-60.car1.Dallas1.Level3.net (4.69.145.3)  161.890 ms  157.270 ms
    ae-31-80.car1.Dallas1.Level3.net (4.69.145.131)  126.606 ms
16  vnsc-pri.sys.gtei.net (4.2.2.1)  124.015 ms  133.627 ms  127.210 ms

reply to koolkid1563
The bizmuth, is obviously when you go to congentco and I go to qwest. That's pretty obvious. AND DRASTIC.

What's confusing is that for the DNS of 4.2.2.1, we both go through Level-3. I hop them 5 times, and you hope them 8 times. Now granted, because of LCR, we could have taken different/cheaper routes, and Level-3 could have actually done the re-route on you; but the fact that I average 50's - 80's in latency, and you average 120's - 160's is interesting. Is the additional delay actually with Level-3, or in the actual OOL connection lagging in your area. We are even hitting the same Level-3 connection at 4.53.10.97. But you hit in the 120-150ms and I hit at 56-58ms. Way interesting. Almost sounds like Hardware issues on the handoff. You also have 8 Bresnan handoffs and I have 4.

No sense of mentioning the 3rd hit, because it's similar. Sounds to me like it's hardware with OOL/Bresnan that is saturated and needs upgrading. We're being handed off at the same point, but I'm doing it in almost 1/3 the time.

reply to koolkid1563
Here's mine in Billings, kk1563.
-=-=-=-=-=-=-=-=-=-=-
myrouter ~ # traceroute ny-monitor.dslreports.com
traceroute to ny-monitor.dslreports.com (74.208.229.54), 30 hops max, 60 byte packets
1 host-69-144-102-18.jcs-wy.client.bresnan.net (69.144.102.18) 6.847 ms 7.146 ms 7.120 ms
2 host-72-175-111-65.bln-mt.client.bresnan.net (72.175.111.65) 7.079 ms 7.050 ms 7.012 ms
3 blnmtfh1cr5-XE-4-0-0-U0.int.bresnan.net (72.175.110.148) 6.981 ms 6.978 ms 10.718 ms
4 cspwy001hb1-GE-2-1.int.bresnan.net (72.175.110.93) 17.791 ms 17.790 ms 17.778 ms
5 72.175.111.20 (72.175.111.20) 28.798 ms 28.786 ms 28.784 ms
6 blnmtdc1dr5-GE-4-0-3-U0.int.bresnan.net (72.175.110.68) 62.764 ms 24.735 ms 24.607 ms
7 12.90.77.21 (12.90.77.21) 60.196 ms 60.490 ms 12.90.77.17 (12.90.77.17) 24.582 ms
8 cr2.st6wa.ip.att.net (12.123.46.130) 30.997 ms 31.029 ms 31.010 ms
9 cr81.st0wa.ip.att.net (12.122.5.197) 27.423 ms 27.505 ms 27.266 ms
10 12.122.82.9 (12.122.82.9) 25.095 ms 25.874 ms 25.803 ms
11 te8-4-10G.ar1.PAO2.gblx.net (64.208.27.81) 45.100 ms 45.455 ms 64.208.110.213 (64.208.110.213) 45.014 ms
12 te2-1-10G.ar5.CHI1.gblx.net (67.17.106.133) 138.241 ms 138.079 ms 137.513 ms
13 64.209.105.234 (64.209.105.234) 140.810 ms 140.643 ms 140.568 ms
14 te-1-1.bb-c.ws.mkc.us.oneandone.net (74.208.1.81) 98.766 ms te-1-4.bb-c.slr.lxa.us.oneandone.net (74.208.6.106) 135.148 ms te-1-1.bb-c.ws.mkc.us.oneandone.net (74.208.1.81) 98.643 ms
15 te-2-2.bb-d.slr.lxa.us.oneandone.net (74.208.1.77) 134.399 ms ae-11.gw-distp-a.slr.lxa.oneandone.net (74.208.1.117) 99.248 ms 100.065 ms
16 ae-10.gw-distp-a.slr.lxa.oneandone.net (74.208.1.101) 132.781 ms ae-1.gw-prtr-r5-a.slr.lxa.oneandone.net (74.208.1.167) 100.148 ms ae-10.gw-distp-a.slr.lxa.oneandone.net (74.208.1.101) 134.999 ms
17 ae-1.gw-prtr-r5-a.slr.lxa.oneandone.net (74.208.1.167) 99.840 ms 99.767 ms u15150124.onlinehome-server.com (74.208.229.54) 99.474 ms

myrouter ~ # traceroute bismuth.vcn.com
traceroute to bismuth.vcn.com (209.193.68.5), 30 hops max, 60 byte packets
1 host-69-144-102-18.jcs-wy.client.bresnan.net (69.144.102.18) 7.926 ms 7.853 ms 7.795 ms
2 host-72-175-111-65.bln-mt.client.bresnan.net (72.175.111.65) 7.762 ms 7.718 ms 7.686 ms
3 blnmtfh1cr5-XE-4-0-0-U0.int.bresnan.net (72.175.110.148) 29.500 ms 29.523 ms 29.510 ms
4 cspwy001hb1-GE-2-1.int.bresnan.net (72.175.110.93) 15.299 ms 15.603 ms 15.624 ms
5 72.175.111.20 (72.175.111.20) 26.292 ms 26.289 ms 26.276 ms
6 blnmtdc1dr5-GE-4-0-3-U0.int.bresnan.net (72.175.110.68) 26.311 ms 89.868 ms 54.159 ms
7 te7-4.ccr01.sea02.atlas.cogentco.com (38.104.126.53) 62.587 ms 62.669 ms 62.640 ms
8 te8-3.ccr01.sea01.atlas.cogentco.com (154.54.81.117) 62.617 ms te3-4.ccr01.sea01.atlas.cogentco.com (154.54.1.197) 26.155 ms 26.384 ms
9 te9-1.ccr01.slc01.atlas.cogentco.com (154.54.80.10) 220.914 ms te7-1.ccr01.slc01.atlas.cogentco.com (154.54.5.22) 254.557 ms te3-4.ccr01.slc01.atlas.cogentco.com (154.54.5.34) 221.200 ms
10 te3-3.mpd02.den01.atlas.cogentco.com (154.54.3.13) 62.963 ms te7-2.mpd02.den01.atlas.cogentco.com (154.54.45.46) 62.578 ms 62.893 ms
11 te3-1.ccr01.den03.atlas.cogentco.com (154.54.45.186) 95.492 ms 95.531 ms 93.159 ms
12 38.122.114.18 (38.122.114.18) 92.476 ms 92.334 ms 92.301 ms
13 bismuth.vcn.com (209.193.68.5) 69.710 ms 70.002 ms 69.745 ms

myrouter ~ # traceroute 4.2.2.1
traceroute to 4.2.2.1 (4.2.2.1), 30 hops max, 60 byte packets
1 host-69-144-102-18.jcs-wy.client.bresnan.net (69.144.102.18) 16.031 ms 16.328 ms 16.411 ms
2 host-72-175-111-65.bln-mt.client.bresnan.net (72.175.111.65) 16.375 ms 16.548 ms 16.525 ms
3 blnmtfh1cr5-XE-4-0-0-U0.int.bresnan.net (72.175.110.148) 32.184 ms 32.165 ms 32.159 ms
4 mslmt001cr5-XE-5-3-0-U0.int.bresnan.net (72.175.110.75) 24.399 ms 24.414 ms 24.705 ms
5 seawafh1cr5-XE-5-1-0-U0.int.bresnan.net (72.175.111.23) 31.759 ms 31.760 ms 31.703 ms
6 gdjco001cr5-XE-5-3-0-U0.int.bresnan.net (72.175.110.41) 63.626 ms 61.815 ms 62.240 ms
7 gdjco002cr5-XE-5-0-0-U0.int.bresnan.net (72.175.110.231) 62.194 ms 62.175 ms 62.169 ms
8 dencofh1cr5-XE-5-1-0-U0.int.bresnan.net (72.175.111.154) 66.643 ms 66.658 ms 66.610 ms
9 dencofh1tr5-XE-4-3-0-U0.int.bresnan.net (72.175.111.142) 84.820 ms 84.791 ms 84.765 ms
10 te-9-3.car1.Denver1.Level3.net (4.53.10.97) 83.990 ms xe-8-2-3.edge3.Denver1.Level3.net (4.28.20.29) 82.718 ms 82.819 ms
11 vlan51.ebr1.Denver1.Level3.net (4.69.147.94) 84.188 ms 80.428 ms 80.255 ms
12 ae-2-2.ebr2.Dallas1.Level3.net (4.69.132.106) 116.791 ms 116.651 ms 116.715 ms
13 ae-92-92.csw4.Dallas1.Level3.net (4.69.151.165) 87.986 ms ae-82-82.csw3.Dallas1.Level3.net (4.69.151.153) 83.087 ms 83.031 ms
14 ae-31-80.car1.Dallas1.Level3.net (4.69.145.131) 248.445 ms ae-11-60.car1.Dallas1.Level3.net (4.69.145.3) 241.122 ms ae-41-90.car1.Dallas1.Level3.net (4.69.145.195) 240.962 ms
15 vnsc-pri.sys.gtei.net (4.2.2.1) 115.930 ms 116.551 ms 116.524 ms
-=-=-=-=-=-=-=-=-=-=-
Why on earth is my first hop in Wyoming in all on them?
--
Bresnan 30M/5M | CenturyLink 5M/896K
MyWS[PnmIIX3@3.3G,8G RAM,500G+1.5T+2T HDDs,Win7]
WifeWS[A64@2G,2G RAM,120G HDD,Win7]
Router[2xP3@1G,1G RAM,18G HDD,Allied Telesyn AT2560FX,2xDigital QP DE504,Compaq DP NC3131,2xSun QP GigaSwift, SMC 8432BTA, Gentoo]

Your first hop will be the CMTS located at the headend where the fiber from your node is terminated. The reverse DNS is just that, a Name that is associated with an IP. The IP/subnet probably was assigned at some point, and the reverse name has just not been corrected. The rDNS does not effect anything.
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore.

I talked with a representative for the 2nd time tonight. They are saying that this problem is off of OOL's network, so they have no responsibility for it.

Fuck this ISP, tired of messing with pompous assholes. I'll be switching at sometime this week.

Not making light of your stats, but you said previously that you're having a hard time doing ANYTHING on the internet. I see you have latency issues, but saying you can't do anything on the internet, and you want to switch, seems a little drastic. Just a few years ago, the highest amount of bandwidth you could get was around 1.5mb. Prior to that, many were on dialup. Are you saying it's so bad now that you were actually better off years ago?

I can understand fighting for an adjustment to your bill. I can see still fighting with them for quality service. But I don't know about you, but where I live, there aren't a lot of "better" options. I could get DSL. I had it prior to ATT/Bresnan/OOL. But the best I can get is 1.5mb/896kb. I could get wireless canopy or cellular, but the average latency is around 150-200ms. So for me, 30mb/5mb with high latency is better than lower latency and 1.5mb bandwidth. Granted, my latency issues aren't as bad as some others; but I really think saying you're going to be "Switching" is a little rash. Especially considering the alternatives. Now; if you happen to have 20mb dsl available, that's great. Most of us don't have that option.

I only use DSL as my secondary connection while I use Optimum as my primary connection. I have a Linux router handling all three connections (Optimum, CenturyLink, and Verizon via my cell).

As for latency issues, why not post a traceroute from your location.

He actually did post a tracert on page 1 of this thread. He had some high latencies in the 170-200ms range.

Personally, I think way too much importance is given to latency. I know there are those that are big time gamers, do a lot of torrents, etc... and latency is important to them; but latency isn't all that. Bandwidth also needs to be considered.

Looking at my choices of broadband, there's:
1. Wireless 3mb/1mb with latency in the 150-200ms normal
2. DSL 1.5mb/896kb with latency in the 75-95ms normal
3. OOL 30mb/5mb with latency in the 60ms normal with occasional spikes in the 150ms range.

So; which is better and preferred? I guess if the only thing that matters to you is gaming, then the lowest latency is. If you do a lot of downloading, then the bandwidth would be. If you're the normal surfer, emailer, occasional youtube, etc... then the cheapest would be the most important. Even if my latency was on average of 150ms, I'd still prefer the 30/5mb bandwidth, because except for voip, everything I use bandwidth for can buffer. So latency isn't that important. But for the gamer lives on milliseconds and feels they can't compete in their cyber world if they are 50ms less than someone else; well, I guess their priorities are different.

reply to christcorp
Yes, It appears I have 20 mb DSL available from CenturyLink in my area. More speed than OOL, dedicated line, less latency, and cheaper. Plus, even if Centurylink's customer service is bad, it can't be worse than OOL.

Latency is really all I care about for my internet line. High latency = can't pay games. Any bandwidth over 2mb is fine by me. So, saying I can't do anything on the internet is true as it applies to me. I can't play games averaging at 250ms.

FYI. DSL sounds like it's a "Dedicated Line", but it's only dedicated from your house to the DSLAM. If your dslam is at the central office, then that's fine. If the DSLAM is located in your housing area or down the street, then you will SHARE connectivity from there back to the main gateway with everyone else.

Also; you need to be specific with Qwest/Centurylink. I live in Cheyenne. Main hub. Definitely 20mb service in cheyenne. My neighborhood however is 1.5mb/896kb max. Been that way for over 10 years.

reply to christcorp
While true, latency isn't everything, at least in my case the high latency is a sign of congestion which equals low bandwidth. This is one circumstance where the two are working in tandem, the low availability of bandwidth upstream causes high latency so it is a little easier to spot where the issue may be in the network (spot the hop with the most gain). When I pay for 30Mb/s DS and get maybe 5Mb/s during peak hours with 200ms latency once outside of Bresnan/OOL, CenturyLink's 7Mb/s or 12Mb/s or what have you might be better as long as it is at least consistent on both fronts.

I doubt us customers can speak directly to the NOC, but it would probably get something done or at the very least get it escalated. I am sure they have monitoring software to check their equipment and are aware but when tech support never escalates these issues to them because from their 'training' it is off network. What they forget is that they hold the other end of that link so they are partly at fault or should at the very least escalate for investigation to determine it isn't them and if not escalate to Level3, Cogent, and ATT. The NOC probably figures it isn't an issue because they never receive tickets regarding it. To blatantly deny an issue because the hop that has high latency doesn't belong to them when it is at the handoff point of their network isn't the right way to handle an issue.

Agree 100%. I notice that if I go to the optimum speed test, and check Cheyenne, Casper, or grand junction, I always get the 30/5m, If I check the Billings MT, it runs in the 26-28mb area. If I go to Missoula, it drops to around 12mb. So that tells me that either the missoula center doesn't have the equipment to handle the number of customers and bandwidth; OR; their handoff (Which is what I suspect) is not good.

reply to Simba7
Tracing route to bismuth.vcn.com [209.193.68.5]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 30 ms 22 ms 17 ms host-69-144-102-94.jcs-wy.client.bresnan.net [69.144.102.94]
3 22 ms 21 ms * ftmco001hb6-GE-0-0-0-U152.int.bresnan.net [69.146.239.153]
4 21 ms 21 ms 17 ms chywy001hb7-SO-0-3-1-U0.int.bresnan.net [72.175.110.150]
5 13 ms 11 ms 24 ms chywy001cr5-GE-4-0-1-U0.int.bresnan.net [72.175.110.144]
6 18 ms 17 ms 15 ms dencofh1tr5-XE-5-3-0-U0.int.bresnan.net [72.175.110.229]
7 24 ms 28 ms 32 ms host-72-175-111-144.bln-mt.client.bresnan.net [72.175.111.144]
8 82 ms 78 ms 62 ms dvr-edge-13.inet.qwest.net
[65.124.87.21]
9 64 ms 56 ms 49 ms 205.170.77.238
10 55 ms 49 ms 52 ms bismuth.vcn.com [209.193.68.5]

*************************************************
Tracing route to bismuth.vcn.com [209.193.68.5]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 34 ms 32 ms 26 ms host-69-144-102-94.jcs-wy.client.bresnan.net [69.144.102.94]
3 36 ms 33 ms 14 ms ftmco001hb6-GE-0-0-0-U152.int.bresnan.net [69.146.239.153]
4 46 ms 81 ms 28 ms chywy001hb7-SO-0-3-1-U0.int.bresnan.net [72.175.110.150]
5 28 ms 44 ms 21 ms chywy001cr5-GE-4-0-1-U0.int.bresnan.net [72.175.110.144]
6 27 ms 24 ms 36 ms dencofh1tr5-XE-5-3-0-U0.int.bresnan.net [72.175.110.229]
7 31 ms 28 ms 17 ms host-72-175-111-144.bln-mt.client.bresnan.net [72.175.111.144]
8 87 ms 76 ms 69 ms dvr-edge-13.inet.qwest.net [65.124.87.21]
9 52 ms * * 205.170.77.238
10 66 ms 48 ms 65 ms bismuth.vcn.com [209.193.68.5]

Trace complete.
*************************************************

What do the asterisks mean? Taken within 1minute of each other.

Asterisks mean dropped packets.

reply to livinfree
Technically the asterisks mean no response was received within the time set by the program for a response to be received. As has been said it can mean several different things.

so as a synopsis

If you see 3 asterisks at a hop all the time and the following hops do not show asterisks, it means the equipment is configured so that it will not reply to the trace.

If you see a hop reply and then asterisks it means the program did not receive a response in the time allotted. This can be due to a late arriving packet, a lost packet or a packet dropped due to the hop being busy. Since ICMP is low priority it is not always a sign that the hop has a problem but normally it is at least indicative of some problem either at that hop or prior to the hop. The reason the problem can occur prior to that hop or on the way back from the hop is that as a trace proceeds every packet must flow through the previous hops, to get the hop that will respond, and if the problem is an intermittent one, it could occur on some packets and not others.
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore.

reply to Dtere
It's funny that they say the problem is off network...Coming the reverse direction it looks to be on Bresnan's network to me. Too many things point to a Bresnan issue. Can those in the OOL Direct forum take cases from OOL West customers yet?

                                                     Packets      Latency
 Host                                              Loss%   Snt   Last   Avg
 1. [powell firewall]                               0.0%  1500    1.2   0.7
 2. ???
 3. pwll-7606-vl426.infrastructure.tctwest.net      0.0%  1500    1.4   2.1
 4. lvll-7606-te1-1.infrastructure.tctwest.net      0.0%  1500    2.3   3.0
 5. sgbl-7606-te1-1.infrastructure.tctwest.net      0.0%  1500    9.4   3.6
 6. bahe-6506-te2-1.infrastructure.tctwest.net      0.0%  1500    3.8   4.9
 7. dnvr-7603-g1-1.infrastructure.tctwest.net       0.1%  1500   13.5  14.7
 8. 66.62.168.245                                   0.0%  1500   14.3  15.8
 9. den1-core-02-ae1.360.net                        0.0%  1500   13.8  15.1
10. den1-core-01-ae0.360.net                        0.0%  1500   15.6  14.4
11. xe-8-3-0.edge3.denver1.level3.net               0.0%  1500   20.0  16.7
12. ae-21-52.car1.denver1.level3.net                0.0%  1500   15.2  37.1
13. bresnan-com.car1.denver1.level3.net             0.0%  1500   14.8  16.2
14. host-72-175-111-143.bln-mt.client.bresnan.net   0.0%  1500   19.7  17.5
15. host-72-175-111-155.bln-mt.client.bresnan.net   0.0%  1500   19.6  20.2
16. gdjco001cr5-xe-5-0-0-u0.int.bresnan.net         0.0%  1500   20.4  23.0
17. blnmtfh1cr5-ge-3-0-0-u0.int.bresnan.net         0.0%  1500   55.1  55.0
18. mslmt001cr5-xe-5-1-0-u0.int.bresnan.net         0.0%  1500  143.7 140.8
19. blnmtfh1cr5-xe-5-3-0-u0.int.bresnan.net         0.0%  1500  149.6 144.0
20. blnmtfh2cr5-xe-5-0-0-u0.int.bresnan.net         0.0%  1500  130.8 124.5
21. butmtfh1hb6-ge-1-3-0-u0.int.bresnan.net         0.0%  1500  153.0 147.2
22. ???
23. [butte firewall]                                0.0%  1500  161.8 155.1