WoW Patch 3.2.2????

[#1]

Hi there,
Recently joined Plusnet, just waiting on my line activation. I have switched over from AOL due to complete fail since patch 3.2.2 on World of Warcraft.
Basically what im asking is are any other Plusnet WoW players within the UK experiencing issues since this patch? I know alot of AOL, VM and tiscali players are.
Lag, Dc's etc etc.
My apologies if this is stated somewhere else but i am new to this forum 😃
Thanks
/Niix

[#2]

200-250 ping with WOW under Plusnet.

[#3]

is that with the Pro package? Also is it stable?

[#4]

Thats on unlimited, its stable a little laggy.

[#5]

Really appreciate the reply. Anyone else with they're current ms? or problems appearing?

[#6]

theres a handful of customers with the 250ms ping, not many thoe and if there was wide spread issue with wow i would expect the forum to crash due to the amount of wow players complaining
http://community.plus.net/forum/index.php/topic,79693.0.html

[#7]

Yeah, in the last month my ping in WoW has gone from a normal 40ms-100ms (which is acceptable) to a constant 250ms+.  This is on the EU realm, Kul Tiras. 

[#8]

Hopefully this will help improve the situation. I've just had a look through the relevant change control and it would appear that there's some WoW stuff to be tweaked tomorrow morning.

[#9]

How it makes a difference was runnng with a ping fo 400 earlier today.

[#10]

test the wow's servers traffic with wireshark and if its not coming back as 0x0a (gaming prioity) then theres a good chance the changes made tomoro will pick the servers traffic up right and improve the latency

[#11]

How is the latency now with the test Plusnet did today???

[#12]

Still not good for me. Im on plusnet pro.
Trace to the datacenter in germany:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\*****>tracert 80.139.149.103
Tracing route to p508B9567.dip0.t-ipconnect.de [80.139.149.103]
over a maximum of 30 hops:
 1    65 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
 2   106 ms    75 ms    53 ms  lo0-plusnet.ptn-ag2.plus.net [195.166.128.53]
 3    78 ms    56 ms    65 ms  gi2-2-204.ptn-gw02.plus.net [84.92.3.93]
 4    68 ms   249 ms   161 ms  te2-2.pte-gw2.plus.net [212.159.1.106]
 5    67 ms    59 ms   159 ms  80.239.193.141
 6    55 ms    55 ms    81 ms  ldn-bb1-link.telia.net [80.91.248.90]
 7    61 ms    51 ms    51 ms  ldn-b4-link.telia.net [80.91.251.17]
 8    76 ms    59 ms    54 ms  62.156.138.53
 9    67 ms    73 ms    75 ms  e-ea1-i.E.DE.NET.DTAG.DE [62.154.76.34]
10     *        *        *     Request timed out.
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.

[#13]

If you're on Pro you shouldn't really have been affected by any changes that we made on our traffic management platform (although the traffic should be marke as titanium instead of gold).
Is your latency poor consistently?  Do you see the same after rebooting and connecting on a different gateway?

[#14]

Yeah it's the same after rebooting. Just rebooted again, included trace below. It's consistently... not good i would say. By that i mean, when i first load the game it's good (~80ms), but it gradually climbs until the level bugs me and i restart the game, at which point the cycle begins again. It takes about 30 mins to get to ~200 ms, then i restart. Worst i seen is when i went away for a while, came back and it was 312ms. Wireshark says it prioritised correctly.
Havent mentioned it before as it says somewhere to not report what you think is a problem until 7 days have past after you get connected, it's been 5 i think.
Recent trace to same location:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\yada>tracert 80.139.149.103
Tracing route to p508B9567.dip0.t-ipconnect.de [80.139.149.103]
over a maximum of 30 hops:
  1    32 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2    78 ms    75 ms    53 ms  lo0-plusnet.ptn-ag2.plus.net [195.166.128.53]
  3    47 ms    56 ms    65 ms  gi2-2-204.ptn-gw02.plus.net [84.92.3.93]
  4  131 ms    71 ms    61 ms  te2-2.pte-gw2.plus.net [212.159.1.106]
  5    67 ms  159 ms    46 ms  80.239.193.141
  6    55 ms    55 ms  181 ms  ldn-bb1-link.telia.net [80.91.248.90]
  7    61 ms    51 ms    81 ms  ldn-b4-link.telia.net [80.91.251.17]
  8    76 ms    59 ms    54 ms  62.156.138.53
  9    67 ms    73 ms    75 ms  e-ea1-i.E.DE.NET.DTAG.DE [62.154.76.34]
10    *        *        *    Request timed out.
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.

[#15]

Quote from: breakat

Yeah it's the same after rebooting. Just rebooted again, included trace below. It's consistently... not good i would say. By that i mean, when i first load the game it's good (~80ms), but it gradually climbs until the level bugs me and i restart the game, at which point the cycle begins again. It takes about 30 mins to get to ~200 ms, then i restart. Worst i seen is when i went away for a while, came back and it was 312ms. Wireshark says it prioritised correctly.

I am also getting the same thing as breakat

Tracing route to 80-239-185-33.customer.teliacarrier.com [80.239.185.33]
over a maximum of 30 hops:

 1    59 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
 2    90 ms    94 ms    64 ms  lo0.plusnet.thn-ag1.plus.net [195.166.128.101]
 3    58 ms    59 ms    65 ms  vl703.thn-gw1.plus.net [84.92.4.241]
 4    59 ms    60 ms    64 ms  ldn-b4-link.telia.net [213.248.84.201]
 5    63 ms    58 ms    64 ms  ldn-bb2-link.telia.net [80.91.249.133]
 6    64 ms    80 ms    79 ms  prs-bb1-link.telia.net [80.91.247.34]
 7    73 ms    67 ms    69 ms  prs-b-link.telia.net [80.91.251.47]
 8     *        *        *     Request timed out.
 9     *        *        *     Request timed out.
10     *        *        *     Request timed out.
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     *

This is The latency in the Game
0ms
65ms
64ms
66ms
90ms
137ms
125ms
163ms
175ms
162ms
172ms
163ms
175ms
166ms
162ms
155ms
170ms
163ms
I Tried Off Peak-times and i am still getting Lag a little better but no improvement :(. I tried port-fowarding, Turning my firewall off. Reconnecting my router.  The WoW server is in Paris.
In Other games Like Team fortress 2 i connect to a french server and my ping is 60-90. in Uk servers i Get 50-70 latency
My Spec
Intel Core 2 quad Q6600 (2.4Ghz Clock Speed)
Nvidia Geforce 9800GT SLI (Core Clock 600Mhz) (Memory clock 900MHz) (Shader clock 1500MHz)
3GB Kingston, Samsung Memory (801 (DDR2) MHz)
Motherboard (Vendor NVIDIA) (Version 2.0) (Model NVK84CRB)
DirectX 9.0c
Microsoft Windows XP Professional Service pack 3, build 2600
NVIDIA Nforce Networking Controller
Plusnet Package: Unlimited
Do you think the Peer 2 Peer Trafic Management Might of caused this. I was downloading the Patch (1.62GB) and my download from the connection prefences are showing 40.00KB - 120.00KB During Peak Times and then it was 11PM 60.00KB - 200.00KB.  The blizzard downloader uses Bittorrent.
Some Say That WoW Uses Peer 2 Peer in the Game itself but i don't know if this is true or not.