All the lag, network issues are server side [CONFIRMED]

[Gonzothegreat198]

A majority of all 90k I have experienced have NOT been from SE servers disconnecting me, but from issues with my network provider.
Whenever it happens, the gateway at my network provider stops responding to ping, and there's no way that SE can cause that.
My network provider keep saying there is no problem, even when I can prove there is A problem on their side.

The times I've been certain that it was on SE's side the disconnection occurred, it also affected everyone connected to the same instance/world server.

The lag issues are in general separate from the 90k issues and mostly happen during peak times when servers are congested.

My problem with 90k happens because i'm currently on wireless until my friend sends me some cat6 cabling. The issue being is i'm in an 80foot long modular home with me on the one side and the wireless router on the other, and even then it only happens rarely.

[Gonzothegreat198]

I'm not reading more into it, the SE guys didn't have me run any tests, this is what they flat out told me was the problem. My own traceroutes I have run here on the forums are fine and the ones you are referring to about other people "proving" some aren't SE's fault is BS. A 200 ms ping is 1/5 of a second. That is what cogent is giving those people, 1/5 a sec of lag. What everyone is complaining about is actually several full seconds of lag, timeouts, etc that are the fault of the server. You guys have been wrong from the start and know next to nothing about how a traceroute actually even works. I saw someone blame a lone * (timeout) as the problem in someone's traceroute, not a full timeout mind you, but 1 lone asterisk.

Please, please stop while you're ahead. You've taken an automated response from SE to mean that you are now an expert and know what you are talking about and you don't. You're not even close, 200 ms while seemingly small is enough of a latency issue to cause congestion, especially when is a multitude of packets being sent and not just three, which is what a tracert sends, hell if you think its not go talk to some of the aussies playing on NA/EU servers.

I have gotten the 90k. I KNOW FOR A FACT THAT IT WAS NOT DUE TO SE HARDWARE FAILURE! I know for a fact it was due to my wifi connection losing the signal to the router, guess how i knew that? Thats right because my little wifi icon got a big red x at the same time i got the 90k.

[Marishi-Ten]

So after requesting a refund for the subscription I paid for this month because I haven't been able to play this is the message I received from SE support:

"Dear Customer,

Regarding your request for account support. Please find your answer below.

If you are receiving an Error 90000 when attempting to access FINAL FANTASY XIV: A Realm Reborn, please try again later. This error simply means that the server is congested and you will need to keep trying until you are able to login. We apologize for any inconvenience this may cause you.

Thank you for contacting the SQUARE ENIX Support Center."

Take that you white knight "gurus" of supposed throttling knowledge.

The error 90000 is a general error used to point the admins in a general direction to look. Basically, Error 90000 is a disconnect. You can unplug your router and wait for the error to populate on your client. This doesn't mean that the server is having an issue, it means you cannot connect to the network due to packet loss and the client being unable to authenticate itself with the host.

This error can populate anywhere from hop one to end point. It doesn't mean that the issue is directly related to Square as a disconnect can happen literally anywhere on the route path.

The email you received also looks to be either a canned response or an auto generated reply. Normally, these emails are used as a blanket email by tech firms that are overloaded with support requests. Instead of their agents typing out individual responses, they use a blanket statement to essentially dissuade people from contacting them with egregious requests and/or repeat inquiries from the same login. If you read between the lines, that email actually reads as a "stop contacting us" email.

I don't think anyone has claimed the issue is throttling and I don't think anyone is "white knighting". You may have misinterpreted statements made by others.

[Appleh4x]

This thread is so full of denial. Look over my other posts if you want more specifics on what I've already covered regarding the issue.

[KraggyKor]

So after requesting a refund for the subscription I paid for this month because I haven't been able to play this is the message I received from SE support:

"Dear Customer,

Regarding your request for account support. Please find your answer below.

If you are receiving an Error 90000 when attempting to access FINAL FANTASY XIV: A Realm Reborn, please try again later. This error simply means that the server is congested and you will need to keep trying until you are able to login. We apologize for any inconvenience this may cause you.

Thank you for contacting the SQUARE ENIX Support Center."

Take that you white knight "gurus" of supposed throttling knowledge.

Since the error SE's mail is discussing has nothing to do with 'lag' or 'throttling' your comment is as irrelevant as your ignorance of what causes 'lag' and what 'throttling' is, as we already established when you tried to proffer 'ping' times as evidence for your flawed views.

[Appleh4x]

Since the error SE's mail is discussing has nothing to do with 'lag' or 'throttling' your comment is as irrelevant as your ignorance of what causes 'lag' and what 'throttling' is, as we already established when you tried to proffer 'ping' times as evidence for your flawed views.

That was the second letter in a line about a lag issue, the header for the email actually states that it is about lag and disconnects.

[Appleh4x]

Bump for relevance because there are 8 new topics on this in 5 hours.

[Marishi-Ten]

Bump for relevance because there are 8 new topics on this in 5 hours.

Tell you what, you get a Sr. Systems Admin from the Montreal office to send you an email confirming the problem is on them (providing details) and I'll consider it relevant.

I can't take a canned response seriously when it's basically telling you to go away.

I know this because my company actively uses these responses to deal with our some of our more problematic end users and we don't want to waste time explaining and issue and how to fix as they won't listen because it's not the answer they want to hear.

[Appleh4x]

Tell you what, you get a Sr. Systems Admin from the Montreal office to send you an email confirming the problem is on them (providing details) and I'll consider it relevant.

I can't take a canned response seriously when it's basically telling you to go away.

I know this because my company actively uses these responses to deal with our some of our more problematic end users and we don't want to waste time explaining and issue and how to fix as they won't listen because it's not the answer they want to hear.

Oh, you mean this guy? 5 steps ahead of you. http://www.square-enix-montreal.com/team/Tony-Pressacco

[Twilite]

Once again, this all happened to me at least AFTER the Oct 1rst maintenance. I'm not throwing out conspiracy or whatever, but me thinks something messed up during that maintenance that slipped by them.

There's another one friday, if going by their maintenance schedule. So maybe things will stabilize.