Guild Wars 2

I know this may sounds crazy, but… I’d like to play the game I paid for and invested all this time into.

“Dear player, we sinc- -logize for a- the inc-nience th- pa- has -aused y-, bu- maybe y- shou- -sider playi- a diffe- -ame.”
Sincerely,
-September Massive Lag Spike Patch

I decided to take the time to do your tracerts n stuff while nothing and I mean absolutely nothing is working properly right now. I managed to get online after 30mins of trying and the forums barely load for me. No, this is not an ISP issue as I’ve done speed tests and everything else works properly. Only guild wars 2 (website & game, which are directly linked) doesn’t work at all. Well, barely.

Microsoft Windows [Version 6.3.9600]
© 2013 Microsoft Corporation. All rights reserved.

C:\Users\Maxime>tracert 64.25.33.8

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

1 <1 ms <1 ms <1 ms mynetwork.home [192.168.2.1]
2 17 ms 42 ms 11 ms 10.11.18.193
3 * 12 ms 12 ms 10.178.206.158
4 12 ms 12 ms 12 ms 10.178.206.159
5 13 ms 12 ms 12 ms agg1-montreal02_7-2-0.net.bell.ca [64.230.32.14]

6 16 ms 16 ms 14 ms core4-montreal02_xe0-0-4-0_core.net.bell.ca [64.
230.170.249]
7 13 ms 12 ms 12 ms bx4-montreal02_so-1-0-0.net.bell.ca [64.230.170.
178]
8 12 ms 13 ms 13 ms peer_Level3_bx4-montreal02.net.bell.ca [67.69.24
6.126]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 69 ms 62 ms 62 ms 4.59.197.34
14 62 ms 64 ms 63 ms 64.25.32-9.ncsoft.com [64.25.32.9]
15 54 ms 53 ms 54 ms 64.25.32-26.ncsoft.com [64.25.32.26]
16 54 ms 54 ms 54 ms 64.25.32-82.ncsoft.com [64.25.32.82]
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.

Microsoft Windows [Version 6.3.9600]
© 2013 Microsoft Corporation. All rights reserved.

C:\Users\Maxime>pathping -4 -q 100 64.25.33.88

Tracing route to 64.25.33-88.ncsoft.com [64.25.33.88]
over a maximum of 30 hops:
0 Steeve-PC.home [192.168.2.11]
1 mynetwork.home [192.168.2.1]
2 10.11.18.193
3 * 10.178.206.158
4 10.178.206.159
5 agg2-montreal02_5-2-0.net.bell.ca [64.230.32.12]
6 core3-montreal02_xe0-8-2-0_core.net.bell.ca [64.230.170.245]
7 bx4-montreal02_pos3-1-0.net.bell.ca [64.230.169.190]
8 peer_Level3_bx4-montreal02.net.bell.ca [67.69.246.126]
9 * * *
Computing statistics for 200 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Steeve-PC.home [192.168.2.11]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% mynetwork.home [192.168.2.1]
0/ 100 = 0% |
2 11ms 0/ 100 = 0% 0/ 100 = 0% 10.11.18.193
0/ 100 = 0% |
3 —- 100/ 100 =100% 100/ 100 =100% 10.178.206.158
0/ 100 = 0% |
4 —- 100/ 100 =100% 100/ 100 =100% 10.178.206.159
0/ 100 = 0% |
5 15ms 0/ 100 = 0% 0/ 100 = 0% agg2-montreal02_5-2-0.net.bell.ca
[64.230.32.12]
0/ 100 = 0% |
6 15ms 0/ 100 = 0% 0/ 100 = 0% core3-montreal02_xe0-8-2-0_core.ne
t.bell.ca [64.230.170.245]
0/ 100 = 0% |
7 13ms 0/ 100 = 0% 0/ 100 = 0% bx4-montreal02_pos3-1-0.net.bell.c
a [64.230.169.190]
0/ 100 = 0% |
8 40ms 0/ 100 = 0% 0/ 100 = 0% peer_Level3_bx4-montreal02.net.bel
l.ca [67.69.246.126]

Trace complete.

You need to send this to your ISP, not Anet (but opening a ticket with Anet would get you farther than posting it here).

Trace shows a definite issue with backkittenouting, equipment failure (prior to Anet server farm) and Anet can’t fix that. Very likely someone is throttling your connection and is simply incompetent at doing so.

I think you forgot the part where everything worked perfectly fine before the september patch and how there’s always issues every time a new patch comes out.

MystikaLsmuRF.7150:

I think you forgot the part where everything worked perfectly fine before the september patch and how there’s always issues every time a new patch comes out.

The patch has nothing to do with (nor will it affect) routing issues.

Some firewall (internet security) programs have problems when the GW2 executable file has been changed, but again, that isn’t problem with the A-net servers.

Seeing as I use the Windows firewall instead of a third-party firewall, I never have an issue with ‘internet security’ programs messing with GW2.

Ok….so you think ANETs code being updated can cause a router to drop packets in a LEVEL 3 data center in CA? (what the data you provided indicates is happening).

Do whatever you want, I was just trying to make a logical suggestion based on the info you provided. Good luck.

/waves at Brother Grimm

Despite my (in)sanity, for some reason, I still try to help people understand how the internet works.

Bro if your dog gets hit by a car and the next day he has trouble walking, it’s easy to say that it’s because he got hit by a car, don’t you agree?
Well if I didn’t have packet loss before the patch and now I do and literally cannot play most of the day ever since the september patch when I’ve been playing this game for over a year without problems (except when new patches come out and takes a month or so to gets fixed), then it has to be my ISP doesn’kitten

Let’s find a common ground here, both the anet servers and my ISP are messed up, aight ? ‘Cause I def ain’t the only one struggling with the servers ever since that patch bruhz no matter how much you guys will defend in every thread complaining about the patch there’s something similar in ALL those darn threads: the issue appeared with the patch. What’s so complicated about this ?