AgentHawk.1092 Posted November 11, 2017 Share Posted November 11, 2017 as the title says, this diag seems to show packet loss to ncsoft servers which leads me to believe its an issue with anet servers is there a way to fix this or do i need to ride it out? my geo location is US, server Seafarers Rest [EU] in game /IP command says 10.83.75.37 [NetworkDiag](http://pastebin.com/8T2PB2k6 "pastebin.com/8T2PB2k6") Link to comment Share on other sites More sharing options...
Healix.5819 Posted November 11, 2017 Share Posted November 11, 2017 Estimated packet loss is the in-between lines with the | on the pathping command. Only the first result shows packet loss (4%, 1.3% factoring the others), which happens as early as your ISP. There's more further down the route with Telia, but you're not using that. The original NCSoft servers aren't really used anymore. The 10.* IPs are Amazon's private network, the same as your 192.168 home network. If you want the real IP, you need to use the -maploadinfo option. These server block pings, so you can only calculate packet loss up to them, though I wouldn't expect Amazon to have network problems. To run the command yourself to Amazon's EU servers, open a command prompt (cmd.exe) and enter: pathping -w 500 -q 50 -4 52.59.151.62 Link to comment Share on other sites More sharing options...
AgentHawk.1092 Posted November 11, 2017 Author Share Posted November 11, 2017 > To run the command yourself to Amazon's EU servers, open a command prompt (cmd.exe) and enter: > pathping -w 500 -q 50 -4 52.59.151.62 heres what i got: >! Computing statistics for 125 seconds... >! Source to Here This Node/Link >! Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address >! 0 DESKTOP-ECSD7QB [192.168.1.38] >! 0/ 50 = 0% | >! 1 0ms 0/ 50 = 0% 0/ 50 = 0% router.asus.com [192.168.1.1] >! 0/ 50 = 0% | >! 2 9ms 0/ 50 = 0% 0/ 50 = 0% 96.120.40.177 >! 0/ 50 = 0% | >! 3 12ms 0/ 50 = 0% 0/ 50 = 0% 69.139.250.161 >! 0/ 50 = 0% | >! 4 11ms 2/ 50 = 4% 2/ 50 = 4% 162.151.146.150 >! 0/ 50 = 0% | >! 5 10ms 0/ 50 = 0% 0/ 50 = 0% 68.86.167.13 >! 0/ 50 = 0% | >! 6 18ms 2/ 50 = 4% 2/ 50 = 4% be-33668-cr02.350ecermak.il.ibone.comcast.net [68.86.90.45] >! 0/ 50 = 0% | >! 7 17ms 0/ 50 = 0% 0/ 50 = 0% be-10563-pe01.350ecermak.il.ibone.comcast.net [68.86.82.158] >! 3/ 50 = 6% | >! 8 18ms 3/ 50 = 6% 0/ 50 = 0% ae7.cr6-chi1.ip4.gtt.net [199.229.229.249] >! 47/ 50 = 94% | >! 9 --- 50/ 50 =100% 0/ 50 = 0% et-0-0-49.cr11-fra2.ip4.gtt.net [89.149.180.226] >! 0/ 50 = 0% | >! 10 --- 50/ 50 =100% 0/ 50 = 0% a100-gw.ip4.gtt.net [77.67.66.206] and IP from maploadinfo is 18.194.120.12 Link to comment Share on other sites More sharing options...
AgentHawk.1092 Posted November 11, 2017 Author Share Posted November 11, 2017 also >! Tracing route to ec2-18-194-120-12.eu-central-1.compute.amazonaws.com [18.194.120.12] >! over a maximum of 30 hops: >! 0 DESKTOP-ECSD7QB [192.168.1.38] >! 1 router.asus.com [192.168.1.1] >! 2 96.120.40.177 >! 3 69.139.250.161 >! 4 * 162.151.146.150 >! 5 68.86.167.13 >! 6 be-33668-cr02.350ecermak.il.ibone.comcast.net [68.86.90.45] >! 7 be-10563-pe01.350ecermak.il.ibone.comcast.net [68.86.82.158] >! 8 ae7.cr6-chi1.ip4.gtt.net [199.229.229.249] >! 9 xe-11-2-0.cr1-fra6.ip4.gtt.net [89.149.184.61] >! 10 ip4.gtt.net [77.67.121.202] >! 11 * * * >! Computing statistics for 125 seconds... >! Source to Here This Node/Link >! Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address >! 0 DESKTOP-ECSD7QB [192.168.1.38] >! 0/ 50 = 0% | >! 1 0ms 0/ 50 = 0% 0/ 50 = 0% router.asus.com [192.168.1.1] >! 0/ 50 = 0% | >! 2 9ms 1/ 50 = 2% 1/ 50 = 2% 96.120.40.177 >! 0/ 50 = 0% | >! 3 12ms 0/ 50 = 0% 0/ 50 = 0% 69.139.250.161 >! 0/ 50 = 0% | >! 4 13ms 4/ 50 = 8% 4/ 50 = 8% 162.151.146.150 >! 0/ 50 = 0% | >! 5 11ms 0/ 50 = 0% 0/ 50 = 0% 68.86.167.13 >! 0/ 50 = 0% | >! 6 19ms 3/ 50 = 6% 3/ 50 = 6% be-33668-cr02.350ecermak.il.ibone.comcast.net [68.86.90.45] >! 0/ 50 = 0% | >! 7 17ms 0/ 50 = 0% 0/ 50 = 0% be-10563-pe01.350ecermak.il.ibone.comcast.net [68.86.82.158] >! 3/ 50 = 6% | >! 8 19ms 3/ 50 = 6% 0/ 50 = 0% ae7.cr6-chi1.ip4.gtt.net [199.229.229.249] >! 8/ 50 = 16% | >! 9 --- 50/ 50 =100% 39/ 50 = 78% xe-11-2-0.cr1-fra6.ip4.gtt.net [89.149.184.61] >! 0/ 50 = 0% | >! 10 131ms 11/ 50 = 22% 0/ 50 = 0% ip4.gtt.net [77.67.121.202] is to the maploadinfo IP if this helps anyone Link to comment Share on other sites More sharing options...
Keller.3914 Posted November 11, 2017 Share Posted November 11, 2017 Something happened in the last few days that increased my ping by ~50ms. I can still ping the old ncsoft servers and the latency is fine, but when pinging the current ones you can see a huge difference. Old server ip ping: ![](https://i.gyazo.com/eb505221e85727c245d79c9cccd79709.png "") New server ip ping: ![](https://i.gyazo.com/8df216e68a0a05d004c56dcae14db926.png "") Edit: I tried using a VPN to check if the problem was my ISP, but the results were the same. Link to comment Share on other sites More sharing options...
zoomborg.9462 Posted November 11, 2017 Share Posted November 11, 2017 Nah, same thing happened to me as well (EU), as soon as those new IP's started popping i had major increase in latency and packet loss, something is really fishy here and why are anet moving servers anyway? Performance used to be a lot better than this........ Link to comment Share on other sites More sharing options...
vaxjani.9073 Posted November 11, 2017 Share Posted November 11, 2017 yep same im getting increased ping too nowadays (EU) Link to comment Share on other sites More sharing options...
Healix.5819 Posted November 11, 2017 Share Posted November 11, 2017 > @AgentHawk.1092 said: > heres what i got: There's a little packet loss between Comcast and GTT's network. There's much higher packet loss within GTT's network, but that's also where they start blocking pings, so it may be a false positive. Pathping stops on the first blocked ping, so it only goes up to GTT's network in Germany, but that's also where both Amazon and NCSoft are hosted, in Frankfurt. The only thing you can really do is try different VPNs around the world in an attempt to get routed through different networks. > @Keller.3914 said: > Something happened in the last few days that increased my ping by ~50ms. I can still ping the old ncsoft servers and the latency is fine, but when pinging the current ones you can see a huge difference. You're being routed differently and that's mostly the cause of your higher ping. Notice hop 9 for the old servers and hop 10 for the new ones are the same, but due to the route, it's now +30ms. That hop is also in Texas, which is where the old servers were hosted, whereas the new servers are in Northern Virginia, so your route is now longer, which is naturally going to have a higher ping. If 164ms was your old normal, the best you can expect now is around 180ms, if that initial route changes. If you've only noticed this in the past few days, note that PoF's open world was launched on the new servers and that's when ArenaNet really started using them. They've only become increasingly common after that and personally, the last old server I saw was over a week ago. > @zoomborg.9462 said: > why are anet moving servers anyway? Maybe once they're fully transitioned, they'll talk about it. Alternatively, ask during the next AMA. Link to comment Share on other sites More sharing options...
MLGKorno.5419 Posted November 12, 2017 Share Posted November 12, 2017 > @Keller.3914 said: > Something happened in the last few days that increased my ping by ~50ms. I can still ping the old ncsoft servers and the latency is fine, but when pinging the current ones you can see a huge difference. > > Old server ip ping: > ![](https://i.gyazo.com/eb505221e85727c245d79c9cccd79709.png "") > > New server ip ping: > ![](https://i.gyazo.com/8df216e68a0a05d004c56dcae14db926.png "") > > Edit: I tried using a VPN to check if the problem was my ISP, but the results were the same. A few days ago I made a topic about the exact thing you describe: https://en-forum.guildwars2.com/discussion/14616/video-proof-west-coast-players-all-getting-high-ping-in-pvp#latest Note that this "persistently higher ping" issue is not the same problem as the (insert four digit number) ping spikes. The persistently higher ping is purely because of the server being hosted somewhere else now. I myself have not gotten ping spikes (apart from when gw2 was being ddos'd) Link to comment Share on other sites More sharing options...
AgentHawk.1092 Posted November 12, 2017 Author Share Posted November 12, 2017 i cant play for more than 15m before i start to get too laggy this is ridiculous 600+ in game ping right now where i started at my normal 150 doing a gathering run, then slowly started to notice jittery movement in fights and skill lag what is the deal here? Link to comment Share on other sites More sharing options...
Ellieanna.5027 Posted November 12, 2017 Share Posted November 12, 2017 4 11ms 2/ 50 = 4% 2/ 50 = 4% 162.151.146.150 This was from the first link you posted, you have a 4% packet loss which is right near your ISP. 2 9ms 1/ 50 = 2% 1/ 50 = 2% 96.120.40.177 This was from the second link, 2% packet loss at your ISP. I linked them both for a reason. It will cause a trickle effect down everything from there. At least for the 2nd one, keep watching the 2nd and 3nd hop and see if that stays the same or increases, and if it does, contact your ISP, that is 100% your ISPs node. With regards to the 4th hop on the first post, I can't tell if it's still your ISP or not, but if you are getting it right after your house, something on their line is having some issues. Link to comment Share on other sites More sharing options...
AgentHawk.1092 Posted November 12, 2017 Author Share Posted November 12, 2017 > @Ellieanna.5027 said: > 4 11ms 2/ 50 = 4% 2/ 50 = 4% 162.151.146.150 > This was from the first link you posted, you have a 4% packet loss which is right near your ISP. > > 2 9ms 1/ 50 = 2% 1/ 50 = 2% 96.120.40.177 > This was from the second link, 2% packet loss at your ISP. > > I linked them both for a reason. It will cause a trickle effect down everything from there. At least for the 2nd one, keep watching the 2nd and 3nd hop and see if that stays the same or increases, and if it does, contact your ISP, that is 100% your ISPs node. With regards to the 4th hop on the first post, I can't tell if it's still your ISP or not, but if you are getting it right after your house, something on their line is having some issues. > > thanks for the info, i didnt know those little packet losses would cause much issue Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now