Guild Wars 2

The issue is persistent during peak times in all game modes. Getting 140-200ms instead of the usual 70-80ms.
Tried running in both “Gw2-64.exe” -clientport 80" and “Gw2-64.exe” -clientport 443"
Tracert and pathping to the address provided by running “/ip” in game (in wvw) :

C:\Windows\System32>tracert 206.127.146.13

Tracing route to 206-127-146-13.ncsoft.com [206.127.146.13]
over a maximum of 30 hops:

1 1 ms <1 ms 2 ms 192.168.1.2
2 8 ms 9 ms 7 ms 10.13.128.1
3 14 ms 12 ms 10 ms bzq-115-189-146.cust.bezeqint.net [192.115.189.1
46]
4 10 ms 9 ms 10 ms bzq-115-189-145.cust.bezeqint.net [192.115.189.1
45]
5 9 ms 10 ms 8 ms bzq-25-82-82.cust.bezeqint.net [212.25.82.82]
6 9 ms 9 ms 10 ms bzq-25-77-2.cust.bezeqint.net [212.25.77.2]
7 11 ms 9 ms 10 ms bzq-219-189-90.dsl.bezeqint.net [62.219.189.90]

8 49 ms 47 ms 47 ms ae3.mrs10.ip4.gtt.net [141.136.96.141]
9 63 ms 62 ms 63 ms xe-10-0-4.fra61.ip4.gtt.net [89.149.129.194]
10 139 ms 139 ms 141 ms cdnetworks-gw.ip4.gtt.net [77.67.71.122]
11 138 ms 142 ms 141 ms 206-127-157-94.ncsoft.com [206.127.157.94]
12 137 ms 133 ms 137 ms 206-127-157-102.ncsoft.com [206.127.157.102]
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.
______________________________________________________
C:\Windows\System32>pathping -n -q 100 206.127.146.13

Tracing route to 206.127.146.13 over a maximum of 30 hops

0 192.168.1.16
1 192.168.1.2
2 10.13.128.1
3 192.115.189.146
4 192.115.189.145
5 212.25.82.82
6 212.25.77.2
7 62.219.189.90
8 141.136.96.141
9 141.136.105.110
10 77.67.71.122
11 206.127.157.94
12 206.127.157.102
13 * * *
Computing statistics for 300 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.1.16
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.2
0/ 100 = 0% |
2 —- 100/ 100 =100% 100/ 100 =100% 10.13.128.1
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% 192.115.189.146
0/ 100 = 0% |
4 11ms 0/ 100 = 0% 0/ 100 = 0% 192.115.189.145
0/ 100 = 0% |
5 13ms 0/ 100 = 0% 0/ 100 = 0% 212.25.82.82
0/ 100 = 0% |
6 13ms 0/ 100 = 0% 0/ 100 = 0% 212.25.77.2
0/ 100 = 0% |
7 11ms 0/ 100 = 0% 0/ 100 = 0% 62.219.189.90
0/ 100 = 0% |
8 50ms 0/ 100 = 0% 0/ 100 = 0% 141.136.96.141
0/ 100 = 0% |
9 65ms 0/ 100 = 0% 0/ 100 = 0% 141.136.105.110
0/ 100 = 0% |
10 144ms 0/ 100 = 0% 0/ 100 = 0% 77.67.71.122
100/ 100 =100% |
11 —- 100/ 100 =100% 0/ 100 = 0% 206.127.157.94
0/ 100 = 0% |
12 —- 100/ 100 =100% 0/ 100 = 0% 206.127.157.102

Trace complete.
___________________________________________________
From what I can see it is getting bad on your end.

Also experiencing latency issues post 11/21. From stable 70-80 having stable 180-200.

Blinding powder triggered the cd (while not a ability itself) of Signet of agility.
Happened in wvw ONLY, after the balance patch. Blinding powder was set to 7 and Signet of agility was set to 8.
Happened every time, also after client restart.

Workaround:
Swap the two abilities (Signet of agility to 7 and Blinding powder to 8 ). Bug is gone, even if you swap it back to the initial binds.