Thanks for sharing. This seems like a very accurate measure of latency while in-game.
Printable View
Boston. Went from 50-60 average (wireless) to 105-110. Still no packet loss though, so I'll deal. East Coast always get shafted.
Us west coast players have been playing the game with ~150+ ping the since the game has been out and it is fine. They said the game was made with 200 ping in mind.
If you live in Brazil and the game is suffering from 300ms+ latency, the real latency we should be getting is between 190ms and 210ms. Telefónica is routing 204.2.229.0/24 packets through Amsterdan. It only happens between Telefonica and NTT. Running this check to test the latency of the AWS CA servers can be a rough simulation of what you should be getting.
If your traceroute log shows hops named "ae1-0-ntt-grtamstc1.net.telefonicaglobalsolutions.com" and/or "amstnl02.nl.bb.gin.ntt.net" I encourage you to call tech support and apply generous quantities of salt.
I have gone from around 60-70 ms ping to well over 110-120. The effect is very noticeable, and as a healer the added latency has dramatically affected how well I can heal.
I REALLY hope that they will either optimize the servers to allow for improved latency somehow to bring people on the east coast back up to speed, or move to a centralized location.
Not to say that there weren't any who benefited from this move, but I believe that they could have moved with less detriment to people who live on the east coast.
I am probably jumping the gun a little bit, but it freaks me out that the problems I am experiencing have no clear solution in the works, and SE has not addressed it as of this moment.
looking through the resource monitor shows up as an remote address of 204.2.229.84 for Coeurl which looking into the trace puts it in Colorado. Not sure why people are saying Sacramento.
cmd tells me 176, game tells me 2k+. I don't know what to believe anymore.
routing tables are still being rebuilt ripple by ripple. It will likely take weeks for everything to settle down from the changes. I bet that the DNS changes haven't fully propagated yet either, Though I'm sure the main root DNS servers are updated otherwise it wouldn't work at all.
Regarding the data center location, unless SE has confirmed a state for it, I wouldn't make any assumptions until things settle in terms of routing.