WoW - Excessive Ping.

[#1]

As the title suggests it's another one of those WoW related threads again! I'm sorry to have to make one but I'm stumped as to what the cause is.
I've always experienced higher than normal latency  to WoW servers, and upon resubscribing it's still way over what It should be(280-300 avg), in comparison to other UK/Welsh players.
The traceroute to my server(Nordrassil EU, based in Frankfurt) -

Tracing route to 195.12.239.45 over a maximum of 30 hops
 1    17 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
 2    33 ms    35 ms    33 ms  lo0-central3.thn-ag2.plus.net [195.166.128.231]
 3    33 ms    34 ms    33 ms  gi1-11-231.thn-gw1.plus.net [84.92.6.208]
 4    32 ms    33 ms    34 ms  te2-3.thn-gw2.plus.net [212.159.1.58]
 5    34 ms    34 ms    32 ms  te-3-4.car5.London1.Level3.net [217.163.45.181]
 6    87 ms    34 ms    39 ms  ae-12-51.car2.London1.Level3.net [4.69.139.67]
 7    33 ms    34 ms    39 ms  telia-level3-ge.London1.Level3.net [4.68.111.182]
 8    34 ms    33 ms    33 ms  ldn-bb2-link.telia.net [80.91.250.238]
 9    41 ms    41 ms    47 ms  prs-bb1-link.telia.net [80.91.254.209]
10    40 ms    40 ms    42 ms  prs-b4-link.telia.net [80.91.251.112]
11    40 ms    40 ms    41 ms  prs-sdix-i1-link.telia.net [80.91.253.74]
12     *        *        *     Request timed out.
13     *    

--------------------------------------------------------------------------------------------------------------------------------------

Also got a PingPlotter to the same IP, and the packetloss recorded wasn't here and there, I ran it for about 35mins and got constant packetloss, mostly in London on Level3's network by the looks of it. - http://www.mediafire.com/?w3n9u0gayywc41e
I'm sort of stumped, I get the same sort of ms to other servers, even ones located in Paris, which is a stones throw away! and if accessed on for instance a dataserver or other gaming server, would get me well under 100ms.

Any insight would be much appreciated, and I'll be actively checking back and willing to do any tests needed.
Thanks!

[#2]

Ran another Trace, I can only assume the server Ip changes somewhat, same server, but getting a different PP IP.

Tracing route to 195.12.242.212 over a maximum of 30 hops
 1    75 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
 2    36 ms    39 ms    45 ms  lo0-central3.thn-ag2.plus.net [195.166.128.231]
 3    68 ms    34 ms   215 ms  gi1-11-231.thn-gw1.plus.net [84.92.6.208]
 4    33 ms    33 ms    32 ms  te2-3.thn-gw2.plus.net [212.159.1.58]
 5    32 ms    33 ms    33 ms  te-3-4.car5.London1.Level3.net [217.163.45.181]
 6   233 ms   220 ms   229 ms  ae-12-51.car2.London1.Level3.net [4.69.139.67]
 7    88 ms    98 ms    34 ms  telia-level3-ge.London1.Level3.net [4.68.111.182]
 8    34 ms    33 ms    40 ms  ldn-bb2-link.telia.net [80.91.249.133]
 9    40 ms    40 ms    41 ms  prs-bb1-link.telia.net [80.91.247.34]
10    50 ms    48 ms    48 ms  ffm-bb2-link.telia.net [80.91.246.180]
11    49 ms    50 ms    49 ms  ffm-b10-link.telia.net [80.91.247.77]
12     *        *        *     Request timed out.
As you can see the unusual ping on hop 6, It's not usually that high in a trace, just fluxuates greatly trace to trace.
Also did a Wireshark(To this new IP) http://www.mediafire.com/?38uhemztcubd51c -

Another Trace for you to get some comparison -

Tracing route to 195.12.242.212 over a maximum of 30 hops
 1    34 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
 2    35 ms    34 ms    34 ms  lo0-central3.thn-ag2.plus.net [195.166.128.231]
 3    34 ms    33 ms    33 ms  gi1-11-231.thn-gw1.plus.net [84.92.6.208]
 4    32 ms    34 ms    32 ms  te2-3.thn-gw2.plus.net [212.159.1.58]
 5    32 ms    33 ms    32 ms  te-3-4.car5.London1.Level3.net [217.163.45.181]
 6    33 ms    34 ms    34 ms  ae-12-51.car2.London1.Level3.net [4.69.139.67]
 7    33 ms    33 ms    33 ms  telia-level3-ge.London1.Level3.net [4.68.111.182]
 8    33 ms    33 ms    33 ms  ldn-bb2-link.telia.net [80.91.249.133]
 9    41 ms    41 ms    41 ms  prs-bb1-link.telia.net [80.91.247.34]
10    49 ms    49 ms   144 ms  ffm-bb1-link.telia.net [80.91.246.204]
11    50 ms    50 ms    50 ms  ffm-b10-link.telia.net [80.91.251.120]
12     *    

And as suggested in Blizzard's troubleshooting, to tracert to their logon servers aswell.

Tracing route to eu.logon.battle.net [213.248.127.130]
over a maximum of 30 hops:
  1    92 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2    33 ms    33 ms    33 ms  lo0-central3.thn-ag2.plus.net [195.166.128.231]
  3  123 ms  177 ms    96 ms  gi1-11-231.thn-gw1.plus.net [84.92.6.208]
  4    32 ms    34 ms    33 ms  te2-3.thn-gw2.plus.net [212.159.1.58]
  5    33 ms    33 ms    33 ms  te-3-4.car5.London1.Level3.net [217.163.45.181]
  6    50 ms    33 ms    35 ms  ae-12-51.car2.London1.Level3.net [4.69.139.67]
  7    33 ms    34 ms    34 ms  telia-level3-ge.London1.Level3.net [4.68.111.182]
  8    33 ms    33 ms    34 ms  ldn-bb1-link.telia.net [80.91.250.234]
  9    41 ms    40 ms    40 ms  prs-bb2-link.telia.net [80.91.247.240]
10    49 ms    48 ms    49 ms  ffm-bb2-link.telia.net [80.91.246.180]
11    49 ms    49 ms    49 ms  ffm-b10-link.telia.net [80.91.247.187]
12    *        *        *    Request timed out.


So yeah, that's me done, I'll just wait for a response!

[#3]

What do you get using ping instead of traceroute ?
I got pings of around 30ms using the IP address from your last posting -

[#4]

An average of 50ms pinging that IP, over 100 pings. 0% packetloss.
Hmm, pinging the  ae-12-51.car2.London1.Level3.net [4.69.139.67] got me some weird results, over 100 pings for the first 40 or so it was at a solid 31/32, then it jumped and did 4-5 200ms+ results, and around the 90 ping mark it did a few low 100s.

Considering that's ~200miles away, It shouldn't be doing that.. surely.
Did the same to bbc.co.uk and a solid 31ms average, no jumps above 33ms.

[#5]

$ ping ae-12-51.car2.London1.Level3.net
PING ae-12-51.car2.London1.Level3.net (4.69.139.67) 56(84) bytes of data.
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=1 ttl=249 time=14.5 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=2 ttl=249 time=14.1 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=3 ttl=249 time=14.1 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=4 ttl=249 time=14.5 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=5 ttl=249 time=13.9 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=6 ttl=249 time=13.7 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=7 ttl=249 time=13.8 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=8 ttl=249 time=13.7 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=9 ttl=249 time=14.5 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=10 ttl=249 time=14.6 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=11 ttl=249 time=14.3 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=12 ttl=249 time=13.0 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=13 ttl=249 time=14.5 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=14 ttl=249 time=13.9 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=15 ttl=249 time=13.5 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=16 ttl=249 time=13.6 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=17 ttl=249 time=14.7 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=18 ttl=249 time=14.8 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=19 ttl=249 time=14.3 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=20 ttl=249 time=13.6 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=21 ttl=249 time=14.8 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=22 ttl=249 time=13.5 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=23 ttl=249 time=14.7 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=24 ttl=249 time=13.8 ms
64 bytes from ae-12-51.car2.London1.Level3.net (4.69.139.67): icmp_seq=25 ttl=249 time=13.8 ms

[#6]

Still stumped as to what it is, It sure as hell doesn't look like a problem on my end. 

[#7]

If it's a single server off our network that's returning high pings then please perform a pathping to that server, this should provide sufficient detail to tell you whether the problem is on the PN network or external.

[#8]

Quote

Tracing route to gi1-11-231.thn-gw1.plus.net [84.92.6.208] over a maximum of 30 hops:   0  Steff-PC.lan [192.168.1.64]   1  dsldevice.lan [192.168.1.254]   2  lo0-central3.thn-ag2.plus.net [195.166.128.231]   3  gi1-11-231.thn-gw1.plus.net [84.92.6.208] Computing statistics for 75 seconds...             Source to Here  This Node/Link Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address   0                                          Steff-PC.lan [192.168.1.64]                                 0/ 100 =  0%  |   1    0ms    0/ 100 =  0%    0/ 100 =  0%  dsldevice.lan [192.168.1.254]                                 0/ 100 =  0%  |   2  ---    100/ 100 =100%  100/ 100 =100%  lo0-central3.thn-ag2.plus.net [195.166.128.231]                                 0/ 100 =  0%  |   3  43ms    0/ 100 =  0%    0/ 100 =  0%  gi1-11-231.thn-gw1.plus.net [84.92.6.208] Trace complete.

That's one of the problem hops, If needed I can do them all.

[#9]

[quote=Gef]3  43ms    0/ 100 =  0%    0/ 100 =  0%  gi1-11-231.thn-gw1.plus.net [84.92.6.208]
I only get about half that delay !

> pathping 84.92.6.208
Tracing route to gi1-11-231.thn-gw1.plus.net [84.92.6.208]
            Source to Here  This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                                            My_PC [192.168.xxx.xxx]
  1    2ms    0/ 100 =  0%    0/ 100 =  0%  My_ADSL_Gateway [192.168.xxx.xxx]
  2  16ms    0/ 100 =  0%    0/ 100 =  0%  lo0-homesurf.pcl-ag03.plus.net [195.166.128.110]
  3  29ms    0/ 100 =  0%    0/ 100 =  0%  gi1-6-705.pcl-gw02.plus.net [84.92.0.188]
  4  23ms    0/ 100 =  0%    0/ 100 =  0%  te2-2.pte-gw1.plus.net [212.159.0.186]
  5  23ms    0/ 100 =  0%    0/ 100 =  0%  gi1-11-231.thn-gw1.plus.net [84.92.6.208]
Trace complete.

[#10]

Whereas a normal ping is nearly half less again !
> ping 84.92.6.208
PING 84.92.6.208 (84.92.6.208) 56(84) bytes of data.
64 bytes from 84.92.6.208: icmp_seq=1 ttl=251 time=14.8 ms
64 bytes from 84.92.6.208: icmp_seq=2 ttl=251 time=14.2 ms
64 bytes from 84.92.6.208: icmp_seq=3 ttl=251 time=13.8 ms
64 bytes from 84.92.6.208: icmp_seq=4 ttl=251 time=13.7 ms
64 bytes from 84.92.6.208: icmp_seq=5 ttl=251 time=13.7 ms
64 bytes from 84.92.6.208: icmp_seq=6 ttl=251 time=13.7 ms
64 bytes from 84.92.6.208: icmp_seq=7 ttl=251 time=13.4 ms
64 bytes from 84.92.6.208: icmp_seq=8 ttl=251 time=12.7 ms
64 bytes from 84.92.6.208: icmp_seq=9 ttl=251 time=13.8 ms

[#11]

Cheers guys, those traces were to servers that were still on our network, we'll need to see results all the way to the WoW servers to see if we can locate the source of the problem.

[#12]

> pathping 195.12.239.45
Tracing route to 195.12.239.45 over a maximum of 30 hops
           Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
0                                                            My_PC [192.168.xxx.xxx]
1     2ms     0/ 100 =  0%     0/ 100 =  0%  My_ADSL_Gateway [192.168.xxx.xxx]
2   19ms     0/ 100 =  0%     0/ 100 =  0%  lo0-homesurf.pcl-ag02.plus.net [195.166.128.40]
3   24ms     0/ 100 =  0%     0/ 100 =  0%  gi1-13-906.pcl-gw01.plus.net [84.92.0.148]
4   27ms     0/ 100 =  0%     0/ 100 =  0%  te2-1.pcl-gw02.plus.net [212.159.1.114]
5   16ms     0/ 100 =  0%     0/ 100 =  0%  195.50.122.129
6   47ms     0/ 100 =  0%     0/ 100 =  0%  ae-12-51.car2.London1.Level3.net [4.69.139.67]
7  ---     100/ 100 =100%   100/ 100 =100%  telia-level3-ge.London1.Level3.net [4.68.111.182]
8   17ms     0/ 100 =  0%     0/ 100 =  0%  ldn-bb1-link.telia.net [80.91.249.131]
9   25ms     0/ 100 =  0%     0/ 100 =  0%  prs-bb2-link.telia.net [80.91.247.240]
10   24ms     0/ 100 =  0%     0/ 100 =  0%  prs-b4-link.telia.net [80.91.251.114]
11   24ms     0/ 100 =  0%     0/ 100 =  0%  prs-sdix-i1-link.telia.net [80.91.253.74]
Trace complete.

[#13]

This is to the Battlenet Logon servers -

Quote

Tracing route to 213-248-127-13.customer.teliacarrier.com [213.248.127.13] over a maximum of 30 hops:   0  Steff-PC.lan [192.168.1.64]   1  dsldevice.lan [192.168.1.254]   2  lo0-central3.thn-ag2.plus.net [195.166.128.231]   3  gi1-11-231.thn-gw1.plus.net [84.92.6.208]   4  te2-3.thn-gw2.plus.net [212.159.1.58]   5  te-3-4.car5.London1.Level3.net [217.163.45.181]   6  ae-12-51.car2.London1.Level3.net [4.69.139.67]   7  telia-level3-ge.London1.Level3.net [4.68.111.182]   8  ldn-bb2-link.telia.net [80.91.250.238]   9  prs-bb1-link.telia.net [80.91.247.34] 10  ffm-bb1-link.telia.net [80.91.246.206] 11  ffm-b10-link.telia.net [80.91.247.185] 12    *        *        *    Computing statistics for 275 seconds...             Source to Here  This Node/Link Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address   0                                          Steff-PC.lan [192.168.1.64]                                 0/ 100 =  0%  |   1    0ms    0/ 100 =  0%    0/ 100 =  0%  dsldevice.lan [192.168.1.254]                                 0/ 100 =  0%  |   2  35ms    0/ 100 =  0%    0/ 100 =  0%  lo0-central3.thn-ag2.plus.net [195.166.128.231]                                 0/ 100 =  0%  |   3  40ms    0/ 100 =  0%    0/ 100 =  0%  gi1-11-231.thn-gw1.plus.net [84.92.6.208]                                 0/ 100 =  0%  |   4  37ms    0/ 100 =  0%    0/ 100 =  0%  te2-3.thn-gw2.plus.net [212.159.1.58]                                 0/ 100 =  0%  |   5  50ms    0/ 100 =  0%    0/ 100 =  0%  te-3-4.car5.London1.Level3.net [217.163.45.181]                                 0/ 100 =  0%  |   6  47ms    1/ 100 =  1%    1/ 100 =  1%  ae-12-51.car2.London1.Level3.net [4.69.139.67]                                 0/ 100 =  0%  |   7  ---    100/ 100 =100%  100/ 100 =100%  telia-level3-ge.London1.Level3.net [4.68.111.182]                                 0/ 100 =  0%  |   8  37ms    0/ 100 =  0%    0/ 100 =  0%  ldn-bb2-link.telia.net [80.91.250.238]                                 0/ 100 =  0%  |   9  45ms    0/ 100 =  0%    0/ 100 =  0%  prs-bb1-link.telia.net [80.91.247.34]                                 0/ 100 =  0%  | 10  50ms    0/ 100 =  0%    0/ 100 =  0%  ffm-bb1-link.telia.net [80.91.246.206]                                 0/ 100 =  0%  | 11  51ms    0/ 100 =  0%    0/ 100 =  0%  ffm-b10-link.telia.net [80.91.247.185] Trace complete.

This is to my server -

Quote

Tracing route to 195.12.242.212 over a maximum of 30 hops   0  Steff-PC.lan [192.168.1.64]   1  dsldevice.lan [192.168.1.254]   2  lo0-central3.thn-ag2.plus.net [195.166.128.231]   3  gi1-11-231.thn-gw1.plus.net [84.92.6.208]   4  te2-3.thn-gw2.plus.net [212.159.1.58]   5  te-3-4.car5.London1.Level3.net [217.163.45.181]   6  ae-12-51.car2.London1.Level3.net [4.69.139.67]   7  telia-level3-ge.London1.Level3.net [4.68.111.182]   8  ldn-bb1-link.telia.net [80.91.249.131]   9  prs-bb1-link.telia.net [80.91.247.254] 10  ffm-bb2-link.telia.net [80.91.246.180] 11  ffm-b10-link.telia.net [80.91.247.79] 12    *        *        *    Computing statistics for 275 seconds...             Source to Here  This Node/Link Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address   0                                          Steff-PC.lan [192.168.1.64]                                 0/ 100 =  0%  |   1    0ms    0/ 100 =  0%    0/ 100 =  0%  dsldevice.lan [192.168.1.254]                                 0/ 100 =  0%  |   2  37ms    0/ 100 =  0%    0/ 100 =  0%  lo0-central3.thn-ag2.plus.net [195.166.128.231]                                 0/ 100 =  0%  |   3  40ms    0/ 100 =  0%    0/ 100 =  0%  gi1-11-231.thn-gw1.plus.net [84.92.6.208]                                 0/ 100 =  0%  |   4  42ms    0/ 100 =  0%    0/ 100 =  0%  te2-3.thn-gw2.plus.net [212.159.1.58]                                 0/ 100 =  0%  |   5  39ms    0/ 100 =  0%    0/ 100 =  0%  te-3-4.car5.London1.Level3.net [217.163.45.181]                                 0/ 100 =  0%  |   6  44ms    0/ 100 =  0%    0/ 100 =  0%  ae-12-51.car2.London1.Level3.net [4.69.139.67]                                 0/ 100 =  0%  |   7  ---    100/ 100 =100%  100/ 100 =100%  telia-level3-ge.London1.Level3.net [4.68.111.182]                                 0/ 100 =  0%  |   8  35ms    0/ 100 =  0%    0/ 100 =  0%  ldn-bb1-link.telia.net [80.91.249.131]                                 0/ 100 =  0%  |   9  43ms    0/ 100 =  0%    0/ 100 =  0%  prs-bb1-link.telia.net [80.91.247.254]                                 0/ 100 =  0%  | 10  53ms    0/ 100 =  0%    0/ 100 =  0%  ffm-bb2-link.telia.net [80.91.246.180]                                 0/ 100 =  0%  | 11  52ms    0/ 100 =  0%    0/ 100 =  0%  ffm-b10-link.telia.net [80.91.247.79] Trace complete.

[#14]

As an aside, have you tried:  http://www.wowinterface.com/downloads/info13581-LeatrixLatencyFix.html
It reduced my ping by a chunk when I tried it.  If you are having network problems it won't help of course though!

[#15]

Yeah i've tried the fix, I got marginally better but it wasn't anything special, and it had a tendancy to absolutely cripple my website loading/Blizzard torrenting.