Guild Wars 2

Hi Anet,

It seems that there is a high % of packet loss at the following nodes:
206-127-156-86.plaync.com (76%)
64.25.32.26 plaync (node) – (68%)

This is causing large lagging for many players and should be investigated.
The Level3 backbone is also seems to have problems between Paris -> Washington

Network routes enclosed (From a GW2 / diag):
—> 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:
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 <REMOVED> [<REMOVED>]
0/ 25 = 0% |
1 0ms 0/ 25 = 0% 0/ 25 = 0% <REMOVED>
1/ 25 = 4% |
2 29ms 3/ 25 = 12% 2/ 25 = 8% lo0-central10.pcl-ag05.plus.net [195.166.128.186]
0/ 25 = 0% |
3 26ms 3/ 25 = 12% 2/ 25 = 8% link-a-central10.pcl-gw01.plus.net [212.159.2.176]
0/ 25 = 0% |
4 28ms 1/ 25 = 4% 0/ 25 = 0% 208.core.access.plus.net [212.159.0.208]
0/ 25 = 0% |
5 26ms 3/ 25 = 12% 2/ 25 = 8% xe-11-1-0.edge3.London2.Level3.net [212.187.201.209]
0/ 25 = 0% |
6 34ms 1/ 25 = 4% 0/ 25 = 0% ae-3-3.ebr1.Paris1.Level3.net [4.69.141.86]
0/ 25 = 0% |
7 35ms 2/ 25 = 8% 1/ 25 = 4% ae-61-61.csw1.Paris1.Level3.net [4.69.161.78]
0/ 25 = 0% |
8 34ms 1/ 25 = 4% 0/ 25 = 0% ae-62-62.ebr2.Paris1.Level3.net [4.69.161.93]
2/ 25 = 8% |
9 50ms 3/ 25 = 12% 0/ 25 = 0% ae-45-45.ebr1.Frankfurt1.Level3.net [4.69.143.133]
1/ 25 = 4% |
10 39ms 5/ 25 = 20% 1/ 25 = 4% ae-91-91.csw4.Frankfurt1.Level3.net [4.69.140.14]
0/ 25 = 0% |
11 39ms 4/ 25 = 16% 0/ 25 = 0% ae-4-90.edge6.Frankfurt1.Level3.net [4.69.154.202]
0/ 25 = 0% |
12 37ms 4/ 25 = 16% 0/ 25 = 0% 195.16.161.58
2/ 25 = 8% |
13 —- 25/ 25 =100% 19/ 25 = 76% 206-127-157-86.plaync.com [206.127.157.86]
0/ 25 = 0% |
14 40ms 6/ 25 = 24% 0/ 25 = 0% p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]

Trace complete.

Next trace in next msg..

Second trace with more PlayNC Packet Loss:

—> pathping -w 500 -q 25 -4 64.25.39.1 <--

Tracing route to 64.25.39.1 over a maximum of 30 hops
Computing statistics for 118 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 <REMOVED> [<REMOVED>]
0/ 25 = 0% |
1 0ms 0/ 25 = 0% 0/ 25 = 0% <REMOVED>
1/ 25 = 4% |
2 34ms 4/ 25 = 16% 3/ 25 = 12% lo0-central10.pcl-ag05.plus.net [195.166.128.186]
0/ 25 = 0% |
3 25ms 3/ 25 = 12% 2/ 25 = 8% link-a-central10.pcl-gw01.plus.net [212.159.2.176]
0/ 25 = 0% |
4 26ms 4/ 25 = 16% 3/ 25 = 12% 208.core.access.plus.net [212.159.0.208]
0/ 25 = 0% |
5 26ms 3/ 25 = 12% 2/ 25 = 8% xe-11-2-0.edge3.London2.Level3.net [212.187.201.213]
0/ 25 = 0% |
6 34ms 2/ 25 = 8% 1/ 25 = 4% ae-3-3.ebr1.Paris1.Level3.net [4.69.141.86]
0/ 25 = 0% |
7 33ms 3/ 25 = 12% 2/ 25 = 8% ae-91-91.csw4.Paris1.Level3.net [4.69.161.90]
0/ 25 = 0% |
8 35ms 1/ 25 = 4% 0/ 25 = 0% ae-92-92.ebr2.Paris1.Level3.net [4.69.161.105]
5/ 25 = 20% |
9 107ms 7/ 25 = 28% 1/ 25 = 4% ae-44-44.ebr2.Washington1.Level3.net [4.69.137.62]
0/ 25 = 0% |
10 102ms 7/ 25 = 28% 1/ 25 = 4% ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
0/ 25 = 0% |
11 106ms 7/ 25 = 28% 1/ 25 = 4% ae-81-81.ebr1.Washington1.Level3.net [4.69.134.137]
0/ 25 = 0% |
12 118ms 6/ 25 = 24% 0/ 25 = 0% ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
0/ 25 = 0% |
13 139ms 8/ 25 = 32% 2/ 25 = 8% ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
0/ 25 = 0% |
14 141ms 8/ 25 = 32% 2/ 25 = 8% ae-63-63.csw1.Dallas1.Level3.net [4.69.151.133]
0/ 25 = 0% |
15 138ms 6/ 25 = 24% 0/ 25 = 0% ae-1-60.edge2.Dallas1.Level3.net [4.69.145.11]
1/ 25 = 4% |
16 132ms 7/ 25 = 28% 0/ 25 = 0% 4.59.197.34
0/ 25 = 0% |
17 140ms 7/ 25 = 28% 0/ 25 = 0% 64.25.32.9
1/ 25 = 4% |
18 —- 25/ 25 =100% 17/ 25 = 68% 64.25.32.26
0/ 25 = 0% |
19 138ms 8/ 25 = 32% 0/ 25 = 0% 64.25.39.1

Trace complete.
Section completed in 204.16 seconds

This lag is killing our toons. Help please.

Did you guys start experiencing this lag 2 days ago? Because I’ve been having the same issue, and it’s making SAB more or less impossible to complete because the server keeps thinking I’m in rapids/lava/poison water when I’m not.

The 100% isn’t all that interesting(but it might be masking an issue). That looks one of their routers is configured to ignore pings.

The above path pings indicate that the issue likely lies around the “lo0-central10.pcl-ag05.plus.net [195.166.128.186]” hop – if it’s got packet loss, it’ll be losing data for anything after it too (i.e. it doesn’t pass it on, so the packets never actually reach the NCSoft/ArenaNet servers). I’d be starting to speak with your ISP and providing them with those pathping results at that rate, given that this seems to be the first hop from your premises to theirs.

I’d also suggest checking a few other random servers around the net – I suspect you’ll get the same profile of packet loss being introduced at the [195.166.128.186] point, which’ll help your ISP track the issue. (If you were in Australia, I’d say that was a congestion issue at your local telephone exchange, because that’s a pretty classic type of failure here that gives exactly the type of pathpings you’re showing above. I don’t know what your local phone systems are like though, so I don’t know if that applies to where you live).

Okay – ran a few checks got all my ISP side issues sorted. Now its looking more like a Level 3 -> ANET problem. (Packet loss – > 48% at hops 14-15) I no longer have any packet loss before these hops.

Target Name: N/A
IP: 64.25.38.235
Date/Time: 26/09/2013 00:42:34 to 26/09/2013 01:35:41

Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 2277 0 0.0 0 2 0 [192.168.1.254]
2 2277 0 0.0 24 405 30 lo0-central10.pcl-ag08.plus.net [195.166.128.189]
3 2277 0 0.0 24 330 25 link-a-central10.pcl-gw01.plus.net [212.159.2.188]
4 2277 0 0.0 24 389 28 xe-9-1-0.pcl-cr01.plus.net [212.159.0.220]
5 2277 0 0.0 24 410 27 xe-11-1-0.edge3.London2.Level3.net [212.187.201.209]
6 2277 0 0.0 134 567 136 ae-3-3.ebr1.Paris1.Level3.net [4.69.141.86]
7 2277 3 0.1 136 583 137 ae-71-71.csw2.Paris1.Level3.net [4.69.161.82]
8 2277 2 0.1 136 644 137 ae-72-72.ebr2.Paris1.Level3.net [4.69.161.97]
9 195 0 0.0 137 315 140 ae-44-44.ebr2.Washington1.Level3.net [4.69.137.62]
10 192 0 0.0 136 294 139 ae-72-72.csw2.Washington1.Level3.net [4.69.134.150]
11 193 0 0.0 138 300 140 ae-71-71.ebr1.Washington1.Level3.net [4.69.134.133]
12 2277 2 0.1 136 634 137 ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
13 2277 1 0.0 134 598 136 ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
14 2067 1 0.0 136 560 138 ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]
15 2070 1011 48.8 135 294 138 ae-3-80.edge2.Dallas1.Level3.net [4.69.145.139]
16 2277 5 0.2 134 484 137 [4.59.197.34]
17 2277 5 0.2 136 450 138 [64.25.32.9]
18 2277 0 0.0 136 412 138 [64.25.32.26]
19 2277 4 0.2 135 330 137 [64.25.32.82]
20 2275 2275 100.0 0 0 0 [-]
21 2275 2275 100.0 0 0 0 [-]
22 2275 2275 100.0 0 0 0 [-]
23 2275 2275 100.0 0 0 0 [-]
24 2275 2275 100.0 0 0 0 [-]
25 2275 2275 100.0 0 0 0 [-]
26 2275 2275 100.0 0 0 0 [-]
27 2275 2275 100.0 0 0 0 [-]
28 2275 2275 100.0 0 0 0 [-]
29 2275 2275 100.0 0 0 0 [-]
30 2275 2275 100.0 0 0 0 [-]
31 2275 2275 100.0 0 0 0 [-]
32 2275 2275 100.0 0 0 0 [-]
33 2275 2275 100.0 0 0 0 [-]
34 2275 2275 100.0 0 0 0 [-]
35 2275 2275 100.0 0 0 0 [-]

Destination not reached in 35 hops

It’s getting ridiculous right now, I can barely do anything in the game.
It wasn’t like that before.

I have tested my connection multiple times on multiple games.

Countless speedtests on random servers across the world, everything is absolutely normal and working as expected on my end. It’s absurd that we’re experiencing so much lag PvP/PvE, just everywhere.

This has been reported to my ISP who hopefully can communicate with Level 3 to resolve these issues. My ISP has also confirmed that this is affecting a ‘lot’ of traffic from the UK to this destination.
The problem here is Level 3 @ Dallas router: ae-3-80.edge2.Dallas1.Level3.net [4.69.145.139]

Target Name: N/A
IP: 64.25.38.235
Date/Time: 26/09/2013 16:29:15 to 26/09/2013 16:52:33

Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 1000 0 0.0 0 2 0 [192.168.1.254]
2 1000 0 0.0 25 322 49 lo0-central10.pcl-ag08.plus.net [195.166.128.189]
3 1000 0 0.0 24 239 43 link-a-central10.pcl-gw01.plus.net [212.159.2.188]
4 1000 0 0.0 24 200 45 xe-9-1-0.pcl-cr01.plus.net [212.159.0.220]
5 1000 1 0.1 24 194 44 xe-11-1-0.edge3.London2.Level3.net [212.187.201.209]
6 1000 2 0.2 134 194 152 ae-3-3.ebr1.Paris1.Level3.net [4.69.141.86]
7 1000 1 0.1 136 213 154 ae-71-71.csw2.Paris1.Level3.net [4.69.161.82]
8 1000 1 0.1 136 203 154 ae-72-72.ebr2.Paris1.Level3.net [4.69.161.97]
9 1000 0 0.0 138 207 155 ae-44-44.ebr2.Washington1.Level3.net [4.69.137.62]
10 964 3 0.3 136 208 155 ae-72-72.csw2.Washington1.Level3.net [4.69.134.150]
11 11 0 0.0 137 171 157 ae-81-81.ebr1.Washington1.Level3.net [4.69.134.137]
12 1000 2 0.2 137 213 155 ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
13 1000 2 0.2 136 231 154 ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
14 991 2 0.2 137 247 156 ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]
15 989 318 32.2 137 235 157 ae-3-80.edge2.Dallas1.Level3.net [4.69.145.139]
16 999 1 0.1 135 210 154 [4.59.197.34]
17 999 1 0.1 137 217 155 [64.25.32.9]
18 999 0 0.0 137 209 155 [64.25.32.26]
19 999 1 0.1 136 233 155 [64.25.32.82]
20 997 997 100.0 0 0 0 [-]

Takato.4976:

It’s getting ridiculous right now, I can barely do anything in the game.
It wasn’t like that before.

I have tested my connection multiple times on multiple games.

Countless speedtests on random servers across the world, everything is absolutely normal and working as expected on my end. It’s absurd that we’re experiencing so much lag PvP/PvE, just everywhere.

Same problem here too.Anet cant understand that its their problem and they answering that we have to look our connection and change this,change that and bla bla.Iam playing GW from my home and netcafe from 2 different cities and ISP’S and the lag is the same .Anet we are not all TechGuru , and u have to admire that is your problem and not ours!

Please elaborate on how what appears to be a LEVEL 3 router issue is ANet’s problem to fix?

No doubt ANet needs to have their hardware provider or ISP report these issues of upstream packet loss, but they don’t own or manage the routers in question so how you jumped to the conclusion that THEY are responsible for the problem is beyond me.

welp going on a little more than a week and still unbearable lag in wvw/spvp. Noticing it now happens in dungeons as well. Funny thing is all my other games seem to not have this issue just guild wars 2.

Well – I sent it to the ISP the feedback was as follows:
Not a lot they can do (Its not them) – they wont even escalate it to Level 3.

I’m seeing ^50% packet loss on the dallas1.level3.net edge routers.
There has got to start being a better way of reporting these internet problems to backbone providers.

Does anyone have a level 3 ciruit ID? (This I think is the only way we can report it to level 3 to get this fixed)

I’m having the same issue with around 50% packet loss at the level three server in Dallas. Is there any way to avoid this?

I’m getting this extreme lag too.

same with me …. (my problem seems to be here ..). Any ideas?
1st. try:
9 —- 25/ 25 =100% 22/ 25 = 88% ae0-135.cr1.fra1.de.ipv4.kaiagloba
l.com [195.13.60.141]

2nd. try:
9 —- 25/ 25 =100% 21/ 25 = 84% ae0-135.cr1.fra1.de.ipv4.kaiagloba
l.com [195.13.60.141]

Is Anet going to do anything about this, I don’t know about anyone else but I have not been able to play for almost three weeks now.

Don’t jump on the bandwagon of people who don’t know what they are talking about. I have also not experienced lag anytime in the past month, so if you are, I would check everything with your local ISP to make sure your own line is running up to par.

Btw, 0% packet loss from that Level3 server that everyone wants to jump up and blame. If you are in Europe and on the NA server, why aren’t you playing on a local server instead of connecting to one across the ocean o.O Don’t blame a server that is working absolutely fine in Dallas.

im getting massive packet loss at Dallas1.level3.net as well. Is there anything that ANEt can do about this or not

Same here, Grievous. Shows ae-4-90.edge2.dallas1.level3.net shows to be a big problem.

Same issues @ Dallas1.level3.net… maybe Anet can escalate the issue to the appropriate ppl??

Here is mine.
Neither Anet or my ISP provider can assist me:

================ = Tracing network paths ================
—> pathping -w 500 -q 25 -4 64.25.39.1 <--

Tracing route to 64.25.39.1 over a maximum of 30 hops

0 JeffSher-PC.domain.actdsltmp [192.168.1.7]
1 192.168.1.1
2 L100.LSANCA-DSL-59.verizon-gni.net [98.119.43.1]
3 G0-6-0-5.LSANCA-LCR-21.verizon-gni.net [130.81.193.2]
4 ae4-0.LAX01-BB-RTR1.verizon-gni.net [130.81.199.98]
5 0.ae2.XT3.DFW9.ALTER.NET [140.222.225.55]
6 GigabitEthernet4-0-0.GW12.DFW9.ALTER.NET [152.63.97.86]
7 65.205.119.210
8 64.25.32.9
9 64.25.32.26
10 64.25.39.1

Computing statistics for 62 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 JeffSher-PC.domain.actdsltmp [192.168.1.7]
0/ 25 = 0% |
1 2ms 0/ 25 = 0% 0/ 25 = 0% 192.168.1.1
0/ 25 = 0% |
2 48ms 4/ 25 = 16% 4/ 25 = 16% L100.LSANCA-DSL-59.verizon-gni.net [98.119.43.1]
0/ 25 = 0% |
3 38ms 0/ 25 = 0% 0/ 25 = 0% G0-6-0-5.LSANCA-LCR-21.verizon-gni.net [130.81.193.2]
0/ 25 = 0% |
4 36ms 4/ 25 = 16% 4/ 25 = 16% ae4-0.LAX01-BB-RTR1.verizon-gni.net [130.81.199.98]
0/ 25 = 0% |
5 74ms 5/ 25 = 20% 5/ 25 = 20% 0.ae2.XT3.DFW9.ALTER.NET [140.222.225.55]
0/ 25 = 0% |
6 63ms 0/ 25 = 0% 0/ 25 = 0% GigabitEthernet4-0-0.GW12.DFW9.ALTER.NET [152.63.97.86]
5/ 25 = 20% |
7 75ms 5/ 25 = 20% 0/ 25 = 0% 65.205.119.210
0/ 25 = 0% |
8 80ms 5/ 25 = 20% 0/ 25 = 0% 64.25.32.9
1/ 25 = 4% |
9 —- 25/ 25 =100% 19/ 25 = 76% 64.25.32.26
0/ 25 = 0% |
10 78ms 6/ 25 = 24% 0/ 25 = 0% 64.25.39.1

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 JeffSher-PC.domain.actdsltmp [192.168.1.7]
1 192.168.1.1
2 L100.LSANCA-DSL-59.verizon-gni.net [98.119.43.1]
3 G0-6-0-5.LSANCA-LCR-21.verizon-gni.net [130.81.193.2]
4 so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
5 0.ge-5-1-0.XL3.CHI13.ALTER.NET [152.63.0.190]
6 TenGigE0-6-2-0.GW2.CHI13.ALTER.NET [152.63.65.137]
7 tinet-gw.customer.alter.net [152.179.92.6]
8 * xe-0-0-1.fra23.ip4.tinet.net [141.136.110.121]
9 * 89.149.164.42
10 * 206-127-157-86.plaync.com [206.127.157.86]
11 p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]

Computing statistics for 68 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 JeffSher-PC.domain.actdsltmp [192.168.1.7]
0/ 25 = 0% |
1 2ms 0/ 25 = 0% 0/ 25 = 0% 192.168.1.1
1/ 25 = 4% |
2 33ms 2/ 25 = 8% 1/ 25 = 4% L100.LSANCA-DSL-59.verizon-gni.net [98.119.43.1]
0/ 25 = 0% |
3 31ms 1/ 25 = 4% 0/ 25 = 0% G0-6-0-5.LSANCA-LCR-21.verizon-gni.net [130.81.193.2]
1/ 25 = 4% |
4 33ms 2/ 25 = 8% 0/ 25 = 0% so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
2/ 25 = 8% |
5 93ms 6/ 25 = 24% 2/ 25 = 8% 0.ge-5-1-0.XL3.CHI13.ALTER.NET [152.63.0.190]
0/ 25 = 0% |
6 82ms 4/ 25 = 16% 0/ 25 = 0% TenGigE0-6-2-0.GW2.CHI13.ALTER.NET [152.63.65.137]
0/ 25 = 0% |
7 84ms 4/ 25 = 16% 0/ 25 = 0% tinet-gw.customer.alter.net [152.179.92.6]
5/ 25 = 20% |
8 —- 25/ 25 =100% 16/ 25 = 64% xe-0-0-1.fra23.ip4.tinet.net [141.136.110.121]
0/ 25 = 0% |
9 215ms 19/ 25 = 76% 10/ 25 = 40% 89.149.164.42
0/ 25 = 0% |
10 —- 25/ 25 =100% 16/ 25 = 64% 206-127-157-86.plaync.com [206.127.157.86]
0/ 25 = 0% |
11 203ms 9/ 25 = 36% 0/ 25 = 0% p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]

Trace complete.
Section completed in 151.63 seconds

@jayvux.4128 i had same problems after EotM patch and i found that the level3 top network had issues , like you have with tinet.net .

it seems that there is 100% packet lost between this network and you and this affect the next network hopes inside plaync domain.

if you want you can check some things. 1. apply static ip in your network card ( 192.168.1.7 ) if you don’t know how : http://www.howtogeek.com/howto/19249/how-to-assign-a-static-ip-address-in-xp-vista-or-windows-7/ . 2. clear your dns cache : http://www.tech-recipes.com/rx/233/clear_windows_dns_cache/ 3. close and unplug your home router for at least 15 minutes to loose any static charge and your dslam if you have adsl it will reset your position on it and as a final solution 4. speak with your isp and said them that you found the problem that is coming from tinet.net network and if they can check or change the route to plaync network .some times a router restart from their side can solve the problem

i did all of these and the problem fixed …. where was the problem i didn’t find yet ,because i did all of them at the same time

I will definite give this a go, thanks Reborn

ISP agents said they don’t know anything about this, neither do their specialists :X

jayvux.4128:

ISP agents said they don’t know anything about this, neither do their specialists :X

From windows command prompt issue the following

tracert 206.127.158.1

when completed right click and choose mark. Highlight all the text then right click again. and paste it here.

Your wasting your time posting your TRACE ROUTES Anet will deny it is their problem until it goes away.

Colly.4073:

Your wasting your time posting your TRACE ROUTES Anet will deny it is their problem until it goes away.

Trace routes prove where the issue lays.

If its not anet, its not anet….its pretty black and white you know.

Oh I was referring to the whole tineti and plaync network matter, but here it is @ sirsquishy

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Jeff Sher>tracert 206.127.158.1

Tracing route to p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 15 ms 17 ms 9 ms L100.LSANCA-DSL-59.verizon-gni.net [98.119.43.1

3 11 ms 12 ms 13 ms G0-6-0-5.LSANCA-LCR-21.verizon-gni.net [130.81.
93.2]
4 11 ms 10 ms 14 ms so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.8
.29.124]
5 62 ms 61 ms 62 ms 0.xe-4-0-3.XL3.CHI13.ALTER.NET [152.63.64.118]
6 65 ms 63 ms 62 ms TenGigE0-4-1-0.GW2.CHI13.ALTER.NET [152.63.65.2
9]
7 60 ms 60 ms 62 ms tinet-gw.customer.alter.net [152.179.92.6]
8 251 ms 249 ms 249 ms xe-7-3-2.fra23.ip4.tinet.net [141.136.110.97]
9 254 ms 254 ms 254 ms 89.149.164.42
10 250 ms 252 ms 248 ms 206-127-157-86.plaync.com [206.127.157.86]
11 296 ms 254 ms 297 ms p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]

Trace complete.

C:\Users\Jeff Sher>

jayvux.4128:

Oh I was referring to the whole tineti and plaync network matter, but here it is @ sirsquishy

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Jeff Sher>tracert 206.127.158.1

Tracing route to p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 15 ms 17 ms 9 ms L100.LSANCA-DSL-59.verizon-gni.net [98.119.43.1

3 11 ms 12 ms 13 ms G0-6-0-5.LSANCA-LCR-21.verizon-gni.net [130.81.
93.2]
4 11 ms 10 ms 14 ms so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.8
.29.124]
5 62 ms 61 ms 62 ms 0.xe-4-0-3.XL3.CHI13.ALTER.NET [152.63.64.118]
6 65 ms 63 ms 62 ms TenGigE0-4-1-0.GW2.CHI13.ALTER.NET [152.63.65.2
9]
7 60 ms 60 ms 62 ms tinet-gw.customer.alter.net [152.179.92.6]
8 251 ms 249 ms 249 ms xe-7-3-2.fra23.ip4.tinet.net [141.136.110.97]
9 254 ms 254 ms 254 ms 89.149.164.42
10 250 ms 252 ms 248 ms 206-127-157-86.plaync.com [206.127.157.86]
11 296 ms 254 ms 297 ms p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]

Trace complete.

C:\Users\Jeff Sher>

This is your affected Hop, its even before tinet. the nice thing, you can call Verizon and have them do Head to head testing with Alternet since thats the main handoff going in Anets direction from you.

5 62 ms 61 ms 62 ms 0.xe-4-0-3.XL3.CHI13.ALTER.NET [152.63.64.118]

sirsquishy.8531:

jayvux.4128:

Oh I was referring to the whole tineti and plaync network matter, but here it is @ sirsquishy

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Jeff Sher>tracert 206.127.158.1

Tracing route to p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 15 ms 17 ms 9 ms L100.LSANCA-DSL-59.verizon-gni.net [98.119.43.1

3 11 ms 12 ms 13 ms G0-6-0-5.LSANCA-LCR-21.verizon-gni.net [130.81.
93.2]
4 11 ms 10 ms 14 ms so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.8
.29.124]
5 62 ms 61 ms 62 ms 0.xe-4-0-3.XL3.CHI13.ALTER.NET [152.63.64.118]
6 65 ms 63 ms 62 ms TenGigE0-4-1-0.GW2.CHI13.ALTER.NET [152.63.65.2
9]
7 60 ms 60 ms 62 ms tinet-gw.customer.alter.net [152.179.92.6]
8 251 ms 249 ms 249 ms xe-7-3-2.fra23.ip4.tinet.net [141.136.110.97]
9 254 ms 254 ms 254 ms 89.149.164.42
10 250 ms 252 ms 248 ms 206-127-157-86.plaync.com [206.127.157.86]
11 296 ms 254 ms 297 ms p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]

Trace complete.

C:\Users\Jeff Sher>

This is your affected Hop, its even before tinet. the nice thing, you can call Verizon and have them do Head to head testing with Alternet since thats the main handoff going in Anets direction from you.

5 62 ms 61 ms 62 ms 0.xe-4-0-3.XL3.CHI13.ALTER.NET [152.63.64.118]

Thanks a bunch, I’ll give that a shot =)

I found I was getting packet loss when I fired a projectile (fireball) and saw it hit the target without any animation from my character. The animation happened another 1-2secs later.

I tried the same procedure for packet loss as above.

• Hop #9: [65ms] bundle-ether1.pad-gw2.sydney.telstra.net [203.50.6.29] = 96% packet loss.
• Hop #11: [—-] i-0-3-0-1.paix-core01.bx.telstraglobal.net [202.84.140.165] = 100% packet loss.
• Hop #13: [225ms] i-0-0-0-5.eqnx03.bi.telstraglobal.net [202.84.251.22] = 96% packet loss.
• Hop #14: [248ms] l3-peer.eqnx03.pr.telstraglobal.net [134.159.62.198] = 36% packet loss.
• Hop #15: [239ms] vlan60.csw1.SanJose.Level3.net [4.69.152.62] = 36% packet loss.
• Hop #16: [239ms] ae-62-62.ebr2.SanJose.Level3.net [4.69.153.17] = 88% packet loss.
• Hop #18: [222ms] ae-6-6.ebr2.LosAngeles1.Level3.net [4.69.148.201] = 96% packet loss.
• Hop #20: [—-] ae-73-73.csw2.Dallas1.Level3.net [4.69.151.145] = 100% packet loss.
• Hop #22: [255ms] 4.59.197.34 = 100% packet loss.
• Hop #24: [—-] 64.25.32.26 = 100% packet loss.

These are all the areas that my connection suffers from packet loss. Out of 25 total hops, it’s subjected to severe packet loss in 40% of them. The last one is most concerning, since that’s admist GW2’s servers.