Guild Wars 2

I’ve been having frequent d/cs, like many others, for months now. I’ve tried rebooting my router, re-installing GW2, diagnostic, port, and repair tests to no avail, so here is the diagnostic report. Maybe someone can help me figure out what’s going on.

Tracing Network Paths

Same here buddy :S. Reoccurring error 7s every 2 to 10 minutes. It is getting unplayable.
And I would be getting the pvp debuff “dishonored” :-(.

Other games would work just fine in terms of connection; can go on for hours/days straight without any DCs

Same error, same issues. This is terrible. It also doesn’t affect all my characters equally much – very weird. I just bought the game and think highly of it, and have spent lots of money already in the shop. At the moment, it sadly completely unplayable. GW2 team, please work hard to locate the problem and fix it for us.

Ashley Segovia.8276:

Hi MrGladiusii,

Unfortunately I can’t see a full traceroute here which makes this difficult to troubleshoot. Have you tried bypassing your router and connecting directly to the modem via Ethernet cable so that you’re able to eliminate both a wireless connection and your router from being the cause of the issue?

Ultimately I’d recommend getting in contact with your ISP to see if there’s anything that they’re able to do for you as this is usually the cause of this particular error.

I have taken on all standard procedures with the anet tech team. They concluded it is due to server hopping which isn’t a fault on neither the player’s nor anet’s. :/

I have the same problem, in that I can’t login with any of my characters, but if I use battleping (http://battleping.com), the game loads and runs fine. This means that there is a problem somewhere, but I don’t know where. I believe that a lot of players with problems are UK based.

================ = Tracing network paths ================

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

Tracing route to 64.25.39.1 over a maximum of 30 hops

0 JeffSher-PC.domain.actdsltmp [192.168.1.7]
1 192.168.1.1
2 L100.LSANCA-DSL-59.verizon-gni.net [98.119.43.1]
3 G0-6-0-5.LSANCA-LCR-21.verizon-gni.net [130.81.193.2]
4 ae4-0.LAX01-BB-RTR1.verizon-gni.net [130.81.199.98]
5 0.ae2.XT3.DFW9.ALTER.NET [140.222.225.55]
6 GigabitEthernet4-0-0.GW12.DFW9.ALTER.NET [152.63.97.86]
7 65.205.119.210
8 64.25.32.9
9 64.25.32.26
10 64.25.39.1

Computing statistics for 62 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 JeffSher-PC.domain.actdsltmp [192.168.1.7]
0/ 25 = 0% |
1 2ms 0/ 25 = 0% 0/ 25 = 0% 192.168.1.1
0/ 25 = 0% |
2 48ms 4/ 25 = 16% 4/ 25 = 16% L100.LSANCA-DSL-59.verizon-gni.net [98.119.43.1]
0/ 25 = 0% |
3 38ms 0/ 25 = 0% 0/ 25 = 0% G0-6-0-5.LSANCA-LCR-21.verizon-gni.net [130.81.193.2]
0/ 25 = 0% |
4 36ms 4/ 25 = 16% 4/ 25 = 16% ae4-0.LAX01-BB-RTR1.verizon-gni.net [130.81.199.98]
0/ 25 = 0% |
5 74ms 5/ 25 = 20% 5/ 25 = 20% 0.ae2.XT3.DFW9.ALTER.NET [140.222.225.55]
0/ 25 = 0% |
6 63ms 0/ 25 = 0% 0/ 25 = 0% GigabitEthernet4-0-0.GW12.DFW9.ALTER.NET [152.63.97.86]
5/ 25 = 20% |
7 75ms 5/ 25 = 20% 0/ 25 = 0% 65.205.119.210
0/ 25 = 0% |
8 80ms 5/ 25 = 20% 0/ 25 = 0% 64.25.32.9
1/ 25 = 4% |
9 —- 25/ 25 =100% 19/ 25 = 76% 64.25.32.26
0/ 25 = 0% |
10 78ms 6/ 25 = 24% 0/ 25 = 0% 64.25.39.1

Trace complete.

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

Tracing route to p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]
over a maximum of 30 hops:
0 JeffSher-PC.domain.actdsltmp [192.168.1.7]
1 192.168.1.1
2 L100.LSANCA-DSL-59.verizon-gni.net [98.119.43.1]
3 G0-6-0-5.LSANCA-LCR-21.verizon-gni.net [130.81.193.2]
4 so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
5 0.ge-5-1-0.XL3.CHI13.ALTER.NET [152.63.0.190]
6 TenGigE0-6-2-0.GW2.CHI13.ALTER.NET [152.63.65.137]
7 tinet-gw.customer.alter.net [152.179.92.6]
8 * xe-0-0-1.fra23.ip4.tinet.net [141.136.110.121]
9 * 89.149.164.42
10 * 206-127-157-86.plaync.com [206.127.157.86]
11 p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]

Computing statistics for 68 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 JeffSher-PC.domain.actdsltmp [192.168.1.7]
0/ 25 = 0% |
1 2ms 0/ 25 = 0% 0/ 25 = 0% 192.168.1.1
1/ 25 = 4% |
2 33ms 2/ 25 = 8% 1/ 25 = 4% L100.LSANCA-DSL-59.verizon-gni.net [98.119.43.1]
0/ 25 = 0% |
3 31ms 1/ 25 = 4% 0/ 25 = 0% G0-6-0-5.LSANCA-LCR-21.verizon-gni.net [130.81.193.2]
1/ 25 = 4% |
4 33ms 2/ 25 = 8% 0/ 25 = 0% so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
2/ 25 = 8% |
5 93ms 6/ 25 = 24% 2/ 25 = 8% 0.ge-5-1-0.XL3.CHI13.ALTER.NET [152.63.0.190]
0/ 25 = 0% |
6 82ms 4/ 25 = 16% 0/ 25 = 0% TenGigE0-6-2-0.GW2.CHI13.ALTER.NET [152.63.65.137]
0/ 25 = 0% |
7 84ms 4/ 25 = 16% 0/ 25 = 0% tinet-gw.customer.alter.net [152.179.92.6]
5/ 25 = 20% |
8 —- 25/ 25 =100% 16/ 25 = 64% xe-0-0-1.fra23.ip4.tinet.net [141.136.110.121]
0/ 25 = 0% |
9 215ms 19/ 25 = 76% 10/ 25 = 40% 89.149.164.42
0/ 25 = 0% |
10 —- 25/ 25 =100% 16/ 25 = 64% 206-127-157-86.plaync.com [206.127.157.86]
0/ 25 = 0% |
11 203ms 9/ 25 = 36% 0/ 25 = 0% p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]

Trace complete.
Section completed in 151.63 seconds

Same for me.

It started after last week’s patch; game is unplayable in the evening hours, which are the only ones I can play during the week (only few crashes in the morning and in the afternoon). It doesn’t matter if I’m in a city or a fairly empty map, I get massive lag and dc – providing I can log in at all. Usually the furthest I can get is character selection screen. After that it’s just a long wait in the loading screen and an error message after 2-3 min.

I’m in UK, my internet provider is BT.
I never had this kind of issue, not before the patch.

So, essentially we are kitten out of luck, right?