dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2158
share rss forum feed

celticmoose

join:2010-05-29
Helena, MT

Helena Problems

I had been getting a solid 8mbps & 105 ping connection up until about 10 days ago, now I am lucky to get 3. I always used the Kalispell server on speedtest.net. My tracert shows horrible ms on some Level3 servers. I actually called Level3 and told them about it, and they fixed it the next day. Bresnan, however has done nothing to help my connection since I ping just fine in network. Thank goodness I get 8Mbps on that bresnan.com/speedtest site!

Now I ping over 200 to Kalispell. I don't care so much about the downstream, but I'm a gamer and I can hardly get any pings under 100 on Counter-Strike, or any server for that matter. MW2 for PS3 (which I tried wiring straigh from the modem itself) I can't get better than about 115 MS.

Has anyone else noticed any bad slowdowns in Helena lately? I'm out by Rossiter school.



junction

@qwest.net

I've seen the same problems in Casper. Pings of 70+ to Denver, in April they were in the 20s. Not to mention being routed to dallas & back after leaving bresnan's network in denver. Traffic returning from denver to me goes to sj & sf then seattle and then billings before coming back to casper. Bresnan won't even reply to the emails they asked for.



TSWYO
Premium
join:2003-05-03
Cheyenne, WY

I am in Cheyenne and seeing pings over 100ms to Denver.

I have equipment in two datacenters, both connect with Bresnan's upstream providers, and I am still seeing 100ms+



TSWYO
Premium
join:2003-05-03
Cheyenne, WY

Does this routing make sense? The trace was going to a DC in Denver.

3 9 ms 11 ms 12 ms chywy002dr5-GE-3-0-8-U0.int.bresnan.net [72.175.110.193]
4 14 ms 12 ms 11 ms chywy001cr5-XE-5-2-0-U0.int.bresnan.net [72.175.110.130]
5 40 ms 43 ms 18 ms gdjco002cr5-XE-5-3-0-U0.int.bresnan.net [72.175.111.44]
6 17 ms 19 ms 18 ms gdjco001cr5-XE-5-0-0-U0.int.bresnan.net [72.175.110.230]
7 64 ms 62 ms 71 ms mslmtfh1cr5-XE-5-3-0-U0.int.bresnan.net [72.175.111.21]
8 70 ms 65 ms 65 ms mslmt001cr5-XE-5-2-0-U0.int.bresnan.net [72.175.110.14]
9 78 ms 80 ms 77 ms seawafh1tr5-XE-5-3-0-U0.int.bresnan.net [72.175.111.23]



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

While it doesn't make sense, it might also depend on how their routing tables are weighted to determine the best way out. I am somewhat surprised to see that much latency on a 10Gb/s link all the way through (except for hop 3) though, even if it traverses that far.

After Bresnan's Seattle hop, where does it go? I was suspecting Level3 but Bresnan has a link with them through Cheyenne to Denver which would bypass the whole route IMO, unless they are doing something in Cheyenne right now...

This is why I said was suspecting above...This is Level3's BGP table for the subnet my IP in Butte is on from their Seattle location and also a partial trace which still goes to Bresnan's Denver location, so I don't think they actually have ties to them, though there are several other peering options in Seattle as well.

BGP routing table entry for 72.175.188.0/22
Paths: (2 available, best #2)
33588
AS-path translation: { ASN-Bresnan }
car1.Denver1 (metric 3627)
Origin IGP, metric 0, localpref 100, valid, internal
Community: North_America Lclprf_100 Level3_Customer United_States Denver 33588:11022
Originator: car1.Denver1

33588
AS-path translation: { ASN-Bresnan }
car1.Denver1 (metric 3627)
Origin IGP, metric 0, localpref 100, valid, internal, best
Community: North_America Lclprf_100 Level3_Customer United_States Denver 33588:11022
Originator: car1.Denver1

1 ae-32-52.ebr2.Seattle1.Level3.net (4.68.105.62) 12 msec 8 msec 0 msec
2 ae-2-2.ebr2.Denver1.Level3.net (4.69.132.54) 32 msec 28 msec 32 msec
3 ae-21-54.car1.Denver1.Level3.net (4.68.107.102) 28 msec
ae-21-56.car1.Denver1.Level3.net (4.68.107.166) 24 msec
ae-21-52.car1.Denver1.Level3.net (4.68.107.38) 28 msec
4 BRESNAN-COM.car1.Denver1.Level3.net (4.53.10.98) 28 msec 24 msec 28 msec
5 chywy001cr5-XE-5-3-0-U0.int.bresnan.net (72.175.110.228) [AS33588 {ASN-Bresnan}] 32 msec 32 msec 32 msec
6 gdjco002cr5-XE-5-3-0-U0.int.bresnan.net (72.175.111.44) [AS33588 {ASN-Bresnan}] 36 msec 36 msec 40 msec
7 gdjco001cr5-XE-5-0-0-U0.int.bresnan.net (72.175.110.230) [AS33588 {ASN-Bresnan}] 36 msec 36 msec 40 msec
8 mslmtfh1cr5-XE-5-3-0-U0.int.bresnan.net (72.175.111.21) [AS33588 {ASN-Bresnan}] 80 msec 84 msec 80 msec
9 mslmt001hb7-GE-1-0-1-U0.int.bresnan.net (72.175.110.22) [AS33588 {ASN-Bresnan}] 84 msec 84 msec 88 msec
10 hlnmt002hb7-GE-0-1-0-U432.int.bresnan.net (69.144.26.98) [AS33588 {ASN-Bresnan}] 84 msec 100 msec 84 msec
11 butmtfh2hb6-SO-0-3-0-U0.int.bresnan.net (69.144.94.162) [AS33588 {ASN-Bresnan}] 68 msec 72 msec 68 msec


What gets interesting is Bresnan's route from Cheyenne to Butte which is lining up with the strange route you saw going to Denver.



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

1 edit

FWIW here is a trace from Level3's Denver router on May 15th and this morning. Notice how much more latency there is now compared to not more than a month ago because it dips down to Grand Junction, CO instead of just going North to Billings. Though even before it bounces from Billings to Casper back to Billings then on to Butte so even then there was some strange routing going on.

May 15th:

1 BRESNAN-COM.car1.Denver1.Level3.net (4.53.10.98) 0 msec 0 msec 0 msec
2 chywy001cr5-XE-5-3-0-U0.int.bresnan.net (72.175.110.228) [AS33588 {BRESNAN-AS}] 4 msec 0 msec 0 msec
3 chywyat1cr5-XE-5-1-0-U0.int.bresnan.net (72.175.110.129) [AS33588 {BRESNAN-AS}] 4 msec 4 msec 4 msec
4 host-72-175-110-224.bln-mt.client.bresnan.net (72.175.110.224) [AS33588 {BRESNAN-AS}] 8 msec 4 msec 8 msec
5 cspwy002CR5-XE-5-0-0-U0.int.bresnan.net (72.175.110.95) [AS33588 {BRESNAN-AS}] 8 msec 8 msec 8 msec
6 host-72-175-110-120.bln-mt.client.bresnan.net (72.175.110.120) [AS33588 {BRESNAN-AS}] 12 msec 16 msec 12 msec
7 host-72-175-110-119.bln-mt.client.bresnan.net (72.175.110.119) [AS33588 {BRESNAN-AS}] 12 msec 16 msec 12 msec
8 butmtfh1hb6-GE-1-3-0-U0.int.bresnan.net (72.175.110.35) [AS33588 {BRESNAN-AS}] 20 msec 20 msec 20 msec
9 butmt002cm1-GE-0-2-U96.int.bresnan.net (69.144.94.100) [AS33588 {BRESNAN-AS}] 24 msec 20 msec 20 msec


This morning

1 BRESNAN-COM.car1.Denver1.Level3.net (4.53.10.98) 0 msec 0 msec 0 msec
2 chywy001cr5-XE-5-3-0-U0.int.bresnan.net (72.175.110.228) [AS33588 {ASN-Bresnan}] 4 msec 4 msec 4 msec
3 gdjco002cr5-XE-5-3-0-U0.int.bresnan.net (72.175.111.44) [AS33588 {ASN-Bresnan}] 12 msec 12 msec 12 msec
4 gdjco001cr5-XE-5-0-0-U0.int.bresnan.net (72.175.110.230) [AS33588 {ASN-Bresnan}] 8 msec 12 msec 12 msec
5 mslmtfh1cr5-XE-5-3-0-U0.int.bresnan.net (72.175.111.21) [AS33588 {ASN-Bresnan}] 56 msec 56 msec 56 msec
6 mslmt001hb7-GE-1-0-1-U0.int.bresnan.net (72.175.110.22) [AS33588 {ASN-Bresnan}] 60 msec 56 msec 56 msec
7 hlnmt002hb7-GE-0-1-0-U432.int.bresnan.net (69.144.26.98) [AS33588 {ASN-Bresnan}] 60 msec 60 msec 104 msec
8 butmtfh2hb6-SO-0-3-0-U0.int.bresnan.net (69.144.94.162) [AS33588 {ASN-Bresnan}] 40 msec 52 msec 64 msec
9 butmtfh1hb6-GE-0-0-0-U96.int.bresnan.net (69.144.94.97) [AS33588 {ASN-Bresnan}] 44 msec 52 msec 44 msec
10 butmt002cm1-GE-0-1-U120.int.bresnan.net (69.144.94.124) [AS33588 {ASN-Bresnan}] 44 msec 40 msec 40 msec



TSWYO
Premium
join:2003-05-03
Cheyenne, WY

1 edit
reply to koolkid1563

I'll update this when I get home, but the first hop after Seatle is AT&T.

First two hops is my network

3 12 ms 15 ms 11 ms chywy002dr5-GE-3-0-8-U0.int.bresnan.net [72.175.10.193]
4 18 ms 9 ms 12 ms chywy001cr5-XE-5-2-0-U0.int.bresnan.net [72.175.10.130]
5 20 ms 18 ms 19 ms gdjco002cr5-XE-5-3-0-U0.int.bresnan.net [72.175.11.44]
6 20 ms 18 ms 28 ms gdjco001cr5-XE-5-0-0-U0.int.bresnan.net [72.175.10.230]
7 65 ms 72 ms 92 ms mslmtfh1cr5-XE-5-3-0-U0.int.bresnan.net [72.175.11.21]
8 66 ms 64 ms 70 ms mslmt001cr5-XE-5-2-0-U0.int.bresnan.net [72.175.10.14]
9 78 ms 77 ms 80 ms seawafh1tr5-XE-5-3-0-U0.int.bresnan.net [72.175.11.23]
10 79 ms 77 ms 76 ms 12.90.77.21
11 121 ms 126 ms 102 ms cr1.st6wa.ip.att.net [12.123.46.6]
12 110 ms 101 ms 102 ms cr2.sffca.ip.att.net [12.122.31.194]
13 100 ms 102 ms 161 ms ggr3.cgcil.ip.att.net [12.122.86.201]
14 110 ms 101 ms 101 ms ae0.sjc12.ip4.tinet.net [77.67.78.93]
15 138 ms 143 ms 140 ms xe-1-2-0.den10.ip4.tinet.net [89.149.184.82]

The next hop is the DC