High latency, trace report included.

[animaxa]

Hello, about a week ago I have been having trouble with WoW (at peak hours) with latency, I log on and my latency jumps to 400-500. I have talked to my ISP and they have told me its not them, I talked to blizzard and they told me its not them so heres where I stand, completely lost. I have read allot of issues with this same problem on the real WoW tech forums and people seem to have trouble as well. I am living in Canada and I'm using the ISP Rogers Digital Cable.
I am using a Intel(R) Pro/100 VE Network Connection, I am also using a D-LINK 524 with my ports opened to blizzard, I have also tried plugging into my internet directly but still the same latency trouble.


Tracing route to 206.17.111.37 over a maximum of 30 hops



1 7 ms 6 ms 5 ms 10.43.160.1

2 6 ms 6 ms 5 ms gw03.slnt.phub.net.cable.rogers.com [66.185.90.145]

3 7 ms 6 ms 5 ms gw01.slnt.phub.net.cable.rogers.com [66.185.93.201]

4 11 ms 11 ms 11 ms so-5-0-0.gw02.bloor.phub.net.cable.rogers.com [66.185.81.77]

5 12 ms 13 ms 13 ms so-1-0-0.gw02.wlfdle.phub.net.cable.rogers.com [66.185.80.45]

6 28 ms * * pos-1-0-0.igw01.vaash.phub.net.cable.rogers.com [66.185.80.190]

7 36 ms 27 ms 27 ms POS2-1.ar2.DCA3.gblx.net [208.51.239.201]

8 180 ms 174 ms 171 ms 192.205.33.33

9 48 ms 162 ms 163 ms tbr1.wswdc.ip.att.net [12.122.84.158]

10 40 ms 40 ms 38 ms cr2.wswdc.ip.att.net [12.122.16.37]

11 190 ms 191 ms * cr2.n54ny.ip.att.net [12.122.3.37]

12 39 ms 43 ms 40 ms tbr2.n54ny.ip.att.net [12.122.16.222]

13 259 ms 248 ms 240 ms tbr1.cb1ma.ip.att.net [12.122.10.21]

14 * 248 ms 246 ms 12.127.5.109

15 * 197 ms 191 ms 12-122-254-14.attens.net [12.122.254.14]

16 245 ms 252 ms 240 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.130.0.174]

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 *


Anyways , i hope you guys can be a bigger help then Blizzard!

Thanks

Animaxa

[animaxa]

here is a trace report from tonight:




Tracing route to 206.17.111.37 over a maximum of 30 hops



1 7 ms 5 ms 7 ms 10.43.160.1

2 7 ms 7 ms 6 ms gw03.slnt.phub.net.cable.rogers.com [66.185.90.145]

3 7 ms 5 ms 5 ms gw01.slnt.phub.net.cable.rogers.com [66.185.93.193]

4 15 ms 11 ms 12 ms so-5-0-0.gw02.bloor.phub.net.cable.rogers.com [66.185.81.77]

5 12 ms 13 ms 14 ms so-1-0-0.gw02.wlfdle.phub.net.cable.rogers.com [66.185.80.45]

6 26 ms 27 ms 27 ms pos-1-0-0.igw01.vaash.phub.net.cable.rogers.com [66.185.80.190]

7 32 ms 37 ms 27 ms POS2-1.ar2.DCA3.gblx.net [208.51.239.201]

8 286 ms 275 ms 262 ms 192.205.33.33

9 305 ms 333 ms 303 ms tbr2.wswdc.ip.att.net [12.122.84.202]

10 248 ms 247 ms 274 ms cr2.wswdc.ip.att.net [12.122.16.77]

11 289 ms 289 ms 277 ms cr2.n54ny.ip.att.net [12.122.3.37]

12 41 ms 40 ms 39 ms tbr2.n54ny.ip.att.net [12.122.16.222]

13 270 ms 294 ms 287 ms tbr1.cb1ma.ip.att.net [12.122.10.21]

14 298 ms 300 ms 324 ms 12.127.5.109

15 298 ms 279 ms 240 ms 12-122-254-14.attens.net [12.122.254.14]

16 296 ms 290 ms 281 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.130.0.174]

17 * * * Request timed out.

18 * *

[NtherBlast]

Yes also been having his problem from last sunday around 6pm est my latency goes up to 400-800. I also have rogers and live in Ontario I called them they said everything is fine and this high latency is only for WoW lots of others also have this problem that I have seen on the WoW forums here is my tracert.




Tracing route to us.logon.worldofwarcraft.com [12.129.232.114]

over a maximum of 30 hops:



1 <1 ms <1 ms <1 ms 192.168.1.1

2 8 ms 7 ms 21 ms 10.7.96.1

3 * * * Request timed out.

4 9 ms 9 ms 8 ms gi-7-0-3.gw01.etob.phub.net.cable.rogers.com [24.153.7.209]

5 9 ms 10 ms 11 ms so-4-0-0.gw02.wlfdle.phub.net.cable.rogers.com [66.185.82.97]

6 25 ms 24 ms 24 ms pos-0-0-0.igw01.vaash.phub.net.cable.rogers.com [24.153.5.230]

7 43 ms 44 ms 47 ms POS2-1.ar2.DCA3.gblx.net [208.51.239.201]

8 25 ms 27 ms 25 ms 192.205.33.33

9 322 ms 320 ms 339 ms tbr1.wswdc.ip.att.net [12.122.80.98]

10 358 ms 340 ms 336 ms tbr1.sl9mo.ip.att.net [12.122.10.30]

11 344 ms 354 ms 353 ms tbr2.sl9mo.ip.att.net [12.122.9.142]

12 325 ms 320 ms 315 ms tbr2.la2ca.ip.att.net [12.122.10.14]

13 346 ms 349 ms 361 ms 12.127.3.189

14 337 ms 320 ms 329 ms 12.122.255.74

15 104 ms 106 ms 107 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]

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.

[cmecu]

Look at this mess

Tracing route to us.logon.worldofwarcraft.com [12.129.224.117]

over a maximum of 30 hops:



1 <1 ms <1 ms <1 ms 192.168.169.9

2 180 ms 248 ms 321 ms 10.255.255.9

3 186 ms 127 ms 178 ms 10.242.80.14

4 27 ms 29 ms 99 ms 10.255.255.2

5 297 ms 310 ms 380 ms host-24-81.graftonfostercare.org [216.12.24.81]

6 * 53 ms 52 ms 10.242.80.13

7 55 ms 70 ms 48 ms 0.so-3-0-0.CL2.RIC2.ALTER.NET [152.63.37.230]

8 * * * Request timed out.

9 * * * Request timed out.

10 371 ms * * 192.205.34.49

11 475 ms 485 ms * tbr1.n54ny.ip.att.net [12.122.105.46]

12 316 ms * 248 ms cr2.n54ny.ip.att.net [12.122.16.149]

13 * 189 ms * cr2.wswdc.ip.att.net [12.122.3.38]

14 * 280 ms 251 ms tbr1.wswdc.ip.att.net [12.122.16.14]

15 339 ms * * tbr1.sl9mo.ip.att.net [12.122.10.30]

16 384 ms 354 ms * tbr2.sl9mo.ip.att.net [12.122.9.142]

17 * 293 ms 319 ms tbr2.la2ca.ip.att.net [12.122.10.14]

18 331 ms 286 ms 297 ms 12.127.3.189

19 312 ms * * 12.122.255.74

20 * * 328 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]

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.



How can one find, and contact these places that time out . I know the last ones are blizzards , and the are intentionally hidden, but all those above that, its horrendous .