Guild Wars 2

Today I’m experiencing huge lag. I usually have around 36ms ping towards gw2 servers, but today I’m at 2000ms ping average. Tested with ping command on cmd and half of the packets don’t come back.
Tested my connection speed and it’s fine. I’m only having this problem on gw2 and today.

It makes even impossible to run around Dry Top since I get rubberbanded everywhere.

Here is the tracert from windows cmd
Posted 2, the first going well, the second one where probably is the issue. Made many of them, and the problem is always on those 2 nodes (when there is a problem).

I’m running a test now with -diag parameter on GW2.exe

Will post soon

Here is the -diag traceroute. Yep, problems there and after ncsoft node.

================ = Tracing network paths (about 10 mins) ================

• pathping -w 500 -q 50 -4 64.25.39.1 <--*

Traccia route verso 64.25.33-1.ncsoft.com [64.25.39.1]
su un massimo di 30 punti di passaggio:
0 Gundam.lan [192.168.1.65]
1 dsldevice.lan [192.168.1.254]
2 10.88.246.194
3 10.251.178.49
4 10.251.174.24
5 10.251.175.1
6 10.247.125.133
7 10.251.179.186
8 10.1.152.2
9 10.254.0.137
10 10.254.12.161
11 93.57.68.102
12 93.57.68.14
13 * 62-101-124-73.fastres.net [62.101.124.73]
14 mno-b2-link.telia.net [62.115.55.117]
15 prs-bb3-link.telia.net [62.115.135.72]
16 ldn-bb3-link.telia.net [62.115.115.21]
17 ash-bb3-link.telia.net [80.91.246.68]
18 dls-b21-link.telia.net [80.91.252.122]
19 ncsoft-ic-307708-dls-b21.c.telia.net.10.115.62.in-addr.arpa [62.115.10.106]
20 64.25.32-9.ncsoft.com [64.25.32.9]
21 * 64.25.32-26.ncsoft.com [64.25.32.26]
22 64.25.33-1.ncsoft.com [64.25.39.1]

Statistiche di calcolo per 275 secondi…
Da orig. a qui questo nodo/collegamento
Hop RTT Persi/Inv.= Pct Persi/Inv.= Pct Indir.
0 Gundam.lan [192.168.1.65]
0/ 50 = 0% |
1 0ms 0/ 50 = 0% 0/ 50 = 0% dsldevice.lan [192.168.1.254]
0/ 50 = 0% |
2 0ms 0/ 50 = 0% 0/ 50 = 0% 10.88.246.194
0/ 50 = 0% |
3 0ms 0/ 50 = 0% 0/ 50 = 0% 10.251.178.49
0/ 50 = 0% |
4 1ms 0/ 50 = 0% 0/ 50 = 0% 10.251.174.24
0/ 50 = 0% |
5 1ms 0/ 50 = 0% 0/ 50 = 0% 10.251.175.1
0/ 50 = 0% |
6 1ms 0/ 50 = 0% 0/ 50 = 0% 10.247.125.133
0/ 50 = 0% |
7 0ms 0/ 50 = 0% 0/ 50 = 0% 10.251.179.186
0/ 50 = 0% |
8 0ms 0/ 50 = 0% 0/ 50 = 0% 10.1.152.2
1/ 50 = 2% |
9 —- 50/ 50 =100% 49/ 50 = 98% 10.254.0.137
0/ 50 = 0% |
10 —- 50/ 50 =100% 49/ 50 = 98% 10.254.12.161
0/ 50 = 0% |
11 —- 50/ 50 =100% 49/ 50 = 98% 93.57.68.102
0/ 50 = 0% |
12 —- 50/ 50 =100% 49/ 50 = 98% 93.57.68.14
0/ 50 = 0% |
13 14ms 1/ 50 = 2% 0/ 50 = 0% 62-101-124-73.fastres.net [62.101.124.73]
2/ 50 = 4% |
14 12ms 3/ 50 = 6% 0/ 50 = 0% mno-b2-link.telia.net [62.115.55.117]
3/ 50 = 6% |
15 30ms 6/ 50 = 12% 0/ 50 = 0% prs-bb3-link.telia.net [62.115.135.72]
9/ 50 = 18% |
16 38ms 15/ 50 = 30% 0/ 50 = 0% ldn-bb3-link.telia.net [62.115.115.21]
3/ 50 = 6% |
17 145ms 39/ 50 = 78% 21/ 50 = 42% ash-bb3-link.telia.net [80.91.246.68]
0/ 50 = 0% |
18 151ms 21/ 50 = 42% 3/ 50 = 6% dls-b21-link.telia.net [80.91.252.122]
0/ 50 = 0% |
19 —- 50/ 50 =100% 32/ 50 = 64% ncsoft-ic-307708-dls-b21.c.telia.net.10.115.62.in-addr.arpa [62.115.10.106]
0/ 50 = 0% |
20 141ms 20/ 50 = 40% 2/ 50 = 4% 64.25.32-9.ncsoft.com [64.25.32.9]
0/ 50 = 0% |
21 —- 50/ 50 =100% 32/ 50 = 64% 64.25.32-26.ncsoft.com [64.25.32.26]
0/ 50 = 0% |
22 144ms 18/ 50 = 36% 0/ 50 = 0% 64.25.33-1.ncsoft.com [64.25.39.1]

Traccia completata.

• pathping -w 500 -q 50 -4 206.127.158.1 <--*

Traccia route verso 206-127-158-1.ncsoft.com [206.127.158.1]
su un massimo di 30 punti di passaggio:
0 Gundam.lan [192.168.1.65]
1 dsldevice.lan [192.168.1.254]
2 10.88.246.194
3 10.251.178.49
4 10.251.174.24
5 10.251.175.1
6 10.247.125.133
7 10.251.179.218
8 10.1.154.146
9 10.254.9.81
10 10.254.12.161
11 93.57.68.102
12 93.57.68.14
13 89.96.200.114
14 mno-b2-link.telia.net [62.115.55.117]
15 ffm-bb1-link.telia.net [62.115.134.34]
16 * ffm-b1-link.telia.net [213.155.130.227]
17 ncsoft-ic-306349-ffm-b11.c.telia.net [62.115.43.74]
18 206-127-157-86.ncsoft.com [206.127.157.86]
19 206-127-158-1.ncsoft.com [206.127.158.1]

Statistiche di calcolo per 237 secondi…
Da orig. a qui questo nodo/collegamento
Hop RTT Persi/Inv.= Pct Persi/Inv.= Pct Indir.
0 Gundam.lan [192.168.1.65]
0/ 50 = 0% |
1 0ms 0/ 50 = 0% 0/ 50 = 0% dsldevice.lan [192.168.1.254]
0/ 50 = 0% |
2 0ms 0/ 50 = 0% 50/ 50 = 0% 10.88.246.194
0/ 50 = 0% |
3 0ms 0/ 50 = 0% 0/ 50 = 0% 10.251.178.49
0/ 50 = 0% |
4 1ms 0/ 50 = 0% 0/ 50 = 0% 10.251.174.24
0/ 50 = 0% |
5 1ms 0/ 50 = 0% 0/ 50 = 0% 10.251.175.1
0/ 50 = 0% |
6 1ms 0/ 50 = 0% 0/ 50 = 0% 10.247.125.133
0/ 50 = 0% |
7 0ms 0/ 50 = 0% 0/ 50 = 0% 10.251.179.218
1/ 50 = 2% |
8 0ms 1/ 50 = 2% 0/ 50 = 0% 10.1.154.146
1/ 50 = 2% |
9 —- 50/ 50 =100% 48/ 50 = 96% 10.254.9.81
0/ 50 = 0% |
10 —- 50/ 50 =100% 48/ 50 = 96% 10.254.12.161
0/ 50 = 0% |
11 —- 50/ 50 =100% 48/ 50 = 96% 93.57.68.102
0/ 50 = 0% |
12 —- 50/ 50 =100% 48/ 50 = 96% 93.57.68.14
0/ 50 = 0% |
13 —- 50/ 50 =100% 48/ 50 = 96% 89.96.200.114
0/ 50 = 0% |
14 11ms 2/ 50 = 4% 0/ 50 = 0% mno-b2-link.telia.net [62.115.55.117]
1/ 50 = 2% |
15 37ms 16/ 50 = 32% 13/ 50 = 26% ffm-bb1-link.telia.net [62.115.134.34]
0/ 50 = 0% |
16 27ms 10/ 50 = 20% 7/ 50 = 14% ffm-b1-link.telia.net [213.155.130.227]
0/ 50 = 0% |
17 —- 50/ 50 =100% 47/ 50 = 94% ncsoft-ic-306349-ffm-b11.c.telia.net [62.115.43.74]
0/ 50 = 0% |
18 —- 50/ 50 =100% 47/ 50 = 94% 206-127-157-86.ncsoft.com [206.127.157.86]
0/ 50 = 0% |
19 25ms 3/ 50 = 6% 0/ 50 = 0% 206-127-158-1.ncsoft.com [206.127.158.1]

Traccia completata.

• pathping -w 500 -q 50 -4 93.188.134.109 <--*

Traccia route verso 93.188.134.109 su un massimo di 30 punti di passaggio

0 Gundam.lan [192.168.1.65]
1 dsldevice.lan [192.168.1.254]
2 10.88.246.194
3 10.251.178.49
4 10.251.174.24
5 10.251.175.1
6 10.247.125.133
7 10.251.179.194
8 10.1.154.93
9 10.254.9.85
10 10.254.1.97
11 93.57.68.129
12 93.57.68.10
13 89.96.200.110
14 mno-b2-link.telia.net [62.115.55.117]
15 cdnetwork-ic-302145-mno-b2.c.telia.net [213.248.71.114]
16 * 93.188.134.109

Statistiche di calcolo per 200 secondi…
Da orig. a qui questo nodo/collegamento
Hop RTT Persi/Inv.= Pct Persi/Inv.= Pct Indir.
0 Gundam.lan [192.168.1.65]
0/ 50 = 0% |
1 0ms 0/ 50 = 0% 0/ 50 = 0% dsldevice.lan [192.168.1.254]
0/ 50 = 0% |
2 0ms 0/ 50 = 0% 0/ 50 = 0% 10.88.246.194
0/ 50 = 0% |
3 1ms 0/ 50 = 0% 0/ 50 = 0% 10.251.178.49
0/ 50 = 0% |
4 1ms 0/ 50 = 0% 0/ 50 = 0% 10.251.174.24
0/ 50 = 0% |
5 1ms 0/ 50 = 0% 0/ 50 = 0% 10.251.175.1
0/ 50 = 0% |
6 1ms 0/ 50 = 0% 0/ 50 = 0% 10.247.125.133
0/ 50 = 0% |
7 0ms 0/ 50 = 0% 0/ 50 = 0% 10.251.179.194
0/ 50 = 0% |
8 0ms 0/ 50 = 0% 0/ 50 = 0% 10.1.154.93
1/ 50 = 2% |
9 —- 50/ 50 =100% 49/ 50 = 98% 10.254.9.85
0/ 50 = 0% |
10 —- 50/ 50 =100% 49/ 50 = 98% 10.254.1.97
0/ 50 = 0% |
11 —- 50/ 50 =100% 49/ 50 = 98% 93.57.68.129
0/ 50 = 0% |
12 —- 50/ 50 =100% 49/ 50 = 98% 93.57.68.10
0/ 50 = 0% |
13 —- 50/ 50 =100% 49/ 50 = 98% 89.96.200.110
0/ 50 = 0% |
14 11ms 1/ 50 = 2% 0/ 50 = 0% mno-b2-link.telia.net [62.115.55.117]
1/ 50 = 2% |
15 15ms 5/ 50 = 10% 3/ 50 = 6% cdnetwork-ic-302145-mno-b2.c.telia.net [213.248.71.114]
0/ 50 = 0% |
16 11ms 2/ 50 = 4% 0/ 50 = 0% 93.188.134.109

Traccia completata.
Section completed in 716.18 seconds

I have the same problem. It is impossible to play

The problem seems to be on the route to 206.127.159.XXX.
Now I’m on 206.127.146.62 and it seems fine with avg 40ms ping. Did a tracert and the difference is the ffm-bb1-link-etc…

I’m having latency problems as well. My average ping is around 250 ms but it is playable and responsive. But lately I’m getting bad connections to the game servers, as in 3,000 ms lag spikes, it’s unplayable.

Ping results:

Ping statistics for 64.25.33.44:
Packets: Sent = 100, Received = 83, Lost = 17 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 246ms, Maximum = 259ms, Average = 247ms

Trace route results:

Tracing route to 64.25.33-44.ncsoft.com [64.25.33.44]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms
2 20 ms 19 ms 31 ms
3 21 ms 20 ms 21 ms
4 19 ms 20 ms 19 ms
5 19 ms 18 ms 19 ms
6 168 ms 171 ms 163 ms sea-b1-link.telia.net [80.239.135.33]
7 176 ms 176 ms 176 ms sjo-b21-link.telia.net [62.115.135.24]
8 230 ms 229 ms 228 ms las-b21-link.telia.net [213.155.135.186]
9 247 ms 246 ms 247 ms dls-b21-link.telia.net [213.248.80.14]
10 250 ms 250 ms 250 ms 62.115.10.106
11 250 ms 251 ms 249 ms 64.25.32-9.ncsoft.com [64.25.32.9]
12 * * 251 ms 64.25.32-26.ncsoft.com [64.25.32.26]
13 262 ms 261 ms 260 ms 64.25.32-82.ncsoft.com [64.25.32.82]
14 246 ms 246 ms 247 ms 64.25.33-44.ncsoft.com [64.25.33.44]

Trace complete.

I tested each of the hops. The problem starts with 213.155.135.186:

Ping statistics for 213.155.135.186:
Packets: Sent = 100, Received = 91, Lost = 9 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 227ms, Maximum = 247ms, Average = 228ms

kittening telia.net. -.- I hope they resolve this problem soon. I’m getting so desperate, I might even try WTFast. Can arenanet contact telia.net on our behalf?

Its the same s…t with every beta or what ever. Every 2 weeks I been getting this problems in the weekend. I Thought it was my PC but it isn’t. Wait for 3 days to pass and you will get back to normal. I start to have this problem from weeks ago probable when they made gw2 for free or when they start patching the game for Hot to test betas. So you can imagine from a week you can play only 4 to 5 days with that lag cause you cant do nothing apart running in empty maps.

However they will say “its not our problem the error that you get its from router , pc , or your Isp”, but if that was true than I wont have my connection and lag back to normal after 2 or 3 days. For me its more that or a lot of people are playing now as it is free so the servers and their routers cant hold all that traffic or because of betas, or lack of maintenance.

Kidel.2057:

The problem seems to be on the route to 206.127.159.XXX.
Now I’m on 206.127.146.62 and it seems fine with avg 40ms ping. Did a tracert and the difference is the ffm-bb1-link-etc…

Your traceroutes are clean, but are you on a campus or something? There are too many 10.xxx.xxx.xxx addresses before you actually hit the internet. So the Latency could be a Firewall in your network that is slowing Packets going to NCSofts servers.