Quote Originally Posted by LegendWait View Post
I got 90006 right at the moment the maintenance started and I was doing an expert roulette. Dont know why that happened since I was already in an instance duty
Being in an instanced duty I believe does not matter. Before acquiring a vpn I would get kicked from duties no matter what content I was in, given this was when the player volume was slightly lower so even with a 500 person queue that just meant a few minutes maybe even seconds in a queue before getting back into the duty. Though I wished there were a system in place for priority queue for those in an instanced duty as to not get a penalty due to ntt nodes not handling traffic properly or the servers buckling under the weight of server load. I am sorry you got booted from your duty.

Even with a vpn now, the issues are all back from a few months back without the vpn and I am wondering if it was not the servers all along.

After maintenance I did notice my position in queue being saved, but unsure if others are experience this as well. I logged in early morning 8am est got booted by 90006 error logged back in waited an hour in the small 500 something queue to finish my cut scene when picking up sage. Went to attempt to warm up in palace of the dead because I didn't want to get booted from a duty and was booted during the second floor attempted to log back but 1500 in queue and I knew it would be pointless.

So.....I attempted anyway for science and found out around 500 in increments that each 500 is about an hour of wait time. I started in queue at 3pm est #2169 ended after two disconnects at around 5:47pm est.

This could just be placebo but the queue wait time is way longer than it use to be. Before 500 in queue meant only a few minutes in queue where now it is guaranteed to be an hour. I don't know if it just a number reporting wrongly or something else, but it is just a strange something I noticed.