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

Now that we know they really went there, is anyone planning to transfer? Either from NA to EU or JP to NA.

Code:

---

neolobby02.ffxiv.com has address 204.2.229.9
neolobby04.ffxiv.com has address 204.2.229.10

---

(these ARE pingable now!)

I'm curious to see how much of a ping improvement I get over in Hawaii.

How... is this known if the servers are still offline.

This is pretty much ideal for me, so nah, i'm not going anywhere. Everything's coming up Milhouse.

Quote:

---

Originally Posted by MeoTwister5

How... is this known if the servers are still offline.

---

Because they updated the DNS records that point to them already.

...and here I expected the midwest; guess you can't expect all developers to make sensible decisions like that. Looks like you won that one, Raikki. lol

"Let's move from one coast to another, that's sensible! Who cares about a more centralized location?!"

T h a n k s sqx.

Time to move to Odin after all these years on Balmeme.

I hope they offer free transfer PLUS money EARNED for over 3 years for EU members wanted to move to a European server.because I have played with 189 ping and you can feel the lag.

I'm so bummed. I was so hoping for central or west coast. I will test and see how bad it is when servers are up. I already played with 160~ and now it'll jump to 200~ ;_;

lol Welp... I never felt I had ping trouble from the ones in Canada.

Hopefully CA to TX will not be any different.

As a Californian I say: Sweet!

Just awesome...if this becomes unplayable in raid environment for EU players like me I might outright quit...
Here's still hoping, but my hopes are getting really low :(

Of course they wouldn't put it in a centralized location like Chicago or Dallas. Why was I expecting anything different?

Quote:

---

Originally Posted by Mature

I hope they offer free transfer PLUS money EARNED for over 3 years for EU members wanted to move to a European server.because I have played with 189 ping and you can feel the lag.

---

They offered EU users free transfers when they moved the EU data center, it would be stupid not to offer the same for NA users.

Perfect for me.

No complaints.

Quote:

---

Originally Posted by thorkellthetall

Of course they wouldn't put it in a centralized location like Chicago or Dallas. Why was I expecting anything different?

---

You shouldn't expect them to know any better. A lotttt of foreigners think traveling from california to texas is like pulling into a walmart, but it really isn't. Heck driving from San Diego, CA to Sacramento is still a hell of a drive probably 12ish hours.

I no longer have an excuse in getting knocked off Titan anymore.

Quote:

---

Originally Posted by Raikki

Because they updated the DNS records that point to them already.

---

Can you tell me what site you used?
Using all kinds of DNS Lookup websites or even simple "ip location" websites I get different locations, mostly around Chicago/Detroit/Kentucky area, one in Colorado.
Haven't found anything that leads to California.

Quote:

---

Originally Posted by Aniya_Estlihn

...and here I expected the midwest; guess you can't expect all developers to make sensible decisions like that. Looks like you won that one, Raikki. lol

---

I'd rather have lost that wager, but it's understandable even though it sucks for a lot of us. It's a Japanese company (NTT), similar to how the Chaos datacenter is hosted by a Japanese company (KDDI); it's more conveniently accessible from Square's US headquarters; and it's a much easier trip if they need to send people over from Japan.

Omg if this is true the Hometown ping for me! lol

Quote:

---

Originally Posted by Hitsuzen

You shouldn't expect them to know any better. A lotttt of foreigners think traveling from california to texas is like pulling into a walmart, but it really isn't. Heck driving from San Diego, CA to Sacramento is still a hell of a drive probably 12ish hours.

---

I don't really understand your response. The Canadian location wasn't manned by Japanese workers with Visas or anything.

Quote:

---

Originally Posted by thorkellthetall

I don't really understand your response. The Canadian location wasn't manned by Japanese workers with Visas or anything.

---

Basically the distance between states is pretty vast, but they probably think it being located in the Country itself is enough for ping times.

I for one would wait to say where they are. The DNS may have been updated but until all locations can fully be resolved. Which it wont until pingable. The routing will not be complete. Most recent info has this IP and host name in 3 locations, Mich, Calf, and Nebraska. Lets wait till live first.

And While you may be right, it's still gonna be about as good as before because the routing may be longer but we will not deal with the routing choke at the final hop for the prior location.

Looked up the IP and it says Dallas for me, so i don't know where you got Cali from :thinking:

https://db-ip.com/204.2.229.10
Actually it looks like it's in Texas after all. Good.

https://www.whois.com/whois/204.2.229.10

Whois data shows it being in Colorado while


https://db-ip.com/204.2.229.10

Shows in texas. Meeh, It'll probably be on one of the three.

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.

Pingtested to CloudPing gave me 168ms to CA, which is a 70 ping increase

Welp, I'm not really happy with that :(

Quote:

---

Originally Posted by Mitsuma

Can you tell me what site you used?
Using all kinds of DNS Lookup websites or even simple "ip location" websites I get different locations, mostly around Chicago/Detroit/Kentucky area, one in Colorado.
Haven't found anything that leads to California.

---

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.

Quote:

---

Originally Posted by Lokryn

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 :D.

Quote:

---

Originally Posted by Lokryn

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:

Code:

---

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:

Code:

---

network:IP-Network-Block:204.2.229.0 - 204.2.229.255

---

Quote:

---

Originally Posted by Lokryn

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?

Quote:

---

Originally Posted by Raikki

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.

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

Quote:

---

Originally Posted by Galaick

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.

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.

Quote:

---

Originally Posted by Lokryn

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.

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.

Quote:

---

Originally Posted by 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..

---

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