Error 90000 still very much unresolved

[wirewitch]

I have largely been unable to play because of this error, yesterday was a joke and a very frustrating one. It really annoyed me that a friend of mine who literally lives across the street was able to play for hours yesterday evening, while I was unceremoniously kicked of and unable to log back in because the world was full and there were no Queue's.

This morning is no different. While I am able to log in after being booted off, I am unable to remain logged in as the error keeps raising its ugly head and giving me the boot.

I have checked with my ISP as I am with BT and I can see a lot of people who are having issues. However, I am on the BT Infinity 2 option and always have been so I should not be restricted. I have contacted them just to be sure and they have ran all manor of line tests to ensure this is the case.

This error has killed Early Access for a lot of people. While I myself am not that bothered about it as I consider a lot of my head start was in 1.0 if this error sees its way into tomorrow official launch date, I will be ensuring I cancel any subscription until its sorted. I do not need this frustrating time to also be a God-damned waste of money too.

[Wigett]

I am also seeing the 90000 error. i can get in for 20-45 min, seems fine. sometimes longer, but i will get up to go grab a drink, and when i come back. 90000 "connection lost" then when i try and get back in, it struggles.... i have to exit, restart, I use ATT Uverse.

[Grimscythe]

Am seeing it as well, but it only occurs whenever i try to enter an instance, for example, my main quest and the duty finder. My linkshells and free company also do work as well.

[wirewitch]

I just got two 90k errors in a row on Sargatana's and a whole mess of lag surrounding the spawning of a FATE at the Silver Bazzar in Thanalan.

And prior to this I got two 90k errors on Garuda as another FATE spawned nearby. This can't be a coincidence...