Guild Wars 2

I cant even use a skill or open merchants in LA, trade post takes about 10 seconds to sell something, major chat lag, whats going on with this lag? It just started today was fine yesterday. And no it’s NOT my internet. I’m in Canada so It’s not the Seattle issue others are having.

LOL @ “it’s NOT my internet”. There could be 15+ hops between you and Anet; any one of those could have issues. Going to Anet and to another game will not take the same path and therefore could be fine.

Let’s rule that out; when ingame, type in /ip to get the IP address of the server.

Then in Windows, go to Start and type in “cmd” and hit enter. At the command prompt, type in “pathping <ipaddress>” and post the results.

Also, what server are you on? US or EU?

Well others would be like FIX YOUR ROUTER, get faster internet etc. and I will test that ping one sec. I’m on USA servers, never had this lag before until today “been playing since launch”.

Level3 (major backbone provider in the US) has been having some major issues in the NW portion of the united states. I’ve experienced issues with them in the past going through their Chicago hop.

I tried the ping, I think they have it blocked didn’t work. I will try resource monitor. And my net is probably using Level 3 when it connects to states ya, would make sense but it’s weird because I had no lag yesterday and people reported lag yesterday with level 3.

Alright ping in resource monitor says 150-300 for the server IP. So it seems to me it must be a packet issue not ping hmm it has to be the Level 3 stuff.

Well dang. It would be nice to see the Path you are taking. What server are you on?

Just to clarify, you are using “pathping” and not just “ping”?

Yea I was using pathping 100% with server IP, let me see if I can figure out another way to get the paths. I’m on maguuma

I am guesting on Maguuma now to see how it responds to me. I am going to head to LA and test it out.

Microsoft Windows [Version 6.2.9200]
© 2012 Microsoft Corporation. All rights reserved.

>pathping 206.127.146.49

Tracing route to 206-127-146-49.plaync.com [206.127.146.49]
over a maximum of 30 hops:
0 xxx
1 xxx
2 xxx
3 static-74-214-52-134.cpe.metrocast.net [74.214.52.134]
4 static-65-175-142-217.cpe.metrocast.net [65.175.142.217]
5 TBD-65-175-128-2.metrocast.net [65.175.128.2]
6 te0-7-0-5.ccr22.bos01.atlas.cogentco.com [38.122.126.73]
7 te0-6-0-3.mpd22.jfk02.atlas.cogentco.com [154.54.5.250]
8 be2059.ccr21.jfk07.atlas.cogentco.com [154.54.1.222]
9 tinet.jfk07.atlas.cogentco.com [154.54.10.142]
10 xe-0-0-0.fra23.ip4.tinet.net [141.136.110.117]
11 89.149.164.42
12 206-127-157-86.plaync.com [206.127.157.86]
13 206-127-157-102.plaync.com [206.127.157.102]
14 * * *
Computing statistics for 325 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 xxx
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% xxx []
0/ 100 = 0% |
2 8ms 0/ 100 = 0% 0/ 100 = 0%
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% static-74-214-52-134.cpe.metrocast
.net [74.214.52.134]
0/ 100 = 0% |
4 20ms 0/ 100 = 0% 0/ 100 = 0% static-65-175-142-217.cpe.metrocas
t.net [65.175.142.217]
0/ 100 = 0% |
5 26ms 0/ 100 = 0% 0/ 100 = 0% TBD-65-175-128-2.metrocast.net [65
.175.128.2]
0/ 100 = 0% |
6 26ms 0/ 100 = 0% 0/ 100 = 0% te0-7-0-5.ccr22.bos01.atlas.cogent
co.com [38.122.126.73]
0/ 100 = 0% |
7 27ms 0/ 100 = 0% 0/ 100 = 0% te0-6-0-3.mpd22.jfk02.atlas.cogent
co.com [154.54.5.250]
0/ 100 = 0% |
8 27ms 0/ 100 = 0% 0/ 100 = 0% be2059.ccr21.jfk07.atlas.cogentco.
com [154.54.1.222]
0/ 100 = 0% |
9 29ms 0/ 100 = 0% 0/ 100 = 0% tinet.jfk07.atlas.cogentco.com [15
4.54.10.142]
0/ 100 = 0% |
10 115ms 0/ 100 = 0% 0/ 100 = 0% xe-0-0-0.fra23.ip4.tinet.net [141.
136.110.117]
83/ 100 = 83% |
11 119ms 83/ 100 = 83% 0/ 100 = 0% 89.149.164.42
17/ 100 = 17% |
12 —- 100/ 100 =100% 0/ 100 = 0% 206-127-157-86.plaync.com [206.127
.157.86]
0/ 100 = 0% |
13 —- 100/ 100 =100% 0/ 100 = 0% 206-127-157-102.plaync.com [206.12
7.157.102]

Trace complete.

Tracing route to 64.25.38.190 over a maximum of 30 hops

1 * * * Request timed out.
2 14 ms 14 ms 11 ms 24.156.135.185
3 9 ms 10 ms 15 ms 24.156.156.157
4 10 ms 7 ms 12 ms so-5-1-3.gw02.mtnk.phub.net.cable.rogers.com [66
.185.81.181]
5 * * * Request timed out.
6 * 107 ms 108 ms xe-2-0-0.er1.lga5.us.above.net [64.124.128.193]

7 103 ms * 103 ms 0.xe-8-2-0.BR2.NYC4.ALTER.NET [204.255.168.25]
8 * * * Request timed out.
9 134 ms * 138 ms GigabitEthernet5-0-0.GW12.DFW9.ALTER.NET [152.63
.97.90]
10 * 194 ms 193 ms 65.205.119.210
11 145 ms 145 ms 145 ms 64.25.32.9
12 212 ms 204 ms 216 ms 64.25.32.26
13 * 141 ms 138 ms 64.25.32.82
14 * * * Request timed out.
15 * * * Request timed out.

Something seems off.

10 115ms 0/ 100 = 0% 0/ 100 = 0% xe-0-0-0.fra23.ip4.tinet.net [141.136.110.117]
83/ 100 = 83% |
11 119ms 83/ 100 = 83% 0/ 100 = 0% 89.149.164.4217/ 100 = 17% |
12 —- 100/ 100 =100% 0/ 100 = 0% 206-127-157-86.plaync.com [206.127.157.86]

83% packet loss, that is ugly. Looks like that fra23.ip4.tinet.net is the issue.

CrazyDuck.4610:

Tracing route to 64.25.38.190 over a maximum of 30 hops

1 * * * Request timed out.
2 14 ms 14 ms 11 ms 24.156.135.185
3 9 ms 10 ms 15 ms 24.156.156.157
4 10 ms 7 ms 12 ms so-5-1-3.gw02.mtnk.phub.net.cable.rogers.com [66
.185.81.181]
5 * * * Request timed out.
6 * 107 ms 108 ms xe-2-0-0.er1.lga5.us.above.net [64.124.128.193]

7 103 ms * 103 ms 0.xe-8-2-0.BR2.NYC4.ALTER.NET [204.255.168.25]
8 * * * Request timed out.
9 134 ms * 138 ms GigabitEthernet5-0-0.GW12.DFW9.ALTER.NET [152.63
.97.90]
10 * 194 ms 193 ms 65.205.119.210
11 145 ms 145 ms 145 ms 64.25.32.9
12 212 ms 204 ms 216 ms 64.25.32.26
13 * 141 ms 138 ms 64.25.32.82
14 * * * Request timed out.
15 * * * Request timed out.

Something seems off.

CrazyDuck, it looks like ALTER is having some issues; as you get getting timeouts. Unfortunately pathping would provide packet loss as well. Hopefully it will clear up by tomorrow.

Thanks for help again Ya hopefully it’s strange that it happened right after patch today though must just be coincidence.

Now Im dcing