dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
73775
share rss forum feed
« New Speeds!
prev page · 1 · 2 · 3 · 4 · 5 · 6 · 7 ... 24 · 25 · 26 · next


itsburd

@bresnan.net
reply to bigburd

Re: Massive Slowdowns?

yah I think it's like a cron job/scheduled task/scheduled access restriction (QOS) type thing or something. Over the last week I've even wondered if Bresnan was being attacked by a botnet or something maybe. It's too bad they can't get it right I really liked this service prior to the outtage. They were NOT prepared for any kind of worst case scenarios at all IMO. I mean it's pretty clear. Anyhow I experienced slow internet connectivity at odd times today including around 2:30pm.



koolkid1563
Premium,MVM
join:2005-11-06
Powell, WY
reply to bigburd

Looks like I was down for about an hour and a half last night.


bigburd

join:2009-09-14
Butte, MT
kudos:1
reply to bigburd

traceroute to google.com (74.125.45.100), 30 hops max, 38 byte packets
1 host-10-252-148-1.but-mt.client.bresnan.net (10.252.148.1) 7.721 ms 30.821 ms 13.786 ms
2 butmtfh2hb6-GE-0-0-1-U96.int.bresnan.net (69.144.94.98) 13.436 ms 10.909 ms 17.781 ms
3 hlnmt002hb7-SO-1-2-0-U10.int.bresnan.net (69.144.94.161) 15.762 ms 12.301 ms 14.589 ms
4 mslmtfh1hb6-GE-1-3-0-U432.int.bresnan.net (69.144.26.102) 16.635 ms 17.773 ms 18.297 ms
5 host-72-175-110-1.bln-mt.client.bresnan.net (72.175.110.1) 18.894 ms 17.617 ms 16.559 ms
6 host-72-175-110-10.bln-mt.client.bresnan.net (72.175.110.10) 90.225 ms 98.776 ms 85.851 ms
7 66.62.136.49 (66.62.136.49) 103.997 ms 105.504 ms 111.101 ms
8 six.sea01.google.com (206.81.80.17) 114.461 ms 114.391 ms 123.320 ms
9 209.85.249.34 (209.85.249.34) 121.892 ms 202.616 ms 113.580 ms
10 216.239.43.81 (216.239.43.81) 168.610 ms 72.14.233.117 (72.14.233.117) 173.258 ms 216.239.43.81 (216.239.43.81) 162.364 ms
11 72.14.239.90 (72.14.239.90) 198.051 ms 72.14.236.26 (72.14.236.26) 188.909 ms 209.85.242.215 (209.85.242.215) 198.845 ms
12 72.14.232.215 (72.14.232.215) 178.668 ms 180.754 ms 187.959 ms
13 209.85.253.133 (209.85.253.133) 184.534 ms 209.85.253.145 (209.85.253.145) 196.269 ms 209.85.253.133 (209.85.253.133) 184.972 ms
14 yx-in-f100.google.com (74.125.45.100) 182.764 ms 178.855 ms 174.372 ms

Same Old Same Old.. This is at 11:15pm



kckid

@bresnan.net
reply to bigburd

This poor service has been going on as far back as 2006.

I tried to help the local Bresnan service guy trouble shoot the problem. For 3/4 of 2007, I logged Bresnan's as well as 2 or 3 other's speed tests, 2-3-4 times a day. The local Bresnan service guy knew there was a problem and, to this date, is the only Bresnan representative to admit it and be honest with me. I think he was causing too many waves because he got fired. I gave copies of my log comparison sheets to the "higher up's" and that's the last I heard of it. I still have 4-5 months of data from 2007 but quit logging comparisons after the local rep left.

I'm supposed to have the 8.0 package. I think my all time low speed (DSL Reports) was 69 down on 2-10-2009. I've been at 200-800 kbps after about 5:00 pm for the last couple of weeks. As other's have said, Bresnan's response is, it's our problem, not Bresnan's. Of course, the Bresnan speed test always shows around 8,000 kbps. I've told the tech support guys that the program is written to show 8,000 even if my computer is unplugged. They say that the 8,000 measures speed between my computer and theirs and, once you get on the internet, all sorts of mysterious things can happen and they're not responsible for any of it. I told them I wasn't really interested in spending $50/month to show high speeds between our computers and that I really wanted fast speeds on the internet like they advertise constantly on their cable service.

Bottom line, there are evidently very few people who realize they are not getting what they're paying for and the one's that do know are reluctant to change ISP's.

Their cable service has been good. But, every 10 minutes when I see Bresnan adds that tell me how their internet service blows the socks off DSL or see the "good ol' boys" talk about pride and their "name on the door", I want to throw a brick through the TV screen! Yeah, "It's Personal".

A good analogy to Bresnan's service is going to a gas station and buying a gallon of gas for $2.70 and getting 1/2 ounce of gas instead of the promised one gallon. People wouldn't stand for that for a minute. But, as long as people do not complain about the poor sevice, I can't see where Bresnan has any incentive to upgrade their equipment to deliver what they're selling.

Now I think I'll go search for a new ISP.


alphainfinit2

join:2007-07-16
Whitefish, MT

2 edits
reply to AnonInsider

Hello,

Thanks for the updates. During the day it does appear as though the situation is resolved. At night however during peak time, we are still seeing spikes in latency above 100ms which of course makes working on a vpn connection fairly painful. I understand that ICMP requests are normally de-prioritized but the behavior over the last week would lead me to believe that this is not the case with the Bresnan network devices. You can see in the graphs that the behavior is repeated every evening.

I have provided traceroutes to support that show that the primary issue starts between the 72.175.110.25 and 72.175.110.12 Bresnan network devices where latency goes from 20ms on device one to 80-100 ms on device 2. At this point in time we havn't left the Bresnan network out to the internet yet.

--

bigburd

join:2009-09-14
Butte, MT
kudos:1
reply to bigburd

tired of this. Another IT worker asked me if it was them or if their cable is slow.. another person that has heard the story about the truth about bresnan. Anyhow they were unable to connect to the work vpn it was so bad.


alphainfinit2

join:2007-07-16
Whitefish, MT

1 edit
reply to bigburd

Click for full size
firewall (root) ~ $ traceroute www.google.com
traceroute: Warning: www.google.com has multiple addresses; using 74.125.127.103
traceroute to www.l.google.com (74.125.127.103), 30 hops max, 38 byte packets
1 * * *
2 host-69-144-26-145.static.bresnan.net (69.144.26.145) 8.100 ms 9.092 ms 9.822 ms
3 mslmtfh1hb7-SO-0-3-0-U0.int.bresnan.net (69.144.26.69) 14.962 ms 15.168 ms 12.814 ms
4 host-72-175-110-3.bln-mt.client.bresnan.net (72.175.110.3) 12.830 ms 14.787 ms 12.825 ms
MPLS Label=341632 CoS=3 TTL=1 S=0
5 host-72-175-110-10.bln-mt.client.bresnan.net (72.175.110.10) 188.202 ms 170.029 ms 171.137 ms
6 66.62.136.57 (66.62.136.57) 189.574 ms 191.060 ms 190.440 ms
7 six.sea01.google.com (206.81.80.17) 188.736 ms 195.417 ms 204.613 ms
8 209.85.249.32 (209.85.249.32) 200.740 ms 196.287 ms 209.85.249.34 (209.85.249.34) 197.354 ms
9 72.14.239.12 (72.14.239.12) 206.970 ms 209.85.250.126 (209.85.250.126) 201.808 ms 72.14.239.12 (72.14.239.12) 193.069 ms
MPLS Label=707365 CoS=3 TTL=1 S=0
10 216.239.48.32 (216.239.48.32) 199.265 ms 202.637 ms 209.85.250.146 (209.85.250.146) 199.916 ms
11 64.233.174.99 (64.233.174.99) 199.711 ms 216.239.48.141 (216.239.48.141) 195.353 ms 216.239.48.143 (216.239.48.143) 209.499 ms
12 216.239.46.22 (216.239.46.22) 199.286 ms 194.364 ms 216.239.46.2 (216.239.46.2) 232.155 ms
13 pz-in-f103.google.com (74.125.127.103) 201.406 ms 203.997 ms 191.369 ms

--

miniskunk

join:2008-04-13
Cut Bank, MT
reply to bigburd

I noticed you just posted graphs on tonight. It's bad...bandwidth down to 1/5 it should be down and 1/5 to 1/3 up. Ping time is around 300 ms making online gaming unplayable. I have spoken with a tech person and forwarded their internet trouble form with ping times. No matter where I ping the bottleneck happens at 66.62.160.25 located somewhere in Seattle.



koolkid1563
Premium,MVM
join:2005-11-06
Powell, WY

4 edits

traceroute to google.com (74.125.45.100), 30 hops max, 38 byte packets
1 10.252.148.1 (10.252.148.1) 8.878 ms 52.404 ms 42.225 ms
2 butmtfh2hb6-GE-0-0-0-U120.int.bresnan.net (69.144.94.122) 28.845 ms 29.394 ms 34.865 ms
3 hlnmt002hb7-SO-1-2-0-U10.int.bresnan.net (69.144.94.161) 32.531 ms 23.453 ms 16.413 ms
4 mslmtfh1hb6-GE-1-3-0-U432.int.bresnan.net (69.144.26.102) 17.978 ms 23.999 ms 21.696 ms
5 host-72-175-110-1.bln-mt.client.bresnan.net (72.175.110.1) 24.592 ms 30.423 ms 35.217 ms
6 host-72-175-110-10.bln-mt.client.bresnan.net (72.175.110.10) 86.547 ms 67.911 ms 77.657 ms
7 66.62.136.49 (66.62.136.49) 148.105 ms 159.484 ms 152.591 ms
8 six.sea01.google.com (206.81.80.17) 152.193 ms 180.752 ms 155.266 ms
9 209.85.249.34 (209.85.249.34) 151.037 ms 144.636 ms 209.85.249.32 (209.85.249.32) 160.911 ms
10 216.239.43.81 (216.239.43.81) 181.980 ms 72.14.233.117 (72.14.233.117) 197.457 ms 216.239.43.81 (216.239.43.81) 192.702 ms
11 209.85.242.215 (209.85.242.215) 192.303 ms 72.14.236.26 (72.14.236.26) 217.510 ms 209.85.242.215 (209.85.242.215) 235.934 ms
12 72.14.232.215 (72.14.232.215) 210.518 ms 209.85.254.241 (209.85.254.241) 193.683 ms 72.14.232.215 (72.14.232.215) 215.731 ms
13 209.85.253.141 (209.85.253.141) 198.985 ms 209.105 ms 247.604 ms
14 yx-in-f100.google.com (74.125.45.100) 206.744 ms 212.588 ms 187.682 ms

From home:
traceroute to google.com (74.125.45.100), 30 hops max, 38 byte packets
1 sub-96-31-116-2.tctwest.net (96.31.116.2) 17.298 ms 4.577 ms 4.478 ms
2 sub-96-31-116-1.tctwest.net (96.31.116.1) 4.034 ms 3.409 ms 3.902 ms
3 66.62.227.33 (66.62.227.33) 17.777 ms 17.727 ms 18.164 ms
4 den1-core-02.360.net (66.62.4.2) 47.264 ms 47.411 ms 47.471 ms
5 lax1-core-01.360.net (66.62.3.41) 47.063 ms 46.980 ms 46.790 ms
6 lax1-edge-01.360.net (66.62.5.195) 47.119 ms 47.314 ms 47.525 ms
7 core1-0-1-0.lax.net.google.com (198.32.146.46) 47.365 ms 48.282 ms 47.550 ms
8 216.239.43.12 (216.239.43.12) 48.154 ms 47.882 ms 48.160 ms
9 216.239.43.125 (216.239.43.125) 102.984 ms 102.902 ms 102.313 ms
10 72.14.232.213 (72.14.232.213) 103.015 ms 106.084 ms 72.14.232.215 (72.14.232.215) 103.368 ms
11 209.85.253.137 (209.85.253.137) 109.541 ms 209.85.253.141 (209.85.253.141) 108.144 ms 209.85.253.137 (209.85.253.137) 113.893 ms
12 yx-in-f100.google.com (74.125.45.100) 102.533 ms 102.319 ms 103.382 ms

Notice the highlighted route. Both ISPs use 360 but look at the latency difference on the handoff of the two to 360, Bresnan's always looks a lot worse. Even when the route through Bresnan's network looks OK their first hop out always looks bad.

Whats even more interesting is the route and latency going from my home connection to that exact same IP that is supposedly causing Bresnan's problem:
Tracing route to 66.62.136.49 over a maximum of 30 hops

1 17 ms 4 ms 5 ms sub-96-31-116-2.tctwest.net [96.31.116.2]
2 3 ms 4 ms 4 ms sub-96-31-116-1.tctwest.net [96.31.116.1]
3 18 ms 17 ms 17 ms 66.62.227.33
4 45 ms 45 ms 46 ms den1-core-02.360.net [66.62.4.66]
5 45 ms 46 ms 47 ms 66.62.3.46
6 56 ms 52 ms 45 ms 66.62.136.49

I ran the same from my router but it resulted in a slightly different ending IP:
traceroute to 66.62.136.49 (66.62.136.49), 30 hops max, 38 byte packets
1 sub-96-31-116-2.tctwest.net (96.31.116.2) 4.395 ms 3.822 ms 8.916 ms
2 sub-96-31-116-1.tctwest.net (96.31.116.1) 3.909 ms 3.364 ms 3.599 ms
3 66.62.227.33 (66.62.227.33) 18.533 ms 18.082 ms 17.487 ms
4 den1-core-02.360.net (66.62.4.66) 46.263 ms 45.783 ms 45.797 ms
5 66.62.3.46 (66.62.3.46) 45.737 ms 47.549 ms 45.802 ms
6 66.62.8.67 (66.62.8.67) 45.694 ms * 46.031 ms



anonburd

@bresnan.net
reply to bigburd

Just a little note with what I sent Bresnan last night. I have an open ticket via their email support system so I drop them a line every other day or so letting them know they are still broken. It beats the crap out of calling them because I don't have to listen to their lame excuses anymore NOR get my time wasted being bounced from here to there to there.

Just a note to everyone that reads this.. PLEASE read in the earlier posts, go to the FCC and FTC sites, fill out the complaint forms and send them in, it only takes about 10 minutes. This company NEEDS a punch in the gut at this point so do everything you can to pressure them.

"Just a ping letting you all know this issue is still at hand. I can't believe you are actually charging me for this *lack of* service. It's been over a month since I've had the service I am paying for. LOTS of folks are experiencing the same thing. Nobody at my work can VPN in if they have Bresnan at home, I have't been able to do any of my web work over this internet connection since this started over a month ago now. What I am saying is you are COSTING PEOPLE MONEY AND PREVENTING COMPANIES FROM OPERATING PROPERLY... First person that mentions class action lawsuit and I'm jumping on board full throttle. GET THIS CRAP FIXED I'M TIRED OF THIS!"



anonburd

@bresnan.net
reply to bigburd

Just a note about how bad this sucks. I am tired of having to get up at 4:30am to get any work done. This morning I installed Debian Linux on my new machine via network install and the entire basic stuff all the way to KDE desktop took me an hour and a half. This was about 2GB worth of downloading. Right now I am installing a small gaggle of software that was 90MB and it has been running almost 40 minutes. FED UP!



koolkid1563
Premium,MVM
join:2005-11-06
Powell, WY
reply to bigburd

It seems it goes 4 days with no problem latency wise (speed problem is still there though) then it gets terrible on all fronts again.

traceroute to ny-monitor.dslreports.com (217.160.255.49), 30 hops max, 38 byte packets
1 10.252.148.1 (10.252.148.1) 17.710 ms 7.178 ms 10.872 ms
2 butmtfh2hb6-GE-0-0-1-U96.int.bresnan.net (69.144.94.98) 10.412 ms 8.408 ms 10.484 ms
3 hlnmt002hb7-SO-1-2-0-U10.int.bresnan.net (69.144.94.161) 13.874 ms 12.800 ms 21.765 ms
4 mslmtfh1hb7-GE-0-0-0-U432.int.bresnan.net (69.144.26.101) 28.263 ms 28.628 ms 32.406 ms
5 host-72-175-110-3.bln-mt.client.bresnan.net (72.175.110.3) 19.959 ms 28.138 ms 22.447 ms
6 host-72-175-110-10.bln-mt.client.bresnan.net (72.175.110.10) 107.016 ms 98.955 ms 99.531 ms
7 66.62.136.49 (66.62.136.49) 171.644 ms 178.376 ms 183.468 ms
8 pdx1-core-02.360.net (66.62.4.130) 175.405 ms 174.332 ms 167.652 ms
9 66.62.3.45 (66.62.3.45) 174.028 ms 183.482 ms 177.630 ms
10 den1-edge-01.360.net (66.62.4.3) 178.123 ms 177.309 ms 182.634 ms
11 ge-6-16.car2.Denver1.Level3.net (4.53.2.25) 188.093 ms 193.796 ms 187.126 ms
12 ae-32-56.ebr2.Denver1.Level3.net (4.68.107.190) 198.182 ms 197.817 ms 201.695 ms
13 ae-3.ebr1.Chicago2.Level3.net (4.69.132.62) 225.197 ms 210.923 ms 211.088 ms
14 ae-6.ebr1.Chicago1.Level3.net (4.69.140.189) 210.739 ms 215.923 ms 212.843 ms
15 ae-2-2.ebr2.NewYork2.Level3.net (4.69.132.66) 236.610 ms 250.329 ms 249.696 ms
16 ae-6-6.ebr4.NewYork1.Level3.net (4.69.141.21) 229.283 ms 230.608 ms 234.728 ms
17 ae-84-84.csw3.NewYork1.Level3.net (4.69.134.122) 239.081 ms 236.684 ms 241.390 ms
18 ae-43-99.car3.NewYork1.Level3.net (4.68.16.197) 230.696 ms 231.313 ms 234.201 ms
19 level3-up.nyc.schlund.net (4.78.164.2) 238.269 ms 241.681 ms 244.491 ms
20 vl-840.gw-core-b.whn.oneandone.net (74.208.1.221) 248.050 ms 244.213 ms 240.730 ms
21 ae-1.gw-prtr-b.whn.oneandone.net (74.208.6.54) 253.277 ms 244.149 ms 249.719 ms
22 u15150124.onlinehome-server.com (217.160.255.49) 267.821 ms 239.187 ms 252.801 ms

traceroute to wc-monitor.dslreports.com (64.81.79.41), 30 hops max, 38 byte packets
1 10.252.148.1 (10.252.148.1) 9.960 ms 6.315 ms 8.877 ms
2 butmtfh2hb6-GE-0-0-0-U120.int.bresnan.net (69.144.94.122) 10.539 ms 9.302 ms 6.374 ms
3 hlnmt002hb7-SO-1-2-0-U10.int.bresnan.net (69.144.94.161) 12.388 ms 18.732 ms 13.917 ms
4 mslmtfh1hb6-GE-1-3-0-U432.int.bresnan.net (69.144.26.102) 15.894 ms 20.491 ms 17.444 ms
5 host-72-175-110-1.bln-mt.client.bresnan.net (72.175.110.1) 15.457 ms 15.359 ms 17.420 ms
6 host-72-175-110-10.bln-mt.client.bresnan.net (72.175.110.10) 99.979 ms 105.285 ms 104.514 ms
7 66.62.136.49 (66.62.136.49) 171.106 ms 176.004 ms 177.119 ms
8 ge-7-10.car2.Seattle1.Level3.net (4.53.146.97) 179.150 ms 173.853 ms 175.180 ms
9 ae-32-52.ebr2.Seattle1.Level3.net (4.68.105.62) 187.604 ms 170.457 ms 183.080 ms
10 ae-1-100.ebr1.Seattle1.Level3.net (4.69.132.17) 180.715 ms 180.506 ms 170.113 ms
11 ae-7.ebr2.SanJose1.Level3.net (4.69.132.49) 180.174 ms 195.968 ms 195.635 ms
12 ae-62-62.csw1.SanJose1.Level3.net (4.69.134.210) 194.234 ms 205.801 ms 188.657 ms
13 ae-11-69.car1.SanJose1.Level3.net (4.68.18.3) 180.649 ms 171.914 ms 172.598 ms
14 unknown.Level3.net (209.247.156.222) 182.166 ms 202.264 ms 192.179 ms
15 dslreports-west2.speakeasy.net (64.81.79.41) 195.690 ms 192.667 ms 191.668 ms



koolkid1563
Premium,MVM
join:2005-11-06
Powell, WY

Getting worse...

traceroute to ny-monitor.dslreports.com (217.160.255.49), 30 hops max, 38 byte packets
1 10.252.148.1 (10.252.148.1) 12.228 ms 6.747 ms 15.960 ms
2 butmtfh2hb6-GE-0-0-1-U96.int.bresnan.net (69.144.94.98) 11.163 ms 14.526 ms 15.653 ms
3 hlnmt002hb7-SO-1-2-0-U10.int.bresnan.net (69.144.94.161) 25.755 ms 29.892 ms 14.617 ms
4 mslmtfh1hb7-GE-0-0-0-U432.int.bresnan.net (69.144.26.101) 22.528 ms 19.940 ms 24.187 ms
5 host-72-175-110-3.bln-mt.client.bresnan.net (72.175.110.3) 29.904 ms 24.899 ms 25.746 ms
6 host-72-175-110-10.bln-mt.client.bresnan.net (72.175.110.10) 90.020 ms 81.748 ms 82.770 ms
7 66.62.136.49 (66.62.136.49) 284.932 ms 270.186 ms 272.605 ms
8 pdx1-core-02.360.net (66.62.4.130) 270.894 ms 296.249 ms 320.427 ms
9 66.62.3.45 (66.62.3.45) 388.224 ms 357.086 ms 305.547 ms
10 den1-edge-01.360.net (66.62.4.3) 273.782 ms 279.729 ms 297.602 ms
11 ge-6-16.car2.Denver1.Level3.net (4.53.2.25) 305.849 ms 283.353 ms 273.126 ms
12 ae-32-56.ebr2.Denver1.Level3.net (4.68.107.190) 272.889 ms 281.061 ms 288.576 ms
13 ae-3.ebr1.Chicago2.Level3.net (4.69.132.62) 313.473 ms 301.158 ms 306.357 ms
14 ae-6.ebr1.Chicago1.Level3.net (4.69.140.189) 319.199 ms 306.754 ms 323.626 ms
15 ae-2-2.ebr2.NewYork2.Level3.net (4.69.132.66) 337.479 ms 342.733 ms 328.658 ms
16 ae-6-6.ebr4.NewYork1.Level3.net (4.69.141.21) 330.445 ms 359.811 ms 336.849 ms
17 ae-64-64.csw1.NewYork1.Level3.net (4.69.134.114) 346.838 ms ae-74-74.csw2.NewYork1.Level3.net (4.69.134.118) 340.528 ms 348.399 ms
18 ae-23-79.car3.NewYork1.Level3.net (4.68.16.69) 348.797 ms 339.576 ms 340.934 ms
19 level3-up.nyc.schlund.net (4.78.164.2) 333.950 ms 337.131 ms 344.772 ms
20 vl-840.gw-core-b.whn.oneandone.net (74.208.1.221) 331.914 ms 356.037 ms 339.211 ms
21 ae-1.gw-prtr-b.whn.oneandone.net (74.208.6.54) 345.112 ms 349.504 ms 373.298 ms
22 u15150124.onlinehome-server.com (217.160.255.49) 347.058 ms 344.637 ms 342.649 ms

traceroute to wc-monitor.dslreports.com (64.81.79.41), 30 hops max, 38 byte packets
1 10.252.148.1 (10.252.148.1) 16.430 ms 12.714 ms 8.946 ms
2 butmtfh2hb6-GE-0-0-0-U120.int.bresnan.net (69.144.94.122) 11.344 ms 8.481 ms 12.384 ms
3 hlnmt002hb7-SO-1-2-0-U10.int.bresnan.net (69.144.94.161) 11.340 ms 13.847 ms 14.618 ms
4 mslmtfh1hb6-GE-1-3-0-U432.int.bresnan.net (69.144.26.102) 20.874 ms 21.840 ms 21.051 ms
5 host-72-175-110-1.bln-mt.client.bresnan.net (72.175.110.1) 21.295 ms 32.009 ms 26.902 ms
6 host-72-175-110-10.bln-mt.client.bresnan.net (72.175.110.10) 76.929 ms 75.496 ms 75.998 ms
7 66.62.136.49 (66.62.136.49) 284.795 ms 283.538 ms 288.327 ms
8 ge-7-10.car2.Seattle1.Level3.net (4.53.146.97) 288.297 ms 293.299 ms 291.373 ms
9 ae-32-52.ebr2.Seattle1.Level3.net (4.68.105.62) 320.430 ms 288.065 ms 291.816 ms
10 ae-1-100.ebr1.Seattle1.Level3.net (4.69.132.17) 314.315 ms 323.043 ms 310.356 ms
11 ae-7.ebr2.SanJose1.Level3.net (4.69.132.49) 324.166 ms 318.095 ms 311.790 ms
12 ae-72-72.csw2.SanJose1.Level3.net (4.69.134.214) 311.880 ms 313.071 ms 315.438 ms
13 ae-21-79.car1.SanJose1.Level3.net (4.68.18.67) 304.007 ms ae-31-89.car1.SanJose1.Level3.net (4.68.18.131) 308.044 ms 307.026 ms
14 unknown.Level3.net (209.247.156.222) 310.456 ms 312.483 ms 303.983 ms
15 dslreports-west2.speakeasy.net (64.81.79.41) 315.298 ms 305.654 ms 302.571 ms



koolkid1563
Premium,MVM
join:2005-11-06
Powell, WY

And a traceroute from home to 66.62.136.49:

root@ :~# traceroute 66.62.136.49
traceroute to 66.62.136.49 (66.62.136.49), 30 hops max, 38 byte packets
1 sub-96-31-116-2.tctwest.net (96.31.116.2) 4.670 ms 4.301 ms 4.380 ms
2 sub-96-31-116-1.tctwest.net (96.31.116.1) 4.136 ms 3.598 ms 3.464 ms
3 66.62.227.33 (66.62.227.33) 18.209 ms 17.799 ms 18.516 ms
4 den1-core-02.360.net (66.62.4.66) 46.807 ms 45.826 ms 47.848 ms
5 66.62.3.46 (66.62.3.46) 64.554 ms 46.534 ms 47.409 ms
6 66.62.8.67 (66.62.8.67) 47.429 ms * 47.046 ms



soadlink

join:2002-11-17
USA

1 edit
reply to bigburd

I have informed the level 2 tech about this tonight while we were discussing my other issue I currently have a ticket in for.

He said he thought they fixed it and closed all the tickets about it, but apparently they have not. I sent him my smokeping tests and said he will be putting in another ticket for that.

I told him it was currently ongoing, and that if an engineer was nearby that he could tell them to check it out WHILE it's happening. I don't know how a company the size of Bresnan couldn't already be aware (i'm sure they are), but it couldn't hurt for him to let them know.

Tracing route to 74.125.45.100 with TTL of 32:

1 0ms 192.168.1.1
2 * Request timed out.
3 12ms 69.144.26.153
4 19ms 69.144.26.69
5 15ms 72.175.110.3
6 110ms 72.175.110.10
7 127ms 66.62.136.49
8 135ms 206.81.80.17
9 140ms 209.85.249.34
10 178ms 216.239.43.81
11 212ms 72.14.236.26
12 206ms 72.14.232.213
13 210ms 209.85.253.145
14 199ms 74.125.45.100



koolkid1563
Premium,MVM
join:2005-11-06
Powell, WY

3 edits

Just got off the phone w/tech support. Apparently they are aware that the issue is with 360...I told him otherwise. He did say 360 was telling Bresnan that it was Bresnan that was the problem and not them, which our traces seem to back up for the most part. My traces to that 360 hop from my FTTH connection show it isn't with 360 and my traces here show Bresnan's own internal network was part of the problem. He was not aware of anything wrong on their network so I sent him my traces through the usual means...like it will actually get looked at...


alphainfinit2

join:2007-07-16
Whitefish, MT

2 edits
reply to bigburd

Click for full size
This is most certainly a Bresnan issue as most of the traceroutes in this 105 response thread show the same problem IP over and over again. This is at the edge of the Bresnan network BEFORE you hit 360. This is within their own network and most likely within the same data center! The 72.175.110.110 device simply can't handle the amount of traffic that is being thrown at it on one or multiple interfaces. Notice the latency on hops 4 and 5. Hop 4 is normal, hop 5 is problematic and blows the latency out of the water for all the hops after it. Now, it is possible that there could be some type of routing issue between the Bresnan and 360 device, but at the end of the day Bresnan is responsible for resolving any issues that occur between them and 360.

traceroute to www.l.google.com (74.125.155.104), 30 hops max, 38 byte packets
1 * * *
2 host-69-144-26-145.static.bresnan.net (69.144.26.145) 8.285 ms 9.179 ms 9.383 ms
3 mslmt002hb7-SO-1-2-2-U0.int.bresnan.net (69.144.26.181) 13.699 ms 13.134 ms 12.801 ms
4 host-72-175-110-1.bln-mt.client.bresnan.net (72.175.110.1) 17.595 ms 21.614 ms 15.820 ms
MPLS Label=341600 CoS=5 TTL=1 S=0
5 host-72-175-110-10.bln-mt.client.bresnan.net (72.175.110.10) 125.626 ms 114.355 ms 117.500 ms

6 66.62.136.57 (66.62.136.57) 136.448 ms 132.704 ms 131.709 ms
7 six.sea01.google.com (206.81.80.17) 135.957 ms 134.460 ms 135.974 ms
8 209.85.249.32 (209.85.249.32) 137.696 ms 209.85.249.34 (209.85.249.34) 129.936 ms 209.85.249.32 (209.85.249.32) 131.942 ms
9 209.85.250.126 (209.85.250.126) 132.051 ms 143.505 ms 137.245 ms
MPLS Label=553047 CoS=5 TTL=1 S=0
10 209.85.250.146 (209.85.250.146) 128.675 ms 209.85.250.144 (209.85.250.144) 134.520 ms 216.239.48.34 (216.239.48.34) 126.382 ms
11 216.239.48.137 (216.239.48.137) 137.516 ms 64.233.174.131 (64.233.174.131) 134.464 ms 146.521 ms
12 209.85.254.150 (209.85.254.150) 148.482 ms 144.325 ms 139.842 ms
13 px-in-f104.google.com (74.125.155.104) 135.559 ms 128.055 ms 128.683 ms
--


koolkid1563
Premium,MVM
join:2005-11-06
Powell, WY

It is at it again:
traceroute to sea.speakeasy.net (66.93.87.2), 30 hops max, 38 byte packets
1 10.252.148.1 (10.252.148.1) 7.360 ms 7.286 ms 8.363 ms
2 butmtfh2hb6-GE-0-0-0-U120.int.bresnan.net (69.144.94.122) 6.897 ms 14.424 ms 7.374 ms
3 hlnmt002hb7-SO-1-2-0-U10.int.bresnan.net (69.144.94.161) 13.913 ms 14.226 ms 11.291 ms
4 mslmtfh1hb6-GE-1-3-0-U432.int.bresnan.net (69.144.26.102) 16.897 ms 15.847 ms 19.361 ms
5 host-72-175-110-1.bln-mt.client.bresnan.net (72.175.110.1) 17.460 ms 17.469 ms 18.895 ms
6 host-72-175-110-10.bln-mt.client.bresnan.net (72.175.110.10) 165.624 ms 163.090 ms 169.643 ms
7 66.62.136.57 (66.62.136.57) 221.231 ms 219.083 ms 221.218 ms
8 ge-7-10.car2.Seattle1.Level3.net (4.53.146.97) 220.699 ms 219.204 ms 217.693 ms
9 SPEAKEASY-I.car4.Seattle1.Level3.net (209.247.91.170) 226.680 ms 223.086 ms 221.220 ms
10 dns.sea1.speakeasy.net (66.93.87.2) 223.717 ms 234.157 ms 255.279 ms



soadlink

join:2002-11-17
USA
reply to bigburd

1 0ms 192.168.1.1
2 * Request timed out.
3 9ms 69.144.26.153
4 16ms 69.144.26.69
5 27ms 72.175.110.3
6 294ms 72.175.110.10
7 296ms 66.62.136.49
8 299ms 206.81.80.17
9 302ms 209.85.249.34
10 361ms 216.239.43.81
11 380ms 72.14.239.90
12 397ms 72.14.232.215
13 398ms 209.85.253.133
14 393ms 74.125.45.100

Unbelievable.



koolkid1563
Premium,MVM
join:2005-11-06
Powell, WY

Way worse now, showing upwards of 300ms pings on that hop inside their network...

traceroute to wc-monitor.dslreports.com (64.81.79.41), 30 hops max, 38 byte packets
1 10.252.148.1 (10.252.148.1) 18.095 ms 7.609 ms 11.380 ms
2 butmtfh2hb6-GE-0-0-0-U120.int.bresnan.net (69.144.94.122) 6.866 ms 10.446 ms 8.031 ms
3 hlnmt002hb7-SO-1-2-0-U10.int.bresnan.net (69.144.94.161) 11.232 ms 42.151 ms 11.380 ms
4 mslmtfh1hb6-GE-1-3-0-U432.int.bresnan.net (69.144.26.102) 36.408 ms 21.592 ms 19.428 ms
5 host-72-175-110-1.bln-mt.client.bresnan.net (72.175.110.1) 24.933 ms 21.525 ms 25.912 ms
6 host-72-175-110-10.bln-mt.client.bresnan.net (72.175.110.10) 310.758 ms 317.019 ms 334.378 ms
7 66.62.136.49 (66.62.136.49) 266.276 ms 265.926 ms 266.275 ms
8 ge-7-10.car2.Seattle1.Level3.net (4.53.146.97) 255.759 ms 259.956 ms 270.776 ms
9 ae-32-52.ebr2.Seattle1.Level3.net (4.68.105.62) 267.266 ms 263.249 ms 277.744 ms
10 ae-1-100.ebr1.Seattle1.Level3.net (4.69.132.17) 276.277 ms 257.061 ms 262.276 ms
11 ae-7.ebr2.SanJose1.Level3.net (4.69.132.49) 277.620 ms 275.569 ms 261.759 ms
12 ae-92-92.csw4.SanJose1.Level3.net (4.69.134.222) 259.266 ms 270.328 ms 261.762 ms
13 ae-41-99.car1.SanJose1.Level3.net (4.68.18.195) 267.738 ms ae-11-69.car1.SanJose1.Level3.net (4.68.18.3) 262.551 ms 264.533 ms
14 unknown.Level3.net (209.247.156.222) 266.271 ms 270.469 ms 258.244 ms
15 dslreports-west2.speakeasy.net (64.81.79.41) 257.469 ms 269.183 ms 271.390 ms



koolkid1563
Premium,MVM
join:2005-11-06
Powell, WY





Latencywhere

@174.44.38.x
reply to bigburd

It's strange how the latency is next to the ip that is in billings but they say it's out of their network.

So who is in control after those hops? I'd call those people and tell them Bresnan is telling it's customers it's the fault of whomever is in control of the datacenters on those hops.

Let them get in a legal battle of deffamatory accusations and stuff. Someone will have to bend.

Tracing route to google.com [74.125.45.100]
over a maximum of 30 hops:

1 * * * Request timed out.
2 10 ms 7 ms 9 ms host-69-144-26-161.static.bresnan.net
[69.144.26.161]
3 13 ms 12 ms 12 ms mslmtfh1hb7-SO-0-3-0-U0.int.bresnan.net
[69.144.26.69]
4 14 ms 15 ms 15 ms host-72-175-110-3.bln-mt.client.bresnan.net
[72.175.110.3]
5 292 ms 292 ms 286 ms host-72-175-110-10.bln-
mt.client.bresnan.net [72.175.110.10]
6 312 ms 303 ms 306 ms 66.62.136.49
7 308 ms 306 ms 311 ms six.sea01.google.com [206.81.80.17]
8 319 ms 311 ms 310 ms 209.85.249.32
9 388 ms 423 ms 364 ms 72.14.233.117
10 364 ms 415 ms 384 ms 209.85.242.215
11 524 ms 387 ms 382 ms 72.14.232.213
12 372 ms 372 ms 374 ms 209.85.253.141
13 381 ms 381 ms 388 ms yx-in-f100.google.com [74.125.45.100]



koolkid1563
Premium,MVM
join:2005-11-06
Powell, WY

Looks like they are either fixing something or they are losing their connectivity to 360. What is surprising to me is that even though the 360 hop won't respond the hop that we have been noticing on Bresnan's side still has crappy latency with presumably little to no traffic going across that link.


jodokast82

join:2007-10-26
Great Falls, MT

1 edit

Click for full size
who runs this server?
I have been seeing a TON of disconnects happening at the highlighted IP in this pic. Is it Bresnan losing connection to 360 or is it 360 going down??? Bresnan is, as usual, clueless and asked me to reboot my modem. It is working good in this pic and unfortunately I haven't been able to catch it in the act. My screen cap skillz are not up to snuff, i guess.


koolkid1563
Premium,MVM
join:2005-11-06
Powell, WY

1 edit

That is 360's first hop, however Bresnan has the other end of it so if Bresnan was doing maint on their edge router it could also make that hop go down.


jodokast82

join:2007-10-26
Great Falls, MT

2 edits

Click for full size
finally got it
Confirmed with Bresnan. This is an issue in Billings, supposedly, and it is within Bresnan's network. The engineers are aware of it and have been hard at work on it for several hours. Now, how much of that is lip service and how much is customer service is still to be seen.

alphainfinit2

join:2007-07-16
Whitefish, MT

I spoke to them last night while the problem was occuring and the person I spoke to wasn't aware of any issues. Very interesting because the wait time to talk to a rep was 40 minutes.
--
[URL=http://www.speedtest.net][IMG]»www.speedtest.net/result/5780826···G][/URL]


bigburd

join:2009-09-14
Butte, MT
kudos:1
reply to jodokast82

this issue has been going on for over a month, you just haven't noticed it.


bigburd

join:2009-09-14
Butte, MT
kudos:1

2 edits
reply to bigburd

Just so everyone knows, I ping bresnan every few days via email in order to keep my help ticket open, after 7 days no contact your ticket expires (Edit: This may not be totally correct, either way they are getting my 2 cents regularly fo rmy frustrations. :] ). I also keep them updated on how many times I contact the FTC and FCC. The last few times I have been getting the identical prepared response other than the time I got NOTHING, just a notice they got my email. Here is the response:

"Thank you for contacting Bresnan. We still have a ticket entered and being worked on related to slow speeds. If it were resolved and you were still experiencing and issue we could certainly enter a new ticket, at this time we are still working on it. Thank you for your patience."

At least it is not a line of crap and I don't have to wait on hold for insane amounts of time. My recommendation is for everyone to use their help email. Give them the information to attach it to your phone calls and "ping" them at least once every 4 days until it is fixed. Saves you time while getting more messages through without the hassle and the aggravation.

Edit: Thought you might want to know what I am telling them when I am emailing them as well.

Once again another ping letting you know the service was pretty much unusable tonight. Folks from all over the state having the same issue. Nobody at my work can VPN in at night. Your costing people money and time and we still don't have a fix over a month later. You know you have an issue so get on it already. With the dozens of traceroutes I have seen from all over the state and wyoming it's pretty clear that you are overloading a device/segment in Billings, this was not like this before the massive outtage a month ago, if all else fails why not try putting the network back together like it was? I mean geez at least it was WORKING, didn't you people have documentation or something, I mean really this service has gone from first rate to lost in space over night.. wtf

On another note. Just a few pointers for your "support desk" folks.

1. Don't tell me that your speed test is the only thing that matters. I'm not paying you to provide me a connection to your internal network I am paying you to provide me with a reliable connection to the internet at a reasonably close speed to what you advertise, which you are not.

2. Stop blaming people's routers at the first sign of trouble. Every person I have talked to has said your help desk people has blamed their router.We all know routers are very reliable pieces of equipment and are usually set it and forget it. Yah sure a person might have a router problem here and there but the reality of the matter is your folks are deaf to listen to people's issues and simply want to pop out a quick fix and get you off the line. TERRIBLE!

3. Stop asking people to tear down their networks for your testing. This is your friggin dime not mine. You wanna come to my house and measure your network speed, fine, set up a friggin appointment and it better be at the times I tell you my issue is happening.

4. Stop expecting people to put a wrench in their life just so you can work when you feel like it. Like I said before this is your friggin dime not mine. I paid for this stuff and I am not getting what I paid for period. You work for me not the other way around.

Just so you know I will be contacting the FTC AGAIN this week and pushing for my complaint to be moved forward or expedited. I will also be pinging the FCC with my case number as well. This has gone on way too long and a class action lawsuit is not out of order at all. I will be contacting lawyers throughout the state starting with the Montana State Attorney General beginning next week. If you are going to waste a boatload of my time I might as well make it worth it.



soadlink

join:2002-11-17
USA

I can see it starting to rise again on my smokeping charts -- should be another night of fun for the Bresnan call center!

If anyone wants, I have another smoke ping (from dslreports, not from my home) for the hop right after it leaves the Bresnan network (at least the hop for me) -- »/r3/smokeping.···9d&r=643

The stability for that particular test proves it's not a 360 issue. We all know this, because it spikes at a BRESNAN IP... but their braindead network analysts and engineers love to place the blame elsewhere.