TrueWoW

rellumb wrote: ↑

13 Apr 2020 23:28

That's a decent ping given the distance from the USA to the server in France. And it shouldn't result in problems if it's always like that.

Connecting from Belgium. Disconnected around 6 times in 1 minute, while doing Naxx on Primal. I have never disconnected from the sever this badly before.

Microsoft Windows [Version 10.0.18363.836]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\WPD_ps>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=8ms TTL=54
Reply from 188.165.210.113: bytes=32 time=7ms TTL=54
Reply from 188.165.210.113: bytes=32 time=7ms TTL=54
Reply from 188.165.210.113: bytes=32 time=7ms TTL=54

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

C:\Users\WPD_ps>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 mymodem.lan [192.168.1.1]
2 151 ms 211 ms 200 ms 1.80-177-91.adsl-dyn.isp.belgacom.be [91.177.80.1]
3 5 ms 5 ms 4 ms ae-65-100.iarstr4.isp.proximus.be [91.183.241.204]
4 5 ms 5 ms 5 ms ae-23-1000.ibrstr6.isp.belgacom.be [91.183.246.114]
5 * * * Request timed out.
6 10 ms 9 ms 9 ms be105.rbx-g1-nc5.fr.eu [178.33.100.200]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 7 ms 7 ms 8 ms ns309753.ip-188-165-210.eu [188.165.210.113]

Trace complete.

I've examined your diagnostic results.

Check for interference from nearby mobile / cordless or power supply devices in proximity to your modem / router. These can include cordless landline phones in the 2.4 to 5.8 ghz range. Other things to check for are smartphones, tablets, etc.

It's also possible that hop # 5 in your trace may be responsible. Whenever transit servers experience malfunctions, lag /DCs/packet loss can occur and are usually are expected.
Such servers handle all traffic between users and the intended destination of their signal packets.
This also puts the issue out of both out of our hands and yours.

One thing is certain.
Your issue doesn't originate from our end.
Contact your ISP for further assistance.

Connecting from Singapore, ping starts spiking to 700~1200ms during peak server periods at 1930~2000hrs

Microsoft Windows [Version 10.0.18362.900]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\User>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=344ms TTL=40
Request timed out.
Reply from 188.165.210.113: bytes=32 time=343ms TTL=40
Reply from 188.165.210.113: bytes=32 time=343ms TTL=40

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

C:\Users\User>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 Singtel-ACPlus [192.168.1.254]
2 2 ms 1 ms 1 ms bb42.60-171-254.singnet.com.sg [42.60.171.254]
3 4 ms 2 ms 2 ms 202.166.123.130
4 1 ms 1 ms 1 ms 202.166.123.129
5 1 ms 1 ms 1 ms ae8-0.qt-cr03.singnet.com.sg [202.166.121.101]
6 2 ms 2 ms 2 ms ae13-0.tp-cr03.singnet.com.sg [202.166.120.109]
7 2 ms 2 ms 2 ms ae4-0.tp-er03.singnet.com.sg [202.166.123.70]
8 2 ms 2 ms 1 ms 203.208.191.113
9 2 ms 2 ms 2 ms 203.208.153.246
10 2 ms 2 ms 2 ms 203.208.158.186
11 2 ms 3 ms 2 ms 203.208.158.18
12 * * * Request timed out.
13 234 ms 234 ms 414 ms be104.rbx-g2-nc5.fr.eu [94.23.122.242]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 243 ms 243 ms 243 ms ns309753.ip-188-165-210.eu [188.165.210.113]

Trace complete.

C:\Users\User>

Staff Edit: Responded in-game & dealt with.

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\nischal ghimire>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=299ms TTL=42
Reply from 188.165.210.113: bytes=32 time=261ms TTL=42
Reply from 188.165.210.113: bytes=32 time=360ms TTL=42
Reply from 188.165.210.113: bytes=32 time=325ms 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 = 261ms, Maximum = 360ms, Average = 311ms

C:\Users\nischal ghimire>tracert login.truewow.org

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

1 8 ms 6 ms 6 ms 192.168.100.1
2 10 ms 7 ms 7 ms lo-bng1.firstlink.net.np [103.104.28.37]
3 8 ms 7 ms 8 ms 18-tx8-br1.firstlink.net.np [103.104.28.18]
4 12 ms 9 ms 8 ms 103.104.28.9
5 * * * Request timed out.
6 11 ms 9 ms 9 ms ae-5-80.42.gwmj-dhbi-01.wlink.com.np [202.79.42.
80]
7 13 ms 17 ms 12 ms be8-32.42.gwmc-lahn-01.wlink.com.np [202.79.42.3
2]
8 14 ms 15 ms 15 ms be7-30.42.gwmc-dkbr-01.wlink.com.np [202.79.42.3
0]
9 276 ms 36 ms 14 ms be8-28.42.gwmc-chpr-01.wlink.com.np [202.79.42.2
8]
10 12 ms 12 ms 12 ms be7-26.42.gwmc-plwa-01.wlink.com.np [202.79.42.2
6]
11 18 ms 15 ms 11 ms ae8-24.42.gwmj-htda-01.wlink.com.np [202.79.42.2
4]
12 16 ms 15 ms 16 ms ae-20-137.41.gwmj-awtd-01.wlink.com.np [202.79.4
1.137]
13 14 ms 13 ms 13 ms ae15-201.41.gw-jwl-core-03.wlink.com.np [202.79.
41.201]
14 13 ms 15 ms 13 ms ae-15-170.40.gw-jwl-core-01.wlink.com.np [202.79
.40.170]
15 13 ms 12 ms 14 ms 103.225.212.161
16 51 ms 52 ms 51 ms ix-xe-3-1-0-1-0.tcore1.mlv-mumbai.as6453.net [18
0.87.38.50]
17 167 ms 168 ms * if-ae-5-2.tcore1.wyn-marseille.as6453.net [80.23
1.217.29]
18 198 ms * 161 ms if-ae-8-1600.tcore1.pye-paris.as6453.net [80.231
.217.6]
19 180 ms 182 ms 182 ms if-ae-11-2.tcore1.pvu-paris.as6453.net [80.231.1
53.49]
20 232 ms 237 ms 236 ms be6453.agr21.par04.atlas.cogentco.com [130.117.1
5.69]
21 238 ms 241 ms 242 ms be3169.ccr31.par04.atlas.cogentco.com [154.54.37
.237]
22 * * * Request timed out.
23 308 ms 318 ms 312 ms be101.par-gsw-sbb1-nc5.fr.eu [94.23.122.215]
24 * * * Request timed out.
25 271 ms 266 ms 273 ms be101.par-gsw-sbb1-nc5.fr.eu [94.23.122.215]
26 * 245 ms * be102.rbx-g2-nc5.fr.eu [94.23.122.214]
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 255 ms 256 ms 251 ms ns309753.ip-188-165-210.eu [188.165.210.113]

Trace complete.

Connectiong from Asia,Nepal
normally in game I am suppose to get 175-185ms but recently I have been getting abouve 360ms

Staff Edit: Responded in-game & dealt with.

Reported in-a-game with Nautilidae and here is a trace report

Microsoft Windows [Version 10.0.19042.685]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Users\SMC>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=44ms TTL=54
Reply from 188.165.210.113: bytes=32 time=50ms TTL=54
Reply from 188.165.210.113: bytes=32 time=43ms TTL=54
Reply from 188.165.210.113: bytes=32 time=47ms TTL=54

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

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

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

1 734 ms 303 ms 167 ms 192.168.0.1
2 24 ms 313 ms 154 ms cable-178-148-252-1.dynamic.sbb.rs [178.148.252.1]
3 58 ms 17 ms 15 ms bg-tp-m-10-be11.sbb.rs [89.216.4.10]
4 12 ms 16 ms * bg-tp-m-0-be102.sbb.rs [89.216.5.8]
5 22 ms 22 ms 21 ms at-vie-r-1-be1.sbb.rs [89.216.5.76]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 46 ms 42 ms 43 ms be103.rbx-g4-nc5.fr.eu [54.36.50.229]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 66 ms 47 ms 54 ms ns309753.ip-188-165-210.eu [188.165.210.113]

Trace complete.

Staff Edit: Responded in-game as well as on forum & dealt with.

obolence wrote: ↑

19 Dec 2020 18:20

Reported in-a-game with Nautilidae and here is a trace report

Microsoft Windows [Version 10.0.19042.685]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Users\SMC>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=44ms TTL=54
Reply from 188.165.210.113: bytes=32 time=50ms TTL=54
Reply from 188.165.210.113: bytes=32 time=43ms TTL=54
Reply from 188.165.210.113: bytes=32 time=47ms TTL=54

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

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

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

1 734 ms 303 ms 167 ms 192.168.0.1
2 24 ms 313 ms 154 ms cable-178-148-252-1.dynamic.sbb.rs [178.148.252.1]
3 58 ms 17 ms 15 ms bg-tp-m-10-be11.sbb.rs [89.216.4.10]
4 12 ms 16 ms * bg-tp-m-0-be102.sbb.rs [89.216.5.8]
5 22 ms 22 ms 21 ms at-vie-r-1-be1.sbb.rs [89.216.5.76]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 46 ms 42 ms 43 ms be103.rbx-g4-nc5.fr.eu [54.36.50.229]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 66 ms 47 ms 54 ms ns309753.ip-188-165-210.eu [188.165.210.113]

Trace complete.

I contacted several players from your region, none of whom seemed to be having the same issue as you.
I recommend you try again later and see if your connection stabilizes.
Good luck.

I am getting "unable to connect error"

Microsoft Windows [Version 10.0.18363.1256]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\admin>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=117ms TTL=48
Reply from 188.165.210.113: bytes=32 time=118ms TTL=48
Reply from 188.165.210.113: bytes=32 time=118ms TTL=48
Reply from 188.165.210.113: bytes=32 time=119ms TTL=48

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

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

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

1 6 ms 1 ms 1 ms 192.168.0.1
2 15 ms 12 ms 27 ms 072-031-136-153.res.spectrum.com [72.31.136.153]
3 15 ms 17 ms 19 ms 072-031-067-076.res.spectrum.com [72.31.67.76]
4 17 ms 17 ms 17 ms bundle-ether36.orld71-car2.bhn.net [72.31.194.110]
5 18 ms 32 ms 17 ms 072-031-067-218.res.spectrum.com [72.31.67.218]
6 28 ms 18 ms 22 ms 0.xe-2-2-1.pr0.atl20.tbone.rr.com [66.109.9.138]
7 34 ms 35 ms 46 ms 0.xe-11-3-3.pr0.dca10.tbone.rr.com [66.109.1.32]
8 52 ms 52 ms 51 ms bu-ether12.asbnva1611w-bcr00.tbone.rr.com [66.109.6.33]
9 41 ms 37 ms 39 ms 66.109.5.117
10 37 ms 42 ms 43 ms ash-1-n7.va.us [142.44.208.194]
11 114 ms 117 ms 115 ms par-gsw-sbb1-nc5.fr.eu [54.36.50.228]
12 126 ms 124 ms 117 ms be103.rbx-g4-nc5.fr.eu [54.36.50.229]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 124 ms 119 ms 118 ms ns309753.ip-188-165-210.eu [188.165.210.113]

Trace complete.

C:\Users\admin>

It was a temporary problem. I can now connect. Please disregard

Disclaimer: I am sure this is posted somewhere else just can't find it.

I attempted to log in to bugtracker, using my forum credentials. It fails and I get a warning that my account may be disabled if I keep trying.

Is it separate credentials?

You can ping me on Discord if necessary - Axis, Andrius, I believe we are already connected.

Edit: Fixed. Move to "Resolved" please

I DC every few seconds after logging in on Brainlicker (Yes I'm the OG Brainlicker, not the other dweeb).

I'm having a heck of a time staying connected. Sometimes I get upwards of a dozen in an hour. Here're my tests as suggested. I'm trying windows 8 compatibility mode and running as an administrator, hoping that might help. I'm playing in the US

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

C:\Users\og353></> CODE: SELECT ALL
Access is denied.

C:\Users\og353>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=131ms TTL=47
Reply from 188.165.210.113: bytes=32 time=126ms TTL=47
Reply from 188.165.210.113: bytes=32 time=127ms TTL=47
Reply from 188.165.210.113: bytes=32 time=127ms 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 = 126ms, Maximum = 131ms, Average = 127ms

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

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

1 4 ms 3 ms 4 ms RAC2V1S [192.168.1.1]
2 42 ms 22 ms 42 ms 142-254-130-133.inf.spectrum.com [142.254.130.133]
3 39 ms 43 ms 26 ms 70.125.216.105
4 21 ms 20 ms 23 ms agg25.dllmtxkd02r.texas.rr.com [24.175.50.21]
5 23 ms 32 ms 21 ms agg22.dllbtxlb02r.texas.rr.com [24.175.36.248]
6 20 ms 20 ms 19 ms agg21.hstqtxl301r.texas.rr.com [24.175.49.8]
7 41 ms 25 ms 21 ms bu-ether16.hstqtx0209w-bcr00.tbone.rr.com [66.109.6.108]
8 42 ms 43 ms 42 ms 66.109.9.28
9 43 ms 43 ms 43 ms 0.ge-0-0-0.ar0.den30.tbone.rr.com [66.109.6.150]
10 44 ms 45 ms 54 ms 66.109.5.117
11 65 ms 53 ms 47 ms ash-1-n7.va.us [142.44.208.194]
12 126 ms 127 ms 125 ms be105.par-gsw-sbb1-nc5.fr.eu [94.23.122.245]
13 133 ms 130 ms 139 ms be102.rbx-g2-nc5.fr.eu [94.23.122.214]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 144 ms 128 ms 132 ms ns309753.ip-188-165-210.eu [188.165.210.113]

Trace complete.

Microsoft Windows [Version 10.0.19043.1165]
(c) 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=93ms TTL=52
Reply from 188.165.210.113: bytes=32 time=90ms TTL=52
Reply from 188.165.210.113: bytes=32 time=91ms TTL=52
Reply from 188.165.210.113: bytes=32 time=91ms TTL=52

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

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

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

1 4 ms 3 ms 3 ms 10.0.0.1
2 13 ms 11 ms 22 ms 96.120.65.97
3 27 ms 19 ms 24 ms 68.87.154.237
4 15 ms 15 ms 15 ms be-320-ar01.needham.ma.boston.comcast.net [162.151.151.237]
5 22 ms 19 ms 21 ms be-32021-cs02.newyork.ny.ibone.comcast.net [96.110.42.5]
6 23 ms 19 ms 17 ms be-1212-cr12.newyork.ny.ibone.comcast.net [96.110.35.134]
7 21 ms 26 ms 21 ms be-302-cr11.newark.nj.ibone.comcast.net [96.110.36.149]
8 23 ms 24 ms 20 ms be-1211-cs02.newark.nj.ibone.comcast.net [96.110.35.69]
9 22 ms 23 ms 19 ms be-2203-pe03.newark.nj.ibone.comcast.net [96.110.37.70]
10 20 ms 23 ms 26 ms be100-153.nwk-5-a9.nj.us [192.99.146.53]
11 93 ms 97 ms 90 ms be104.lon-drch-sbb1-nc5.uk.eu [192.99.146.132]
12 101 ms 107 ms 97 ms be101.rbx-g2-nc5.fr.eu [213.251.130.102]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 94 ms 89 ms 90 ms ns309753.ip-188-165-210.eu [188.165.210.113]

Trace complete.

C:\WINDOWS\system32>
I play in east coast NA and I don't experience lag all the time. Usually when I do, it involves spells and abilities (I will click the key I have an ability bound to, and a few seconds will pass before it actually casts, or I have to click it multiple times to get it to cast.) Occasionally I will experience lag with movement as well, but this is usually only when many other people on the server are experiencing lag as well. I play on a laptop plugged into an ethernet cable.

Lags never were an issue for me. Kyiv, Ukraine. Mostly less than 40ms.

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

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

Pinging login.truewow.org [188.165.193.175] with 32 bytes of data:
Reply from 188.165.193.175: bytes=32 time=237ms TTL=49
Reply from 188.165.193.175: bytes=32 time=247ms TTL=49
Reply from 188.165.193.175: bytes=32 time=249ms TTL=49
Reply from 188.165.193.175: bytes=32 time=249ms TTL=49

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

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

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

1 <1 ms <1 ms <1 ms 192.168.100.1
2 2 ms 2 ms 1 ms 100.64.0.0
3 2 ms * 2 ms 10.10.3.1
4 3 ms 3 ms 3 ms 103.104.28.29
5 7 ms 7 ms 7 ms 103.104.30.22
6 7 ms 7 ms 7 ms 103.225.212.177
7 10 ms 10 ms 9 ms 103.225.212.122
8 248 ms 248 ms 248 ms 116.119.68.58
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 245 ms 245 ms 245 ms be101.rbx-g1-nc5.fr.eu [94.23.122.144]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 249 ms 248 ms 248 ms

I normally get 175 MS in game and past 2 days its not stable whe nI login it sometimes goes up to 11k ms