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

[Bresnan] DOCSIS 3.0 + Channel Bonding in Butte

DOCSIS 3

Speedtest

»Bonded channels blue light cheyenne

Another user also posted that they now have multiple DS channels.

Is Boost 30/5 over there still? Surprised you're not seeing closer to 30.
--
University of Southern California - Fight On!

Yeah - Boost 30/5 is as high as we can go for the moment. That test is the fastest one I have gotten so far. Now I am getting 12-14Mb/s on the Billings server as well as the others on the OOL speedcheck site - less on external speedtest sites. The bottleneck now is probably the backhauls coming into Butte...

It doesn't make sense, though...The server is only a few hops out from me and the latency looks perfect:
traceroute to billings.speedtest.bresnan.net (69.145.254.140), 64 hops max, 52 byte packets
1 * * *
2 butmtfh1hb6-ge-0-0-0-U168.int.bresnan.net (72.175.110.169) 10.491 ms 7.860 ms 9.720 ms
3 blnmtfh2cr5-GE-3-0-9-U0.int.bresnan.net (72.175.110.34) 16.290 ms 14.585 ms 16.376 ms
4 billings.speedtest.bresnan.net (69.145.254.140) 15.443 ms 14.888 ms 15.944 ms

External sites I can understand, as I collect a good 70-80ms of latency traversing Bresnan's network but I don't get the on-network speeds slumping so low...
traceroute to wc-monitor.dslreports.com (64.81.79.41), 64 hops max, 52 byte packets
1 * * *
2 butmtfh1hb6-ge-0-0-0-U168.int.bresnan.net (72.175.110.169) 10.251 ms 11.127 ms 12.794 ms
3 blnmtfh2cr5-GE-3-0-9-U0.int.bresnan.net (72.175.110.34) 38.621 ms 14.738 ms 16.156 ms
4 blnmtfh1cr5-XE-5-0-0-U0.int.bresnan.net (72.175.110.72) 15.810 ms 18.218 ms 15.663 ms
5 mslmt001cr5-XE-5-3-0-U0.int.bresnan.net (72.175.110.75) 22.999 ms 25.330 ms 22.507 ms
6 seawafh1cr5-XE-5-1-0-U0.int.bresnan.net (72.175.111.23) 35.524 ms 37.872 ms 37.869 ms
7 gdjco001cr5-XE-5-3-0-U0.int.bresnan.net (72.175.110.41) 73.956 ms 72.182 ms 73.354 ms
8 gdjco002cr5-XE-5-0-0-U0.int.bresnan.net (72.175.110.231) 70.571 ms 71.805 ms 70.713 ms
9 dencofh1cr5-XE-5-1-0-U0.int.bresnan.net (72.175.111.154) 75.403 ms 74.566 ms 77.368 ms
10 dencofh1tr5-XE-4-3-0-U0.int.bresnan.net (72.175.111.142) 76.637 ms 53.300 ms 77.846 ms
11 xe-8-2-3.edge3.Denver1.Level3.net (4.28.20.29) 53.418 ms
te-9-3.car1.Denver1.Level3.net (4.53.10.97) 71.632 ms 72.803 ms
12 vlan52.ebr2.Denver1.Level3.net (4.69.147.126) 68.704 ms 68.124 ms 69.903 ms
13 ae-3-3.ebr1.Chicago2.Level3.net (4.69.132.62) 107.625 ms 114.559 ms 99.629 ms
14 ae-6-6.ebr1.Chicago1.Level3.net (4.69.140.189) 106.645 ms 112.076 ms 104.303 ms
15 ae-12-51.car2.Chicago1.Level3.net (4.69.138.4) 93.923 ms 92.740 ms 93.261 ms
16 MEGAPATH-NE.car2.Chicago1.Level3.net (4.71.182.42) 80.081 ms 89.404 ms 82.684 ms
17 ge-0-1-2-0.chcgilgb-mxc1.bb.megapath.net (155.229.70.57) 104.098 ms 103.198 ms 104.091 ms
18 ae0-0.chcgilgb-mxc2.bb.megapath.net (155.229.57.22) 101.891 ms 103.345 ms 103.620 ms
19 ae4-0.lsancagb-mxc2.bb.megapath.net (155.229.57.109) 112.016 ms 108.638 ms 108.689 ms
20 ae0-0.lsancagb-mxc1.bb.megapath.net (155.229.57.1) 133.039 ms 131.663 ms 131.244 ms
21 ae4-0.snvacaid-mxc1.bb.megapath.net (155.229.70.238) 107.361 ms 108.697 ms 108.832 ms
22 ae0-0.snvacaid-mxc2.bb.megapath.net (155.229.57.14) 132.435 ms 132.892 ms 132.445 ms
23 ge-2-1-0-0.c01.pao.bb.megapath.net (155.229.70.222) 131.670 ms 131.727 ms 132.554 ms
24 spk-mega.c01.pao.megapath.net (66.80.133.30) 127.222 ms 163.694 ms 124.975 ms
25 dslreports-west2.speakeasy.net (64.81.79.41) 132.968 ms 134.144 ms 131.780 ms

reply to Thinkdiff

Success?

I ran tests to all the west servers when the link was posted in the other thread, and noticed the WY and MT servers were consistently 2/3 the speed of the CO server. Out of curiosity, try a test to the server at »speedtest.cogeco.net/ .
--
***ATMFAQ***DIFAQ***Kitchen Sink***

That didn't look very good at all - and Bresnan even peers directly with Cogent...



traceroute to speedtest.cogeco.net (24.226.10.93), 64 hops max, 52 byte packets
1 * * *
2 butmtfh1hb6-ge-0-0-0-U168.int.bresnan.net (72.175.110.169) 73.982 ms 10.003 ms 33.485 ms
3 blnmtfh2cr5-GE-3-0-9-U0.int.bresnan.net (72.175.110.34) 18.462 ms 22.299 ms 18.481 ms
4 blnmtfh1cr5-XE-5-0-0-U0.int.bresnan.net (72.175.110.72) 15.849 ms 23.589 ms 18.609 ms
5 cspwy001hb1-GE-2-1.int.bresnan.net (72.175.110.93) 26.926 ms 23.238 ms 25.618 ms
6 72.175.111.20 (72.175.111.20) 39.188 ms 38.620 ms 53.392 ms
7 blnmtdc3hb6-GE-0-1-3-U0.int.bresnan.net (72.175.110.45) 40.584 ms 35.294 ms 36.443 ms
8 te7-4.ccr01.sea02.atlas.cogentco.com (38.104.126.53) 38.578 ms 38.760 ms 38.073 ms
9 te3-4.ccr01.sea01.atlas.cogentco.com (154.54.1.197) 117.348 ms
te7-1.ccr01.sea01.atlas.cogentco.com (154.54.82.33) 227.326 ms
te7-8.ccr01.sea01.atlas.cogentco.com (154.54.82.37) 89.289 ms
10 te7-1.ccr01.slc01.atlas.cogentco.com (154.54.5.22) 133.305 ms
te3-4.ccr01.slc01.atlas.cogentco.com (154.54.5.34) 219.361 ms
te7-1.ccr01.slc01.atlas.cogentco.com (154.54.5.22) 205.509 ms
11 te3-3.mpd02.den01.atlas.cogentco.com (154.54.3.13) 199.893 ms
te7-2.mpd01.den01.atlas.cogentco.com (154.54.45.42) 210.477 ms
te7-2.mpd02.den01.atlas.cogentco.com (154.54.45.46) 197.705 ms
12 te0-4-0-2.ccr22.mci01.atlas.cogentco.com (154.54.45.54) 78.441 ms
te0-4-0-2.mpd21.mci01.atlas.cogentco.com (154.54.24.82) 78.193 ms
te0-4-0-2.ccr22.mci01.atlas.cogentco.com (154.54.45.54) 83.092 ms
13 te0-2-0-3.mpd21.ord01.atlas.cogentco.com (154.54.30.106) 95.480 ms
te0-0-0-3.ccr22.ord01.atlas.cogentco.com (154.54.30.102) 95.594 ms
te0-0-0-3.mpd21.ord01.atlas.cogentco.com (154.54.2.234) 99.324 ms
14 te3-8.ccr02.cle04.atlas.cogentco.com (154.54.43.122) 199.508 ms
te7-2.ccr02.cle04.atlas.cogentco.com (154.54.45.133) 318.942 ms 253.418 ms
15 te3-2.ccr01.buf02.atlas.cogentco.com (154.54.43.118) 239.258 ms
te4-4.ccr01.buf02.atlas.cogentco.com (154.54.44.81) 123.750 ms
te4-1.ccr01.buf02.atlas.cogentco.com (154.54.27.85) 222.440 ms
16 te7-2.ccr01.yhm01.atlas.cogentco.com (154.54.24.222) 310.838 ms
te4-3.ccr01.yhm01.atlas.cogentco.com (154.54.82.102) 299.775 ms
te7-2.ccr01.yhm01.atlas.cogentco.com (154.54.24.222) 289.317 ms
17 38.122.17.18 (38.122.17.18) 113.624 ms 118.145 ms
38.122.17.10 (38.122.17.10) 149.830 ms
18 201-0-226-24.cgocable.net (24.226.0.201) 112.655 ms 114.027 ms 111.674 ms

It times out after hop 18.

It isn't Cogent- it's Cogeco, a cable provider in Ontario. I use it from here because it's as stable a speed test as the NY speakeasy was, and reports back here.

Mine:



That's on the lowest tier. You could also try the Denver test here: »/speedtest?flash=1
--
***ATMFAQ***DIFAQ***Kitchen Sink***

This is the only 'non-OOL' test that shows sort of what it should, only problem is that Green House Data is 'on-network' as they also have Bresnan/OOL as one of their providers:

traceroute to speedtest.greenhousedata.com (208.89.163.194), 64 hops max, 52 byte packets
 1  * * *
 2  butmtfh1hb6-ge-0-0-0-U168.int.bresnan.net (72.175.110.169)  8.399 ms  10.595 ms  9.358  ms
 3  blnmtfh2cr5-GE-3-0-9-U0.int.bresnan.net (72.175.110.34)  19.350 ms  14.893 ms  19.172  ms
 4  blnmtfh1cr5-XE-5-0-0-U0.int.bresnan.net (72.175.110.72)  15.542 ms
    blnmtaT1cr5-XE-4-0-0-U0.int.bresnan.net (72.175.110.118)  15.014 ms
    blnmtfh1cr5-XE-5-0-0-U0.int.bresnan.net (72.175.110.72)  15.976 ms
 5  cspwy002cr5-XE-5-1-0-U0.int.bresnan.net (72.175.110.121)  27.817 ms  21.318 ms
    cspwy001hb1-GE-2-1.int.bresnan.net (72.175.110.93)  27.689 ms
 6  cspwy001cr5-XE-5-0-0-U0.int.bresnan.net (72.175.110.94)  21.811 ms
    72.175.111.20 (72.175.111.20)  35.956 ms
    cspwy001cr5-XE-5-0-0-U0.int.bresnan.net (72.175.110.94)  28.115 ms
 7  chywyaT1cr5-XE-5-3-0-U0.int.bresnan.net (72.175.110.225)  44.309 ms  44.387 ms  58.458  ms
 8  chywy001hb7-GE-1-1-1-U0.int.bresnan.net (72.175.110.141)  59.804 ms  65.359 ms  59.310  ms
 9  host-69-144-127-18.static.bresnan.net (69.144.127.18)  88.030 ms  65.918 ms  44.455 ms
10  CYSWYDC01ESW1-001-1-1.GREENHOUSEDATA.NET (208.89.160.11)  61.222 ms  67.184 ms  43.785  ms
11  SPEEDTEST.GREENHOUSEDATA.COM (208.89.163.194)  44.132 ms  27.715 ms  44.296 ms

Could be:

1) Defective modem
2) Bad job reconnecting drop at pole
3) New source of ingress causing a problem.
4) One or two more people slamming the downstream traffic fairly consistently

Doubt it's a defective modem.

I retried it (hooked directly to my Cisco 2950 switch instead of via 11n) and pulling around 20mbps. Better, but could use improvement. I'm calling them up and see if they see it on their end.

None of this really matters. Optimum has saturated connectivity every single night. Latency gets really bad starting around 4 p.m. Mountain and stays that way until midnight. I can get 30 just fine in the morning and early afternoon. I am lucky to see 10 after 3 in the afternoon now. They obviously are short on capacity. Traceroutes all the way out to Denver are fine. It is there that they are having some capacity problems.

CC - have no clue what bonding does - but same with me everynight - it gets pretty much useless past Denver when I guess we get handed off to either Level3 or Qwest's network?

This is actually tame below and is usually 150ms plus on the Denver hop (always #9 for me):

Tracing route to www.cnn.com [157.166.226.25] over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 10 ms 9 ms 9 ms cspwy001hb7-GE-0-2-1-U0.int.bresnan.net [72.175.110.113]
4 29 ms 8 ms 9 ms host-69-145-214-217.chy-wy.client.bresnan.net [69.145.214.217]
5 14 ms 15 ms 15 ms chywyaT1cr5-XE-5-3-0-U0.int.bresnan.net [72.175.110.225]
6 13 ms 14 ms 16 ms chywy001cr5-XE-5-1-0-U0.int.bresnan.net [72.175.110.128]
7 45 ms 17 ms 15 ms dencofh1tr5-XE-5-3-0-U0.int.bresnan.net [72.175.110.229]
8 46 ms 58 ms 45 ms host-72-175-111-144.bln-mt.client.bresnan.net [72.175.111.144]
9 136 ms 134 ms 138 ms xe-8-2-3.edge3.Denver1.Level3.net [4.28.20.29]
10 130 ms 132 ms 136 ms vlan51.ebr1.Denver1.Level3.net [4.69.147.94]
11 150 ms 152 ms 153 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
12 144 ms 143 ms 144 ms ae-82-82.csw3.Dallas1.Level3.net [4.69.151.153]
13 154 ms 149 ms 150 ms ae-83-83.ebr3.Dallas1.Level3.net [4.69.151.158]
14 170 ms 170 ms 171 ms ae-7-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
15 163 ms 163 ms 167 ms ae-63-63.ebr1.Atlanta2.Level3.net [4.69.148.242]
16 170 ms 169 ms 178 ms ae-1-51.edge4.Atlanta2.Level3.net [4.69.150.13]

If you have an ideas what we can do (or tell OOL) - I'd love to hear any ideas - as I USED to like to game with friends at night - but like Scott said above - is a laggy/high latency mess & not even worth trying until after midnight usually. I did speak with them - but since it's a peer agreement - they said nothing they can do...

EDIT: I did ask them why the server says BLN-MT (Billings?) - but they said the name doesn't matter - but didn't tell if it was really physically in Denver.

p.s. Thx ahead for any help sir...

Had to add in another post - but speedtest (and pingtest) to Dallas:

I did a tracert to cnn.com to be similar to you. I live in Cheyenne Wyoming.

Tracing route to www.cnn.com [157.166.255.19]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms SHYPANDA [192.168.1.1]
2 * * * Request timed out.
3 11 ms 11 ms 9 ms chywy002dr5-GE-3-0-6-0.int.bresnan.net [72.175.110.177]
4 47 ms 10 ms 11 ms chywy001cr5-XE-5-2-0U0.int.bresnan.net [72.175.110.130]
5 12 ms 11 ms 11 ms dencofh1tr5-XE-5-3-0U0.int.bresnan.net [72.175.110.229]
6 13 ms 12 ms 13 ms host-72-175-111-144.blnmt.client.bresnan.net [72.175.111.144]
7 93 ms 93 ms 94 ms xe-8-2-3.edge3.Denver1.Level3.net[4.28.20.29]
8 96 ms 92 ms 92 ms vlan51.ebr1.Denver1.Level3.net[4.69.147.94]
9 92 ms 96 ms 92 ms ae-2-2.ebr2.Dallas1.Level3.net[4.69.132.106]
10 82 ms 83 ms 77 ms ae-62-62.csw1.Dallas1.Level3.net[4.69.151.129]
11 89 ms 91 ms 92 ms ae-63-63.ebr3.Dallas1.Level3.net[4.69.151.134]
12 75 ms 76 ms 74 ms ae-7-7.ebr3.Atlanta2.Level3.net[4.69.134.22]
13 81 ms 76 ms 76 ms ae-73-73.ebr2.Atlanta2.Level3.net[4.69.148.254]
14 76 ms 112 ms 77 ms ae-21-52.car1.Atlanta1.Level3.net[4.69.150.67]

So while my latency also increases once it hits the backhaul with level-3, it's almost half of what yours is. Remember, a tracert shows the time from you to a specific spot. It's possible that the connection from Cheyenne to Casper to You isn't robust enough, and you're getting the extra time there. Me being in Cheyenne, it doesn't have to go any further. It stops here. My last 2 handoffs before Level 3, are 12 and 13ms. Yours are boosting up to around 45ms. That's before the handoff. These times, while not exponential, definitely do add up. Tracert are great for seeing a single bad spot, but not for determining total health. My tracert was done about an hour after yours.

P.S. Doing a speed test to Dallas is NOT a good example. You have no idea how good the server or bandwidth is at the other end. I did the same test as you, and I had 190ms latency and 11mb down and 3mb up. I did the same test to Los Angeles, and I had 27mb down and 4.5mb up, and 50ms latency. Same test to New York city is 30mb down; 3.5mb up; and 95ms latency.

P.S.S. My Pingtest, I did to Los Angeles is an "A". 0 lost packets, 50ms ping, and 2ms jitter. Don't test dallas. Matter of fact, test at least 3-4 random places. I suggest far and big pipes like LA and NYC. or even Chicago.

Thx sir & I was checking to Dallas/Chicago because that's where a lot of the game servers are. Was good to see you take the same route though - but have to say I used to skate right through Denver (on both Qwest/Level 3) with lil to no issues - so maybe they moved a bunch of us or added more to our internet backbone on ramp...lol

I usually use this neat lil free tool/utility called Axence Nettools - which will also shows (among many things) the packet loss and etc in the tracert.

I am having the exact same problem as you guys. I'm in Belgrade Montana. This problem just came up about 1.5 - 2 weeks ago. It's been frustrating doing ANYTHING on the internet the past two weeks. Considering switching.

Called customer support, and they are basically worthless. They have had no reports of problems (are you kidding me?).

They only take blame for what's on their network, even if it effects their users.

Here's mine to cnn.com as well.

Tracing route to www.cnn.com [157.166.255.19]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms DD-WRT [192.168.1.1]
2 9 ms 8 ms 7 ms host-69-144-102-34.jcs-wy.client.bresnan.net [69
.144.102.34]
3 6 ms 7 ms 7 ms bzmmt001hb6-GE-1-3-0-U0.int.bresnan.net [72.175.
111.56]
4 12 ms 10 ms 12 ms 69.145.247.150
5 11 ms 12 ms 12 ms mslmt001cr5-XE-5-0-0-U0.int.bresnan.net [72.175.
110.9]
6 25 ms 25 ms 29 ms seawafh1cr5-XE-5-1-0-U0.int.bresnan.net [72.175.
111.23]
7 59 ms 60 ms 65 ms gdjco001cr5-XE-5-3-0-U0.int.bresnan.net [72.175.
110.41]
8 59 ms 61 ms 60 ms gdjco002cr5-XE-5-0-0-U0.int.bresnan.net [72.175.
110.231]
9 65 ms 63 ms 64 ms dencofh1cr5-XE-5-1-0-U0.int.bresnan.net [72.175.
111.154]
10 64 ms 64 ms 69 ms dencofh1tr5-XE-4-3-0-U0.int.bresnan.net [72.175.
111.142]
11 172 ms 172 ms 245 ms te-9-3.car1.Denver1.Level3.net [4.53.10.97]
12 173 ms 171 ms 171 ms vlan51.ebr1.Denver1.Level3.net [4.69.147.94]
13 172 ms 170 ms 170 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
14 173 ms 175 ms 173 ms ae-82-82.csw3.Dallas1.Level3.net [4.69.151.153]

15 170 ms 170 ms 169 ms ae-83-83.ebr3.Dallas1.Level3.net [4.69.151.158]

16 191 ms 188 ms 190 ms ae-7-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
17 194 ms 200 ms 199 ms ae-73-73.ebr2.Atlanta2.Level3.net [4.69.148.254]

18 285 ms 233 ms 189 ms ae-21-52.car1.Atlanta1.Level3.net [4.69.150.67]