Since the 2 hour maintenance break we just had (April 16), I have been experiencing severe latency.
I have tried restarting both my computer and my router. I have also tried logging into other games etc, and the problem is unique to GW2.
In eternal battlegrounds I asked in /m if anyone else is experiencing this and the answer was no. Anyone on these forums having the same problem, or is it just me?
Some help would be appreciated.
Hey gang – For those of you who are experiencing lag from AFTER maintenance (not those who may have been having lag issues prior to maintenance), could you please post some net diags to this thread so we can look through them?
To do so, please follow the steps below:
1. Navigate to your Guild Wars 2 folder.
2. Right-click on “Gw2.exe” and select “Create Shortcut.”
3. Right-click on “Gw2.exe – Shortcut” and select “Rename.”
4. Rename this file to “Guild Wars 2 Diagnostic.”
5. Right-click on “Guild Wars 2 Diagnostic” and select “Properties.”
6. Locate the “Target” line and add the following to the end " -diag"
Your target line should look like this: “C:\Games\Guild Wars 2\Gw2.exe” -diag
7. Click OK to save your changes.
8. Open “Guild Wars 2 Diagnostic” to start the test.
Once completed, please click “View Results” and save the results to a text file on your desktop. Once saved, please attach that to this thread for review (click More posting &formatting options… to attach).
EDIT: Can I also get you guys to provide what server you’re on as well?
Hey guys – Thanks so much for all of the net diag reports! After taking a look through all the provided reports, there does appear to be sporadic and high amounts of packet loss across many of the hops prior to reaching the game servers. For example:
1 4ms 0/ 25 = 0% 0/ 25 = 0% 192.168.0.1
1/ 25 = 4% |
2 29ms 1/ 25 = 4% 0/ 25 = 0% esr10.manchester6.broadband.bt.net [217.xx.xxx.xxx]
1/ 25 = 4% |
3 64ms 3/ 25 = 12% 1/ 25 = 4% 217.xx.xxx.xx
0/ 25 = 0% |
4 —- 25/ 25 =100% 23/ 25 = 92% 213.1.67.xx
0/ 25 = 0% |
5 —- 25/ 25 =100% 23/ 25 = 92% 213.1.67.xxx
0/ 25 = 0% |
6 —- 25/ 25 =100% 23/ 25 = 92% 213.1.78.238
0/ 25 = 0% |
7 —- 25/ 25 =100% 23/ 25 = 92% 213.1.79.86
0/ 25 = 0% |
8 39ms 2/ 25 = 8% 0/ 25 = 0% 87.237.20.244
0/ 25 = 0% |
9 42ms 2/ 25 = 8% 0/ 25 = 0% 80.150.171.89
1/ 25 = 4% |
10 38ms 3/ 25 = 12% 0/ 25 = 0% lon-sb3-i.LON.GB.NET.DTAG.DE [62.154.5.34]
2/ 25 = 8% |
11 —- 25/ 25 =100% 20/ 25 = 80% 62.157.248.198
0/ 25 = 0% |
12 183ms 8/ 25 = 32% 3/ 25 = 12% ae-52-52.csw2.London1.Level3.net [4.69.139.120]
0/ 25 = 0% |
13 37ms 5/ 25 = 20% 0/ 25 = 0% ae-59-224.ebr2.London1.Level3.net [4.69.153.141]
0/ 25 = 0% |
14 104ms 5/ 25 = 20% 0/ 25 = 0% ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]
0/ 25 = 0% |
15 108ms 5/ 25 = 20% 0/ 25 = 0% ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
0/ 25 = 0% |
16 106ms 5/ 25 = 20% 0/ 25 = 0% ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33]
1/ 25 = 4% |
17 144ms 7/ 25 = 28% 1/ 25 = 4% ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121]
0/ 25 = 0% |
18 145ms 7/ 25 = 28% 1/ 25 = 4% ae-92-92.csw4.Dallas1.Level3.net [4.69.151.165]
0/ 25 = 0% |
19 143ms 7/ 25 = 28% 1/ 25 = 4% ae-4-90.edge2.Dallas1.Level3.net [4.69.145.203]
0/ 25 = 0% |
20 144ms 7/ 25 = 28% 1/ 25 = 4% 4.59.197.34
0/ 25 = 0% |
21 142ms 6/ 25 = 24% 0/ 25 = 0% 64.25.32.9
0/ 25 = 0% |
22 —- 25/ 25 =100% 19/ 25 = 76% 64.25.32.26
0/ 25 = 0% |
23 146ms 6/ 25 = 24% 0/ 25 = 0% 64.25.39.1
Trace complete.
This is just one example of heavy packet loss. This could also potentially be due to the fact that the original trace begins in Europe and ends on a North American game server. The same cannot be said for all players who submitted reports as some traceroutes were incomplete, possibly due to security software, router firewalls, or ISP’s blocking the trace.
That being said, for those of you who have a high degree of packet loss within the traceroutes you’ve run, you will need to contact your ISP directly to have them resolve this issue. This is simply because they are the ones that control the route your data takes. Both NCSOFT or ArenaNet have no control over your data until it reaches our servers and as such, we need to get your ISP involved.
I would also highly recommend creating a technical support ticket because I am not at all saying for every player who is experiencing this issue that this is at the fault of their IP. This is just based on the traceroutes that we’ve looked at in this thread. If you were to contact support we can go through some more in depth troubleshooting and will allow us to collect more information to look into for further investigation if this issue does appear to be on our end.
Hello all I just want to reiterate that my last response was largely based off of the majority of reports that were provided. Again, if you do not feel this is the fault of your ISP please contact the Technical Support Department directly so that we can better further investigate this issue.
