90006/2/1 Errors and then subsequent 2002 errors

[NightPort]

It seems these errors are happening most often when moving between instanced servers. For example, MSQ instance quests caused multiple 90k errors and I had to ultimately do them on very easy just to have a HOPE of getting through the content. Add in the que times and everything else took about 10 hours cumulatively to get through a single instance quest which is collectively worse than the issue with Raubahn in Stormblood.

Another point where i hit 90k errors the most happens when I leave a dungeon. Now this can be during the cut scene of a new dungeon (causing the most frustration because it ends it through the disconnect) or simply leaving a dungeon I have run before.

Finally, these can happen when moving between areas or switching instances in an area I am in.

Once these occur I then must wait in a queue length for an hour or more depending on when they occurred (usually an hour after 1pm central time) causing more strife. Of course when attempting to get back in I seem to encounter a large number of 2002 errors that ultimately result in me being pushed to the end of the queue line because the game will not load within the small window needed after an error has occurred to retain my spot in the queue.

These are issues that SE has seemingly liked to chalk up to the "users internet connection" and yet multiple posts and people have provided evidence that this is not the case. I have, in fact, maintained a consistent connection via discord talking through the errors with my friends via the voice chat. If there was an issue with my connection then I would also drop my voice chat at the same time. Of course this doesn't happen because it is happening outside my network and SE has no buffers in place to assist in these packet losses and instead throws out the 90k errors.

These issues have gained momentum since the "fix" of 2002, 4004, and 3001 errors in the most recent hot fix. However, it seems as though very little is being done to resolve these issues. Please take in all the different posts regarding these issues and actually make some concentrated effort into solving them.

[Hikuro_Kenshi]

I agree I just 90006'd and it would take many hours in the 3k+ que to reconnect, so I guess I'm done playing for today.

It isn't my internet that's the problem. Everything else works just fine. It's either a problem in the pathway to the server or a problem with the server. Either way, it's something we have no control over and needs to be fixed.

[Jarlan]

I agree I just 90006'd and it would take many hours in the 3k+ que to reconnect, so I guess I'm done playing for today.

It isn't my internet that's the problem. Everything else works just fine. It's either a problem in the pathway to the server or a problem with the server. Either way, it's something we have no control over and needs to be fixed.

It literally just happened to me too, in the middle of a raid actually. It's happening to clusters of people at the exact same time, a member in my FC and me get dc'ed at the same time every time too.

[select20]

Just got the 2002 error myself after waiting almost 3 hours. I immediately tried logging in again, and the que was back to where I started.

[Dadswell]

This is also happening to me. Logged in at 9:07 AM this morning waited for 2 hours to get in. Did about 3-4 quests in Sharlayan and got DCed during a cutscene. Re opened the game immediately and was now in a queue double what it was not even an hour before. I get back in 3 and a half hours later. I did two...two more quests and get into another cutscene and dced again. Re open the game and lose my place. I don't mind waiting in a queue im used to it. But the dc's are actually starting to frustrate me. Everyone pays for their time and i believe people can truly play how they want but there needs to be a way of looking at people who are just idle in the cities dancing or playing instruments and start letting people who can't even really begin the story in. I'm frustrated because i feel like the small amount of time i get to play is spent watching a queue screen and i can't just walk away because if i do that's when i'll get dced and restart queue all over again. Sorry for the rant.

[Devourn]

Be it the crappy nodes of us.bb.gin.ntt.net that are constantly packet lossing, to the Square server instability, I'm at my wits end. My friends from Australia connecting to the NA servers have more stability when it comes to crap NTT though, so its definitely routing when it comes to that. Square blaming people's internet connections is lip service, while this maybe true for very few, it is an exception rather than the case, results like people experiencing enmasse is akin to being called stupid by Square.

[NightPort]

Be it the crappy nodes of us.bb.gin.ntt.net that are constantly packet lossing, to the Square server instability, I'm at my wits end. My friends from Australia connecting to the NA servers have more stability when it comes to crap NTT though, so its definitely routing when it comes to that. Square blaming people's internet connections is lip service, while this maybe true for very few, it is an exception rather than the case, results like people experiencing enmasse is akin to being called stupid by Square.

This seems like something SE can work directly with NTT to figure out. These nodes should be capable of dealing with the load to them, and yet they seem to be struggling. I also find that it seems to be specific to regions, meaning that people in a similar area of the country experience it more than others because of the routing to these nodes.

[Darneltia]

Greetings fellow Eorzean,

We apologize for the inconvenience you have experienced with server congestion on Final Fantasy XIV. Due to the recent release of Endwalker, we are experiencing an extremely high surge in player base which may result in long queue times and possible connection based errors such as 2002. We are aware of this inconvenience and have addressed it in the following Lodestone post:

https://na.finalfantasyxiv.com/lodes...9264ac9f24986f

We appreciate your patience and understanding regarding this matter and ask that you try again at a later time to see if the issue persists along with keeping an eye out on the Lodestone website when further updates will become available. The development team is hard at work on these issues and will address them as soon as possible.

Thank you for visiting the Final Fantasy XIV Technical Support forums!

[NightPort]

Greetings fellow Eorzean,

We apologize for the inconvenience you have experienced with server congestion on Final Fantasy XIV. Due to the recent release of Endwalker, we are experiencing an extremely high surge in player base which may result in long queue times and possible connection based errors such as 2002. We are aware of this inconvenience and have addressed it in the following Lodestone post:

https://na.finalfantasyxiv.com/lodes...9264ac9f24986f

We appreciate your patience and understanding regarding this matter and ask that you try again at a later time to see if the issue persists along with keeping an eye out on the Lodestone website when further updates will become available. The development team is hard at work on these issues and will address them as soon as possible.

Thank you for visiting the Final Fantasy XIV Technical Support forums!

Darneltia...responding in the exact same way to errors is not really helping the issue. The fact is, it seems as though SE isn't taking the 90k disconnects seriously even though multiple points of proof have shown that these issues are not stemming from outside the players internet and therefore not their issue with connectivity. It would be nice to see more of a direct response from the development team regarding this issue. Simply saying they see no issues isn't really looking into the problem. Just a "wait and see" approach. Unfortunately, this is not a great way to handle this issue as they continue to grow among the player base.

[Hikuro_Kenshi]

Here we go again today. This is becoming an everyday occurrence and it's making the game unplayable.