World of Warcraft®

15 52 ms 47 ms 49 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
16 * * * Request timed out.

same point that my trace is timing out

ISP: SHAW
Kamloops, BC

Through reloading the game I get 10-15 mins of slightly laggy gameplay then the game just stalls. If I leave the game in that state it takes another 10-15mins to kick me from WoW.

Only other time I have come across something like this is when I had issues with ventrilo packets being delayed because this ISP used to treat it as a P2P program. Those delays would be 10 mins ish and then whatever I said would go through fine. That only ever happened back in TBC.

No my friend with shaw is on KJ also and is he going through 2 routers! lives 5-10 min away from my house.

I can call shaw if you guys want.. I really rather not due to my low daytime minute plan on my phone but If it means getting this BS fixed faster I don't mind. anything anybody would like me to ask them!?!

Like I said. I am on Shaw in Vancouver Area with no issues on KJ. This seems to be limited to certain customers, possibly with a particular model of modem.

I am using the Shaw Cisco DPC3825 Router/Modem

sunshine coast BC, only been a problem since Tuesday. What changed?

Ignore any timeouts after mdf002c7613r0002-gig-10-1.phx1.attens.net [63.241.130.206]

Or anywhere after attens.net on a tracert. This is working as intended

Would like to see some input on the blue side for this if they know of anything that is going on here yet?

Ignore any timeouts after mdf002c7613r0002-gig-10-1.phx1.attens.net [63.241.130.206]

Or anywhere after attens.net on a tracert. This is working as intended

The latency spikes seem to start when the path tries to get through an ATT database. For most people with this problem, it looks like this on their route (taken from fist post):

8 32 ms 23 ms 35 ms 192.205.36.153
9 82 ms 79 ms 67 ms cr1.st6wa.ip.att.net [12.122.146.50]
10 101 ms 70 ms 66 ms cr2.sffca.ip.att.net [12.122.31.194]
11 68 ms 81 ms 71 ms cr1.sffca.ip.att.net [12.122.3.69]
12 66 ms 66 ms 159 ms cr1.la2ca.ip.att.net [12.122.3.122]
13 70 ms 67 ms 79 ms cr2.phmaz.ip.att.net [12.122.31.190]

But it does reach the end, otherwise we would have a bigger problem. Hopefully blizzard is fixing this. It's just the fact that they don't like to respond to threads like these for some reason.

It's nothing to do with my modem I have talked to shaw again today and he said everything is perfect with my modem. He also was nice enough to add another ip address for free to my account. not sure what it will do but maybe help who knows..

Fixed my problem it was my dad's computer seeding torrents the whole entire time wow i feel so dumb :( hope you all figure your problem out gl!

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

C:\Windows\system32>tracert 63.240.161.189

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.254
2 37 ms 36 ms 35 ms d198-53-0-1.abhsia.telus.net [198.53.0.1]
3 37 ms 37 ms 36 ms 96.1.176.169
4 69 ms 69 ms 77 ms chcgildtgr00.bb.telus.com [154.11.11.30]
5 * * * Request timed out.
6 82 ms 83 ms 82 ms 192.205.37.173
7 98 ms 96 ms 94 ms cr1.cgcil.ip.att.net [12.122.84.54]
8 92 ms 184 ms 109 ms gar2.clboh.ip.att.net [12.122.133.197]
9 93 ms 84 ms 85 ms 12.122.251.22
10 * 93 ms 93 ms 63.240.130.210
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Windows\system32>
Same issue, Im with telus and I live in central Alberta. I can't even play anymore!

I also have been having this issue for the past week or so.

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.254
2 19 ms 19 ms 19 ms 10.246.192.1
3 20 ms 20 ms 20 ms 96.1.253.174
4 27 ms 30 ms 26 ms 209.121.73.186
5 * * * Request timed out.
6 31 ms 30 ms 30 ms MTLXPQVVBR02.core.tac.net [204.225.245.137]
7 30 ms 31 ms 41 ms te7-4.ccr02.sea02.atlas.cogentco.com [154.54.10.45]
8 102 ms 215 ms 211 ms te4-8.ccr02.sea01.atlas.cogentco.com [154.54.81.113]
9 51 ms 52 ms 52 ms te0-7-0-4.ccr21.slc01.atlas.cogentco.com [154.54.80.10]
10 250 ms 217 ms 198 ms te8-1.ccr01.den01.atlas.cogentco.com [154.54.82.218]
11 79 ms 79 ms 79 ms te0-4-0-2.ccr22.mci01.atlas.cogentco.com [154.54.45.54]
12 79 ms 79 ms 79 ms te0-5-0-4.ccr22.ord01.atlas.cogentco.com [154.54.45.150]
13 79 ms 79 ms 79 ms te0-6-0-0.ccr22.ord03.atlas.cogentco.com [154.54.29.22]
14 92 ms 92 ms 92 ms att.ord03.atlas.cogentco.com [154.54.12.86]
15 96 ms 95 ms 95 ms cr2.cgcil.ip.att.net [12.122.84.94]
16 92 ms * 92 ms gar2.clboh.ip.att.net [12.122.133.197]
17 94 ms 93 ms 93 ms 12.122.251.50
18 94 ms 94 ms 94 ms 63.240.130.210
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

I am having such bad lag spikes, I cannot Arena, BG or do any sort of PvP. I have never had this connection issue before. I am in Bleeding Hollow server. I also live on the West coast in British Columbia.

What do we do now to fix this is all I really want to know. I am in Surrey, BC and lag is crazy Telus says it's Blizz and Blizz says it's our internet provider. I play on Rampage battlegroup but had no problems before now.

It's not Blizzard and it's not Shaw or Telus it is the broken backbone somewhere around Wichita, Kansas. The same problem that is causing hundreds of posts on this forum. Until Cogentco and AT&T get their act together we will be lagging. Both Shaw and Telus run the same path to certain Blizzard Battlegroup servers.

Here is a 8.5 hour WinMTR trace from last Sunday - the packet loss is really bad.

Sent 30,000 packets - once a second. Received less than 26,000

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.254 - 0 | 30005 | 30005 | 0 | 0 | 4 | 0 |
| -191-128-1.abhsia.telus.net - 0 | 29994 | 29994 | 7 | 9 | 218 | 7 |
| 154.11.197.66 - 0 | 29981 | 29981 | 6 | 8 | 150 | 7 |
| chcgildtgr00.bb.telus.com - 0 | 29984 | 29984 | 36 | 41 | 229 | 37 |
| 173.182.200.2 - 1 | 29592 | 29489 | 44 | 46 | 213 | 45 |
|1.ccr22.ord01.atlas.cogentco.com - 1 | 29528 | 29410 | 37 | 38 | 193 | 38 |
|3.ccr22.mci01.atlas.cogentco.com - 1 | 29524 | 29404 | 49 | 50 | 241 | 50 |
|4.ccr22.dfw01.atlas.cogentco.com - 1 | 29520 | 29399 | 59 | 60 | 262 | 60 |
|-1.ccr22.iah01.atlas.cogentco.com - 1 | 29578 | 29472 | 72 | 74 | 257 | 72 |
|-5.ccr22.lax01.atlas.cogentco.com - 1 | 29576 | 29469 | 79 | 80 | 212 | 79 |
|-4.ccr22.lax05.atlas.cogentco.com - 1 | 29548 | 29435 | 82 | 84 | 221 | 84 |
| 192.205.35.5 - 5 | 25688 | 24609 | 83 | 128 | 317 | 135 |
| cr2.la2ca.ip.att.net - 5 | 25753 | 24690 | 76 | 119 | 281 | 79 |
| gar20.la2ca.ip.att.net - 5 | 25765 | 24705 | 76 | 127 | 382 | 146 |
| 12.122.251.190 - 5 | 25753 | 24690 | 76 | 123 | 510 | 77 |
| 206.16.68.46 - 4 | 25873 | 24840 | 80 | 125 | 492 | 81 |
| No response from host - 100 | 6001 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 6001 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 6001 | 0 | 0 | 0 | 0 | 0 |
| ________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

This is where the big internet mud bog is:

|-4.ccr22.lax05.atlas.cogentco.com - 1 | 29548 | 29435 | 82 | 84 | 221 | 84 |
| 192.205.35.5 - 5 | 25688 | 24609 | 83 | 128 | 317 | 135 |

Almost 4000 packets lost right here.

It is the handoff between Cogentco and AT&T somewhere near Wichita, Kansas.

(recorded near Edmonton on a Dedicated ADSL line - POT splitter - I could hit the main Telus switch station with a baseball)

I sure hope this gets sorted out. this is unbearable

Same here, I'm in near Chilliwack B.C, having insane lag spikes making the game un-enjoyable and extremely frustrating trying to heal and then randomly having like a 4 second wait inbetween any actions. I just wish Blizz would give some form of an update for Canadians, they've made it clear that they're looking into the American COX problem but no update on Canadian problem. ISP says the problem is on Blizz's end and Blizz is saying it's ISP. Fix it, this is ridiculous

I'm in Surrey, BC, Canada with Telus and having the same issue

Having the same problem in Chilliwack. I can play for about 5-10 minutes, then everything freezes and I get disconnected.

Richmond BC reporting in

Having this problem here as well