Random 90K since patch

Quote:

---

Originally Posted by Zakalwe

Was just on a DF CM run and the same thing happened to most on the run, myself included. One party member a couple of times.

---

Same as my DF CM run, I got kicked once and one of our healers multiple times. I joined in progress and the other tank was gone since the start, very strange.

Ive disconnecting like crazy today. what the hell is up!

Error 9000 is back!
And so far, no word of a fix...
Yay..

same , was getting on Titan (DF) , also other players of random parties was get same 90000

Myself and several members of my FC have been getting a large amount of 90ks while attempting Binding Coil Turn 5. Please look in to it SE.
And yes, it follows with a 5003 authentication error afterwards, just in case anyone was thinking it was our internet connections.

Just got this error, 90k then a "Authentication Failed" when trying to get back on. Have to close out the game completely to get back on.

Quote:

---

Originally Posted by Sofy

Error 9000 is back!
And so far, no word of a fix...
Yay..

---

Error 90000 will never be gone. People are now in the mindset that any time you get 90000 it is always SE's fault, which is false. 90000 on its own, is just a simple disconnect, which can be cause by a great many things. In this case however, the 5003 afterwards DOES point to SE.

in this case its 100% squares fault.

I also received the 90k and 5003 errors twice today while fishing, but some of my friends from my FC seem to be constantly getting them. ;/

agreed it's se fault. I check routes, call internet isp , do pingtest for quality. I have a good certified a+ line. Does me proud every place I go but ffxiv server. Imagine that. No way is this my issue to own. Way too many ppl from all around the globe having the issue. I could kinda understand a route issue if it was just west coast or east coast or even just NA datacenter. However this is on jp data center an issue as well. I and several friends have characters on both and get the 90k and authentication error right after. FYI this is the progression of a bigger issue that started the maint before this one. The big put a stop to RMT fix they applied to the servers. After this random s0 or r0 ever since.