Important Information Regarding North American Data Center Relocation

[Valkyrie_Lenneth]

There's been no update over the last 2 weeks on the issues.
I'm part of the group of people that stopped playing because the ping doubled and the game because unplayable.

Is there really anything being done about this? Doesn't feel like it is.

Ping doubled to what? If it doubled to 80-100, and you think its unplayable, thats on you. West coast had been playing with that and more for years.

[Fourbestintoner]

Ping doubled to what? If it doubled to 80-100, and you think its unplayable, thats on you. West coast had been playing with that and more for years.

They also have been complaining for years, and so did Euros before their DC was moved.
Almost like 200ms being perfectly playable is a lie.
130ms on the NA data center.
110ms on the EU data center.
Guess I'm EU now.

[Valkyrie_Lenneth]

They also have been complaining for years, and so did Euros before their DC was moved.
Almost like 200ms being perfectly playable is a lie.
130ms on the NA data center.
110ms on the EU data center.
Guess I'm EU now.

I dont recall seeing much complaining. I certainly never did. I moved from Florida to Washington State, and barely saw a ping increase. Most ISP's can't route network traffic for crap.

[KisaiTenshi]

I dont recall seeing much complaining. I certainly never did. I moved from Florida to Washington State, and barely saw a ping increase. Most ISP's can't route network traffic for crap.

Most Tier 1 backbones have no problem routing things. The problem is that large ISP's like AT&T, Verizon and Comcast own their own backbones, so it's cheaper for them to not use any peers until the last hop possible. However many of these Tier 1 ISP's are also really evil to each other and have been known to route traffic over unfair peering agreements. Cogent and level3 are known for "breaking the internet"

eg:
http://www.telecompetitor.com/comcas...pute-resolved/
https://arstechnica.com/business/201...ernet-quality/

It's important to note that level3 and cogent are usually the villains in peering disputes. In the case of Square-Enix, they primarily use NTT's backbone but that tends to still require people to peer over at least one other backbone.

Like using my non-residential connections, a connection from hurricane electric (Fremont California) gets 5ms to FFXIV's gateway servers, but has to over telia in San Jose. My connection from Arizona goes over Cogent at Phoenix NAP. My local connection goes over Level3 at Seattle.

If I use a few lookingglass systems:

3 60 ms 59 ms 77 ms ae-3.r20.miamfl02.us.bb.gin.ntt.net (129.250.2.110)
4 87 ms 87 ms 87 ms ae-4.r23.asbnva02.us.bb.gin.ntt.net (129.250.2.86)
5 87 ms 88 ms 86 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net (129.250.6.237)

So Miami is going to Ashburn, Virginia before it's routed to San Jose, California. So needless to say that's several hundred miles in the wrong direction. Most other route paths go via Chicago, San Jose or directly to Los Angeles.

The only people who should have noticed a drastic change are those who live in the central-california area (where the servers now are) or the people who live in Montreal (where the servers were), everyone else would have been routed through the same gateway systems and with a few exceptions, likely still had the shortest best path.

[Domeric]

The only people who should have noticed a drastic change are those who live in the central-california area (where the servers now are) or the people who live in Montreal (where the servers were), everyone else would have been routed through the same gateway systems and with a few exceptions, likely still had the shortest best path.

I live in the midwest and I see a patented difference in raids and in hunts or fates where a great many people have arrived. I didn't have this problem when the servers were in canada.