Guild Wars 2

I’ve recently started playing gw2 again, and have been experiencing some connectivity issues. These are partly on my end, but occassionally speedtests come out clear while the in-game connectivity and increased ping suggest otherwise.

So I’ve followed the sites’ guidelines to create a GW2 Diagnostic shortcut, and I would like to verify whether or not these results indicate the problem is on my end:

Tracing route to 64.25.33-1.ncsoft.com [64.25.39.1]
over a maximum of 30 hops:
0 Computarella [192.168.0.103]
1 192.168.0.1
2 001-136-128-083.dynamic.caiway.nl [83.128.136.1]
3 * cn-maas-kps-cr02-gb01.kabelfoon.nl [62.45.103.201]
4 * cn-bgh-agw-cr10-gi2-23-vln756.caiw.net [62.45.103.9]
5 cn-ah-tvl-cr15-be10.caiw.net [62.45.63.117]
6 cn-asd-kbw-cr15-be8.caiw.net [62.45.63.109]
7 * adm-b2-link.telia.net [62.115.145.128]
8 adm-bb4-link.telia.net [80.91.253.183]
9 ldn-bb2-link.telia.net [213.155.136.96]
10 nyk-bb2-link.telia.net [213.155.133.7]
11 * dls-b22-link.telia.net [62.115.120.175]
12 dls-b22-link.telia.net [62.115.120.87]
13 ncsoft-ic-317391-dls-b22.c.telia.net.10.115.62.in-addr.arpa [62.115.10.106]
14 64.25.32-26.ncsoft.com [64.25.32.26]
15 * 64.25.32-26.ncsoft.com [64.25.32.26]
16 64.25.33-1.ncsoft.com [64.25.39.1]

Computing statistics for 200 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Computarella [192.168.0.103]
0/ 50 = 0% |
1 0ms 0/ 50 = 0% 0/ 50 = 0% 192.168.0.1
5/ 50 = 10% |
2 47ms 8/ 50 = 16% 3/ 50 = 6% 001-136-128-083.dynamic.caiway.nl [83.128.136.1]
0/ 50 = 0% |
3 42ms 9/ 50 = 18% 4/ 50 = 8% cn-maas-kps-cr02-gb01.kabelfoon.nl [62.45.103.201]
0/ 50 = 0% |
4 43ms 6/ 50 = 12% 1/ 50 = 2% cn-bgh-agw-cr10-gi2-23-vln756.caiw.net [62.45.103.9]
0/ 50 = 0% |
5 43ms 5/ 50 = 10% 0/ 50 = 0% cn-ah-tvl-cr15-be10.caiw.net [62.45.63.117]
2/ 50 = 4% |
6 44ms 7/ 50 = 14% 0/ 50 = 0% cn-asd-kbw-cr15-be8.caiw.net [62.45.63.109]
0/ 50 = 0% |
7 49ms 9/ 50 = 18% 2/ 50 = 4% adm-b2-link.telia.net [62.115.145.128]
0/ 50 = 0% |
8 45ms 7/ 50 = 14% 0/ 50 = 0% adm-bb4-link.telia.net [80.91.253.183]
2/ 50 = 4% |
9 64ms 9/ 50 = 18% 0/ 50 = 0% ldn-bb2-link.telia.net [213.155.136.96]
7/ 50 = 14% |
10 128ms 16/ 50 = 32% 0/ 50 = 0% nyk-bb2-link.telia.net [213.155.133.7]
2/ 50 = 4% |
11 165ms 18/ 50 = 36% 0/ 50 = 0% dls-b22-link.telia.net [62.115.120.175]
2/ 50 = 4% |
12 156ms 23/ 50 = 46% 3/ 50 = 6% dls-b22-link.telia.net [62.115.120.87]
0/ 50 = 0% |
13 —- 50/ 50 =100% 30/ 50 = 60% ncsoft-ic-317391-dls-b22.c.telia.net.10.115.62.in-addr.arpa [62.115.10.106]
0/ 50 = 0% |
14 —- 50/ 50 =100% 30/ 50 = 60% 64.25.32-26.ncsoft.com [64.25.32.26]
0/ 50 = 0% |
15 —- 50/ 50 =100% 30/ 50 = 60% 64.25.32-26.ncsoft.com [64.25.32.26]
0/ 50 = 0% |
16 183ms 20/ 50 = 40% 0/ 50 = 0% 64.25.33-1.ncsoft.com [64.25.39.1]

Trace complete.
—> pathping -w 500 -q 50 -4 206.127.158.1 <--

Tracing route to 206-127-158-1.ncsoft.com [206.127.158.1]
over a maximum of 30 hops:
0 Computarella [192.168.0.103]
1 192.168.0.1
2 001-136-128-083.dynamic.caiway.nl [83.128.136.1]
3 * cn-maas-kps-cr02-gb01.kabelfoon.nl [62.45.103.201]
4 * cn-bgh-agw-cr10-gi2-23-vln756.caiw.net [62.45.103.9]
5 cn-ah-tvl-cr15-be10.caiw.net [62.45.63.117]
6 cn-asd-kbw-cr15-be8.caiw.net [62.45.63.109]
7 * ae1-108.ams12.ip4.gtt.net [77.67.72.133]
8 et-3-1-0.fra23.ip4.gtt.net [141.136.105.238]
9 89.149.164.42
10 206-127-157-86.ncsoft.com [206.127.157.86]
11 206-127-158-1.ncsoft.com [206.127.158.1]

Computing statistics for 137 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Computarella [192.168.0.103]
0/ 50 = 0% |
1 0ms 0/ 50 = 0% 0/ 50 = 0% 192.168.0.1
6/ 50 = 12% |
2 41ms 9/ 50 = 18% 3/ 50 = 6% 001-136-128-083.dynamic.caiway.nl [83.128.136.1]
0/ 50 = 0% |
3 35ms 6/ 50 = 12% 0/ 50 = 0% cn-maas-kps-cr02-gb01.kabelfoon.nl [62.45.103.201]
0/ 50 = 0% |
4 38ms 6/ 50 = 12% 0/ 50 = 0% cn-bgh-agw-cr10-gi2-23-vln756.caiw.net [62.45.103.9]
0/ 50 = 0% |
5 47ms 7/ 50 = 14% 1/ 50 = 2% cn-ah-tvl-cr15-be10.caiw.net [62.45.63.117]
0/ 50 = 0% |
6 50ms 6/ 50 = 12% 0/ 50 = 0% cn-asd-kbw-cr15-be8.caiw.net [62.45.63.109]
1/ 50 = 2% |
7 44ms 8/ 50 = 16% 1/ 50 = 2% ae1-108.ams12.ip4.gtt.net [77.67.72.133]
0/ 50 = 0% |
8 54ms 7/ 50 = 14% 0/ 50 = 0% et-3-1-0.fra23.ip4.gtt.net [141.136.105.238]
1/ 50 = 2% |
9 45ms 46/ 50 = 92% 38/ 50 = 76% 89.149.164.42
0/ 50 = 0% |
10 —- 50/ 50 =100% 42/ 50 = 84% 206-127-157-86.ncsoft.com [206.127.157.86]
0/ 50 = 0% |
11 56ms 8/ 50 = 16% 0/ 50 = 0% 206-127-158-1.ncsoft.com [206.127.158.1]

Trace complete.
—> pathping -w 500 -q 50 -4 52.85.246.244 <--

Tracing route to server-52-85-246-244.ams50.r.cloudfront.net [52.85.246.244]
over a maximum of 30 hops:
0 Computarella [192.168.0.103]
1 192.168.0.1
2 001-136-128-083.dynamic.caiway.nl [83.128.136.1]
3 * cn-maas-kps-cr02-gb01.kabelfoon.nl [62.45.103.201]
4 cn-bgh-agw-cr10-gi2-23-vln756.caiw.net [62.45.103.9]
5 cn-ah-tvl-cr15-be10.caiw.net [62.45.63.117]
6 cn-asd-kbw-cr15-be8.caiw.net [62.45.63.109]
7 amsix01-ams1.amazon.com [80.249.210.100]
8 54.239.114.58
9 54.239.114.65
10 176.32.124.12
11 * * *
Computing statistics for 125 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Computarella [192.168.0.103]
0/ 50 = 0% |
1 0ms 0/ 50 = 0% 0/ 50 = 0% 192.168.0.1
0/ 50 = 0% |
2 15ms 0/ 50 = 0% 0/ 50 = 0% 001-136-128-083.dynamic.caiway.nl [83.128.136.1]
0/ 50 = 0% |
3 16ms 1/ 50 = 2% 1/ 50 = 2% cn-maas-kps-cr02-gb01.kabelfoon.nl [62.45.103.201]
0/ 50 = 0% |
4 13ms 0/ 50 = 0% 0/ 50 = 0% cn-bgh-agw-cr10-gi2-23-vln756.caiw.net [62.45.103.9]
0/ 50 = 0% |
5 19ms 0/ 50 = 0% 0/ 50 = 0% cn-ah-tvl-cr15-be10.caiw.net [62.45.63.117]
0/ 50 = 0% |
6 19ms 5/ 50 = 10% 5/ 50 = 10% cn-asd-kbw-cr15-be8.caiw.net [62.45.63.109]
0/ 50 = 0% |
7 22ms 0/ 50 = 0% 0/ 50 = 0% amsix01-ams1.amazon.com [80.249.210.100]
50/ 50 =100% |
8 —- 50/ 50 =100% 0/ 50 = 0% 54.239.114.58
0/ 50 = 0% |
9 —- 50/ 50 =100% 0/ 50 = 0% 54.239.114.65
0/ 50 = 0% |
10 —- 50/ 50 =100% 0/ 50 = 0% 176.32.124.12

Trace complete.
Section completed in 363.02 seconds

These traces all look to me like they’re doing alright up until they’re reaching or getting close to the ncsoft servers. Another thing I noticed is that alot of the signal slowdown or loss happens in telia.net servers. After looking into them, it seems they are a major backbown for internet communication, but also a cause for bad connectivity through their servers across many games, including games from ncsoft, blizzard and riot games.

Any ideas on how to go from here? Am I wrong in my conclusions, and if so what do you recon is the problem? If not, is there a way to bypass telia servers, or would that have to be done on Arenanets’ side? And lastly, does anyone else have similar experiences to share regarding this?

Thanks for reading

Create a support ticket and provide those same details. Besides getting individual attention, if your suspicions are correct, ANet can use your data when they open their own ticket(s) with their ISP.

https://help.guildwars2.com/anonymous_requests/new

Many, many players have issue with Telia. Some use a VPN to create a different path to the ArenaNet servers.

Good luck.

It’s getting pretty ridiculous. Straight out to the error report at least 5-6x per day. Four times the other day from PvP matches. :/

Hey guys, thanks for your replies so far. I’ve included this data with a support ticket sent to the gw2 support team. I’ve also linked this forum thread in that ticket, so keep replying here with similar experiences, guys: it helps!

I will update here as it continues, hopefully something helpful comes out of it.

Skynet.7201:

It’s getting pretty ridiculous. Straight out to the error report at least 5-6x per day. Four times the other day from PvP matches. :/

An error report would mean a crash occurred. That is not related to this topic.