Latency/Ping/FPS Issues [merged]

[abcruziii.9405]

It's nearly 0400UTC and it's usually fine at this time until OCX/SEA prime, however there's already some issue at AWS.

Route to ec2-34-226-98-73.compute-1.amazonaws.com [34.226.98.73]:

! 5 183 ms 182 ms 183 ms las-b3-link.telia.net [62.115.14.32]! 6 179 ms 178 ms 179 ms las-b21-link.telia.net [62.115.136.46]! 7 214 ms 211 ms 210 ms dls-b21-link.telia.net [62.115.123.136]! 8 210 ms 210 ms 210 ms a100-ic-300087-kbn-b3.c.telia.net [62.115.9.126]! 9 218 ms 230 ms 229 ms 176.32.125.148! 10 211 ms 214 ms 210 ms 176.32.125.235! 11 365 ms 357 ms 356 ms 54.239.46.16! 12 349 ms 351 ms 349 ms 54.240.229.173! 13 Request timed out.! 14 353 ms 352 ms 352 ms 205.251.244.133! 15 Request timed out.! 16 Request timed out.! 17 370 ms 367 ms 371 ms 54.239.110.133! 18 349 ms 349 ms 349 ms 54.239.108.129! 19 353 ms 355 ms 355 ms 52.93.24.142! 20 351 ms 347 ms 352 ms 52.93.24.137! 21 Request timed out.! 22 Request timed out.! 23 Request timed out.! 24 Request timed out.! 25 Request timed out.! 26 Request timed out.! 27 Request timed out.! 28 Request timed out.! 29 Request timed out.! 30 * Request timed out.

[abcruziii.9405]

About two minutes after (0402UTC), latency is "normal", as if on schedule.

Route to ec2-34-226-98-73.compute-1.amazonaws.com [34.226.98.73]:

! 5 210 ms 188 ms 182 ms las-b3-link.telia.net [62.115.14.32]! 6 181 ms 179 ms 178 ms las-b21-link.telia.net [62.115.136.46]! 7 211 ms 213 ms 216 ms dls-b21-link.telia.net [62.115.123.136]! 8 211 ms 211 ms 213 ms a100-ic-300087-kbn-b3.c.telia.net [62.115.9.126]! 9 233 ms 229 ms 215 ms 176.32.125.148! 10 211 ms 211 ms 211 ms 176.32.125.235! 11 262 ms 259 ms 253 ms 54.239.46.16! 12 247 ms 248 ms 251 ms 54.240.229.173! 13 Request timed out.! 14 251 ms 251 ms 251 ms 205.251.244.133! 15 Request timed out.! 16 Request timed out.! 17 271 ms 265 ms 264 ms 54.239.110.133! 18 249 ms 249 ms 248 ms 54.239.108.129! 19 262 ms 271 ms 257 ms 52.93.24.142! 20 252 ms 252 ms 251 ms 52.93.24.137! 21 Request timed out.! 22 Request timed out.! 23 Request timed out.! 24 Request timed out.! 25 Request timed out.! 26 Request timed out.! 27 Request timed out.! 28 Request timed out.! 29 Request timed out.! 30 * Request timed out.

Expecting this playable latency to last until OCX/SEA prime time.

[abcruziii.9405]

Early OCX/SEA prime time latency rise today, started around 1039UTC

Route to ec2-54-227-166-74.compute-1.amazonaws.com [54.227.166.74]

! 5 186 ms 186 ms 185 ms las-b3-link.telia.net [62.115.14.32]! 6 182 ms 181 ms 182 ms las-b21-link.telia.net [62.115.136.46]! 7 213 ms 214 ms 217 ms dls-b21-link.telia.net [62.115.123.136]! 8 214 ms 214 ms 213 ms a100-ic-300087-kbn-b3.c.telia.net [62.115.9.126]! 9 222 ms 224 ms 221 ms 176.32.125.136! 10 215 ms 214 ms 214 ms 176.32.125.233! 11 364 ms 359 ms 363 ms 54.239.46.14! 12 355 ms 359 ms 356 ms 54.239.42.188! 13 Request timed out.! 14 Request timed out.! 15 Request timed out.! 16 507 ms 377 ms 54.239.110.185! 17 354 ms 353 ms 353 ms 54.239.111.25! 18 354 ms 353 ms 353 ms 52.93.24.32! 19 353 ms 352 ms 352 ms 205.251.244.91! 20 Request timed out.! 21 Request timed out.! 22 Request timed out.! 23 Request timed out.! 24 Request timed out.! 25 Request timed out.! 26 Request timed out.! 27 Request timed out.! 28 Request timed out.! 29 Request timed out.! 30 * Request timed out.!!

[Jeromai.8203]

@"Gator.5729" said:It has been suggested many times by many people to run pingplotter or traceroute to determine where the problem is. If the results show the problem at the Anet servers (Amazon), then submit a support ticket so it can get addressed. The majority/most of the time, the issue is with "your" route to the servers. This is something that Anet has no control over.

Trust me, I have had this latency issue since the Path of Fire launch, and have recently opened a support ticket one week ago, sending daily Pingplotters directly to Anet support. All of them show 10-20% packet loss at the Amazon servers at a specific time (~UTC: 11.30am, give or take an hour, on the NA servers, aka OCX/SEA prime time)

Anet support has replied back with countless cut-and-paste suggestions, with no acknowledgement of the actual problem.. A more cynical person might think they are hoping we might stop complaining and go away; I'm choosing to be relentlessly optimistic and see it as them covering -every- last possibility for a solution or fix. So I dutifully apply the suggestion, wait for my prime time, and then send yet another Pingplotter, because most of the time, the suggested solution does not solve the network issue. The ticket's still open, and I'm not closing it on my end until the issue is resolved.

As for it being something that Anet has no control over, I beg to differ. For five years, the old NA servers were providing absolutely fine latency to people in South America, OCX and SEA (and presumably the EU servers too for those people in Germany.) During Path of Fire, the servers were silently migrated over time, without announcement or communication, to these new Amazon servers, which has been consistently producing these problems.

It behooves us to be giving feedback that this move has drastically affected our gameplay, so that Anet can consider whatever options they have on their plate - e.g. move back to the old servers, find other -new- servers that do not have this network issue, communicate with Amazon Web Services that they are providing inconsistent server services, figure out a workable solution (even if it's, "sorry we can't do anything but suggest you use a VPN") and/or acknowledge with some communication that a subset of players are having this issue with the new servers.

In the meantime, these forums also serve as a place to confirm that the problem is not isolated to one person, but that others are experiencing similar issues at the same time.

[abcruziii.9405]

@Jeromai.8203 said:Anet support has replied back with countless cut-and-paste suggestions, with no acknowledgement of the actual problem.. A more cynical person might think they are hoping we might stop complaining and go away; I'm choosing to be relentlessly optimistic and see it as them covering -every- last possibility for a solution or fix. So I dutifully apply the suggestion, wait for my prime time, and then send yet another Pingplotter, because most of the time, the suggested solution does not solve the network issue. The ticket's still open, and I'm not closing it on my end until the issue is resolved.

When I submitted a support ticket for this issue, I was advised by tech support to run game advisor diagnostics, submit winmtr reports, and I even gave trace routes. Eventually they simply concluded that it was an issue with my isp and tech support closed the ticket. I hope more people put their voices in the forum to show that the AWS issue not an isolated case.

This trace route was taken around 0110 UTC.

Route to ec2-52-90-17-39.compute-1.amazonaws.com [52.90.17.39]:

! 5 179 ms 178 ms 179 ms las-b3-link.telia.net [62.115.14.32]! 6 211 ms 210 ms 212 ms dls-b22-link.telia.net [62.115.118.246]! 7 213 ms 210 ms 211 ms dls-b21-link.telia.net [62.115.137.106]! 8 210 ms 210 ms 210 ms a100us-ic-303629-dls-bb1.c.telia.net [213.248.85.222]! 9 219 ms 223 ms 233 ms 176.32.125.224! 10 211 ms 212 ms 210 ms 176.32.125.227! 11 352 ms 352 ms 354 ms 54.239.46.0! 12 350 ms 349 ms 350 ms 54.240.229.171! 13 Request timed out.! 14 Request timed out.! 15 Request timed out.! 16 368 ms 353 ms 363 ms 54.239.110.181! 17 350 ms 349 ms 350 ms 54.239.108.131! 18 370 ms 380 ms 52.93.24.46! 19 353 ms 350 ms 351 ms 52.93.24.39! 20 Request timed out.! 21 Request timed out.! 22 Request timed out.! 23 Request timed out.! 24 Request timed out.! 25 Request timed out.! 26 Request timed out.! 27 Request timed out.! 28 Request timed out.! 29 Request timed out.! 30 * Request timed out.! Trace complete.

Here's a trace to the old ncsoft server taken at that time as well.

Route to 64.25.33-1.ncsoft.com [64.25.39.1]:

! 5 188 ms 183 ms 184 ms las-b3-link.telia.net [62.115.14.32]! 6 214 ms 217 ms 215 ms dls-b22-link.telia.net [62.115.118.246]! 7 215 ms 215 ms 215 ms ncsoft-ic-317391-dls-b22.c.telia.net.10.115.62.in-addr.arpa [62.115.10.106]! 8 214 ms 215 ms 215 ms 64.25.32-9.ncsoft.com [64.25.32.9]! 9 214 ms 215 ms 216 ms 64.25.32-26.ncsoft.com [64.25.32.26]! 10 216 ms 216 ms 216 ms 64.25.33-1.ncsoft.com [64.25.39.1]!! Trace complete.

[chemie banger.9624]

This move to amazon is a disaster for me . My normal ping is around 400 to 500ms. Now it is unplayable. I can see loot which vanishes before I can pick it up even :s

[Excelvior.8520]

ping has skyrocketed after PoF. Game is unplayable, all other games play normally (around 50-80 ms), gw2 reaches even 600, sometimes 2k on prime time. So many people tell you the same thing and we don't even receive a response from you ANET, shame (rings bell)

[abcruziii.9405]

Prime time OCX/SEA latency once again, around 1218 UTC.

Route to ec2-34-233-29-250.compute-1.amazonaws.com [34.233.29.250]:

! 5 181 ms 179 ms 180 ms las-b3-link.telia.net [62.115.14.32]! 6 211 ms 211 ms 211 ms dls-b22-link.telia.net [62.115.118.246]! 7 211 ms 210 ms 210 ms dls-b21-link.telia.net [62.115.137.106]! 8 210 ms 211 ms 209 ms a100us-ic-303626-dls-bb1.c.telia.net [62.115.36.38]! 9 223 ms 220 ms 220 ms 176.32.125.162! 10 211 ms 211 ms 211 ms 176.32.125.237! 11 358 ms 359 ms 360 ms 54.239.46.14! 12 360 ms 348 ms 348 ms 54.239.42.188! 13 Request timed out.! 14 Request timed out.! 15 Request timed out.! 16 373 ms 354 ms 54.239.110.155! 17 348 ms 349 ms 54.239.111.11! 18 373 ms 375 ms 369 ms 52.93.24.116! 19 348 ms 348 ms 349 ms 52.93.24.115! 20 Request timed out.! 21 Request timed out.! 22 Request timed out.! 23 Request timed out.! 24 Request timed out.! 25 Request timed out.! 26 Request timed out.! 27 Request timed out.! 28 Request timed out.! 29 Request timed out.! 30 Request timed out.!! Trace complete.

Here's a tracert to ncsoft at this time, too.

! Route to 64.25.33-1.ncsoft.com [64.25.39.1]:!! 1 2 ms 1 ms 3 ms 192.168.1.1! 2 34 ms 34 ms 35 ms 100.92.0.1! 3 35 ms 36 ms 38 ms 122.2.221.22.static.pldt.net [122.2.221.22]! 4 36 ms 34 ms 35 ms 210.213.133.158.static.pldt.net [210.213.133.158]! 5 185 ms 198 ms 186 ms las-b3-link.telia.net [62.115.14.32]! 6 216 ms 215 ms 216 ms dls-b22-link.telia.net [62.115.118.246]! 7 216 ms 215 ms 215 ms ncsoft-ic-317391-dls-b22.c.telia.net.10.115.62.in-addr.arpa [62.115.10.106]! 8 217 ms 215 ms 216 ms 64.25.32-9.ncsoft.com [64.25.32.9]! 9 215 ms 215 ms 215 ms 64.25.32-26.ncsoft.com [64.25.32.26]! 10 216 ms 218 ms 215 ms 64.25.33-1.ncsoft.com [64.25.39.1]!! Trace complete.

[Maybe.7180]

Same here. EU, Vabbi, Latvia.Used to play fine before PoF (it was ok even on bad mobile connections). Had 40-50 ms. Now it's 100 to 300, but it actually feels even worse sometimes (barely managed to do Teqatl today).

Diagnostics:

! Computing statistics for 175 seconds...! Source to Here This Node/Link! Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address! 0 White.zyxel.com [192.168.1.102]! 0/ 50 = 0% |! 1 1ms 0/ 50 = 0% 0/ 50 = 0% 192.168.1.1! 0/ 50 = 0% |! 2 6ms 0/ 50 = 0% 0/ 50 = 0% 195.13.227.1! 1/ 50 = 2% |! 3 8ms 1/ 50 = 2% 0/ 50 = 0% 195.122.0.142! 0/ 50 = 0% |! 4 17ms 3/ 50 = 6% 2/ 50 = 4% s-b5-link.telia.net [62.115.144.74]! 0/ 50 = 0% |! 5 19ms 1/ 50 = 2% 0/ 50 = 0% s-bb4-link.telia.net [62.115.141.198]! 3/ 50 = 6% |! 6 29ms 6/ 50 = 12% 2/ 50 = 4% kbn-bb4-link.telia.net [62.115.120.50]! 0/ 50 = 0% |! 7 116ms 4/ 50 = 8% 0/ 50 = 0% nyk-bb4-link.telia.net [80.91.254.91]! 1/ 50 = 2% |! 8 119ms 23/ 50 = 46% 18/ 50 = 36% ash-bb4-link.telia.net [62.115.136.201]! 0/ 50 = 0% |! 9 131ms 5/ 50 = 10% 0/ 50 = 0% atl-b22-link.telia.net [62.115.125.128]! 21/ 50 = 42% |! 10 154ms 27/ 50 = 54% 1/ 50 = 2% dls-b22-link.telia.net [62.115.120.113]! 0/ 50 = 0% |! 11 --- 50/ 50 =100% 24/ 50 = 48% ncsoft-ic-317391-dls-b22.c.telia.net.10.115.62.in-addr.arpa [62.115.10.106]! 0/ 50 = 0% |! 12 --- 50/ 50 =100% 24/ 50 = 48% 64.25.32-9.ncsoft.com [64.25.32.9]! 0/ 50 = 0% |! 13 --- 50/ 50 =100% 24/ 50 = 48% 64.25.32-26.ncsoft.com [64.25.32.26]! 0/ 50 = 0% |! 14 154ms 26/ 50 = 52% 0/ 50 = 0% 64.25.33-1.ncsoft.com [64.25.39.1]!! Trace complete.! --> pathping -w 500 -q 50 -4 54.192.230.28 <--!! Tracing route to server-54-192-230-28.waw50.r.cloudfront.net [54.192.230.28]! over a maximum of 30 hops:! 0 White.zyxel.com [192.168.1.102]! 1 192.168.1.1! 2 195.13.227.1! 3 195.122.0.138! 4 195.122.0.150! 5 amazon.plix.pl [195.182.218.5]! 6 *
! Computing statistics for 62 seconds...! Source to Here This Node/Link! Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address! 0 White.zyxel.com [192.168.1.102]! 0/ 50 = 0% |! 1 1ms 0/ 50 = 0% 0/ 50 = 0% 192.168.1.1! 0/ 50 = 0% |! 2 5ms 0/ 50 = 0% 0/ 50 = 0% 195.13.227.1! 0/ 50 = 0% |! 3 8ms 0/ 50 = 0% 0/ 50 = 0% 195.122.0.138! 0/ 50 = 0% |! 4 20ms 0/ 50 = 0% 0/ 50 = 0% 195.122.0.150! 50/ 50 =100% |! 5 --- 50/ 50 =100% 0/ 50 = 0% amazon.plix.pl [195.182.218.5]!! Trace complete.! Section completed in 359.06 seconds

Pingplotter shows 150-500ms on telia/ncsoft, no packet loss.

[abcruziii.9405]

With OCX/SEA prime time drawing to a close, the latency issue subsided as expected.

Route to ec2-34-233-29-250.compute-1.amazonaws.com [34.233.29.250] taken around 1345 UTC

! 5 204 ms 190 ms 194 ms las-b3-link.telia.net [62.115.14.32]! 6 211 ms 210 ms 212 ms dls-b22-link.telia.net [62.115.118.246]! 7 211 ms 210 ms 213 ms dls-b21-link.telia.net [62.115.137.106]! 8 210 ms 210 ms 216 ms a100us-ic-303626-dls-bb1.c.telia.net [62.115.36.38]! 9 240 ms 287 ms 233 ms 176.32.125.162! 10 211 ms 216 ms 258 ms 176.32.125.237! 11 261 ms 252 ms 250 ms 54.239.46.16! 12 248 ms 248 ms 249 ms 54.240.229.173! 13 Request timed out.! 14 Request timed out.! 15 Request timed out.! 16 259 ms 256 ms 256 ms 54.239.110.177! 17 247 ms 247 ms 247 ms 54.239.111.1! 18 270 ms 253 ms 281 ms 52.93.24.140! 19 247 ms 247 ms 248 ms 205.251.244.65! 20 Request timed out.! 21 Request timed out.! 22 Request timed out.! 23 Request timed out.! 24 Request timed out.! 25 Request timed out.! 26 Request timed out.! 27 Request timed out.! 28 Request timed out.! 29 Request timed out.! 30 Request timed out.!! Trace complete.

I'm looking forward to the next high latency period when I log in, in about 10-11 hrs.

[chemie banger.9624]

@abcruziii.9405 said:With OCX/SEA prime time drawing to a close, the latency issue subsided as expected.

Route to ec2-34-233-29-250.compute-1.amazonaws.com [34.233.29.250] taken around 1345 UTC

! 5 204 ms 190 ms 194 ms las-b3-link.telia.net [62.115.14.32]! 6 211 ms 210 ms 212 ms dls-b22-link.telia.net [62.115.118.246]! 7 211 ms 210 ms 213 ms dls-b21-link.telia.net [62.115.137.106]! 8 210 ms 210 ms 216 ms a100us-ic-303626-dls-bb1.c.telia.net [62.115.36.38]! 9 240 ms 287 ms 233 ms 176.32.125.162! 10 211 ms 216 ms 258 ms 176.32.125.237! 11 261 ms 252 ms 250 ms 54.239.46.16! 12 248 ms 248 ms 249 ms 54.240.229.173! 13

Request timed out.! 14

Request timed out.! 15

Request timed out.! 16 259 ms 256 ms 256 ms 54.239.110.177! 17 247 ms 247 ms 247 ms 54.239.111.1! 18 270 ms 253 ms 281 ms 52.93.24.140! 19 247 ms 247 ms 248 ms 205.251.244.65! 20

Request timed out.! 21

Request timed out.! 22

Request timed out.! 23

Request timed out.! 24

Request timed out.! 25

Request timed out.! 26

Request timed out.! 27

Request timed out.! 28

Request timed out.! 29

Request timed out.! 30

Request timed out.!! Trace complete.

I'm looking forward to the next high latency period when I log in, in about 10-11 hrs.

Sounds like they are reducing AWS capacity over their night time . Now it's time to got to bed in Aus the game seems better :-/

[Cormac.3871]

@"Gator.5729" said:It has been suggested many times by many people to run pingplotter or traceroute to determine where the problem is. If the results show the problem at the Anet servers (Amazon), then submit a support ticket so it can get addressed. The majority/most of the time, the issue is with "your" route to the servers. This is something that Anet has no control over. Your route is controlled by your ISP and they are the only ones who can fix it. If they won't then you can try a VPN service to force your connection to take a different route.An issue with the game servers would affect "every" single player not just some people. How internet speed tests and other games/services preform means nothing because they are located in different areas and your connection to them takes a different route.

However, by putting the game further away from users in the Oceania region they have increased the number of things that can go wrong on an already fragile connection. This game has been next to unplayable for me in the last month whenever there have been more than three or four other people in combat in the same area as me, so no fractals, no multi player meta events, WvW only if I roam off hours and no PvP.

Going through tracert shows the problem is somewhere in the US, but not in Amazon, so it's not technically a problem with the servers, but where the traffic has to go past. Which means that it is a result of the decision to move where they have. If Anet shrugs their shoulders and says "technically not our fault, so we won't do anything" they can I suppose. However this means they will lose users like me who have stuck around because they love the game but now find it unplayable.

The main point here is that solving these issues is not within ANet's ability, but minimising the disruption caused to users by these problems is.

[Jeromai.8203]

@"Cormac.3871" said:Which means that it is a result of the decision to move where they have. If Anet shrugs their shoulders and says "technically not our fault, so we won't do anything" they can I suppose. However this means they will lose users like me who have stuck around because they love the game but now find it unplayable.The main point here is that solving these issues is not within ANet's ability, but minimising the disruption caused to users by these problems is.

Exactly. If it is an issue with the routing of the new Amazon servers, it's a result of the decision to move where they have. They need to know that this move has affected the gameplay experience of a subset of players. Maybe they'll decide the subset is too small to worry about and shrug their shoulders, and absorb any potential population loss during that timezone as a result - which is fair enough as a business decision.

But if they look at their metrics a month or two later and see a sudden drop in players logged on during that timezone, I wouldn't want them coming to any off-the-mark conclusions ("OCE/SEA players log in for five minutes to do dailies and log back out again - they don't raid, play fractals, wvw, pvp or do map metas") and would rather want them to realize the root cause - well, no, we can't do anything constructive in game when we're ping spiking to 2000-4000ms every couple of minutes during our prime time.

Or maybe we can be optimistic enough to believe that some good people at ArenaNet might try to take positive action to correct the issue if made aware that there is an issue.

[falchion.3652]

Uninstalled finally. Gave it over a month to resolve but should have known better. Thanks for helping me finally kick it!

[abcruziii.9405]

Expected latency rise in ocx/sea time is here again.

Route to ec2-34-233-29-250.compute-1.amazonaws.com [34.233.29.250] around 1045UTC

! 5 178 ms 179 ms 179 ms las-b3-link.telia.net [62.115.14.32]! 6 181 ms 179 ms 179 ms las-b21-link.telia.net [62.115.136.46]! 7 217 ms 214 ms 216 ms dls-b21-link.telia.net [62.115.123.136]! 8 210 ms 210 ms 210 ms a100-ic-300087-kbn-b3.c.telia.net [62.115.9.126]! 9 225 ms 231 ms 222 ms 176.32.125.208! 10 211 ms 211 ms 211 ms 176.32.125.215! 11 350 ms 361 ms 364 ms 54.239.46.0! 12 351 ms 349 ms 351 ms 54.240.229.189! 13 Request timed out.! 14 Request timed out.! 15 Request timed out.! 16 358 ms 366 ms 365 ms 54.239.110.241! 17 350 ms 350 ms 349 ms 54.239.111.65! 18 379 ms 370 ms 377 ms 52.93.25.16! 19 349 ms 349 ms 349 ms 52.93.25.11! 20 Request timed out.! 21 Request timed out.! 22 Request timed out.! 23 Request timed out.! 24 Request timed out.! 25 Request timed out.! 26 Request timed out.! 27 Request timed out.! 28 Request timed out.! 29 Request timed out.! 30 Request timed out.

[Lagg.3960]

@falchion.3652 said:Uninstalled finally. Gave it over a month to resolve but should have known better. Thanks for helping me finally kick it!

I'm with you on this one. After about a month of lag and extreme fps drops on two separate systems (one with an i7 4790K + 16GB DDR3 + GTX 1080, another with an i5 7600K + 16GB DDR4 + GTX 1070) I'm calling it quits. I'll check in periodically to see if there's any improvements, but as far as I'm concerned GW has gone the way of the unoptimized lootbox game.

End of an era for me: 2005 - 2017

[abcruziii.9405]

The last time ANet posted in this topic was November 7. Who knows if they're still looking at these reported AWS issues.

[abcruziii.9405]

I found a website, CloudPing.info, which compares latency across various AWS regions.

If they chose Oregon instead of Virginia, I think these OCX/SEA issues would have probably not come up.

[Healix.5819]

@abcruziii.9405 said:If they chose Oregon instead of Virginia, I think these OCX/SEA issues would have probably not come up.

That would only shift the problem. You're closer to the US west coast, so you get routed through the west, then all the way to the east coast. To the west of you is the opposite, and according to ArenaNet, the east coast was better for the majority, so if they switched, there'd be even more complaints.

In your traces, everything after that last telia.net, starting with 176.32.*, is Amazon's network. In most cases, the ping spike is right there early on, which ArenaNet has no control over. If they did switch to the west coast, that network would be entirely avoided, but you can only guess if Amazon's west coast network has any problems from the eastern side. Considering you have a 100ms difference between Oregon and California, there's going to be problems for some, since those two are actually only about 10-20ms apart. The only other option is using multiple Amazon locations, which they've already shown is possible, but permanently doing it would first require some changes.

[abcruziii.9405]

@Healix.5819 said:That would only shift the problem. You're closer to the US west coast, so you get routed through the west, then all the way to the east coast. To the west of you is the opposite, and according to ArenaNet, the east coast was better for the majority, so if they switched, there'd be even more complaints.

Why would there be more complaints? Having the game hosted on the west coast means it is still in the continental US. OCX/SEA people (who live across the Pacific Ocean) already play at over 200ms latency. Why would people living in the continental US have a problem with having latency that will be less than 200ms where ever in the US the servers are hosted in?

@Healix.5819 said:In your traces, everything after that last telia.net, starting with 176.32.*, is Amazon's network. In most cases, the ping spike is right there early on, which ArenaNet has no control over. If they did switch to the west coast, that network would be entirely avoided, but you can only guess if Amazon's west coast network has any problems from the eastern side. Considering you have a 100ms difference between Oregon and California, there's going to be problems for some, since those two are actually only about 10-20ms apart. The only other option is using multiple Amazon locations, which they've already shown is possible, but permanently doing it would first require some changes.What's 10-20ms latency difference if some people in other parts of the globe play with higher latency than that? The shift to Amazon Web Services is precisely the issue here, more so since they chose to move to the East Coast region to host the game in. This region seems to suffer a lot of instability compared to the West Coast. I've used cloudping.info to verify that when I suffer from lag, only the East Coast server's ping is high.

[Healix.5819]

@abcruziii.9405 said:Why would people living in the continental US have a problem with having latency that will be less than 200ms where ever in the US the servers are hosted in?

You're ignoring everyone else. I was referring to everyone outside of the Americas. India is about the mid-point, so everyone to the west of India is connecting to the US through the east coast, whereas everyone to the east is connecting through the west coast. If they simply moved the servers to the west coast, see what happens? You're only shifting the problem, and according to ArenaNet, the east coast was better for the majority, hence there'll be more complaints.

@abcruziii.9405 said:What's 10-20ms latency difference if some people in other parts of the globe play with higher latency than that? The shift to Amazon Web Services is precisely the issue here, more so since they chose to move to the East Coast region to host the game in. This region seems to suffer a lot of instability compared to the West Coast. I've used cloudping.info to verify that when I suffer from lag, only the East Coast server's ping is high.

Amazon has two west coast datacenters. Notice how your ping was 214ms for Oregon and 334ms for California? That's a 120ms difference for servers that are actually only 10-20ms away from each other. The east coast isn't your only problem. You're either encountering the same problem within Amazon's west coast network, or you're taking a worse overseas route, which either way means the problem isn't solved for everyone.

If you want to ping the servers yourself:dynamodb.us-east-1.amazonaws.comdynamodb.us-west-1.amazonaws.comdynamodb.us-west-2.amazonaws.comdynamodb.eu-central-1.amazonaws.com

[Velox.2031]

Using Comcast and im in colorado. Usual ping is 30-50 but now base ping is 500+ - 4000ping. unplayable.

[abcruziii.9405]

@Healix.5819 said:You're ignoring everyone else. I was referring to everyone outside of the Americas. India is about the mid-point, so everyone to the west of India is connecting to the US through the east coast, whereas everyone to the east is connecting through the west coast. If they simply moved the servers to the west coast, see what happens? You're only shifting the problem, and according to ArenaNet, the east coast was better for the majority, hence there'll be more complaints.

So, the needs of the many outweigh the needs of the few? I think I could say the same for you if you ignore "everyone else" who lives in OCX/SEA. Taking your example, are you saying this from actual experience that people in India connect through the East Coast? Are you sure they aren't suffering latency issues connecting through the East Coast? Internet cables don't follow the closest path - these cables pass through points that connect countries/islands as much as possible.

@Healix.5819 said:If you want to ping the servers yourself:dynamodb.us-east-1.amazonaws.comdynamodb.us-west-1.amazonaws.comdynamodb.us-west-2.amazonaws.comdynamodb.eu-central-1.amazonaws.com

I pinged them for you, while the east coast AWS datacenter was behaving.

Pinging dynamodb.us-east-1.amazonaws.com [52.94.0.126] with 32 bytes of data:

! Reply from 52.94.0.126: bytes=32 time=243ms TTL=232! Reply from 52.94.0.126: bytes=32 time=243ms TTL=232! Reply from 52.94.0.126: bytes=32 time=243ms TTL=232! Reply from 52.94.0.126: bytes=32 time=242ms TTL=232!! Ping statistics for 52.94.0.126:! Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),! Approximate round trip times in milli-seconds:! Minimum = 242ms, Maximum = 243ms, Average = 242ms!

Pinging dynamodb.us-west-1.amazonaws.com [52.94.12.70] with 32 bytes of data:

! Reply from 52.94.12.70: bytes=32 time=212ms TTL=239! Reply from 52.94.12.70: bytes=32 time=212ms TTL=239! Reply from 52.94.12.70: bytes=32 time=211ms TTL=239! Reply from 52.94.12.70: bytes=32 time=212ms TTL=239!! Ping statistics for 52.94.12.70:! Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),! Approximate round trip times in milli-seconds:! Minimum = 211ms, Maximum = 212ms, Average = 211ms

Pinging dynamodb.us-west-2.amazonaws.com [52.94.29.176] with 32 bytes of data:

! Reply from 52.94.29.176: bytes=32 time=193ms TTL=235! Reply from 52.94.29.176: bytes=32 time=193ms TTL=235! Reply from 52.94.29.176: bytes=32 time=193ms TTL=235! Reply from 52.94.29.176: bytes=32 time=193ms TTL=235!! Ping statistics for 52.94.29.176:! Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),! Approximate round trip times in milli-seconds:! Minimum = 193ms, Maximum = 193ms, Average = 193ms

Pinging dynamodb.eu-central-1.amazonaws.com [52.94.17.12] with 32 bytes of data:

! Reply from 52.94.17.12: bytes=32 time=285ms TTL=239! Reply from 52.94.17.12: bytes=32 time=285ms TTL=239! Reply from 52.94.17.12: bytes=32 time=285ms TTL=239! Reply from 52.94.17.12: bytes=32 time=285ms TTL=239!! Ping statistics for 52.94.17.12:! Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),! Approximate round trip times in milli-seconds:! Minimum = 285ms, Maximum = 285ms, Average = 285ms

Looking at these results, I really don't care where in the continental US they could deploy the game in. The deeper issue is that the East Coast AWS server has shown high latency issues serving OCX/SEA at certain times of the day, for example, OCX/SEA prime time. If it were stable then there wouldn't have been any issue.

[abcruziii.9405]

Here's the ping results during OCX/SEA prime time latency.

Pinging dynamodb.us-east-1.amazonaws.com [52.119.226.36] with 32 bytes of data:

! Reply from 52.119.226.36: bytes=32 time=349ms TTL=228! Request timed out.! Reply from 52.119.226.36: bytes=32 time=350ms TTL=228! Reply from 52.119.226.36: bytes=32 time=349ms TTL=228!! Ping statistics for 52.119.226.36:! Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),! Approximate round trip times in milli-seconds:! Minimum = 349ms, Maximum = 350ms, Average = 349ms!

Pinging dynamodb.us-west-1.amazonaws.com [52.94.12.80] with 32 bytes of data:

! Reply from 52.94.12.80: bytes=32 time=341ms TTL=239! Reply from 52.94.12.80: bytes=32 time=319ms TTL=239! Reply from 52.94.12.80: bytes=32 time=319ms TTL=239! Reply from 52.94.12.80: bytes=32 time=326ms TTL=239!! Ping statistics for 52.94.12.80:! Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),! Approximate round trip times in milli-seconds:! Minimum = 319ms, Maximum = 341ms, Average = 326ms!

Pinging dynamodb.us-west-2.amazonaws.com [52.94.28.38] with 32 bytes of data:

! Reply from 52.94.28.38: bytes=32 time=185ms TTL=232! Reply from 52.94.28.38: bytes=32 time=185ms TTL=232! Reply from 52.94.28.38: bytes=32 time=185ms TTL=232! Reply from 52.94.28.38: bytes=32 time=185ms TTL=232!! Ping statistics for 52.94.28.38:! Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),! Approximate round trip times in milli-seconds:! Minimum = 185ms, Maximum = 185ms, Average = 185ms

Pinging dynamodb.eu-central-1.amazonaws.com [52.94.17.132] with 32 bytes of data:

! Reply from 52.94.17.132: bytes=32 time=401ms TTL=239! Reply from 52.94.17.132: bytes=32 time=401ms TTL=239! Reply from 52.94.17.132: bytes=32 time=401ms TTL=239! Reply from 52.94.17.132: bytes=32 time=400ms TTL=239!! Ping statistics for 52.94.17.132:! Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),! Approximate round trip times in milli-seconds:! Minimum = 400ms, Maximum = 401ms, Average = 400ms

[Healix.5819]

@abcruziii.9405 said:Looking at these results, I really don't care where in the continental US they could deploy the game in. The deeper issue is that the East Coast AWS server has shown high latency issues serving OCX/SEA at certain times of the day, for example, OCX/SEA prime time. If it were stable then there wouldn't have been any issue.

What about after your last post? It's not just the east coast, your ping spikes everywhere except for the one west coast datacenter in Oregon, and that's probably only because you're not having to go through a larger Amazon network.

us-east-1: Virginia (GW2 NA)us-west-1: Californiaus-west-2: Oregoneu-central-1: Frankfurt (GW2 EU)

I'm assuming their traces look similar, where the spikes begin inside Amazon's network.

@abcruziii.9405 said:So, the needs of the many outweigh the needs of the few? I think I could say the same for you if you ignore "everyone else" who lives in OCX/SEA. Taking your example, are you saying this from actual experience that people in India connect through the East Coast? Are you sure they aren't suffering latency issues connecting through the East Coast? Internet cables don't follow the closest path - these cables pass through points that connect countries/islands as much as possible.

Routing over the internet tries to take the shortest path first, but what that is exactly is entirely up to the networks, since they don't all connect to each other. As a general rule, you're going to be connecting to the US through whichever coast you're closest to. If ArenaNet switched to the west coast, Europe, Africa and everyone in between would now have your problem. Although switching would help you, it's not a solution for everyone and would only worsen the problem. They could only try to minimize the problem by using both datacenters, but that's not something they could just do immediately or may even be looking into.

The actual problem here is something only Amazon can solve, though they'd likely suggest using their datacenters in Asia. In the meantime, you can try to fix the problem yourself by using a VPN to avoid parts of their network, or perhaps, avoid being throttled by them.