If you are having 90002/90001/Disconnects please REPLY HERE!

[Plastic_Fork]

When are you going to address this, Square? You have a 30+ page thread that's been going on for a year for tons of people having this problem.

This week has been horrible. I've d/c'd due to 900002 errors so many times this week. Five times in the same CLL instance in the same night, during PvP, during 24 man raids, and tonight during BA which cost me a clear as I died as a result and got sucked out during blackhole. Sometimes I see the d/c indicator over my head standing still by the retainer bell doing nothing. This is beyond ridiculous at this point. Why won't you talk to us? Why won't you help us?

I share the same internet as my roommate. I get 90002 errors all the time. They do not. I always connect to 204.2.229.104. They always connect to 204.2.229.106. Same house. Same internet. Same modem. Different computers. Different connection IP. Looked up 204.2.229.104, and it's registered to NTT. When will you have NTT address this? I've never had so many disconnect issues until Shadowbringers went live and it's been plaguing me ever since. Not our ISP. Literally zero issues with any other game or network related service/streaming/anything. Even while playing FF14. Only FF14 disconnects or has lag.

[Drox]

What's weird about my disconnects is I don't get error codes (Like 90001) or lag before the d/c. Mine just happens quick and just with the message "You've been disconnected from the server". The one thing I do have in common with some posting here is my ISP is Spectrum, it's not my PC or connection as both seem fine and the issue only started like maybe the past year or so. Before then I never d/c'd as much as I do now, now it seems to happen at least 3-4 times randomly any given session I play.

So an update to my issue (Maybe this helps others). I changed the permissions of 3 executables to make sure they launch with admin permissions within my steam folders (ffxiv, ffxiv_dx11, and ffxivboot64). Did this a day or so ago, haven't d/c'd yet since changing the permissions. Not sure if this helps anyone but it seems to have curved the issue for me at the moment. For good measure I also did a hard reset on my router.

[Eryoll]

Yesterday was the worst day yet, Sat 26th June, either my wife or myself were being disconnected every 20-40 mins on average, some times sooner. It is still happening today Sun 27th Jun.

[Manuu]

Just to let you all know, they addressed the connection issues today. Let's hope it fixed our problems so we can have fun again

https://na.finalfantasyxiv.com/lodes...5764fa9b8951ce

[Eryoll]

I optimistically look forward to trying again tonight... although, I have had these issues since i bought the game in January, and others have had the issue for much longer, hard to believe this will be THE fix.

[Eryoll]

Lasted about 30 mins before getting booted



Edit: and another 4-5 times over approx 4 hrs

Tonight's broadband quality graph, everything looking OK at my end.

https://www.thinkbroadband.com/broad...3c9-29-06-2021

[Ravare]

Someone in my raid group still got the disconnect.

I've been experiencing pretty significant lag for the past 4 or 5 days. Makes the duty finder ques unplayable because of the rubber banding.

[Manuu]

Same here, I still have lag spikes.

[Stack]

On my route, there's still moderate packet loss being introduced at NTT San Jose (ae-1.r24.snjsca04.us.bb.gin.ntt.net) and significant packet loss at the last hop before the neolobby datacenter servers (204.2.229.234). With this kind of poor network performance, it's no surprise that people are having such trouble staying connected to the game.

This problem can be mitigated (at least on my end, as a central US player attempting to connect to Aether) by finding an alternate route to the game servers (e.g. Mudfish or another VPN service) that bypasses San Jose. Sacramento or another "North California" geolocated endpoint server seems to work solidly for me, but YMMV.

I'm actually seeing the same kind of problems when connecting to a JP data center - the latency is about what you'd expect for a transpacific connection but the packet loss is problematic and 90k disconnects are frequent. Again, this can be mitigated by changing endpoints to avoid as much of the NTT pipe as possible.

I understand why SE chooses to use NTT for their hosting, but these issues are long standing and really need some attention.

[MiaShino]

Me and my partner have been using Exitlag because if we do not use it we cannot play

Just to let you all know, they addressed the connection issues today. Let's hope it fixed our problems so we can have fun again

https://na.finalfantasyxiv.com/lodes...5764fa9b8951ce

Perhaps I have lost the mind but there was a time where I wished to do system and network administration stuffs, also coding this too. From limited knowledge on how this all functions it is not a problem that can easily be fixed. We are running into simple physics limitations and bypassing them would require spending for both Square and NA internet providers (HA!). There are simply not enough connections from NTT to the Comcast/Charter ibone to support one entire country the size of America. The weak link appears to be NTT's nodes or however they have them configured (probably the way they would in Japan).

Thousands and thousands and many many players all connecting into the same node > node becomes unstable and begins (well should) rerouting traffic through other nodes > other nodes are also oversaturated and kerblam disconnected. That is why your address within the NTT network can shift and why some even in same house are disconnected while others are not (husband drops while wife is okay). Square needs to add East Coast and Central servers (one datacenter for each major region). This would split the players across the Comcast ibone leading to less oversaturated nodes and better experience for all. It is also something that will probably not happen