Leviathan Server Queue Broken?

I've been now stuck at 811 after DC'ing out of the game from this morning. I've quit the game fully now 3 times, and switched data centers multiple times only to keep "my spot" in the queue at 811?

Anyone else on Leviathan having the same issue? Or is this precursor to 3001 issues?

Balmung here:

I was getting the 3001 error, and I've been stuck in an 893 person queue for over 40 minutes without the number moving at all.

No response from SE whatsoever. Login servers have been broken all day. No fix in sight.

I've been stuck at #124 in the que for Hyperion for almost an hour as well

I don't think the issue is the queues this time. I think people have learned to bypass the auto-logout functions and are now completely closing off the servers for other players. There's really nothing else that would explain the queue not moving at all.

Greetings fellow Eorzean,

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

https://na.finalfantasyxiv.com/lodes...9cad782363f25b

We appreciate your patience and understanding regarding this matter.

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

When will you actually fix the afk bypass?? Atleast 20 friends of mine have never logged out, I watched as the que got slower and slower the past 2 days. Then what do you know it's too slow yesterday to the point of 6 2002's which I did not recover from by the final one my spot was gone. Today? 3001 literally maxed out ques mid day because everyone refuses to log out along with your inability to handle the amount of people flooding in. I'll join the afk scripters the next time I get in and contribute to the issue if it's the only way to play the game. And I hate that, but until you fix it your servers will be maxed out for the next month or so.

We're having the same 3001 error problem on Gilgamesh

Cactaur here, same issue. Got to 40 in Queue, 3001'd out and now can't queue again. Just gives the error that the World is full. (isn't the world being full what the queue is *for*?)

Same on Cactuar. Couldn't get in at all for a hal fhour. Then got the queue at 1451, where it didn't budget at all until I got booted with a 2002. Got back in adn the queue is over 3000, and hasn't moved at all in 20 minutes.

The queue flat out not moving like this is baffling. Yesterady it would go down occasionally, but this is just totally stuck.

Quote:

---

Originally Posted by Tridus

Same on Cactuar. Couldn't get in at all for a hal fhour. Then got the queue at 1451, where it didn't budget at all until I got booted with a 2002. Got back in adn the queue is over 3000, and hasn't moved at all in 20 minutes.

The queue flat out not moving like this is baffling. Yesterady it would go down occasionally, but this is just totally stuck.

---

Pretty much the same thing here...sat in a 992 queue but it never moved, then 3001 out only to log back into a 3062 queue...and again never moved until I was hit with the 2002 error. Why am I paying for this "experience"?

Then got booted while in the queue with 3001 and keep getting 3001 when trying to get back in, despite being in the queue a minute before.

This is worse than it was before the changes today.