Guild Wars 2

Anyone in NA been experiencing this over the last few days/hours? Massive, unexplainable latency-spikes that are specifically and solely tied into this game, and nothing else.

It’s probably level3 in Texas. Nothing Anet owns or controls. You can check here https://forum-en.gw2archive.eu/forum/support/support/How-to-Lag-Latencey-Issues/first#post6143842

Massive, massive issues the last couple days. And like you said, solely tied into Guild Wars 2. Spiked to 4900 ping in the middle of a fractal. Can’t figure out any reasoning for it.

I can’t play WvW atm, it’s lagging out every second or two, sometimes for 15s or more. Been playing PvE all night no issues, the second I go to WvW it’s unplayable. Needs to be fixed, I’m so angry at it right now and it’s totally destroying the point of playing for me.

http://www.speedtest.net/my-result/5315331865 – Speedtest done immediately after I ragequit. It’s def not my end lol xD

Jugglemonkey.8741:

I can’t play WvW atm, it’s lagging out every second or two, sometimes for 15s or more. Been playing PvE all night no issues, the second I go to WvW it’s unplayable. Needs to be fixed, I’m so angry at it right now and it’s totally destroying the point of playing for me.

http://www.speedtest.net/my-result/5315331865 – Speedtest done immediately after I ragequit. It’s def not my end lol xD

Speed test won’t tell you anything besides your Local connection. If you don’t live in Texas then speed test tells you very little with your connection to the servers. See my link above.

In EU yesterday i had a ping spike of 2090 (my highest ever, that I could see in F11 window). It was so bad, my game froze 2 minutes, then unfroze. When all ppl died in fractals, there was no respawn window. When everybody ragequit (leaving me alone in the frac), the window finally came. Meanwhile i tested youtube, twitch, absolutely no delays in them. Gw2 forums also had high ping.

Phoebe Ascension.8437:

In EU yesterday i had a ping spike of 2090 (my highest ever, that I could see in F11 window). It was so bad, my game froze 2 minutes, then unfroze. When all ppl died in fractals, there was no respawn window. When everybody ragequit (leaving me alone in the frac), the window finally came. Meanwhile i tested youtube, twitch, absolutely no delays in them. Gw2 forums also had high ping.

Testing Youtube, Twitch, speed test or anything does no good. All of those servers are in different locations. Your issues are in the connection between your PC and the Anet server. As stated many times before run “Pingplotter” its free. This will tell you where the problem is and also identify who the owner of the problem is.

In NA, massive lagspikes last night in WvW, the zerg showed up, my powers froze and I appear dead the next 2 minutes.

Huge lag, like 5000 ping!!! Molasses lag! >_<

I also experience lag and disconnects. I found that I was getting 100% packet loss on
7 * ae-3-80.edge7.Frankfurt1.Level3.net [4.69.154.139]
8 ae-3-80.edge7.Frankfurt1.Level3.net [4.69.154.139]
9 206-127-157-86.ncsoft.com [206.127.157.86]

deadrage.8419:

I also experience lag and disconnects. I found that I was getting 100% packet loss on
7 * ae-3-80.edge7.Frankfurt1.Level3.net [4.69.154.139]
8 ae-3-80.edge7.Frankfurt1.Level3.net [4.69.154.139]
9 206-127-157-86.ncsoft.com [206.127.157.86]

Your packet loss will trickle down into Anet servers. It’s really level3 giving you the problem.

ANET is currently having issues, i play on an mpls line provided through my job, nothing on their end can sort it, just gotta wait for anet to approach the provider and get them to fix it before SLA breaches.

Hate to be the one to break the bad news to you, but it’s not Anet. If the problem was Anet it would be affecting “EVERY” player, not just some. Run ping plotter and it will show you where the problem is. You can then provide this to your ISP and they can assist you in trying to get it fixed.

Getting unplayable lag right now in GW2. Was fine for like 6 hours, then suddenly unplayable.

Meanwhile I have 0 packet loss on TS and I’m able to play other video games with sub 50 ping.

Shiyo.3578:

Getting unplayable lag right now in GW2. Was fine for like 6 hours, then suddenly unplayable.

Meanwhile I have 0 packet loss on TS and I’m able to play other video games with sub 50 ping.

Run ping plotter and find out where the problem is.

I’m getting tons of lag here too! Between 2000 and 1500 pings in LA, around 800 in Black Citadel. Tested other games and connections, lag is less and normal. Only GW2 is giving me problems.

I’m from Buenos Aires, Argentina, South America. Also running diagnistics in gw2.exe, I will report back soon!

I have no clue how to read this:

Active Connections

Proto Local Address Foreign Address State
TCP 192.168.1.3:51627 208.78.164.11:27019 ESTABLISHED
TCP 192.168.1.3:51631 23.12.173.49:80 ESTABLISHED
TCP 192.168.1.3:51632 23.12.173.49:80 ESTABLISHED
TCP 192.168.1.3:51633 200.123.197.153:80 ESTABLISHED
TCP 192.168.1.3:51635 200.123.197.153:80 ESTABLISHED
TCP 192.168.1.3:51636 200.123.197.153:80 ESTABLISHED
TCP 192.168.1.3:51637 200.123.197.153:80 ESTABLISHED
TCP 192.168.1.3:51638 200.123.197.153:80 ESTABLISHED
TCP 192.168.1.3:51640 200.123.197.145:80 ESTABLISHED
TCP 192.168.1.3:51709 200.123.197.152:80 ESTABLISHED
TCP 192.168.1.3:51710 200.123.197.152:80 ESTABLISHED
TCP 192.168.1.3:51711 200.123.197.152:80 ESTABLISHED
TCP 192.168.1.3:51712 200.123.197.152:80 ESTABLISHED
TCP 192.168.1.3:51713 200.123.197.152:80 ESTABLISHED
TCP 192.168.1.3:51720 64.233.186.95:443 ESTABLISHED
TCP 192.168.1.3:51722 64.233.186.188:5228 ESTABLISHED
TCP 192.168.1.3:51723 172.217.28.13:443 ESTABLISHED
TCP 192.168.1.3:51724 64.233.186.95:443 TIME_WAIT
TCP 192.168.1.3:51725 172.217.28.13:443 ESTABLISHED
TCP 192.168.1.3:51726 172.217.29.4:443 ESTABLISHED
TCP 192.168.1.3:51727 64.233.186.100:443 ESTABLISHED
TCP 192.168.1.3:51728 216.58.222.174:443 ESTABLISHED
TCP 192.168.1.3:51729 64.233.186.100:443 ESTABLISHED
TCP 192.168.1.3:51730 64.233.186.100:443 ESTABLISHED
TCP 192.168.1.3:51733 172.217.28.35:443 ESTABLISHED
TCP 192.168.1.3:51735 192.16.58.26:443 ESTABLISHED
TCP 192.168.1.3:51736 192.16.58.26:443 ESTABLISHED
TCP 192.168.1.3:51737 192.16.58.26:443 ESTABLISHED
TCP 192.168.1.3:51738 192.16.58.26:443 ESTABLISHED
TCP 192.168.1.3:51739 192.16.58.26:443 ESTABLISHED
TCP 192.168.1.3:51744 104.16.94.234:443 ESTABLISHED
TCP 192.168.1.3:51745 192.16.58.26:443 ESTABLISHED
TCP 192.168.1.3:51746 192.16.58.26:443 ESTABLISHED
TCP 192.168.1.3:51747 192.16.58.26:443 ESTABLISHED
TCP 192.168.1.3:51748 192.16.58.26:443 ESTABLISHED
TCP 192.168.1.3:51749 192.16.58.26:443 ESTABLISHED
TCP 192.168.1.3:51750 192.16.58.26:443 ESTABLISHED
TCP 192.168.1.3:51752 64.233.190.97:443 ESTABLISHED
TCP 192.168.1.3:51754 104.16.19.13:443 ESTABLISHED
TCP 192.168.1.3:51755 52.85.166.55:443 CLOSE_WAIT
TCP 192.168.1.3:51756 64.233.190.97:443 ESTABLISHED
TCP 192.168.1.3:51757 72.21.92.82:80 ESTABLISHED
TCP 192.168.1.3:51759 172.217.29.4:80 ESTABLISHED
TCP 192.168.1.3:51760 104.73.102.141:80 ESTABLISHED
TCP 192.168.1.3:51770 104.73.108.73:80 ESTABLISHED
TCP 192.168.1.3:51778 192.0.80.240:443 ESTABLISHED
TCP 192.168.1.3:51779 192.16.58.26:443 ESTABLISHED
TCP 192.168.1.3:51780 192.0.77.2:443 ESTABLISHED
TCP 192.168.1.3:51787 186.125.202.242:8080 TIME_WAIT
TCP 192.168.1.3:51788 186.125.202.242:8080 TIME_WAIT
TCP 192.168.1.3:51789 186.125.202.242:8080 TIME_WAIT
TCP 192.168.1.3:51790 186.125.202.242:8080 TIME_WAIT
TCP 192.168.1.3:51792 186.125.202.242:8080 TIME_WAIT
TCP 192.168.1.3:51793 186.125.202.242:8080 TIME_WAIT
TCP 192.168.1.3:51794 186.125.202.242:8080 TIME_WAIT
TCP 192.168.1.3:51796 23.4.43.27:80 ESTABLISHED
TCP 192.168.1.3:51797 23.4.43.27:80 ESTABLISHED
Section completed in 0.31 seconds

Diag.ArenaNetworks.com
64.25.38.54:80 – connect succeeded
64.25.38.72:80 – connect succeeded
64.25.38.172:80 – connect succeeded
64.25.38.171:6112 – connect succeeded
64.25.38.171:80 – connect succeeded
64.25.38.51:6112 – connect succeeded
64.25.38.172:6112 – connect succeeded
64.25.38.54:6112 – connect succeeded
64.25.38.51:80 – connect succeeded
64.25.38.72:6112 – connect succeeded

Section completed in 0.76 seconds

assetcdn.101.ArenaNetworks.com.
190.94.183.73:80 – connect succeeded
190.94.183.71:80 – connect succeeded

Section completed in 0.16 seconds

auth1.101.ArenaNetworks.com.
64.25.38.51:6112 – connect succeeded
64.25.38.54:6112 – connect succeeded
64.25.38.72:6112 – connect succeeded
64.25.38.171:6112 – connect succeeded
64.25.38.172:6112 – connect succeeded

Section completed in 3.43 seconds

auth2.101.ArenaNetworks.com.
206.127.159.108:6112 – connect succeeded
206.127.146.74:6112 – connect succeeded
206.127.159.109:6112 – connect succeeded
206.127.146.73:6112 – connect succeeded
206.127.159.77:6112 – connect succeeded
206.127.159.107:6112 – connect succeeded

Section completed in 0.47 seconds

cligate.101.NCPlatform.net.
64.25.40.111:6112 – connect succeeded
64.25.40.110:6112 – connect succeeded
64.25.40.114:6112 – connect succeeded
64.25.40.115:6112 – connect succeeded
64.25.40.109:6112 – connect succeeded
64.25.40.113:6112 – connect succeeded
64.25.40.112:6112 – connect succeeded

Section completed in 9.58 seconds

================ = Tracing network paths (about 10 mins) ================
—> pathping -w 500 -q 50 -4 206.127.158.1 <--

Tracing route to 206-127-158-1.ncsoft.com [206.127.158.1]
over a maximum of 30 hops:
0 Kaylee.Home [192.168.1.3]
1 192.168.1.1
2 host120.200-3-60.telecom.net.ar [200.3.60.120]
3 host4.181-88-170.telecom.net.ar [181.88.170.4]
4 * host236.181-88-108.telecom.net.ar [181.88.108.236]
5 host162.190-225-252.telecom.net.ar [190.225.252.162]
6 xe-8-1-0.baires3.bai.seabone.net [195.22.220.53]
7 et-4-3-0.miami15.mia.seabone.net [195.22.199.177]
8 * et-10-1-0.miami15.mia.seabone.net [89.221.41.175]
9 mai-b1-link.telia.net [80.239.193.161]
10 * ash-bb4-link.telia.net [62.115.136.204]
11 * ffm-bb2-link.telia.net [213.155.135.58]
12 ffm-b1-link.telia.net [62.115.141.239]
13 * ncsoft-ic-306349-ffm-b11.c.telia.net [62.115.43.74]
14 206-127-157-86.ncsoft.com [206.127.157.86]
15 206-127-158-1.ncsoft.com [206.127.158.1]

Computing statistics for 187 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Kaylee.Home [192.168.1.3]
0/ 50 = 0% |
1 0ms 0/ 50 = 0% 0/ 50 = 0% 192.168.1.1
1/ 50 = 2% |
2 30ms 7/ 50 = 14% 6/ 50 = 12% host120.200-3-60.telecom.net.ar [200.3.60.120]
0/ 50 = 0% |
3 29ms 1/ 50 = 2% 0/ 50 = 0% host4.181-88-170.telecom.net.ar [181.88.170.4]
0/ 50 = 0% |
4 34ms 6/ 50 = 12% 5/ 50 = 10% host236.181-88-108.telecom.net.ar [181.88.108.236]
0/ 50 = 0% |
5 28ms 2/ 50 = 4% 1/ 50 = 2% host162.190-225-252.telecom.net.ar [190.225.252.162]
0/ 50 = 0% |
6 28ms 1/ 50 = 2% 0/ 50 = 0% xe-8-1-0.baires3.bai.seabone.net [195.22.220.53]
13/ 50 = 26% |
7 158ms 20/ 50 = 40% 6/ 50 = 12% et-4-3-0.miami15.mia.seabone.net [195.22.199.177]
0/ 50 = 0% |
8 153ms 14/ 50 = 28% 0/ 50 = 0% et-10-1-0.miami15.mia.seabone.net [89.221.41.175]
1/ 50 = 2% |
9 156ms 15/ 50 = 30% 0/ 50 = 0% mai-b1-link.telia.net [80.239.193.161]
6/ 50 = 12% |
10 174ms 21/ 50 = 42% 0/ 50 = 0% ash-bb4-link.telia.net [62.115.136.204]
4/ 50 = 8% |
11 277ms 25/ 50 = 50% 0/ 50 = 0% ffm-bb2-link.telia.net [213.155.135.58]
6/ 50 = 12% |
12 273ms 31/ 50 = 62% 0/ 50 = 0% ffm-b1-link.telia.net [62.115.141.239]
2/ 50 = 4% |
13 —- 50/ 50 =100% 17/ 50 = 34% ncsoft-ic-306349-ffm-b11.c.telia.net [62.115.43.74]
0/ 50 = 0% |
14 —- 50/ 50 =100% 17/ 50 = 34% 206-127-157-86.ncsoft.com [206.127.157.86]
0/ 50 = 0% |
15 290ms 33/ 50 = 66% 0/ 50 = 0% 206-127-158-1.ncsoft.com [206.127.158.1]

Trace complete.
—> pathping -w 500 -q 50 -4 64.25.39.1 <--

Tracing route to 64.25.33-1.ncsoft.com [64.25.39.1]
over a maximum of 30 hops:
0 Kaylee.Home [192.168.1.3]
1 192.168.1.1
2 host120.200-3-60.telecom.net.ar [200.3.60.120]
3 host4.181-88-170.telecom.net.ar [181.88.170.4]
4 host46.181-88-170.telecom.net.ar [181.88.170.46]
5 host166.190-225-252.telecom.net.ar [190.225.252.166]
6 xe-8-1-0.baires3.bai.seabone.net [195.22.220.53]
7 et-10-3-0.miami15.mia.seabone.net [89.221.41.177]
8 * et-10-3-0.miami15.mia.seabone.net [89.221.41.177]
9 * * *
Computing statistics for 100 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Kaylee.Home [192.168.1.3]
0/ 50 = 0% |
1 0ms 0/ 50 = 0% 0/ 50 = 0% 192.168.1.1
3/ 50 = 6% |
2 35ms 4/ 50 = 8% 1/ 50 = 2% host120.200-3-60.telecom.net.ar [200.3.60.120]
0/ 50 = 0% |
3 33ms 3/ 50 = 6% 0/ 50 = 0% host4.181-88-170.telecom.net.ar [181.88.170.4]
0/ 50 = 0% |
4 37ms 3/ 50 = 6% 0/ 50 = 0% host46.181-88-170.telecom.net.ar [181.88.170.46]
1/ 50 = 2% |
5 37ms 5/ 50 = 10% 1/ 50 = 2% host166.190-225-252.telecom.net.ar [190.225.252.166]
0/ 50 = 0% |
6 40ms 4/ 50 = 8% 0/ 50 = 0% xe-8-1-0.baires3.bai.seabone.net [195.22.220.53]
13/ 50 = 26% |
7 159ms 17/ 50 = 34% 0/ 50 = 0% et-10-3-0.miami15.mia.seabone.net [89.221.41.177]
0/ 50 = 0% |
8 161ms 17/ 50 = 34% 0/ 50 = 0% et-10-3-0.miami15.mia.seabone.net [89.221.41.177]

Trace complete.
—> pathping -w 500 -q 50 -4 190.94.183.71 <--

Tracing route to 190.94.183.71 over a maximum of 30 hops

0 Kaylee.Home [192.168.1.3]
1 192.168.1.1
2 host120.200-3-60.telecom.net.ar [200.3.60.120]
3 host4.181-88-170.telecom.net.ar [181.88.170.4]
4 host236.181-88-108.telecom.net.ar [181.88.108.236]
5 host221.181-88-108.telecom.net.ar [181.88.108.221]
6 host202.181-88-134.telecom.net.ar [181.88.134.202]
7 190.94.182.130
8 190.94.183.71

Computing statistics for 100 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Kaylee.Home [192.168.1.3]
0/ 50 = 0% |
1 0ms 0/ 50 = 0% 0/ 50 = 0% 192.168.1.1
2/ 50 = 4% |
2 22ms 3/ 50 = 6% 1/ 50 = 2% host120.200-3-60.telecom.net.ar [200.3.60.120]
0/ 50 = 0% |
3 24ms 4/ 50 = 8% 2/ 50 = 4% host4.181-88-170.telecom.net.ar [181.88.170.4]
0/ 50 = 0% |
4 28ms 3/ 50 = 6% 1/ 50 = 2% host236.181-88-108.telecom.net.ar [181.88.108.236]
0/ 50 = 0% |
5 25ms 4/ 50 = 8% 2/ 50 = 4% host221.181-88-108.telecom.net.ar [181.88.108.221]
0/ 50 = 0% |
6 28ms 2/ 50 = 4% 0/ 50 = 0% host202.181-88-134.telecom.net.ar [181.88.134.202]
3/ 50 = 6% |
7 48ms 5/ 50 = 10% 0/ 50 = 0% 190.94.182.130
1/ 50 = 2% |
8 45ms 6/ 50 = 12% 0/ 50 = 0% 190.94.183.71

Trace complete.
Section completed in 348.63 seconds

================ = Running DirectX diagnostic ================
—> dxdiag /whql:off /t C:\Users\Kitty\AppData\Local\Temp\GWT93EC.tmp <—
Section completed in 0.23 seconds

================ = Result ================
Test complete
<EOF>

Seems that there is a bit of package loss at the near end, near to anet servers, is what I’m reading correct?

It appears that the biggest problem is at this point.

baires3.bai.seabone.net

It is not owned, operated nor has anything to do with Anet. Your best bet is the contact your ISP and give them that information.

Your problem starts here:

2 30ms 7/ 50 = 14% 6/ 50 = 12% host120.200-3-60.telecom.net.ar [200.3.60.120]

This shows [first] 14% packet loss (7 out of 50) and [second] 12% packet loss (6 out of 50).

You always want to look at the node where the packet loss first starts.

It fixed itself after a while, but yes, I need to call my ISP and pray for a competent CS rep to understand what I mean to tell them.

le sighs

Right now it looks like this:

================ = Discovering external address ================
Connect failed
Section completed in 10.05 seconds

================ = Checking server connectivity ================
Section completed in 0.00 seconds

Diag.ArenaNetworks.com
64.25.38.51:80 – connect succeeded
64.25.38.72:80 – connect succeeded
64.25.38.54:80 – connect succeeded
64.25.38.172:80 – connect succeeded
64.25.38.54:6112 – connect succeeded
64.25.38.171:80 – connect succeeded
64.25.38.172:6112 – connect succeeded
64.25.38.171:6112 – connect succeeded
64.25.38.72:6112 – connect succeeded
64.25.38.51:6112 – connect succeeded

Section completed in 0.47 seconds

assetcdn.101.ArenaNetworks.com.
190.94.183.77:80 – connect succeeded
190.94.183.78:80 – connect succeeded

Section completed in 0.14 seconds

auth1.101.ArenaNetworks.com.
64.25.38.72:6112 – connect succeeded
64.25.38.172:6112 – connect succeeded
64.25.38.51:6112 – connect succeeded
64.25.38.54:6112 – connect succeeded
64.25.38.171:6112 – connect succeeded

Section completed in 0.23 seconds

auth2.101.ArenaNetworks.com.
206.127.146.74:6112 – connect succeeded
206.127.159.109:6112 – connect succeeded
206.127.159.77:6112 – connect succeeded
206.127.146.73:6112 – connect succeeded
206.127.159.108:6112 – connect succeeded
206.127.159.107:6112 – connect succeeded

Section completed in 0.55 seconds

cligate.101.NCPlatform.net.
64.25.40.111:6112 – connect succeeded
64.25.40.110:6112 – connect succeeded
64.25.40.112:6112 – connect succeeded
64.25.40.115:6112 – connect succeeded
64.25.40.114:6112 – connect succeeded
64.25.40.109:6112 – connect succeeded
64.25.40.113:6112 – connect succeeded

Section completed in 0.31 seconds

================ = Tracing network paths (about 10 mins) ================
—> pathping -w 500 -q 50 -4 206.127.158.1 <--

Tracing route to 206-127-158-1.ncsoft.com [206.127.158.1]
over a maximum of 30 hops:
0 Kaylee.Home [192.168.1.3]
1 192.168.1.1
2 host120.200-3-60.telecom.net.ar [200.3.60.120]
3 host4.181-88-170.telecom.net.ar [181.88.170.4]
4 host236.181-88-108.telecom.net.ar [181.88.108.236]
5 host162.190-225-252.telecom.net.ar [190.225.252.162]
6 xe-8-1-0.baires3.bai.seabone.net [195.22.220.53]
7 * et-4-3-0.miami15.mia.seabone.net [195.22.199.177]
8 et-10-1-0.miami15.mia.seabone.net [89.221.41.175]
9 * mai-b1-link.telia.net [80.239.193.161]
10 ash-bb4-link.telia.net [62.115.136.204]
11 * ffm-bb2-link.telia.net [213.155.135.58]
12 ffm-b1-link.telia.net [62.115.141.237]
13 * ncsoft-ic-306349-ffm-b11.c.telia.net [62.115.43.74]
14 206-127-157-86.ncsoft.com [206.127.157.86]
15 * 206-127-158-1.ncsoft.com [206.127.158.1]

Computing statistics for 187 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Kaylee.Home [192.168.1.3]
0/ 50 = 0% |
1 0ms 0/ 50 = 0% 0/ 50 = 0% 192.168.1.1
0/ 50 = 0% |
2 21ms 0/ 50 = 0% 0/ 50 = 0% host120.200-3-60.telecom.net.ar [200.3.60.120]
0/ 50 = 0% |
3 22ms 6/ 50 = 12% 6/ 50 = 12% host4.181-88-170.telecom.net.ar [181.88.170.4]
0/ 50 = 0% |
4 26ms 0/ 50 = 0% 0/ 50 = 0% host236.181-88-108.telecom.net.ar [181.88.108.236]
3/ 50 = 6% |
5 24ms 3/ 50 = 6% 0/ 50 = 0% host162.190-225-252.telecom.net.ar [190.225.252.162]
7/ 50 = 14% |
6 58ms 10/ 50 = 20% 0/ 50 = 0% xe-8-1-0.baires3.bai.seabone.net [195.22.220.53]
0/ 50 = 0% |
7 159ms 10/ 50 = 20% 0/ 50 = 0% et-4-3-0.miami15.mia.seabone.net [195.22.199.177]
5/ 50 = 10% |
8 159ms 20/ 50 = 40% 5/ 50 = 10% et-10-1-0.miami15.mia.seabone.net [89.221.41.175]
0/ 50 = 0% |
9 158ms 15/ 50 = 30% 0/ 50 = 0% mai-b1-link.telia.net [80.239.193.161]
1/ 50 = 2% |
10 184ms 16/ 50 = 32% 0/ 50 = 0% ash-bb4-link.telia.net [62.115.136.204]
8/ 50 = 16% |
11 290ms 31/ 50 = 62% 7/ 50 = 14% ffm-bb2-link.telia.net [213.155.135.58]
0/ 50 = 0% |
12 277ms 24/ 50 = 48% 0/ 50 = 0% ffm-b1-link.telia.net [62.115.141.237]
2/ 50 = 4% |
13 292ms 49/ 50 = 98% 23/ 50 = 46% ncsoft-ic-306349-ffm-b11.c.telia.net [62.115.43.74]
0/ 50 = 0% |
14 —- 50/ 50 =100% 24/ 50 = 48% 206-127-157-86.ncsoft.com [206.127.157.86]
0/ 50 = 0% |
15 280ms 26/ 50 = 52% 0/ 50 = 0% 206-127-158-1.ncsoft.com [206.127.158.1]

Trace complete.
—> pathping -w 500 -q 50 -4 64.25.39.1 <--

Tracing route to 64.25.33-1.ncsoft.com [64.25.39.1]
over a maximum of 30 hops:
0 Kaylee.Home [192.168.1.3]
1 192.168.1.1
2 host120.200-3-60.telecom.net.ar [200.3.60.120]
3 * host4.181-88-170.telecom.net.ar [181.88.170.4]
4 host46.181-88-170.telecom.net.ar [181.88.170.46]
5 host166.190-225-252.telecom.net.ar [190.225.252.166]
6 xe-8-1-0.baires3.bai.seabone.net [195.22.220.53]
7 * et-10-3-0.miami15.mia.seabone.net [89.221.41.177]
8 et-10-3-0.miami15.mia.seabone.net [89.221.41.177]
9 * * xe-11-0-0.edge2.miami1.Level3.net [63.209.150.165]
10 * * *
Computing statistics for 112 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Kaylee.Home [192.168.1.3]
0/ 50 = 0% |
1 0ms 0/ 50 = 0% 0/ 50 = 0% 192.168.1.1
1/ 50 = 2% |
2 22ms 2/ 50 = 4% 1/ 50 = 2% host120.200-3-60.telecom.net.ar [200.3.60.120]
0/ 50 = 0% |
3 22ms 1/ 50 = 2% 0/ 50 = 0% host4.181-88-170.telecom.net.ar [181.88.170.4]
1/ 50 = 2% |
4 26ms 3/ 50 = 6% 1/ 50 = 2% host46.181-88-170.telecom.net.ar [181.88.170.46]
0/ 50 = 0% |
5 24ms 2/ 50 = 4% 0/ 50 = 0% host166.190-225-252.telecom.net.ar [190.225.252.166]
6/ 50 = 12% |
6 60ms 8/ 50 = 16% 0/ 50 = 0% xe-8-1-0.baires3.bai.seabone.net [195.22.220.53]
7/ 50 = 14% |
7 159ms 15/ 50 = 30% 0/ 50 = 0% et-10-3-0.miami15.mia.seabone.net [89.221.41.177]
1/ 50 = 2% |
8 160ms 16/ 50 = 32% 0/ 50 = 0% et-10-3-0.miami15.mia.seabone.net [89.221.41.177]
0/ 50 = 0% |
9 159ms 16/ 50 = 32% 0/ 50 = 0% xe-11-0-0.edge2.miami1.Level3.net [63.209.150.165]

Trace complete.
—> pathping -w 500 -q 50 -4 190.94.183.70 <--

Tracing route to 190.94.183.70 over a maximum of 30 hops

0 Kaylee.Home [192.168.1.3]
1 192.168.1.1
2 host120.200-3-60.telecom.net.ar [200.3.60.120]
3 host4.181-88-168.telecom.net.ar [181.88.168.4]
4 host233.181-88-108.telecom.net.ar [181.88.108.233]
5 host225.181-88-108.telecom.net.ar [181.88.108.225]
6 host202.181-88-134.telecom.net.ar [181.88.134.202]
7 190.94.182.130
8 190.94.183.70

Computing statistics for 100 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Kaylee.Home [192.168.1.3]
0/ 50 = 0% |
1 0ms 0/ 50 = 0% 0/ 50 = 0% 192.168.1.1
2/ 50 = 4% |
2 22ms 2/ 50 = 4% 0/ 50 = 0% host120.200-3-60.telecom.net.ar [200.3.60.120]
0/ 50 = 0% |
3 22ms 4/ 50 = 8% 2/ 50 = 4% host4.181-88-168.telecom.net.ar [181.88.168.4]
0/ 50 = 0% |
4 26ms 2/ 50 = 4% 0/ 50 = 0% host233.181-88-108.telecom.net.ar [181.88.108.233]
0/ 50 = 0% |
5 23ms 3/ 50 = 6% 1/ 50 = 2% host225.181-88-108.telecom.net.ar [181.88.108.225]
0/ 50 = 0% |
6 23ms 2/ 50 = 4% 0/ 50 = 0% host202.181-88-134.telecom.net.ar [181.88.134.202]
4/ 50 = 8% |
7 60ms 6/ 50 = 12% 0/ 50 = 0% 190.94.182.130
1/ 50 = 2% |
8 59ms 7/ 50 = 14% 0/ 50 = 0% 190.94.183.70

Trace complete.
Section completed in 350.61 seconds

A bit better?

It’s still telecom and your 2nd hop loses 2%. Are you on wifi? Your router might have issues too.

No, ethernet cable, I called the ISP today, they did say they are having issues.

One month later still with issues Andraus, now they have more packet loss than ever and a hop less…. No official response from Anet… im quitting the game until i get some fix or response, cant play with 300 to 4k ms…

MONO.9273:

One month later still with issues Andraus, now they have more packet loss than ever and a hop less…. No official response from Anet… im quitting the game until i get some fix or response, cant play with 300 to 4k ms…

Sorry I’m not sure if we had spoke before.

But in regards to your attached image, level3 in Dallas is giving you major issues. That is not Anet…. You could if you like, open a ticket and attach that image. They could also explain that to you as well. But there’s nothing they can do on their end….

yeah we spoke a month ago in another post i know that already but i want a official answer, is not only me saying this, is a lot of ppl from latin america, that goes through Dallas…

And I have noticed that its only the maps that have a high volume of players on it.

Eternal Battlegrounds, Lions Arch etc.