Guild Wars 2

DemonSeed.3528:

Joker.4328:

now i get 235ms ping, and i don’t think this is TM Nut’s fault, as there are players from other countries having this same issue as well.

Anyway, thank you ANET if you’ve done something.

No difference on my end (eu).

I pinged the ip above and was getting 285ms though so for that server it’s probably ok.

Can you guys using tmnet tell me what pings you get from these ip’s?

206.127.159.169
206.127.159.151
206.127.159.166
206.127.159.123
206.127.159.150
206.127.159.153
206.127.146.126
206.127.146.39

These are just random ip’s I’ve been connected to in game when doing pve/wvw that I check up with to see general latency with anet servers. If you guys are getting about 240ms ping with any of those servers, can you tell me what ip address range from tmnet you are on? (for example right now I am on 175.144..). Thanks!

Ping statistics for 206.127.159.169:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 386ms, Maximum = 412ms, Average = 396ms

Ping statistics for 206.127.159.151:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 366ms, Maximum = 392ms, Average = 376ms

No time out, but apparently a bit longer ping.

What i got is 64.25.38.xxx

now i get 235ms ping, and i don’t think this is TM Nut’s fault, as there are players from other countries having this same issue as well.

Anyway, thank you ANET if you’ve done something.

Thanks, just decided to grab a PS4 for the holiday due to below result.

Tracing route to 64.25.38-81.ncsoft.com [64.25.38.81]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 23 ms 22 ms 22 ms 115.132.111.114
3 * * * Request timed out.
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 * * * 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.

Just curious, is ANET really looking at our threads? Waiting for 3 days and never seen any reply from them… I’m going to find other game to hanging around…

Yes, same here. Experiencing massive lag from Malaysia Unifi 30mb speed. A lot of time out.
Reply from 64.25.38.81: bytes=32 time=305ms TTL=118
Reply from 64.25.38.81: bytes=32 time=242ms TTL=118
Reply from 64.25.38.81: bytes=32 time=241ms TTL=118
Reply from 64.25.38.81: bytes=32 time=241ms TTL=118
Reply from 64.25.38.81: bytes=32 time=421ms TTL=118
Reply from 64.25.38.81: bytes=32 time=514ms TTL=118
Request timed out.
Request timed out.
Reply from 64.25.38.81: bytes=32 time=513ms TTL=118
Reply from 64.25.38.81: bytes=32 time=513ms TTL=118
Reply from 64.25.38.81: bytes=32 time=513ms TTL=118
Reply from 64.25.38.81: bytes=32 time=512ms TTL=118
Request timed out.
Request timed out.
Reply from 64.25.38.81: bytes=32 time=513ms TTL=118
Reply from 64.25.38.81: bytes=32 time=513ms TTL=118
Request timed out.
Reply from 64.25.38.81: bytes=32 time=514ms TTL=118
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.25.38.81: bytes=32 time=517ms TTL=118
Request timed out.
Request timed out.
Reply from 64.25.38.81: bytes=32 time=489ms TTL=118
Reply from 64.25.38.81: bytes=32 time=368ms TTL=118
Reply from 64.25.38.81: bytes=32 time=276ms TTL=118
Reply from 64.25.38.81: bytes=32 time=242ms TTL=118
Request timed out.
Request timed out.
Request timed out.
Reply from 64.25.38.81: bytes=32 time=513ms TTL=118
Reply from 64.25.38.81: bytes=32 time=513ms TTL=118
Reply from 64.25.38.81: bytes=32 time=512ms TTL=118
Request timed out.
Reply from 64.25.38.81: bytes=32 time=514ms TTL=118
Reply from 64.25.38.81: bytes=32 time=514ms TTL=118
Request timed out.
Reply from 64.25.38.81: bytes=32 time=513ms TTL=118
Reply from 64.25.38.81: bytes=32 time=514ms TTL=118
Request timed out.
Reply from 64.25.38.81: bytes=32 time=515ms TTL=118
Reply from 64.25.38.81: bytes=32 time=513ms TTL=118
Reply from 64.25.38.81: bytes=32 time=514ms TTL=118
Request timed out.
Reply from 64.25.38.81: bytes=32 time=515ms TTL=118
Reply from 64.25.38.81: bytes=32 time=517ms TTL=118
Reply from 64.25.38.81: bytes=32 time=517ms TTL=118
Request timed out.
Request timed out.
Reply from 64.25.38.81: bytes=32 time=517ms TTL=118
Reply from 64.25.38.81: bytes=32 time=517ms TTL=118
Request timed out.
Request timed out.
Request timed out.
Reply from 64.25.38.81: bytes=32 time=516ms TTL=118
Request timed out.
Reply from 64.25.38.81: bytes=32 time=516ms TTL=118
Request timed out.
Reply from 64.25.38.81: bytes=32 time=515ms TTL=118
Request timed out.

Ping statistics for 64.25.38.81:
Packets: Sent = 62, Received = 36, Lost = 26 (41% loss),
Approximate round trip times in milli-seconds:
Minimum = 241ms, Maximum = 517ms, Average = 464ms

Why this lag right after the patch? Does the patch having anything to do with the lag?