Guild Wars 2

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Rodger>tracert guildwars2.com

Tracing route to guildwars2.com [64.25.40.16]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.254
2 16 ms 17 ms 16 ms 216.227.100.16
3 16 ms 17 ms 16 ms yelm-r0.yelmtel.com [216.227.100.33]
4 18 ms 18 ms 18 ms static-216-227-101-254.westin.fairpoint.net [216
.227.101.254]
5 18 ms 18 ms 18 ms 216.243.24.253
6 18 ms 17 ms 18 ms cr2-sea-b-te-0-0-0-23.bb.spectrumnet.us [174.127
.140.125]
7 19 ms 18 ms 18 ms ae9.MPR1.SEA1.us.above.net [208.185.155.61]
8 18 ms 17 ms 17 ms xe-10-3-0.edge2.seattle3.Level3.net [4.68.63.129
]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * 75 ms 75 ms 4.59.197.34
16 78 ms 111 ms 78 ms 64.25.32-9.ncsoft.com [64.25.32.9]
17 * 94 ms 73 ms 64.25.32-26.ncsoft.com [64.25.32.26]
18 76 ms 77 ms * 64.25.32-82.ncsoft.com [64.25.32.82]
19 72 ms 73 ms 73 ms 64.25.40-16.ncsoft.com [64.25.40.16]

Trace complete.

C:\Documents and Settings\Rodger>

I don’t really know what it means. I do know the game is not playable now. Have had minor lag problems in the past but today is all about lag and disconnects. Maybe this will help one of the staff members trace down the problem?

Hopefully. I’m not even gaining rank points on my reward track when I win or lose PvP matches.

Rodger.2831:

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Rodger>tracert guildwars2.com

Tracing route to guildwars2.com [64.25.40.16]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.254
2 16 ms 17 ms 16 ms 216.227.100.16
3 16 ms 17 ms 16 ms yelm-r0.yelmtel.com [216.227.100.33]
4 18 ms 18 ms 18 ms static-216-227-101-254.westin.fairpoint.net [216
.227.101.254]
5 18 ms 18 ms 18 ms 216.243.24.253
6 18 ms 17 ms 18 ms cr2-sea-b-te-0-0-0-23.bb.spectrumnet.us [174.127
.140.125]
7 19 ms 18 ms 18 ms ae9.MPR1.SEA1.us.above.net [208.185.155.61]
8 18 ms 17 ms 17 ms xe-10-3-0.edge2.seattle3.Level3.net [4.68.63.129
]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * 75 ms 75 ms 4.59.197.34
16 78 ms 111 ms 78 ms 64.25.32-9.ncsoft.com [64.25.32.9]
17 * 94 ms 73 ms 64.25.32-26.ncsoft.com [64.25.32.26]
18 76 ms 77 ms * 64.25.32-82.ncsoft.com [64.25.32.82]
19 72 ms 73 ms 73 ms 64.25.40-16.ncsoft.com [64.25.40.16]

Trace complete.

C:\Documents and Settings\Rodger>

I don’t really know what it means. I do know the game is not playable now. Have had minor lag problems in the past but today is all about lag and disconnects. Maybe this will help one of the staff members trace down the problem?

Huge issue here

8 18 ms 17 ms 17 ms xe-10-3-0.edge2.seattle3.Level3.net [4.68.63.129

then it drops off inside of level3’s network until you hit NCSoft’s servers.

Call your ISP and explain that their transport to Arenanet is failing, and thats level 3. They will be able to open a head to head ticket and start getting it resolved.

Sirsquishy, Thank you for the suggestion. Shortly after your post, I contacted my ISP. I have been “dealing” with them since. They were not much help, claiming the problem is on the other end. They finally agreed to look into it further and get back to me. I have done that route trace many times with the same result. No other route trace I’ve tried, to any other address, has any time outs.

I’ve been having the same problems as others and so I did the test below. This test is from support. My findings/numbers were good. So I’m not sure what is going on.

Traceroute Instructions (Windows®)
Guild Wars 2 offers the ability to do a traceroute while in game to check your connection. Please follow the steps below to do so:

Open your Guild Wars 2 folder.
Right-click on GW2.exe and select Create Shortcut.
Right-click on GW2.exe – Shortcut and select Rename.
Rename the file Guild Wars 2 Diagnostic.
Right-click on Guild Wars 2 Diagnostic and select Properties.
Locate the Target line and add –diag to the end of the text there (your target line should look like this: “C:\Gamse\Guild Wars 2\GW2.exe” –diag).
Click OK to save your changes.
Double click Guild Wars 2 Diagnostic to start the test.
Once the test has completed, click View Results and save the results to a text file (.txt) on your desktop.
Open the file and compare your results to those below.

Here is an example of what a bad connection looks like (note the high percentages of lost data):
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
1/ 50 = 2% |
1 1ms 1/ 50 = 2% 0/ 50 = 0%
0/ 50 = 0% |
2 —- 50/ 50 =100% 49/ 50 = 98%
0/ 50 = 0% |
3 —- 50/ 50 =100% 49/ 50 = 98%
0/ 50 = 0% |
4 —- 50/ 50 =100% 49/ 50 = 98%
0/ 50 = 0% |
5 —- 50/ 50 =100% 49/ 50 = 98%
0/ 50 = 0% |
6 29ms 1/ 50 = 2% 0/ 50 = 0%
0/ 50 = 0% |
7 —- 50/ 50 =100% 49/ 50 = 98%
0/ 50 = 0% |
8 —- 50/ 50 =100% 49/ 50 = 98%
0/ 50 = 0% |
9 —- 50/ 50 =100% 49/ 50 = 98%
0/ 50 = 0% |
10 51ms 4/ 50 = 8% 3/ 50 = 6%
0/ 50 = 0% |
11 —- 50/ 50 =100% 49/ 50 = 98%
0/ 50 = 0% |
12 48ms 3/ 50 = 6% 2/ 50 = 4%
0/ 50 = 0% |
13 44ms 1/ 50 = 2% 0/ 50 = 0%
2/ 50 = 4% |
14 46ms 6/ 50 = 12% 3/ 50 = 6%
0/ 50 = 0% |
15 53ms 4/ 50 = 8% 1/ 50 = 2%
0/ 50 = 0% |
16 47ms 8/ 50 = 16% 5/ 50 = 10%
0/ 50 = 0% |
17 39ms 5/ 50 = 10% 2/ 50 = 4%
0/ 50 = 0% |
18 —- 50/ 50 =100% 47/ 50 = 94%
0/ 50 = 0% |
19 40ms 3/ 50 = 6% 0/ 50 = 0%

Here is an example of what a good connection looks like:
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0/ 25 = 0% |
1 0ms 1/ 25 = 4% 1/ 25 = 4%
0/ 25 = 0% |
2 0ms 1/ 25 = 4% 1/ 25 = 4%
0/ 25 = 0% |
3 1ms 1/ 25 = 4% 1/ 25 = 4%
0/ 25 = 0% |
4 11ms 2/ 25 = 8% 2/ 25 = 8%
0/ 25 = 0% |
5 7ms 2/ 25 = 8% 2/ 25 = 8%
0/ 25 = 0% |
6 10ms 0/ 25 = 0% 0/ 25 = 0%
0/ 25 = 0% |
7 8ms 0/ 25 = 0% 0/ 25 = 0%
1/ 25 = 4% |
8 27ms 1/ 25 = 4% 0/ 25 = 0%
1/ 25 = 4% |
9 43ms 2/ 25 = 8% 0/ 25 = 0%
0/ 25 = 0% |
10 48ms 2/ 25 = 8% 0/ 25 = 0%
0/ 25 = 0% |
11 39ms 2/ 25 = 8% 0/ 25 = 0%
3/ 25 = 12% |
12 122ms 5/ 25 = 20% 0/ 25 = 0%
1/ 25 = 4% |
13 129ms 6/ 25 = 24% 0/ 25 = 0%
0/ 25 = 0% |
14 131ms 7/ 25 = 28% 1/ 25 = 4%
0/ 25 = 0% |
15 127ms 6/ 25 = 24% 0/ 25 = 0%
1/ 25 = 4% |
16 129ms 7/ 25 = 28% 0/ 25 = 0%
0/ 25 = 0% |
17 128ms 7/ 25 = 28% 0/ 25 = 0%
1/ 25 = 4% |
18 133ms 8/ 25 = 32% 0/ 25 = 0%

0
0/ 25 = 0% |
1 7ms 0/ 25 = 0% 0/ 25 = 0%
1/ 25 = 4% |
2 14ms 1/ 25 = 4% 0/ 25 = 0%
0/ 25 = 0% |
3 17ms 1/ 25 = 4% 0/ 25 = 0%
0/ 25 = 0% |
4 21ms 2/ 25 = 8% 1/ 25 = 4%
0/ 25 = 0% |
5 19ms 1/ 25 = 4% 0/ 25 = 0%
0/ 25 = 0% |
6 25ms 1/ 25 = 4% 0/ 25 = 0%
0/ 25 = 0% |
7 24ms 1/ 25 = 4% 0/ 25 = 0%
1/ 25 = 4% |
8 24ms 2/ 25 = 8% 0/ 25 = 0%

These are the numbers I got from the tracert and I’m currently unable to play the game due to all the lag and rubberbanding.

You players posting this need to understand that expecting Anet to do anything about this is like Madison Square Garden being expected to fix the George Washington Bridge because some season ticket holders can’t get to a Nicks game….

I get you are asking for help, but only your ISP can assist here.

Gale.4815:

I’ve been having the same problems as others and so I did the test below. This test is from support. My findings/numbers were good. So I’m not sure what is going on.

Traceroute Instructions (Windows®)
Guild Wars 2 offers the ability to do a traceroute while in game to check your connection. Please follow the steps below to do so:

Open your Guild Wars 2 folder.
Right-click on GW2.exe and select Create Shortcut.
Right-click on GW2.exe – Shortcut and select Rename.
Rename the file Guild Wars 2 Diagnostic.
Right-click on Guild Wars 2 Diagnostic and select Properties.
Locate the Target line and add –diag to the end of the text there (your target line should look like this: “C:\Gamse\Guild Wars 2\GW2.exe” –diag).
Click OK to save your changes.
Double click Guild Wars 2 Diagnostic to start the test.
Once the test has completed, click View Results and save the results to a text file (.txt) on your desktop.
Open the file and compare your results to those below.

Here is an example of what a bad connection looks like (note the high percentages of lost data):
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
1/ 50 = 2% |
1 1ms 1/ 50 = 2% 0/ 50 = 0%
0/ 50 = 0% |
2 —- 50/ 50 =100% 49/ 50 = 98%
0/ 50 = 0% |
3 —- 50/ 50 =100% 49/ 50 = 98%
0/ 50 = 0% |
4 —- 50/ 50 =100% 49/ 50 = 98%
0/ 50 = 0% |
5 —- 50/ 50 =100% 49/ 50 = 98%
0/ 50 = 0% |
6 29ms 1/ 50 = 2% 0/ 50 = 0%
0/ 50 = 0% |
7 —- 50/ 50 =100% 49/ 50 = 98%
0/ 50 = 0% |
8 —- 50/ 50 =100% 49/ 50 = 98%
0/ 50 = 0% |
9 —- 50/ 50 =100% 49/ 50 = 98%
0/ 50 = 0% |
10 51ms 4/ 50 = 8% 3/ 50 = 6%
0/ 50 = 0% |
11 —- 50/ 50 =100% 49/ 50 = 98%
0/ 50 = 0% |
12 48ms 3/ 50 = 6% 2/ 50 = 4%
0/ 50 = 0% |
13 44ms 1/ 50 = 2% 0/ 50 = 0%
2/ 50 = 4% |
14 46ms 6/ 50 = 12% 3/ 50 = 6%
0/ 50 = 0% |
15 53ms 4/ 50 = 8% 1/ 50 = 2%
0/ 50 = 0% |
16 47ms 8/ 50 = 16% 5/ 50 = 10%
0/ 50 = 0% |
17 39ms 5/ 50 = 10% 2/ 50 = 4%
0/ 50 = 0% |
18 —- 50/ 50 =100% 47/ 50 = 94%
0/ 50 = 0% |
19 40ms 3/ 50 = 6% 0/ 50 = 0%

Here is an example of what a good connection looks like:
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0/ 25 = 0% |
1 0ms 1/ 25 = 4% 1/ 25 = 4%
0/ 25 = 0% |
2 0ms 1/ 25 = 4% 1/ 25 = 4%
0/ 25 = 0% |
3 1ms 1/ 25 = 4% 1/ 25 = 4%
0/ 25 = 0% |
4 11ms 2/ 25 = 8% 2/ 25 = 8%
0/ 25 = 0% |
5 7ms 2/ 25 = 8% 2/ 25 = 8%
0/ 25 = 0% |
6 10ms 0/ 25 = 0% 0/ 25 = 0%
0/ 25 = 0% |
7 8ms 0/ 25 = 0% 0/ 25 = 0%
1/ 25 = 4% |
8 27ms 1/ 25 = 4% 0/ 25 = 0%
1/ 25 = 4% |
9 43ms 2/ 25 = 8% 0/ 25 = 0%
0/ 25 = 0% |
10 48ms 2/ 25 = 8% 0/ 25 = 0%
0/ 25 = 0% |
11 39ms 2/ 25 = 8% 0/ 25 = 0%
3/ 25 = 12% |
12 122ms 5/ 25 = 20% 0/ 25 = 0%
1/ 25 = 4% |
13 129ms 6/ 25 = 24% 0/ 25 = 0%
0/ 25 = 0% |
14 131ms 7/ 25 = 28% 1/ 25 = 4%
0/ 25 = 0% |
15 127ms 6/ 25 = 24% 0/ 25 = 0%
1/ 25 = 4% |
16 129ms 7/ 25 = 28% 0/ 25 = 0%
0/ 25 = 0% |
17 128ms 7/ 25 = 28% 0/ 25 = 0%
1/ 25 = 4% |
18 133ms 8/ 25 = 32% 0/ 25 = 0%

I see issues, but the output you supplied is nearly completely useless.

you MUST run tracert from windows command prompt to the IP you used for the output above. We need Node resolution to give advice on who to contact. Just showing Hop#’s with % loss is not enough.