Guild Wars 2

no problems yesterday but today i ran the diags and
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 Patrick-PC.home.network [10.0.0.9]
1 10.0.0.1
2 71.193.48.1
3 xe-3-1-1-sur03.sacramento.ca.ccal.comcast.net [69.139.197.241]
4 162-151-18-133-static.hfc.comcastbusiness.net [162.151.18.133]
5 he-3-6-0-0-10-cr01.sanjose.ca.ibone.comcast.net [68.86.90.125]
6 50.242.148.34
7 * vlan70.csw2.SanJose1.Level3.net [4.69.152.126]
8 ae-71-71.ebr1.SanJose1.Level3.net [4.69.153.5]
9 * ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
10 ae-62-62.csw1.NewYork1.Level3.net [4.69.148.34]
11 * ae-61-61.ebr1.NewYork1.Level3.net [4.69.134.65]
12 ae-43-43.ebr2.London1.Level3.net [4.69.137.73]
13 * ae-24-24.ebr2.Frankfurt1.Level3.net [4.69.148.198]
14 ae-62-62.csw1.Frankfurt1.Level3.net [4.69.140.18]
15 * ae-3-80.edge6.Frankfurt1.Level3.net [4.69.154.138]
16 195.16.161.58
17 * 206-127-157-86.plaync.com [206.127.157.86]
18 p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]

Computing statistics for 112 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Patrick-PC.home.network [10.0.0.9]
0/ 25 = 0% |
1 0ms 0/ 25 = 0% 0/ 25 = 0% 10.0.0.1
0/ 25 = 0% |
2 7ms 2/ 25 = 8% 2/ 25 = 8% 71.193.48.1
0/ 25 = 0% |
3 8ms 0/ 25 = 0% 0/ 25 = 0% xe-3-1-1-sur03.sacramento.ca.ccal.comcast.net [69.139.197.241]
0/ 25 = 0% |
4 14ms 0/ 25 = 0% 0/ 25 = 0% 162-151-18-133-static.hfc.comcastbusiness.net [162.151.18.133]
0/ 25 = 0% |
5 12ms 1/ 25 = 4% 1/ 25 = 4% he-3-6-0-0-10-cr01.sanjose.ca.ibone.comcast.net [68.86.90.125]
0/ 25 = 0% |
6 11ms 1/ 25 = 4% 1/ 25 = 4% 50.242.148.34
0/ 25 = 0% |
7 15ms 0/ 25 = 0% 0/ 25 = 0% vlan70.csw2.SanJose1.Level3.net [4.69.152.126]
1/ 25 = 4% |
8 13ms 1/ 25 = 4% 0/ 25 = 0% ae-71-71.ebr1.SanJose1.Level3.net [4.69.153.5]
0/ 25 = 0% |
9 82ms 2/ 25 = 8% 1/ 25 = 4% ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
0/ 25 = 0% |
10 81ms 2/ 25 = 8% 1/ 25 = 4% ae-62-62.csw1.NewYork1.Level3.net [4.69.148.34]
0/ 25 = 0% |
11 79ms 1/ 25 = 4% 0/ 25 = 0% ae-61-61.ebr1.NewYork1.Level3.net [4.69.134.65]
9/ 25 = 36% |
12 148ms 10/ 25 = 40% 0/ 25 = 0% ae-43-43.ebr2.London1.Level3.net [4.69.137.73]
0/ 25 = 0% |
13 176ms 11/ 25 = 44% 1/ 25 = 4% ae-24-24.ebr2.Frankfurt1.Level3.net [4.69.148.198]
0/ 25 = 0% |
14 165ms 10/ 25 = 40% 0/ 25 = 0% ae-62-62.csw1.Frankfurt1.Level3.net [4.69.140.18]
0/ 25 = 0% |
15 165ms 10/ 25 = 40% 0/ 25 = 0% ae-3-80.edge6.Frankfurt1.Level3.net [4.69.154.138]
0/ 25 = 0% |
16 165ms 11/ 25 = 44% 1/ 25 = 4% 195.16.161.58
0/ 25 = 0% |
17 —- 25/ 25 =100% 15/ 25 = 60% 206-127-157-86.plaync.com [206.127.157.86]
0/ 25 = 0% |
18 164ms 10/ 25 = 40% 0/ 25 = 0% p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]

Trace complete.
Section completed in 217.61 seconds

You cannot gauge packetloss with Ping tests. All network equipment is coded to treat ICMP as a LOW level response. So when a system detects pings from a single source, its going to discard them to prevent the routing engine from getting overwhelmed.

its also how they prevent 80% of the DoS and ADDoS attacks against those nodes.

Your tests are invalid and you need to run wireshark while you experience packet loss and run the packetloss detection script against the Pcap when you are finished.

this is from the gw2 diagnostic run

ptegan.9756:

this is from the gw2 diagnostic run

It doesnt matter what app did the diags. Ping is not a good tool to use.

I wish Anet knew better :-)