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

[SeraphicRadiance]

I don't blame them at all for upgrading the servers. We're going to be seeing the benefits very soon with Stormblood. More capacity and power is not a bad thing at all.

I do not agree, however, with the radio silence about where the new servers will be until we find out for ourselves. They could have avoided a lot of panic and ill-will by disclosing the state or general area in the initial announcement.

It's no secret the servers needed to be upgraded, that is a fact, and I fully agree with the decision to finally do so. However, this entire move has been shady because of, yes, radio silence from the get-go. Yoshi-P's initial post clearly shown they had already decided on a location but to this day we have not had official confirmation on the location.

Pardon the conspiracy theory, but it's almost as if they knew it would be received in a negative way if it was revealed to be California.

[Kethic]

...or, they might understand how insanely shady their fanbase is, and are intentionally not talking about the location for actual security reasons.

[Jaxelyn]

It's no secret the servers needed to be upgraded, that is a fact, and I fully agree with the decision to finally do so. However, this entire move has been shady because of, yes, radio silence from the get-go. Yoshi-P's initial post clearly shown they had already decided on a location but to this day we have not had official confirmation on the location.

Pardon the conspiracy theory, but it's almost as if they knew it would be received in a negative way if it was revealed to be California.

You might be an hour behind on the fact that it's probably not Cali and if that's true, everyone has been testing pings to the wrong location. The routing tables are going to take a bit now that the lobby url is actually replying to pings now.

[SeraphicRadiance]

You might be an hour behind on the fact that it's probably not Cali and if that's true, everyone has been testing pings to the wrong location. The routing tables are going to take a bit now that the lobby url is actually replying to pings now.

The waiting game continues, yes, but as previously stated, this is very good news for west coast players' ping at the moment, so...

[Raikki]

You might be an hour behind on the fact that it's probably not Cali and if that's true, everyone has been testing pings to the wrong location. The routing tables are going to take a bit now that the lobby url is actually replying to pings now.

You don't know what you're talking about, please stop confusing people.

[Jaxelyn]

You don't know what you're talking about, please stop confusing people.

Congratz on trying to insult someone who knows what they are talking about.
http://whatismyipaddress.com/ip/204.2.229.9

The IP is now showing Michigan, where before the hop before tracert timed out was California. On top of the fact that I am a network engineer. So everyone can keep crying about California, or they can figure out it's not actually California.

[Ghastly]

Congratz on trying to insult someone who knows what they are talking about.
http://whatismyipaddress.com/ip/204.2.229.9

The IP is now showing Michigan, where before the hop before tracert timed out was California. On top of the fact that I am a network engineer. So everyone can keep crying about California, or they can figure out it's not actually California.

I hope it can be Michigan so canadians can also have a good location. Remember NA is not only US so I hope it's somewhere like Michigan.

[-BlueGreen-]

Those ip locator sites are a joke. Try this one https://www.iplocation.net/ which will query multiple services at the same time. Using neolobby02.ffxiv.com [204.2.229.9] I see...
Greenwood Village Colorado
Michigan (no city, although earlier it said Troy)
Dallas Texas
Lebanon Kentucky

All at the same time. Interestingly, none say anything about California, but at least 3 of the services they list show that the DB they use was updated either May 1st or 2nd meaning those results wouldn't reflect reality anyway because the servers just moved within the last 48 hours.

On the other hand tracert doesn't attempt to tell you where the IP actually is, but the names some of those hops resolve to...
ae-0.r23.dllstx09.us.bb.gin.ntt.net
ae-45.r01.snjsca04.us.bb.gin.ntt.net
xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net (last named hop)

Looks to me like it goes to Dallas, then San Jose, then finally Sacramento before doing the final two hops to the destination. Could it be going some place completely different? Sure, but I doubt it.

So, as for those ip locator sites, it's like they put a map of the US on the wall, have a 5 year old toss some darts on it and return that as a result. That, or because the servers changed IP addresses as part of the move, those locations listed on those sites might be rough locations of the previous owners of said IP addresses.

[Kethic]

I also get Seattle to San Jose to Sacramento in the tracert for now, or Philly to 'asbn' Virginia to San Jose to Sacramento. At the moment, the IP is routed to Sacramento. Maybe in 2 hours it'll change. (shrug)

[Raikki]

Congratz on trying to insult someone who knows what they are talking about.
http://whatismyipaddress.com/ip/204.2.229.9

The IP is now showing Michigan, where before the hop before tracert timed out was California. On top of the fact that I am a network engineer. So everyone can keep crying about California, or they can figure out it's not actually California.

If you knew what you were talking about you would know that geo IP database accuracy is inconsistent and especially bad for servers.