Re: Terrible ping when connecting to server in Chicago in Shaw

Re: Terrible ping when connecting to server in Chicago in Shaw http://www.dslreports.com/forum/r20307391 en Thu, 08 Jan 2009 09:16:02 EDT Thu, 08 Jan 2009 09:16:02 EDT Re: Terrible ping when connecting to server in Chicago http://www.dslreports.com/forum/remark,20376007 dzurawell : My internet has been awful during peak hours for about the last 5 months i get packetloss from about 5pm-10pm the one thing i would do if possible would be to move your server to new york. When we had a Chicago gameserver I usually pinged about 90-100 to it but once we switched to a new york server (with the same company mind you) my ping could sometimes get as low as 60.]]> http://www.dslreports.com/forum/remark,20376007 Wed, 23 Apr 2008 18:34:38 EDT Re: Terrible ping when connecting to server in Chicago http://www.dslreports.com/forum/remark,20317255 Shifty :

said by PanicPooper :

Before signing up with teksavvy be aware that they are in a fight right now with bell who provides there lines . Bell is currently rolling out full traffic shaping , so if you only are playing games this probably won't affect you but if you download a torrent it will.

Keep in mind that I'm in Alberta, so it'll be Telus lines I'm running off rather than Bell.

I'm not big into torrents anyway so that's not a big deal.

Finally got an email response from Shaw (a week later) but it seems it is the generic response that my query has been forwarded to the operations dept.

Shaw was doing work on the lines yesterday so I had hoped things would be better. Alas that hop from Cgy to Van still results in a ping jump from ~30ms to ~150ms]]> http://www.dslreports.com/forum/remark,20317255 Fri, 11 Apr 2008 10:09:45 EDT Re: Terrible ping when connecting to server in Chicago http://www.dslreports.com/forum/remark,20316570 qec99 : Our server is in Texas and even when my connection is as good as it gets I ping between 115-140. Granted, I am in Western Canada but we just got a new clan member that lives in Trinidad (and I don't mean Trinidad, Texas) and he pings in the low 30's all the time. I guess my routing sucks as much as my connection.

I will say it's been back to as normal as it gets since that second night after they said they fixed it.

Hopefully it will get a bit better for me when they finally get us upgraded to Docsis out here.]]> http://www.dslreports.com/forum/remark,20316570 Fri, 11 Apr 2008 01:24:21 EDT Re: Terrible ping when connecting to server in Chicago http://www.dslreports.com/forum/remark,20307391 anon : Before signing up with teksavvy be aware that they are in a fight right now with bell who provides there lines . Bell is currently rolling out full traffic shaping , so if you only are playing games this probably won't affect you but if you download a torrent it will. ]]> http://www.dslreports.com/forum/remark,20307391 Wed, 09 Apr 2008 10:39:55 EDT Re: Terrible ping when connecting to server in Chicago http://www.dslreports.com/forum/remark,20307257 Shifty : Yeah, I've given up on waiting for Shaw to resolve the issue.

Ping has deteriorated to the point where I'm pinging 250+ to that Chicago server. Even got over 300 at one point which is ridiculous when clan members from Norway, Germany etc ping around 120.

Phoned teksavvy & signed up with them so as soon as that modem arrives I'll be hooking it up and hopefully enjoying much more reasonable pings.

Will post back when I've made the change]]> http://www.dslreports.com/forum/remark,20307257 Wed, 09 Apr 2008 10:18:18 EDT Re: Terrible ping when connecting to server in Chicago http://www.dslreports.com/forum/remark,20306287 qec99 : Here's an update on mine. Got an email yesterday morning telling me the issue was resolved and thanks for my patience. Finally! Last night I was able to play COD 4 during prime time with my ping barely over 125.

Too bad it didn't last. Prime time ping to our server tonight was 300-400 and my download speed was again less than 1mb. Did some tracerts to our server, speakeasy, google etc. Same #2 hop causing the same ol' problem. gg Shaw.]]> http://www.dslreports.com/forum/remark,20306287 Wed, 09 Apr 2008 01:32:42 EDT Re: Terrible ping when connecting to server in Chicago http://www.dslreports.com/forum/remark,20291567 qec99 : It just gets very frustrating when the only time I have a good connection is when I'm at work or asleep. That and it's been an on again/off again problem for over 2 years. This is the second or third time it's lasted this long. Going on a month now. Other times it clears up after a few days to a couple weeks.]]> http://www.dslreports.com/forum/remark,20291567 Sun, 06 Apr 2008 12:02:51 EDT Re: Terrible ping when connecting to server in Chicago http://www.dslreports.com/forum/remark,20288206 AnonShawUser : unfortunately, qec, that kind of speed is generous, compared to what I've been under between 3-10pm, for a week and a half. And I'm right outside Downtown Calgary, so I'm close enough to be on their direct business nodes.

But, don't worry too much. They're training up a whole slew of new service techs and installers, so hopefully they'll be able to get the node splits done faster.]]> http://www.dslreports.com/forum/remark,20288206 Sat, 05 Apr 2008 15:44:27 EDT Re: Terrible ping when connecting to server in Chicago http://www.dslreports.com/forum/remark,20285444 qec99 : Good luck. I've been having the same trouble for weeks over a bad hop in Calgary. Got a ticket number assigned but it has not speeded anything up. I guess they just ignore us.
Attached is my download speed at 8:00pm

Tracing route to www.speakeasy.net [69.17.117.156]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 24 ms 23 ms 24 ms 24.66.132.1
3 167 ms 151 ms 146 ms rd1so-ge3-0-0-6.cg.shawcable.net [64.59.132.131]

4 138 ms 146 ms 140 ms rc1so-ge5-0-0.cg.shawcable.net [66.163.71.77]
5 161 ms 164 ms 165 ms rc1wh-pos12-0.vc.shawcable.net [66.163.76.10]
6 191 ms 160 ms 152 ms rc2wt-pos7-0.wa.shawcable.net [66.163.76.154]
7 140 ms 141 ms 135 ms paix.ge-0-2-0.cr1.sea1.speakeasy.net [198.32.134
.49]
8 121 ms 123 ms 130 ms 151.ge-1-3-0.sr1.sea5.speakeasy.net [69.17.82.50
]
9 147 ms 141 ms 137 ms www.speakeasy.net [69.17.117.156]

Trace complete.

]]> http://www.dslreports.com/forum/remark,20285444 Fri, 04 Apr 2008 23:06:11 EDT Terrible ping when connecting to server in Chicago http://www.dslreports.com/forum/remark,20281559 Shifty : Hopefully someone can help me out here as the people at Shaw I spoke with claimed the problem is outside the shaw network so not something they can fix.

Our clan servers are located in Chicago and all have the address 8.9.4.xx
In-game I'm having to deal with pings in the 200+ range, which makes playing FPS games near impossible. Clan members in Europe have lower pings than me!

I can connect to other servers in Chicago and I get 70-100 ping.

I ran ping plotter to compare paths and got some interesting results (see table at end - sorry the formatting is a little messed up)

Looking at those tables it's obvious that the problem lies with hop4 which connects to rc1wh-pos3-0-0.vc.shawcable.net [66.163.77.197]

Not sure how to trace it, but the name vs.shawcable.net would see to indicate that it is within the Shaw system would it not?

My hope is that Shaw can force my connection to take the path shown in the second set (Winnipeg-Illinois-Chicago)

Any suggestions or thoughts as to how I might accomplish this? I'm about ready to switch to the dreaded Telus as gaming is impossible with the ping I'm getting right now.

Target Name: N/A         IP: 8.9.4.75  Date/Time: 03/04/2008 10:17:01 PM  1   27 ms  N/A      21 ms   17 ms  [24.64.18.1] 2   36 ms  N/A      18 ms   21 ms  rd1he-ge3-0-3.rd.shawcable.net [64.59.133.129] 3   32 ms  N/A      24 ms   24 ms  rc1so-atm0-0-5.cg.shawcable.net [66.163.71.145] 4  166 ms  N/A     153 ms  150 ms  rc1wh-pos3-0-0.vc.shawcable.net [66.163.77.197] 5  169 ms  N/A     154 ms  151 ms  rc1wt-pos1-0-0.wa.shawcable.net [66.163.76.2] 6  165 ms  N/A     166 ms  156 ms  te-3-4.car3.Seattle1.Level3.net [4.71.152.25] 7  164 ms  N/A     166 ms  152 ms  ae-32-54.ebr2.Seattle1.Level3.net [4.68.105.126] 8  186 ms  N/A     187 ms  185 ms  ae-2.ebr2.Denver1.Level3.net [4.69.132.54] 9   73 ms  N/A      87 ms   86 ms  ae-3.ebr3.Chicago1.Level3.net [4.69.132.62]10  182 ms  N/A     180 ms  185 ms  ae-78.ebr2.Chicago1.Level3.net [4.69.134.61]11   73 ms  N/A      73 ms   77 ms  ae-24-54.car4.Chicago1.Level3.net [4.68.101.104]12   76 ms  N/A      77 ms   75 ms  [4.79.66.146]13  173 ms  N/A     189 ms  186 ms  [8.9.4.75] Ping statistics for 8.9.4.75Packets: Sent = 3, Received = 3, Lost = 0 (0.0%)Round Trip Times: Minimum = 173ms, Maximum = 189ms, Average = 182ms Target Name: N/A         IP: 8.9.4.75  Date/Time: 03/04/2008 10:17:01 PM to 03/04/2008 10:18:17 PM  1   27 ms  N/A      21 ms   17 ms  N/A      20 ms   20 ms  [24.64.18.1] 2   36 ms  N/A      18 ms   21 ms  N/A      21 ms   21 ms  rd1he-ge3-0-3.rd.shawcable.net [64.59.133.129] 3   32 ms  N/A      24 ms   24 ms  N/A      24 ms   20 ms  rc1so-atm0-0-5.cg.shawcable.net [66.163.71.145] 4  166 ms  N/A     153 ms  150 ms  N/A      62 ms  111 ms  rc1wh-pos3-0-0.vc.shawcable.net [66.163.77.197] 5  169 ms  N/A     154 ms  151 ms  N/A      55 ms  120 ms  rc1wt-pos1-0-0.wa.shawcable.net [66.163.76.2] 6  165 ms  N/A     166 ms  156 ms  N/A      52 ms  118 ms  te-3-4.car3.Seattle1.Level3.net [4.71.152.25] 7  164 ms  N/A     166 ms  152 ms  N/A      67 ms  116 ms  ae-32-54.ebr2.Seattle1.Level3.net [4.68.105.126] 8  186 ms  N/A     187 ms  185 ms  N/A      87 ms  152 ms  ae-2.ebr2.Denver1.Level3.net [4.69.132.54] 9   73 ms  N/A      87 ms   86 ms  N/A      87 ms   80 ms  ae-3.ebr3.Chicago1.Level3.net [4.69.132.62]10  182 ms  N/A     180 ms  185 ms  N/A      86 ms  162 ms  ae-78.ebr2.Chicago1.Level3.net [4.69.134.61]11   73 ms  N/A      73 ms   77 ms  N/A      74 ms   76 ms  ae-24-54.car4.Chicago1.Level3.net [4.68.101.104]12   76 ms  N/A      77 ms   75 ms  N/A      74 ms   72 ms  [4.79.66.146]13  173 ms  N/A     189 ms  186 ms  N/A      80 ms  161 ms  [8.9.4.75] Ping statistics for 8.9.4.75Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)Round Trip Times: Minimum = 80ms, Maximum = 189ms, Average = 157ms Target Name: N/A         IP: 8.9.4.75  Date/Time: 03/04/2008 10:21:21 PM  1   17 ms  [24.64.18.1] 2   18 ms  rd1he-ge3-0-3.rd.shawcable.net [64.59.133.129] 3   33 ms  rc1so-atm0-0-5.cg.shawcable.net [66.163.71.145] 4  122 ms  rc1wh-pos3-0-0.vc.shawcable.net [66.163.77.197] 5  122 ms  rc1wt-pos1-0-0.wa.shawcable.net [66.163.76.2] 6  121 ms  te-3-4.car3.Seattle1.Level3.net [4.71.152.25] 7  126 ms  ae-32-54.ebr2.Seattle1.Level3.net [4.68.105.126] 8  160 ms  ae-2.ebr2.Denver1.Level3.net [4.69.132.54] 9   79 ms  ae-3.ebr3.Chicago1.Level3.net [4.69.132.62]10  162 ms  ae-78.ebr2.Chicago1.Level3.net [4.69.134.61]11   78 ms  ae-24-54.car4.Chicago1.Level3.net [4.68.101.104]12   89 ms  [4.79.66.146]13  161 ms  [8.9.4.75] Ping statistics for 8.9.4.75Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)Round Trip Times: Minimum = 161ms, Maximum = 161ms, Average = 161ms Good connection (also a server in Chicago) Target Name: .         IP: 74.63.68.166  Date/Time: 03/04/2008 10:18:55 PM  1   36 ms  [24.64.18.1] 2   19 ms  rd1he-ge3-0-3.rd.shawcable.net [64.59.133.129] 3   26 ms  rc1no-atm1-0-2.cg.shawcable.net [66.163.76.249] 4   25 ms  rc1so-pos15-0.cg.shawcable.net [66.163.77.9] 5   40 ms  rc2nr-pos11-0-0.wp.shawcable.net [66.163.77.158] 6  218 ms  rc2ch-pos7-0.il.shawcable.net [66.163.76.174] 7  157 ms  rd2ec-pos1-0.il.shawcable.net [66.163.65.14] 8   57 ms  cr1-eqix-peer.chg003.internap.net [206.223.119.103] 9  147 ms  core1.chg.inappnet-42.cr1.chg003.internap.net [66.79.150.130]10   57 ms  border5.pc2-bbnet2.chg.pnap.net [64.94.32.74]11   76 ms  66.90.127.205 [66.90.127.205]12  143 ms  66.90.127.138 [66.90.127.138]13   76 ms  . [74.63.68.166] Ping statistics for .Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)Round Trip Times: Minimum = 76ms, Maximum = 76ms, Average = 76ms Target Name: .         IP: 74.63.68.166  Date/Time: 03/04/2008 10:20:37 PM  1   18 ms  [24.64.18.1] 2   22 ms  rd1he-ge3-0-3.rd.shawcable.net [64.59.133.129] 3   31 ms  rc1no-atm1-0-2.cg.shawcable.net [66.163.76.249] 4   38 ms  rc1so-pos15-0.cg.shawcable.net [66.163.77.9] 5   53 ms  rc2nr-pos11-0-0.wp.shawcable.net [66.163.77.158] 6   70 ms  rc2ch-pos7-0.il.shawcable.net [66.163.76.174] 7  171 ms  rd2ec-pos1-0.il.shawcable.net [66.163.65.14] 8   61 ms  cr1-eqix-peer.chg003.internap.net [206.223.119.103] 9  173 ms  core1.chg.inappnet-42.cr1.chg003.internap.net [66.79.150.130]10   61 ms  border5.pc2-bbnet2.chg.pnap.net [64.94.32.74]11   71 ms  66.90.127.205 [66.90.127.205]12  160 ms  66.90.127.138 [66.90.127.138]13   71 ms  . [74.63.68.166] Ping statistics for .Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)Round Trip Times: Minimum = 71ms, Maximum = 71ms, Average = 71ms

]]> http://www.dslreports.com/forum/remark,20281559 Fri, 04 Apr 2008 10:57:20 EDT