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

[UltimateAoe2]

Folks, you can look up the DNS all day, until the servers are up and pingable the DNS routing tables will not Resolve. so the location will be all over the place as the system tries to find it.

3+ years networking.

Figured people would know that, but eeeh .

[Raikki]

Folks, you can look up the DNS all day, until the servers are up and pingable the DNS routing tables will not Resolve. so the location will be all over the place as the system tries to find it.

3+ years networking.

You're missing the part where 204.2.229.234 is already pingable on that route:

ae-1.r00.scrmca02.us.bb.gin.ntt.net (129.250.7.31) 
xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net (129.250.195.46) 
204.2.229.234 (204.2.229.234)

Same netblock:

network:IP-Network-Block:204.2.229.0 - 204.2.229.255

[Galaick]

Folks, you can look up the DNS all day, until the servers are up and pingable the DNS routing tables will not Resolve. so the location will be all over the place as the system tries to find it.

3+ years networking.

Wait, so help me out here, what does this actually mean? It might not be in CA at all or that the ping test I did to another CA server doesn't have to be accurate?

[Lokryn]

Geo IP lookups are not going to be very useful for freshly delegated IP addresses. Just traceroute to one of the IPs/hosts and it's abundantly obvious by reading the router hostnames.

That works both ways, For all we know that ip could have been in CA before and is no longer there and the routers are looking at the old DNS resolutions. Just because you register an IP/hostname, the full network doesn't automatically update at the same time, not until you can actually connect and resolve the routing tables.

So again, I would wait and see when they are fully pingable and DNS tables have had time to resolve fully.

[Bourne_Endeavor]

Apparently, people are getting different results. So it's not a confirmation just yet.

[Lokryn]

Wait, so help me out here, what does this actually mean? It might not be in CA at all or that the ping test I did to another CA server doesn't have to be accurate?

Until the servers are live your looking for a house that technically hasnt been built yet, so the DNS routing tables are looking for where they guess it may be. But until the final host is live, DNS routing can be wrong. I see it all the time where I work. And we have over 50,000 internal IPs we work with. You cant accurately tracert a dead host that was literally just updated and not on the network. The DNS routing will look at old info.

Now to be fair, it could very well be in CA. But I would wait to skewer SE until we can fully ping them.

[Dagny]

I went ahead and did the traceroute myself and these do appear to be valid in some way or form, so thanks for the information.

However, doing a lookup of the IPs, the locations appear to be all over the map. I've seen California, but I have gotten a lot of Michigan, some Texas, Colorado, and even a couple of hits in Kentucky. I may not be the most savvy on this, but you haven't provided any definitive proof the servers are in California. Please don't try to stir the pot without definitive evidence, so to speak.

[Ryuko]

Folks, you can look up the DNS all day, until the servers are up and pingable the DNS routing tables will not Resolve. so the location will be all over the place as the system tries to find it.

3+ years networking.

This, and also DNS records can be updated/changed very quickly. Maybe SE is just trolling us? Maybe?

The only logical reason I could find for having the new servers on the West Coast is to appease all of the English-speaking players in Hawaii, Australia, New Zealand, etc... who have been playing on the NA datacenter with horrible ping. However, it puts to rout (get it, hahaha) all of the NA players on the East Coast. However, if all of the known routing issues are resolved by placing the datacenter in the US... it may not matter.

I'll wait until the servers are actually up and pingable to freak out. It's not like I could do anything about it anyway. (I'm in NYC and was less than an 8-hour drive away from the previous datacenter. On the other hand, I suffered with *horrible* lag in 1.x when connecting to the JP datacenter and could barely beat any difficult content without making serious adjustments. I remember having to heal myself through every randomized dash in Ifrit Ex because I just couldn't make the reaction time no matter how quick I was. Just not fun. I'm hoping that won't be the case if the servers are on the West Coast. If people in CA could do all raiding through the previous datacenter, I should theoretically be able to do the same. I just have a little anxiety from 1.x days.)

As far as where I thought the datacenter would go... my bet was on Texas. :O

Edit: for what it's worth, all of my tracerts are dropping at Michigan.

[xJimmehx]

Where was Aether originally located?
I hope for east coast(though its a bit selfish) or at least something Central, that way nobody gets put on the opposite coast..
If Aether was not in usa at all before, it might be better even if its centralized or CA, and if thats the case id be happy with either.

[Seradima]

Where was Aether originally located?
I hope for east coast(though its a bit selfish) or at least something Central, that way nobody gets put on the opposite coast..

Aether and Primal were originally located on the East Coast, in Montreal I believe.