TrueWoW

Greetings,

If any of you are experiencing issues with high latency in the past few days (as of this post's date), please take the following steps to inform us so we can attempt to determine the origin of your issue:

1. Open the command prompt.
2. Type this: and press Enter.
3. Allow it to complete.
4. Type this: and press Enter.
5. Allow the trace to complete.
6. In the top left corner of the window, click the tiny icon >> Edit >> Select All, then Edit >> Copy
7. Post your results here ALONG with the country you're playing from and the average latency you're getting in-game.

I also recommend paying a visit to this thread to see if it helps you out with your latency issues on TW & PW:
https://truewow.org/forum/viewtopic.php?f=3&t=14644

Regards.

It took some time but I'm pretty sure the issue is resolved now.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\DreamWeaver>tracert login.truewow.org

Tracing route to login.truewow.org [188.165.210.113]
over a maximum of 30 hops:

1 97 ms 90 ms 104 ms 10.114.55.21
2 1190 ms 839 ms 356 ms 192.168.107.138
3 364 ms 160 ms 190 ms 192.168.117.133
4 62 ms 70 ms 75 ms 192.168.107.206
5 165 ms 214 ms 272 ms 192.168.107.198
6 428 ms 557 ms 452 ms 10.242.217.10
7 1375 ms 1713 ms 1197 ms 10.113.139.157
8 307 ms 485 ms 384 ms vc-196-207-42-19.3g.vodacom.co.za [196.207.42.19
]
9 710 ms 657 ms 679 ms 192.168.250.33
10 133 ms 164 ms 276 ms 41.21.235.18
11 * * * Request timed out.
12 * * * Request timed out.
13 * 3745 ms * be100-1042.rbx-g2-nc5.fr.eu [213.251.130.102]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * Transmit error: code 1231.

Trace complete.

C:\Users\DreamWeaver>tracert login.truewow.org

Tracing route to login.truewow.org [188.165.210.113]
over a maximum of 30 hops:

1 60 ms 55 ms 64 ms 10.113.24.212
2 140 ms 37 ms 53 ms 10.113.139.157
3 153 ms 129 ms 55 ms vc-196-207-42-19.3g.vodacom.co.za [196.207.42.19
]
4 57 ms 57 ms 57 ms 192.168.250.33
5 123 ms 133 ms 67 ms 41.21.235.18
6 200 ms 213 ms 200 ms 10.118.48.53
7 198 ms 199 ms 193 ms 10.118.49.141
8 205 ms 205 ms 205 ms 10.118.49.98
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 224 ms 229 ms 229 ms ns309753.ip-188-165-210.eu [188.165.210.113]

Trace complete.

C:\Users\DreamWeaver>

Connecting from South Africa
Thx
MimziM28

MimziM28 wrote: ↑

25 Mar 2019 13:11

Connecting from South Africa
Thx
MimziM28

Your first trace is all kinds of messed up. Are you using a VPN or an IP Cloner by any chance?
You're encountering high latency before your connection even leaves Johannesburg, just north of La Rochelle (hop 8).
By the time it reaches TW's Data Center in Paris, the signal is losing all cohesion.

Your second trace looks relatively normal (better than mine, in fact), besides the 3 timeouts on hop 9 to 11 at the end, which are a common sight with a majority of the traces to TW. So there's no indication of why you'd be lagging with a result like that.

Try the free (or trial) version of PingZappper and see if it helps:
https://truewow.org/forum/viewtopic.php?f=3&t=14644

Microsoft Windows [Version 10.0.17763.379]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>ping login.truewow.org

Pinging login.truewow.org [188.165.210.113] with 32 bytes of data:
Reply from 188.165.210.113: bytes=32 time=160ms TTL=42
Reply from 188.165.210.113: bytes=32 time=160ms TTL=42
Reply from 188.165.210.113: bytes=32 time=160ms TTL=42
Reply from 188.165.210.113: bytes=32 time=160ms TTL=42

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

C:\WINDOWS\system32>tracert login.truewow.org

Tracing route to login.truewow.org [188.165.210.113]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254]
2 19 ms 36 ms 21 ms 108-83-188-1.lightspeed.frokca.sbcglobal.net [108.83.188.1]
3 18 ms 17 ms 17 ms 71.147.240.104
4 19 ms 18 ms 18 ms 75.29.64.142
5 19 ms 18 ms 18 ms 12.83.77.193
6 24 ms 22 ms 23 ms 12.122.114.5
7 22 ms 22 ms 22 ms 192.205.32.222
8 23 ms 23 ms 23 ms palo-b22-link.telia.net [62.115.125.0]
9 87 ms 86 ms 87 ms be100-105.pao-sv8-bb1-a9.ca.us [192.99.146.32]
10 87 ms 87 ms 87 ms chi-5-a9.il.us [198.27.73.227]
11 94 ms 94 ms 94 ms be100-1324.bhs-g2-nc5.qc.ca [192.99.146.140]
12 * * * Request timed out.
13 157 ms 157 ms 157 ms vl1305.rbx-d2-a75.fr.eu [213.251.128.0]
14 * * * Request timed out.
15 * * * Request timed out.
16 160 ms 160 ms 160 ms ns309753.ip-188-165-210.eu [188.165.210.113]

i get this all the time whenever i play wow on the server it goes up to about 94 ms and such

ramonava939 wrote: ↑

29 Mar 2019 07:24

i get this all the time whenever i play wow on the server it goes up to about 94 ms and such

I don't see anything wrong with your trace, besides the final few hops which always time out for a majority of players on TW & PW.
94 ms from your location (based on the 2nd hop's IP) is pretty good. Even as much as 150-200 ms is pretty much the norm from that distance.
If you have a specific issue you'd like investigated, please inform us.

C:\Users\Michal>tracert login.truewow.org

Tracing route to login.truewow.org [188.165.210.113]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.0.1
2 11 ms 2 ms 2 ms 1106.066.cus.dsidata.sk [80.87.213.66]
3 3 ms 4 ms 4 ms 1110.033.cus.dsidata.sk [80.87.217.33]
4 9 ms 10 ms 11 ms 1104.005.cus.dsidata.sk [80.87.211.5]
5 14 ms 14 ms 14 ms 109.74.148.213.host.vnet.sk [109.74.148.213]
6 * * * Request timed out.
7 20 ms 21 ms 21 ms vie-vie1-bb1-a9.at.eu [54.36.50.74]
8 32 ms 32 ms 31 ms be100-1104.fra-1-a9.de.eu [213.251.128.85]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 200 ms 61 ms 69 ms ns309753.ip-188-165-210.eu [188.165.210.113]

Trace complete.

Tracing route to login.truewow.org [188.165.210.113]
over a maximum of 30 hops:

1 * 2 ms 2 ms 192.168.1.254
2 28 ms 6 ms 7 ms bb121-7-243-254.singnet.com.sg [121.7.243.254]
3 9 ms 6 ms 10 ms 202.166.123.134
4 9 ms 105 ms 4 ms 202.166.123.133
5 5 ms 5 ms 5 ms ae8-0.tp-cr03.singnet.com.sg [202.166.122.50]
6 6 ms 6 ms 5 ms ae4-0.tp-er03.singnet.com.sg [202.166.123.70]
7 5 ms 4 ms 4 ms 203.208.191.197
8 190 ms 189 ms 191 ms 203.208.172.210
9 * * * Request timed out.
10 238 ms 238 ms 238 ms chi-1-a9.il.us [198.27.73.149]
11 258 ms 253 ms 253 ms be100-1320.bhs-g1-nc5.qc.ca [198.27.73.206]
12 * * * Request timed out.
13 263 ms 262 ms 363 ms vl1304.rbx-g1-a75.fr.eu [213.186.32.248]
14 * * * Request timed out.
15 * * * Request timed out.
16 249 ms 249 ms 250 ms ns309753.ip-188-165-210.eu [188.165.210.113]

Trace complete.

Pinging login.truewow.org [188.165.210.113] with 32 bytes of data:
Reply from 188.165.210.113: bytes=32 time=249ms TTL=47
Reply from 188.165.210.113: bytes=32 time=276ms TTL=47
Reply from 188.165.210.113: bytes=32 time=248ms TTL=47
Reply from 188.165.210.113: bytes=32 time=249ms TTL=47

Ping statistics for 188.165.210.113:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 248ms, Maximum = 276ms, Average = 255ms

In game: Typically I should see pings of around 250-600 (which is same as Retail WoW for me and playable). For years didn't have this issue
However it seems now I am not able to get the data from the server, as I currently experience lag spikes where NPCs don't update and I don't get off the flight point mount 'until I receive the update from the server'

Eg: I am currently mounted in an indoor area in Feralas where you should be dismounted and I don't see any NPC updates (the view should update as you close in) and I can't interact with any NPCs or chat


Would then need to open a new client, login to drop the old connection (it seems hung for some reason) to continue playing for however long I am able to receive server data



Unfortunately this time it does not last long


Already tried to use a service similar to pingzapper (wtffast) using a server in France, it doesn't seem to help at all

Recently changed to Windows 10, already disabled Windows firewall

Suspect its my ISP doing something but would like to confirm

Connecting from Singapore

CoolBreeze wrote: ↑

29 Mar 2019 21:25

Your connection seems relatively fine. I've traced each hop and can't find anything wrong with it.
If you have a more specific issue with your connection to TW that you'd like investigated, please inform us.

Kregon wrote: ↑

07 Apr 2019 17:06

Your connection is being routed through Montréal, Canada before it finally arrives at Northern France.
From what I can tell, your signal crosses two oceans before it's relayed to TrueWoW in Paris.
It's already getting extremely high pings in Montréal as well.
I doubt I have to tell you the amount of signal deterioration involved for a signal traversing such a distance.
Unfortunately, it's out of anyone's hands except your ISP.

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Christo>ping login.truewow.org

Pinging login.truewow.org [188.165.210.113] with 32 bytes of data:
Reply from 188.165.210.113: bytes=32 time=172ms TTL=50
Reply from 188.165.210.113: bytes=32 time=173ms TTL=50
Reply from 188.165.210.113: bytes=32 time=172ms TTL=50
Reply from 188.165.210.113: bytes=32 time=172ms TTL=50

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

C:\Users\Christo>tracert login.truewow.org

Tracing route to login.truewow.org [188.165.210.113]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dlinkrouter [192.168.0.1]
2 12 ms 1 ms 1 ms 192.168.16.5
3 17 ms 16 ms 16 ms 192.168.16.41
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 173 ms 172 ms 172 ms ns309753.ip-188-165-210.eu [188.165.210.113]

Trace complete.

C:\Users\Christo>

vylenz wrote:

Your issue is quite evident with your trace results.
You're encountering problems as soon as your signal leaves your city and goes to the first state-wide transit center.
You're due for a conversation with your Internet Service Provider and ask them what's going on.

Regards.

Thank you.

Heya... writing from Brazil (average latency in game is...250 to 300ms I think? never payed much attention unless it was really laggy lol)

C:\>ping login.truewow.org

Disparando login.truewow.org [188.165.210.113] com 32 bytes de dados:
Resposta de 188.165.210.113: bytes=32 tempo=247ms TTL=45
Resposta de 188.165.210.113: bytes=32 tempo=294ms TTL=45
Resposta de 188.165.210.113: bytes=32 tempo=296ms TTL=45
Resposta de 188.165.210.113: bytes=32 tempo=255ms TTL=45

Estatísticas do Ping para 188.165.210.113:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de
perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 247ms, Máximo = 296ms, Média = 273ms

C:\>tracert login.truewow.org

Rastreando a rota para login.truewow.org [188.165.210.113]
com no máximo 30 saltos:

1 5 ms 3 ms 2 ms 192.168.0.1
2 60 ms 18 ms 25 ms 10.50.160.1
3 50 ms 72 ms 29 ms bd040072.virtua.com.br [189.4.0.114]
4 91 ms 54 ms 64 ms embratel-T0-4-0-6-uacc03.ctamc.embratel.net.br [200.211.44.25]
5 46 ms 14 ms 15 ms ebt-H0-0-0-2-tcore01.ctamr.embratel.net.br [200.244.213.1]
6 138 ms 143 ms 159 ms ebt-BP1424-intl04.mianap.embratel.net.br [200.230.220.106]
7 214 ms 180 ms 201 ms be100-153.mia-mi1-bb1-a9.fl.us [192.99.146.104]
8 224 ms 208 ms 186 ms ash-1-a9.fl.us [142.44.208.189]
9 267 ms 344 ms 265 ms be100-1345.gsw-1-a9.fr.eu [94.23.122.245]
10 247 ms 260 ms 256 ms be102.rbx-g2-nc5.fr.eu [94.23.122.214]
11 * * * Esgotado o tempo limite do pedido.
12 * * * Esgotado o tempo limite do pedido.
13 * * * Esgotado o tempo limite do pedido.
14 287 ms 295 ms 258 ms ns309753.ip-188-165-210.eu [188.165.210.113]

Rastreamento concluído.

C:\>

Caveira wrote: ↑

17 Sep 2019 03:55

Heya... writing from Brazil (average latency in game is...250 to 300ms I think? never payed much attention unless it was really laggy lol)

C:\>ping login.truewow.org

Disparando login.truewow.org [188.165.210.113] com 32 bytes de dados:
Resposta de 188.165.210.113: bytes=32 tempo=247ms TTL=45
Resposta de 188.165.210.113: bytes=32 tempo=294ms TTL=45
Resposta de 188.165.210.113: bytes=32 tempo=296ms TTL=45
Resposta de 188.165.210.113: bytes=32 tempo=255ms TTL=45

Estatísticas do Ping para 188.165.210.113:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de
perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 247ms, Máximo = 296ms, Média = 273ms

C:\>tracert login.truewow.org

Rastreando a rota para login.truewow.org [188.165.210.113]
com no máximo 30 saltos:

1 5 ms 3 ms 2 ms 192.168.0.1
2 60 ms 18 ms 25 ms 10.50.160.1
3 50 ms 72 ms 29 ms bd040072.virtua.com.br [189.4.0.114]
4 91 ms 54 ms 64 ms embratel-T0-4-0-6-uacc03.ctamc.embratel.net.br [200.211.44.25]
5 46 ms 14 ms 15 ms ebt-H0-0-0-2-tcore01.ctamr.embratel.net.br [200.244.213.1]
6 138 ms 143 ms 159 ms ebt-BP1424-intl04.mianap.embratel.net.br [200.230.220.106]
7 214 ms 180 ms 201 ms be100-153.mia-mi1-bb1-a9.fl.us [192.99.146.104]
8 224 ms 208 ms 186 ms ash-1-a9.fl.us [142.44.208.189]
9 267 ms 344 ms 265 ms be100-1345.gsw-1-a9.fr.eu [94.23.122.245]
10 247 ms 260 ms 256 ms be102.rbx-g2-nc5.fr.eu [94.23.122.214]
11 * * * Esgotado o tempo limite do pedido.
12 * * * Esgotado o tempo limite do pedido.
13 * * * Esgotado o tempo limite do pedido.
14 287 ms 295 ms 258 ms ns309753.ip-188-165-210.eu [188.165.210.113]

Rastreamento concluído.

C:\>

Responded via Discord & dealt with.
Issue was most likely caused by local interference from other devices which affected WiFi signal.

I play in the eastern united states and usually have no latency unless others online are experiencing similar issues, but sometimes it's hard to tell if latency is on my end or the server's.
Sometimes it's with spells and abilities but often it's with interacting with objects in the world.
Microsoft Windows [Version 10.0.18362.418]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\Owner>
C:\Users\Owner>ping login.truewow.org

Pinging login.truewow.org [188.165.210.113] with 32 bytes of data:
Reply from 188.165.210.113: bytes=32 time=126ms TTL=51
Reply from 188.165.210.113: bytes=32 time=104ms TTL=51
Reply from 188.165.210.113: bytes=32 time=93ms TTL=51
Reply from 188.165.210.113: bytes=32 time=98ms TTL=51

Ping statistics for 188.165.210.113:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 126ms, Average = 105ms

C:\Users\Owner>tracert login.truewow.org

Tracing route to login.truewow.org [188.165.210.113]
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms 10.0.0.1
2 46 ms 29 ms 10 ms 96.120.65.97
3 16 ms 12 ms 19 ms 162.151.169.45
4 28 ms 18 ms 19 ms be-320-ar01.needham.ma.boston.comcast.net [162.151.151.237]
5 21 ms 21 ms 26 ms be-7015-cr02.newyork.ny.ibone.comcast.net [68.86.90.217]
6 22 ms 21 ms 23 ms be-10203-cr01.newark.nj.ibone.comcast.net [68.86.85.185]
7 35 ms 20 ms 21 ms be-10248-pe02.newark.nj.ibone.comcast.net [68.86.85.82]
8 25 ms 20 ms 22 ms nwk-1-a9.nj.us [142.44.208.137]
9 90 ms 89 ms 85 ms be100-1295.ldn-1-a9.uk.eu [192.99.146.126]
10 103 ms 89 ms 97 ms be100-1041.rbx-g1-nc5.fr.eu [94.23.122.144]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 95 ms 96 ms 96 ms ns309753.ip-188-165-210.eu [188.165.210.113]

Trace complete.

C:\Users\Owner>