ISP automatic forums » Bresnan Online → Ping has doubled lately

my ping has doubled to around 100 to all servers. here is a tracert of google, what do you guys think? I play games and now every server I have a ping of at least 120... Support has done nothing to help OF COURSE.

1 1 ms

1 1 ms

1 1 ms

1 1 ms

They installed an upgraded CMTS in Bozeman last Tuesday. Since then my ping has doubled. I noticed that a tracert shows bozeman data being routed to billings, then to missoula, then back to billings. So their routing tables are messed up. I let the techs in Bozeman know but I have not heard back yet.

Oh, also, Bresnan 1st and 2nd tier support is worthless. I was complaining to them for months about poor latency and throughput during peak hours and they insisted my computer was at fault and wanted to send someone out (during non-peak hours). I finally talked to a senior cable guy in Bozeman, explained my problem, and he instantly said it wasn't anything on my end, but it was an over loaded CMTS in Bozeman. That is why they upgraded the CMTS last tuesday but they obviously have some issues to iron out.

@OP. You need to type Code with brackets around it.

My ping has also doubled lately as well. Gaming is rather tedious with the high ~500ms pings now.

Thought it was only slightly bad at first. Pings have been double normal over weekend, even in non-peak times.

Currently sitting at ~500 ms (800ms in games) ping to anywhere on the internet. It looks like via tracert that the problem happens at Level3 in Denver.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

Tracing route to www.l.google.com [74.125.155.99]
over a maximum of 30 hops:

2 9 ms 7 ms 7 ms host-10-39-64-1.bzm-mt.client.bresnan.net [10.39
.64.1]
3 9 ms 9 ms 7 ms bzmmt001hb6-GE-1-3-0-U0.int.bresnan.net [72.175.
111.56]
4 13 ms 13 ms 15 ms mslmt001hb7-GE-0-0-0-U438.int.bresnan.net [69.14
4.26.33]
5 15 ms 13 ms 13 ms mslmtfh1cr5-GE-3-0-1-U0.int.bresnan.net [72.175.
110.23]
6 58 ms 59 ms 57 ms host-72-175-111-20.bln-mt.client.bresnan.net [72
.175.111.20]
7 57 ms 57 ms 57 ms host-72-175-110-231.bln-mt.client.bresnan.net [7
2.175.110.231]
8 65 ms 65 ms 65 ms host-72-175-111-45.bln-mt.client.bresnan.net [72
.175.111.45]
9 67 ms 75 ms 68 ms host-72-175-110-229.bln-mt.client.bresnan.net [7
2.175.110.229]
10 82 ms 84 ms 82 ms te-9-3.car1.Denver1.Level3.net [4.53.10.97]
11 * 454 ms * ae-32-56.ebr2.Denver1.Level3.net [4.68.107.190]

12 371 ms 363 ms 362 ms ae-2-2.ebr2.Seattle1.Level3.net [4.69.132.53]
13 380 ms 390 ms 384 ms ae-2-52.edge1.Seattle3.Level3.net [4.68.105.44]

14 383 ms 388 ms 386 ms GOOGLE-INC.edge1.Seattle3.Level3.net [4.59.232.3
4]
15 418 ms 413 ms 415 ms 209.85.249.32
16 407 ms 413 ms 425 ms 216.239.46.208
17 436 ms 441 ms 446 ms

--------------------------------------------
Please complain to Bresnan... this shit needs to stop. I just really hope LightNex supplies service sometime soon... and it offers better service. Tired of messing with Bresnan's fail customer support and equipment. Their managers on the technician side are fairly decent though.

It's not Bresnan's fault that Level3 is having issues. If LightNex's backbone is through Level3, they'd have the same problems.

Other than Level3 having issues, your pings look rather good.

EDIT: No Level3 issues on my end.. Here's my traceroute:

I have been in contact with the techs in Bozeman regarding the high pings after the CMTS upgrade. They are routing traffic from Bozeman to Missoula then to Billings temporarily while they fix some other infrastructure (no idea what). This is why the pings are so bad out of Bozeman right now. They have an open ticket for me so I should hear back when it's fixed.

Hmm.. Shouldn't matter since both connections are terminating at 229 then handing off to Level3.
I went to ping 4.68.107.190 and didn't have an issue (55ms avg). Maybe it was a slight hiccup.

Yeah, I think the Level3 issue was an isolated issue. Bresnan can and does work with backbone providers on such issues so complaining to Bresnan can help if it is a continual problem, though, I am sure any resolution is out of Bresnan's hands directly.

The thing Bresnan can affect directly is their infrastructure. Which is why I have been on their case about the poor performance of their network during peak hours. Thankfully they appear to be doing something finally. I am getting tired of waiting tho. I hope they get it sorted out soon.

Grrrr... that Level3 node is acting up again.

C:\Users\username>tracert 99.198.108.171
 
Tracing route to server1.frauit.com [99.198.108.171]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    19 ms    20 ms    19 ms  host-10-39-64-1.bzm-mt.client.bresnan.net [10.39.64.1]
  3    19 ms    19 ms    34 ms  bzmmt001hb6-GE-1-3-0-U0.int.bresnan.net [72.175.111.56]
  4    25 ms    23 ms    24 ms  mslmt001hb7-GE-0-0-0-U438.int.bresnan.net [69.144.26.33]
  5    26 ms    26 ms    23 ms  mslmtfh1cr5-GE-3-0-1-U0.int.bresnan.net [72.175.110.23]
  6    71 ms    68 ms    70 ms  host-72-175-111-20.bln-mt.client.bresnan.net [72.175.111.20]
  7    70 ms    70 ms    70 ms  host-72-175-110-231.bln-mt.client.bresnan.net [72.175.110.231]
  8    78 ms    77 ms    77 ms  host-72-175-111-45.bln-mt.client.bresnan.net [72.175.111.45]
  9    81 ms    80 ms    86 ms  host-72-175-110-229.bln-mt.client.bresnan.net [72.175.110.229]
 10    92 ms    93 ms    93 ms  te-9-3.car1.Denver1.Level3.net [4.53.10.97]
 11   446 ms   445 ms   449 ms  ae-31-55.ebr1.Denver1.Level3.net [4.68.107.158]
 12   443 ms   447 ms   455 ms  ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
 13   453 ms   460 ms   467 ms  ae-1-60.edge2.Dallas3.Level3.net [4.69.145.12]
 14   464 ms   466 ms   470 ms  abovenet-levle3-xe.dallas3.level3.net [4.68.63.38]
 15   489 ms   460 ms   404 ms  xe-2-1-0.er1.ord2.us.above.net [64.125.30.62]
 16   104 ms   105 ms   104 ms  64.124.200.142.allocated.above.net [64.124.200.142]
 17   421 ms   418 ms   426 ms  asw-c16.r01.ord02.singlehop.net [67.212.171.138]
 18   441 ms   456 ms   460 ms  server1.frauit.com [99.198.108.171]
 
Trace complete.
 

C:\Users\username>ping -n 30 4.68.107.158
 
Pinging 4.68.107.158 with 32 bytes of data:
Reply from 4.68.107.158: bytes=32 time=461ms TTL=51
Reply from 4.68.107.158: bytes=32 time=466ms TTL=51
Reply from 4.68.107.158: bytes=32 time=482ms TTL=51
Reply from 4.68.107.158: bytes=32 time=459ms TTL=51
Reply from 4.68.107.158: bytes=32 time=423ms TTL=51
Reply from 4.68.107.158: bytes=32 time=428ms TTL=51
Reply from 4.68.107.158: bytes=32 time=439ms TTL=51
Reply from 4.68.107.158: bytes=32 time=445ms TTL=51
Reply from 4.68.107.158: bytes=32 time=457ms TTL=51
Reply from 4.68.107.158: bytes=32 time=464ms TTL=51
Reply from 4.68.107.158: bytes=32 time=467ms TTL=51
Reply from 4.68.107.158: bytes=32 time=483ms TTL=51
Reply from 4.68.107.158: bytes=32 time=458ms TTL=51
Reply from 4.68.107.158: bytes=32 time=436ms TTL=51
Reply from 4.68.107.158: bytes=32 time=456ms TTL=51
Reply from 4.68.107.158: bytes=32 time=444ms TTL=51
Reply from 4.68.107.158: bytes=32 time=466ms TTL=51
Reply from 4.68.107.158: bytes=32 time=464ms TTL=51
Reply from 4.68.107.158: bytes=32 time=471ms TTL=51
Reply from 4.68.107.158: bytes=32 time=483ms TTL=51
Reply from 4.68.107.158: bytes=32 time=455ms TTL=51
Reply from 4.68.107.158: bytes=32 time=433ms TTL=51
Reply from 4.68.107.158: bytes=32 time=424ms TTL=51
Reply from 4.68.107.158: bytes=32 time=445ms TTL=51
Reply from 4.68.107.158: bytes=32 time=459ms TTL=51
Reply from 4.68.107.158: bytes=32 time=484ms TTL=51
Reply from 4.68.107.158: bytes=32 time=456ms TTL=51
Reply from 4.68.107.158: bytes=32 time=468ms TTL=51
Reply from 4.68.107.158: bytes=32 time=446ms TTL=51
Reply from 4.68.107.158: bytes=32 time=472ms TTL=51
 
Ping statistics for 4.68.107.158:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 423ms, Maximum = 484ms, Average = 456ms
 

I thought I would update you on current happenings. Bresnan used to use AT&T routers to send traffic to seatle and Denver. Of late Bresnan appears to me to be doing a bunch of infrastructure changes to use it's own network throughout Montana and Wyoming to route data to Denver where they are then using Level3.net as a transit provider. This is evidenced by my routes previously taking four hops through Bresnan routers before hitting AT&T, and now taking some ten hops through Bresnan routers before hitting Level3 in denver.

I guess their goal is to use their own network and Level3 to improve overall latency. Or perphaps there is savings in it for them to use their own network to hit Denver. Or perhaps the AT&T network was acquired when Bresnan bought them out some years ago and it's become outdated.

In any case a few weeks ago they attempted to use the Bresnan network and Level3 routers. The problem was that the first hop from Bresnan to Level3 completely sucks (450 ms pings during peak hours). Bresnan had a support request in with Level3 but the issue went unfixed for so long that Bresnan gave up and routed traffic back through the AT&T network until Level3 can get their shit together. Will this eventually result in better overall latency? Only time will tell.

So, after Bresnan changed the route back one of their routers in missoula was hosed and another couple of days of suck ensued until they got that sorted out. Now latency seems to be alright, though, not great either. I can at least play tf2 and not get booted, but game play is still frustrating at times due to lag.

I am keeping my fingers crossed that in the end we will end up with lower latency over all. We will see.