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

[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)

[RokkuEkkusu]

To put my perspective in this, I live in Hawaii. I didn't have much trouble playing FFXIV despite the servers being in Montreal at the time (which is very far from Hawaii BTW).

The game ran smoothly, I can dodge aoes, and I can do my rotations smoothly.

I am not sure if a location change will significantly affect my gameplay.

[savageink]

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)

LOL! This is why I was saying wait for the servers to come up and get optimized. Even when the servers come up and you can log in and get an in game ping screen, it doesn't mean the routing will have set in place yet. People expect everything to work faster than it does in reality. That 24 hours might be the best advice in this thread.

[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.

[Hestzhyen]

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 believe you, it's just that it's still going all the way out to Sacramento when I do a tracert. I know enough about networking to be dangerous in the advice I give and assumptions I make- not enough to grasp the full reason why. If the geolocation is Michigan, why am I getting routed out to Sacramento before it resolves?

[technole]

I believe you, it's just that it's still going all the way out to Sacramento when I do a tracert. I know enough about networking to be dangerous in the advice I give and assumptions I make- not enough to grasp the full reason why. If the geolocation is Michigan, why am I getting routed out to Sacramento before it resolves?

The person is wrong, the trace route to NTT's CA2 Sacramento data center is correct.


Going to post this again.


Many people who don't know what they are talking about confusing WHOIS vs a trace route. I'll try to explain it in simple terms.

WHOIS is like the internet phonebook "white pages". Like when you buy a .com name, you have the choice to publish who administers and pays for that domain. The address information is published for anyone to see. This has no bearing where the server(s) for that domain lives. You can protect your assets by just putting a corporate address of your company as the white listing. But your server might actually be in another country.

Traceroute is basically sending a heartbeat from your PC and internet connection to see the actual pipelines it has to go through to get the end connection. This method reports every pipeline hop you have to go through including the end of the tunnel. This is how you actually discover the server(s) you end at because internet backbones and data centers generally use some city codes as part of their pipeline addresses because they have a lot of them.