Regarding Reports on Recent Connection Problems with the NA Data Center

[Kerwin]

As a result of this investigation, it was found that the issues were not related to the FINAL FANTASY XIV servers.

That is NOT the response people want to hear. The server's location is one of the CAUSES to this problem. Your company moved the servers to California which has resulted in nothing but problems for us in comparison to when the servers were located in Montreal. This is in part Square Enix's fault. NTT will do NOTHING in regards to this issue for us because as many people before me stated, WE ARE NOT THEIR CUSTOMERS. They do not provide us servers. They provide for SQUARE ENIX!

If your company will not do something about this, we will continue to have this problem for years to come!

I am severely disappointed. Now I have to explain to every raid group I ever join that I may hinder the group's progression in end game content because of issues OUTSIDE of my control. Unacceptable.

[Enkrateia]

Thank you for patience and assistance while we worked with the upstream ISP in question to investigate the connection issues that have been reported throughout the thread. These reports, details, and traceroutes aided our infrastructure teams in conducting detailed investigations into the difficulties connecting to FINAL FANTASY XIV through certain upstream ISP servers. As a result of this investigation, it was found that the issues were not related to the FINAL FANTASY XIV servers. As such, we have also been sharing the collected data with the upstream ISP in question for further reviews and investigations.

We apologize that these difficulties have been ongoing, and that we don’t have an immediate resolution to share. Although we have no direct control of the situation, we’ll continue to work with the upstream ISP to investigate whether there are any specific troubles that they can isolate and work towards a solution. We’ll also share any additional updates should they become available.

If you wish to make detailed reports about your connection difficulties, we recommend contacting your local ISP directly to try to improve your connection with the upstream ISP.

Thank you again for your patience and assistance throughout this process.

Greetings, everyone.

Based on your concerns about contacting the upstream ISP, we confirmed that there was a misunderstanding that occurred when creating the prior post. For continued connection concerns, you should be working with your local ISP to improve your connection with the upstream ISP, not the upstream ISP directly.

Because of this, I have corrected the information in the post to reflect the appropriate course of action. I apologize for the misunderstanding and the confusion and frustration that it may have generated.

[Callinon]

Greetings, everyone.

Based on your concerns about contacting the upstream ISP, we confirmed that there was a misunderstanding that occurred when creating the prior post. For continued connection concerns, you should be working with your local ISP to improve your connection with the upstream ISP, not the upstream ISP directly.

Because of this, I have corrected the information in the post to reflect the appropriate course of action. I apologize for the misunderstanding and the confusion and frustration that it may have generated.

You're not getting it.

YOUR ISP is the problem. NTT. They are the issue. As much as I enjoy blaming Comcast for everything from sun spots to hair loss, they aren't at fault here. If I open a ticket with Comcast telling them I'm having connection issues outside their network, they're going to rightly throw up their hands and ask what I expect them to do about it. YOU are the ones with the business relationship with NTT, not us, and not Comcast or Time Warner or Qwest or AOL or Mom'n'Pop's Super Internet Service.

Basically what you've said here is that SE has decided to take no action to correct the problems faced by nearly their entire American audience (north, south, and central). You've decided you'd rather just lose the subs than make an effort.

[Runsell]

Greetings, everyone.

Based on your concerns about contacting the upstream ISP, we confirmed that there was a misunderstanding that occurred when creating the prior post. For continued connection concerns, you should be working with your local ISP to improve your connection with the upstream ISP, not the upstream ISP directly.

Because of this, I have corrected the information in the post to reflect the appropriate course of action. I apologize for the misunderstanding and the confusion and frustration that it may have generated.

That's not going to work like you mentioned. I went ahead and talked with my ISP (AT&T) and they are not going to do any type of routing change from my end to your servers, they don't do that. Even more when the issue is reaching the NTT ISP.

I am going to not give too much detail about my personal life, but I do work for AT&T on DATA Traffic for US Restricted customer. We had a customer which I am going to reserve the name, which was getting Downstream issues. Making story long short, we used a different routing path with a new circuit to the customer since we are the ISP providing the traffic to them. They contacted AT&T and we solved the problem. Like other are saying in this forum and how I see it, we are not saying the SE Server is the problem, either that you guys decided to move the server to the west coast with NTT as the provider you are the one responsible to talk to NTT with all the finding we, the users, have shown in previous posts.

It is pretty easy to see, why when we use VPN and personally I made a character in EU servers, we don't see constant DC or LAGS. Once again contacting our ISP and asking them "Hey can you change the routing to 204.2.229.9 using another path?" THAT WILL NOT BE POSSIBLE, and is not our ISP issues. Using once again my example of where I Work, I am the ISP and if a customer have issues since I am their "last mile" routing path I need to take actions, and solve the problem.

Is sadly that you guys are not putting the proper effort on this problem and decided basically to take no action to correct the problem. I would have to take my own actions and see how I can solve this problem (VPN) which shouldn't be the way to play a game at all. I had less problem when the servers were in Montreal compared to where they are now in the West Coast.

[Zarkovitch]

Greetings, everyone.

Based on your concerns about contacting the upstream ISP, we confirmed that there was a misunderstanding that occurred when creating the prior post. For continued connection concerns, you should be working with your local ISP to improve your connection with the upstream ISP, not the upstream ISP directly.

Because of this, I have corrected the information in the post to reflect the appropriate course of action. I apologize for the misunderstanding and the confusion and frustration that it may have generated.

Pulling a Ubisoft I see well good luck with 5.0 sales.I mean look highest peek
https://ffxivcensus.com/2017-11/
now right now
https://ffxivcensus.com/2018-03/
ive check census there always see growth on game abit losses sometimes on odd patches but damn 80k player left NA you might lose more with eureka fiasco.

[hynaku]

I had no problems with servers in old location never got disconnected. But since they moved them to new location get so many 90k all the time makes me wonder why stay. Kind of funny where they moved the servers is way closer to where I live than old location was. Don't mind having my ping back at 200 if means can play and not worry about being disconnected every few minutes. Been loyal fan since ffxi first came out. You keep repeating same thing over and over that did years ago to fix my problems when servers was in Canada. Don't see me ever buying 5.0 when comes out if these disconnects is never fixed.

[Khyrain]

Friend of mine has all these issues, lag spikes, 90k every about 10 seconds in frontlines, PotD, etc. so he switched internet providers to try and fix it. He switched from AT&T Fiber to Google Fiber. Didn't fix anything. Maybe fixed some of the lag spiking, but the 90k error is still constant. So... Can't just be an ISP issue.

[Bluefve]

If you wish to make detailed reports about your connection difficulties, we recommend contacting your local ISP directly to try to improve your connection with the upstream ISP.

Already did. Even got ahold of their Network Engineering team through escalation. They confirmed it was an NTT routing issue. Cox will not (cannot?) do anything about it, and they ended by case. Can't see how sending others to the same route (with potentially worse luck by getting stuck at tier 1 outsourced support) would work.

[Mesarthim]

Greetings, everyone.

Based on your concerns about contacting the upstream ISP, we confirmed that there was a misunderstanding that occurred when creating the prior post. For continued connection concerns, you should be working with your local ISP to improve your connection with the upstream ISP, not the upstream ISP directly.

I'm not so dumb that I'd be sent on a wild goose chase when my (our local) ISP isn't even the problem. It is an NTT problem.

Your ISP, your provider for your servers, you're the customer. This is on you, not us. I mean we can continue to dodge the problem all expansion if you want but you're risking a loss of subscribers if they cannot cleanly connect to your servers through no fault of their own, but yours.

[Riko_Futatabi]

I'm guessing the recent Mod response has killed this thread for the meantime. I haven't posted an update in a while, but I'm letting you know that the situation I've been in for 7 months is still on-going. 90k errors/rubber-banding etc.

While it is nice to have Moderators finally in this part of the forums, even if we ultimately got nowhere in the end. I'm sure it's a pain being a Moderator, having to deal with things that are probably out of your hands or hearing the same thing day after day. I hope the clear message you've got from everyone is that NTT is not capable of reliably dealing with FFXIVs traffic at peak times(and maybe in general) and that this information is passed on so that this can get resolved in future.

Maybe you have some sort of contract with them that you don't wish to break and/or that finding a new provider will cost more initially. Who knows, I'm sure there's some reason why this isn't getting resolved immediately. I'm sure my words are as fleeting as the wind to the ears of those able to do something about this. But Square Enix as a company needs to be more transparent about these situations and improve tenfold with their communication within the company and with relaying that to the community. Much time and frustration could have been averted had we just known this couldn't get resolved any time soon. But you guys also probably didn't know this, or maybe I'm being too lenient!

Anyway, ¯\_(ツ)_/¯ got any VPN recommendations? (Sort of joking, but curious really.)