Egorum.9506 Posted April 21, 2018 Share Posted April 21, 2018 ran a tracert (both google and yahoo), ~30 msPing test shows 50-100 depending on the cityping to the router is <1random 300-1.5k ms spikes ingame that last for several seconds each. what gives? Link to comment Share on other sites More sharing options...
Egorum.9506 Posted April 22, 2018 Author Share Posted April 22, 2018 Ran gw2 diag, it's at 100% packet loss for the NC soft servers. I opened a ticket, but it's definitely on your end Link to comment Share on other sites More sharing options...
WarpSpasm.9721 Posted April 22, 2018 Share Posted April 22, 2018 I not savvy enough to post stats, but my game has been unplayable since Tuesday 17th April. Permanent skill lag & occasional ping up to 4.5k.I keep trying, but quit after 10 mins. Very frustrating. Link to comment Share on other sites More sharing options...
Egorum.9506 Posted April 22, 2018 Author Share Posted April 22, 2018 @WarpSpasm.9721 said:I not savvy enough to post stats, but my game has been unplayable since Tuesday 17th April. Permanent skill lag & occasional ping up to 4.5k.I keep trying, but quit after 10 mins. Very frustrating. Check the support tab for the article on connectivity, follow the diagnostics instructions, then open a latency support ticket and post the results there. Maybe it'll help if they have more information Link to comment Share on other sites More sharing options...
Healix.5819 Posted April 22, 2018 Share Posted April 22, 2018 The -diag option includes the old NCSoft servers, which are no longer used. Regardless, both the old servers and the new ones intentionally block pings through their network, hence the 100% packet loss. You'll need to use PingPlotter if you want to trace their network.If you just want to ping the servers, here's an Amazon server that will respond:dynamodb.us-east-1.amazonaws.comdynamodb.eu-central-1.amazonaws.com Link to comment Share on other sites More sharing options...
Egorum.9506 Posted April 22, 2018 Author Share Posted April 22, 2018 @Healix.5819 said:The -diag option includes the old NCSoft servers, which are no longer used. Regardless, both the old servers and the new ones intentionally block pings through their network, hence the 100% packet loss. You'll need to use PingPlotter if you want to trace their network.If you just want to ping the servers, here's an Amazon server that will respond:dynamodb.us-east-1.amazonaws.comdynamodb.eu-central-1.amazonaws.comTy, I'll try that after lunch and post the results. Ping floats between 150-200 constantly now, still 3k spikes Link to comment Share on other sites More sharing options...
Egorum.9506 Posted April 22, 2018 Author Share Posted April 22, 2018 @Healix.5819 said:The -diag option includes the old NCSoft servers, which are no longer used. Regardless, both the old servers and the new ones intentionally block pings through their network, hence the 100% packet loss. You'll need to use PingPlotter if you want to trace their network.If you just want to ping the servers, here's an Amazon server that will respond:dynamodb.us-east-1.amazonaws.comdynamodb.eu-central-1.amazonaws.comC:\Users\Aric>ping dynamodb.us-east-1.amazonaws.com -tPinging dynamodb.us-east-1.amazonaws.com [52.94.0.32] with 32 bytes of data:Reply from 52.94.0.32: bytes=32 time=62ms TTL=237Reply from 52.94.0.32: bytes=32 time=61ms TTL=237Reply from 52.94.0.32: bytes=32 time=62ms TTL=237Reply from 52.94.0.32: bytes=32 time=61ms TTL=237Reply from 52.94.0.32: bytes=32 time=61ms TTL=237Reply from 52.94.0.32: bytes=32 time=63ms TTL=237Reply from 52.94.0.32: bytes=32 time=61ms TTL=237Reply from 52.94.0.32: bytes=32 time=89ms TTL=237Reply from 52.94.0.32: bytes=32 time=61ms TTL=237Reply from 52.94.0.32: bytes=32 time=87ms TTL=237Reply from 52.94.0.32: bytes=32 time=61ms TTL=237Reply from 52.94.0.32: bytes=32 time=61ms TTL=237Reply from 52.94.0.32: bytes=32 time=62ms TTL=237Reply from 52.94.0.32: bytes=32 time=61ms TTL=237Reply from 52.94.0.32: bytes=32 time=61ms TTL=237Reply from 52.94.0.32: bytes=32 time=61ms TTL=237Reply from 52.94.0.32: bytes=32 time=61ms TTL=237Reply from 52.94.0.32: bytes=32 time=62ms TTL=237Ping statistics for 52.94.0.32:Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:Minimum = 61ms, Maximum = 89ms, Average = 64msControl-C^CC:\Users\Aric>ping dynamodb.eu-central-1.amazonaws.com -tPinging dynamodb.eu-central-1.amazonaws.com [52.94.17.14] with 32 bytes of data:Reply from 52.94.17.14: bytes=32 time=151ms TTL=238Reply from 52.94.17.14: bytes=32 time=149ms TTL=238Reply from 52.94.17.14: bytes=32 time=150ms TTL=238Reply from 52.94.17.14: bytes=32 time=150ms TTL=238Reply from 52.94.17.14: bytes=32 time=149ms TTL=238Reply from 52.94.17.14: bytes=32 time=150ms TTL=238Reply from 52.94.17.14: bytes=32 time=150ms TTL=238Reply from 52.94.17.14: bytes=32 time=150ms TTL=238Reply from 52.94.17.14: bytes=32 time=150ms TTL=238Reply from 52.94.17.14: bytes=32 time=150ms TTL=238Reply from 52.94.17.14: bytes=32 time=150ms TTL=238Reply from 52.94.17.14: bytes=32 time=150ms TTL=238Reply from 52.94.17.14: bytes=32 time=150ms TTL=238Reply from 52.94.17.14: bytes=32 time=149ms TTL=238Reply from 52.94.17.14: bytes=32 time=150ms TTL=238Reply from 52.94.17.14: bytes=32 time=149ms TTL=238Ping statistics for 52.94.17.14:Packets: Sent = 16, Received = 16, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:Minimum = 149ms, Maximum = 151ms, Average = 149msno loss with those, but 150 is high as shit Link to comment Share on other sites More sharing options...
Linken.6345 Posted April 22, 2018 Share Posted April 22, 2018 150 is not much at all. Link to comment Share on other sites More sharing options...
Egorum.9506 Posted April 22, 2018 Author Share Posted April 22, 2018 @Linken.6345 said:150 is not much at all.ran it again:Pinging dynamodb.eu-central-1.amazonaws.com [52.94.17.4] with 32 bytes of data:Reply from 52.94.17.4: bytes=32 time=173ms TTL=238Reply from 52.94.17.4: bytes=32 time=171ms TTL=238Reply from 52.94.17.4: bytes=32 time=427ms TTL=238Reply from 52.94.17.4: bytes=32 time=190ms TTL=238Reply from 52.94.17.4: bytes=32 time=217ms TTL=238Reply from 52.94.17.4: bytes=32 time=296ms TTL=238Reply from 52.94.17.4: bytes=32 time=453ms TTL=238Reply from 52.94.17.4: bytes=32 time=560ms TTL=238Reply from 52.94.17.4: bytes=32 time=238ms TTL=238Request timed out.Reply from 52.94.17.4: bytes=32 time=245ms TTL=238Reply from 52.94.17.4: bytes=32 time=233ms TTL=238Reply from 52.94.17.4: bytes=32 time=171ms TTL=238Reply from 52.94.17.4: bytes=32 time=173ms TTL=238Ping statistics for 52.94.17.4:Packets: Sent = 14, Received = 13, Lost = 1 (7% loss),Approximate round trip times in milli-seconds:Minimum = 171ms, Maximum = 560ms, Average = 272msControl-C^C400+ spikes? 150 is bad for living a state away from anet Link to comment Share on other sites More sharing options...
Healix.5819 Posted April 22, 2018 Share Posted April 22, 2018 @Egorum.9506 said:no loss with those, but 150 is high as kittenThat one was for the EU servers in Frankfurt, Germany (dynamodb.eu-central-1.amazonaws.com). Only ping whichever one you're actually using, which I'm guessing is NA since you're closer, which is located in Northern Virginia, US. Link to comment Share on other sites More sharing options...
Egorum.9506 Posted April 22, 2018 Author Share Posted April 22, 2018 @Healix.5819 said:@Egorum.9506 said:no loss with those, but 150 is high as kittenThat one was for the EU servers in Frankfurt, Germany (dynamodb.eu-central-1.amazonaws.com). Only ping whichever one you're actually using, which I'm guessing is NA since you're closer, which is located in Northern Virginia, US.Ty, that's helpful. Any ideas why I'm getting constant 150-200 in game? Link to comment Share on other sites More sharing options...
Healix.5819 Posted April 23, 2018 Share Posted April 23, 2018 @Egorum.9506 said:Ty, that's helpful. Any ideas why I'm getting constant 150-200 in game? The ping shown in-game isn't your true ping, it's network latency + server processing time, which is around 10-20ms higher than your real ping. Your ping to NA was only 64ms however, whereas 150-200ms is what you'd expect for EU.You can try to find out what your ping is up to Amazon's network, while you're seeing 150-200 in-game. Ideally, you should use the IP of the map you're currently on by using the chat command /ip, but if not, you can use the login server (EU is auth2):tracert auth1.101.arenanetworks.comRegardless, there's not much you can do, since any problem past your ISP is outside of their control. You can only try various VPNs to change how you're routed across the internet, the goal being to avoid whichever hop is causing problems. Link to comment Share on other sites More sharing options...
WarpSpasm.9721 Posted April 25, 2018 Share Posted April 25, 2018 Whatever the patch was today, my week-long lag has gone now & ping is back to normal. Thanks patch ppl! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.