[Data Center USA] Ping increased. Report your changes here.

[Ayerinn]

Wrong. It should only be of concern to players located in NA. Not Oceania. And if it would, then it would be in the center of NA and I couldn't find a single reason to complain about that choice then (actually doing any move is another part).

You have the same choice of Japan where there are some people that speak your language and many people that don't as European people have. Do read my post in whole (and I had to edit it in because of this forums restrictive 1000-sign count).

OCE doesn't have their own servers unlike EU- you can argue whatever you want but EU players should be of no concern in regards to NA datacenters...period. It sucks for EU people but they have an option to move to the EU datacenters - and transfers should be opened up for free without gil restrictions imo.

[Sagittarii]

Hmm, I get Lebanon, Kentucky US when I do a DNS lookup on neolobby02.ffxiv.com. That hostname currently resolves to 204.2.229.9. Of course, they could just update the DNS record later on, but that's what I see now.

[Redarian]

Hmm, I get Lebanon, Kentucky US when I do a DNS lookup on neolobby02.ffxiv.com. That hostname currently resolves to 204.2.229.9. Of course, they could just update the DNS record later on, but that's what I see now.

Oh man, that's barely an hour away from me. Wouldn't that just be the dream.

I'm boggled that Riot (League of Legends) had this huge deal about moving FROM the west coast into Chicago, with the goal of equalizing ping for all players. Yet here is Square-Enix, moving TO the west coast? It's weird. Though maybe Riot has to deal with separate issues than Square-Enix, given the scale of the player base, and how League is much more punishing than FF if your ping is high?

[Sagittarii]

Oh man, that's barely an hour away from me. Wouldn't that just be the dream.

I'm boggled that Riot (League of Legends) had this huge deal about moving FROM the west coast into Chicago, with the goal of equalizing ping for all players. Yet here is Square-Enix, moving TO the west coast? It's weird. Though maybe Riot has to deal with separate issues than Square-Enix, given the scale of the player base, and how League is much more punishing than FF if your ping is high?

I live in Los Angeles, so moving the data-center to the west coast would suit me well. But, at this time, it looks like it will be Kentucky unless they do a last minute DNS change... we're less than 24 hours away from going back online, so I don't think they will screw around with DNS anymore.

[TaurusGilgamesh]

Hmm, I get Lebanon, Kentucky US when I do a DNS lookup on neolobby02.ffxiv.com. That hostname currently resolves to 204.2.229.9. Of course, they could just update the DNS record later on, but that's what I see now.

did you use a website for that? If so, you can't trust that result at all.

[Sagittarii]

Yes, I used a website. https://mxtoolbox.com/DNSLookup.aspx I use this site all the time and I actually work for a company that hosts public DNS. In the past, when I have done updates to public DNS records, that site has captured the updates accurately. It looks like SE is using Akamai to host their DNS.

[Raikki]

Yes, I used a website. https://mxtoolbox.com/DNSLookup.aspx I use this site all the time and I actually work for a company that hosts public DNS. In the past, when I have done updates to public DNS records, that site has captured the updates accurately. It looks like SE is using Akamai to host their DNS.

For people who aren't aware, IPs do not have inherent physical location data attached to them. Instead, various companies compile databases of where IPs are thought to be based on data collection. The accuracy of this data varies wildly, and is particularly not useful for newly assigned/reassigned IP blocks.

[TaurusGilgamesh]

Yes, I used a website. https://mxtoolbox.com/DNSLookup.aspx I use this site all the time and I actually work for a company that hosts public DNS. In the past, when I have done updates to public DNS records, that site has captured the updates accurately. It looks like SE is using Akamai to host their DNS.

and thats the thing... try 10 other web services and you will land in dallas, Kentucky, Detroit etc. You won't get a accurate result this way. And as most ppl here are using third party tools, it all got mixed up.
So as my traceroute using prompt is the same as pinging California directly, I'm sure the OP was right from the beginning.