Just for giggles I ran a number of tracerts and pings on Lusternia. My ping is jumping all over the place from Merry Ole England to Chicago - at its best (112ms) I've shaved between 50-60ms off what it used to be, but a standard ping for me is looking something like this:

Pinging lusternia.com with 32 bytes of data:

Reply from 209.212.145.235: bytes=32 time=116ms TTL=46
Reply from 209.212.145.235: bytes=32 time=226ms TTL=46
Reply from 209.212.145.235: bytes=32 time=142ms TTL=46
Reply from 209.212.145.235: bytes=32 time=265ms TTL=46

Ping statistics for 209.212.145.235:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 116ms, Maximum = 265ms, Average = 187ms

But I'm also getting ones like this quite regularly:

Pinging lusternia.com with 32 bytes of data:

Reply from 209.212.145.235: bytes=32 time=258ms TTL=46
Reply from 209.212.145.235: bytes=32 time=177ms TTL=46
Reply from 209.212.145.235: bytes=32 time=401ms TTL=46
Reply from 209.212.145.235: bytes=32 time=319ms TTL=46

Ping statistics for 209.212.145.235:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 177ms, Maximum = 401ms, Average = 288ms


Seem to be getting the same problem with most US Servers. Any other Europeans having same problem?

Should add that I'm the only person on the network and I have very stable pings with most European servers.

EDIT: Tracert shows that my ping goes to pot after going through *.telia.net servers.

Sweden here, and my ping is amazingly stable.

Svar från 209.212.145.235: byte=32 tid=144ms TTL=44
Svar från 209.212.145.235: byte=32 tid=135ms TTL=44
Svar från 209.212.145.235: byte=32 tid=135ms TTL=44
Svar från 209.212.145.235: byte=32 tid=135ms TTL=44
Svar från 209.212.145.235: byte=32 tid=134ms TTL=44
Svar från 209.212.145.235: byte=32 tid=134ms TTL=44
Svar från 209.212.145.235: byte=32 tid=134ms TTL=44
Svar från 209.212.145.235: byte=32 tid=134ms TTL=44
Svar från 209.212.145.235: byte=32 tid=134ms TTL=44
Svar från 209.212.145.235: byte=32 tid=135ms TTL=44
Svar från 209.212.145.235: byte=32 tid=135ms TTL=44
Svar från 209.212.145.235: byte=32 tid=135ms TTL=44
Svar från 209.212.145.235: byte=32 tid=135ms TTL=44
Svar från 209.212.145.235: byte=32 tid=135ms TTL=44
Svar från 209.212.145.235: byte=32 tid=135ms TTL=44
Svar från 209.212.145.235: byte=32 tid=134ms TTL=44
Svar från 209.212.145.235: byte=32 tid=134ms TTL=44

So must be something closer to you, or we're using different paths.

My tracert shows my ping going byebye at this ip nyk-bb2-link.telia.net which is a Telia server somewhere in Europe. A quick google on Telia shows a lot of people in Europe having problems with lag on WoW servers caused by pings getting knocked about by Telia servers.

I take a different route in Telias network, going through:

s-b2-link.telia.net
s-bb2-link.telia.net
kbn-bb2-link.telia.net
nyk-bb2-link.telia.net
chi-bb1-link.telia.net

So yeah. Might be something there (at least for you and other euros), but it likely wouldn't affect people in the states. From what I can gather, the problem you're experiencing is between nyk-bb1-link.telia.net and chi-bb1-link.telia.net (that's the path I got when I used your IP).

Tracing route to lusternia.com
over a maximum of 30 hops:

8 54 ms 28 ms 24 ms ldn-b2-link.telia.net
9 36 ms 36 ms 27 ms ldn-bb2-link.telia.net
10 98 ms 196 ms 306 ms nyk-bb2-link.telia.net
11 207 ms 304 ms 311 ms chi-bb1-link.telia.net
12 201 ms 306 ms 306 ms ae11.er1.Chi2.Servernap.net
13 184 ms 246 ms 306 ms te9-4.csr2.Chi3.Servernap.net
14 324 ms 307 ms 306 ms p106.ddr3.Chi3.Servernap.net
15 222 ms 273 ms 237 ms www.lusternia.com

Trace complete.

Got the IP of the Telia Server wrong in my post above, oops. Was from a different tracert.

Yeah its between hop 9 and 10 it all goes to hell on every tracert. nyk-bb2-link.telia.net is where I'm going wrong. Would be interested to hear if any other Brits are having the same problem? My ISP is Virgin.

That traceroute looks rather shaky even before entering Telias network, to be honest.

And ah. You go through London instead of Kopenhagen. And the London-NYC-connection looks even shakier. Hard to pinpoint it exactly though.

Full Tracert:

Tracing route to lusternia.com
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms 192.168.1.1
2 33 ms 27 ms 28 ms 10.106.144.1
3 30 ms 19 ms 18 ms osr01newy-v15.network.virginmedia.net
4 17 ms 17 ms 26 ms osr01gate-tenge72.network.virginmedia.net
5 27 ms 13 ms 29 ms gate-core-1a-ge-210-0.network.virginmedia.net
6 26 ms 17 ms 14 ms leed-bb-1a-as4-0.network.virginmedia.net
7 27 ms 20 ms 30 ms tcl3-ic-1-ae0-0.network.virginmedia.net
8 48 ms 39 ms 22 ms ldn-b2-link.telia.net
9 30 ms 42 ms 20 ms ldn-bb2-link.telia.net
10 108 ms 282 ms 289 ms nyk-bb2-link.telia.net
11 286 ms 239 ms 306 ms chi-bb1-link.telia.net
12 323 ms 307 ms 304 ms ae11.er1.Chi2.Servernap.net
13 224 ms 306 ms 308 ms te9-4.csr2.Chi3.Servernap.net
14 227 ms 307 ms 307 ms p106.ddr3.Chi3.Servernap.net
15 230 ms 300 ms 310 ms www.lusternia.com

Trace complete.

Another:

Tracing route to lusternia.com
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 48 ms 12 ms 12 ms 10.106.144.1
3 13 ms 22 ms 14 ms osr01newy-v15.network.virginmedia.net
4 44 ms 12 ms 14 ms osr01gate-tenge72.network.virginmedia.net
5 53 ms 43 ms 9 ms gate-core-1a-ge-210-0.network.virginmedia.net
6 67 ms 14 ms 12 ms leed-bb-1a-as4-0.network.virginmedia.net
7 40 ms 29 ms 45 ms tcl3-ic-1-ae0-0.network.virginmedia.net
8 47 ms 49 ms 112 ms ldn-b2-link.telia.net
9 24 ms 18 ms 16 ms ldn-bb2-link.telia.net
10 141 ms * 473 ms nyk-bb2-link.telia.net
11 391 ms 306 ms 306 ms chi-bb1-link.telia.net
12 225 ms 434 ms 179 ms ae11.er1.Chi2.Servernap.net
13 404 ms 306 ms 306 ms te9-4.csr2.Chi3.Servernap.net
14 247 ms 304 ms 283 ms p106.ddr3.Chi3.Servernap.net
15 211 ms 281 ms 320 ms www.lusternia.com

Trace complete.

Again:

Tracing route to lusternia.com
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 24 ms 15 ms 16 ms 10.106.144.1
3 12 ms 9 ms 9 ms osr01newy-v15.network.virginmedia.net
4 17 ms 22 ms 10 ms osr01gate-tenge72.network.virginmedia.net
5 22 ms 28 ms 18 ms gate-core-1a-ge-210-0.network.virginmedia.net
6 43 ms 26 ms 20 ms leed-bb-1a-as4-0.network.virginmedia.net
7 59 ms 42 ms 29 ms tcl3-ic-1-ae0-0.network.virginmedia.net
8 424 ms 20 ms 21 ms ldn-b2-link.telia.net
9 22 ms 18 ms 18 ms ldn-bb2-link.telia.net
10 102 ms 100 ms 179 ms nyk-bb2-link.telia.net
11 412 ms 298 ms 367 ms chi-bb1-link.telia.net
12 224 ms 306 ms 127 ms ae11.er1.Chi2.Servernap.net
13 222 ms 306 ms 213 ms te9-4.csr2.Chi3.Servernap.net
14 224 ms 305 ms * p106.ddr3.Chi3.Servernap.net
15 292 ms 306 ms 307 ms www.lusternia.com

Trace complete.

Yeah, it is looking a bit shaky before entering Telia, getting much worse as it goes through though.

Compare to a tracert in Russia:


Tracing route to sptimes.ru
over a maximum of 30 hops:

1 1 ms 2 ms <1 ms 192.168.1.1
2 40 ms 21 ms 12 ms 10.106.144.1
3 35 ms 29 ms 21 ms osr01newy-v15.network.virginmedia.net
4 29 ms 20 ms 21 ms osr02gate-tenge72.network.virginmedia.net
5 15 ms 26 ms 17 ms gate-core-1b-ge-010-0.network.virginmedia.net
6 18 ms 20 ms 172 ms manc-bb-1b-as2-0.network.virginmedia.net
7 21 ms 19 ms 20 ms leed-bb-1a-as3-0.network.virginmedia.net
8 32 ms 45 ms 30 ms tcl3-ic-1-ae0-0.network.virginmedia.net
9 39 ms 28 ms 19 ms ldn-b2-link.telia.net
10 29 ms 23 ms 27 ms ldn-bb1-link.telia.net
11 69 ms 41 ms 42 ms hbg-bb1-link.telia.net
12 59 ms 58 ms 59 ms s-bb1-link.telia.net
13 82 ms 86 ms 77 ms mow-b1-link.telia.net
14 95 ms 79 ms 76 ms mow-m9-i2-link.telia.net
15 89 ms 99 ms 89 ms zenon-103945-mow-b2.c.telia.net
16 86 ms 81 ms 80 ms jam-l3sw-2-vlan401.msk.zenon.net
17 82 ms 76 ms 81 ms css-rus3.zenon.net

Trace complete.

Yeah... There's definitely something off with the London-NYC link. Likely something to do with the London borderrouter, or possibly the trans-atlantic cable.

Roark has just loaded some code that addresses some kinks which we think may have been causing some lag. Please let us know if things are better or worse or the same!

I never noticed any lag at all... Was it a general part of the code, or related to a specific skill or function? Mostly curiosity on my part, and it's understandable if you won't answer.

Tracing route to www.lusternia.com
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.101.100.2
2 <1 ms <1 ms <1 ms 192.168.254.1
3 <1 ms <1 ms <1 ms 194.83.103.61
4 1 ms 1 ms 1 ms po0-0.ulcc-gsr.lmn.net.uk
5 3 ms 3 ms 4 ms so-1-0-0.lond-sbr1.ja.net
6 2 ms 2 ms 2 ms so-6-0-0.lond-sbr4.ja.net
7 2 ms 2 ms 2 ms ldn-b4-link.telia.net
8 2 ms 5 ms 3 ms ldn-bb2-link.telia.net
9 72 ms 131 ms 75 ms nyk-bb2-link.telia.net
10 98 ms 98 ms 96 ms chi-bb1-link.telia.net
11 95 ms 96 ms 95 ms ae11.er1.chi2.servernap.net
12 118 ms 95 ms 95 ms te9-4.csr2.chi3.servernap.net
13 97 ms 95 ms 95 ms p106.ddr3.chi3.servernap.net
14 98 ms 97 ms 109 ms www.lusternia.com

Yup, that Telia link kills it for me too. The distance, LON-NYC, should only add about ~27ms. Lots of traffic on that link I guess.

London to NYC should add more than 27ms. Kopenhagen to NYC adds roughly 90ms for me (and always has), so I'd guess that London to NYC should add closer to 70 or so (since it's slightly closer).

Used Nexus and Mush today and everything seems to be fixed. Goodbye X minute lag bursts! Thanks admin!