ok seems like I found the problem with the huge latency.
my tracert to the server I play on routed me through Washington, Im not the only person who get this as many other people using iburst also is getting routed through Washington and causes wow to be unplayable.
My tracert to eu.battle.net (wow's website) showed this.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Dviance>tracert eu.battle.net
Tracing route to eu.battle.net [80.239.186.40]
over a maximum of 30 hops:
1 50 ms 44 ms 44 ms wbs-196-2-100-1.wbs.co.za [196.2.100.1]
2 59 ms 44 ms 163 ms 192.168.0.97
3 42 ms 44 ms 44 ms 192.168.0.114
4 43 ms 199 ms 44 ms iburst-41-213-126-21.iburst.co.za [41.213.126.21
]
5 58 ms 44 ms 44 ms 41.0.4.225
6 328 ms 329 ms 355 ms 41.0.244.5
7 339 ms 324 ms 404 ms ge-9-24.car3.Washington1.Level3.net [4.79.169.22
9]
8 327 ms 314 ms 305 ms ae-2-79.edge1.Washington4.Level3.net [4.68.17.82
]
9 354 ms 310 ms 348 ms ash-bb1-link.telia.net [213.248.81.117]
10 392 ms 334 ms 334 ms prs-bb2-link.telia.net [80.91.254.215]
11 368 ms 339 ms 330 ms prs-b7-link.telia.net [80.91.253.110]
12 364 ms 344 ms 334 ms prs-sdix-i2-link.telia.net [80.91.253.78]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 *
So this leads me to believe that all battle.net games gets routed through Washington, why iburst why??
This means that the traffic has got to go to usa and then to europe and back. wth?
