-
Random d/c into 3001
So I was just out mining, minding my own business, when I'm 90k'd off.
Sighing, I reconnect to find out what kind of monstrous queue awaits me and all I get is:
"The world is currently full. Please wait until an opening is available and try again."
Like.............. that's what a queue is for. Am I just supposed to know when that is?
Guys I get it.. there are server capacity problems you weren't able to solve ahead of EW's launch. But we're going on a week of this now. It's getting real old, real fast if you know what I'm saying.
-
In queue. DC'd. 3001. BS.
-
Same here, waited all morning, reached place 28 in the queue -> 3001.
Haven't been able to join the queue at all since.
Some hardware must have just fell over if we all got 3001 at the same time...I see Xeno is Cactuar as well.
Imagine if software sales had to adhere to the same consumer protection laws as TVs.
-
+1
I am completely unable to even queue up for Cactuar because of 3001 errors. Is there going to be a maintenance to fix these 3001 errors?
-
Yep, I've got the same problem on Cactuar. Was in queue for about 2 hours, got a loading screen as if it was logging in.
Then I'm hit with some 10k error and booted to the title screen.
Now every time I try to rejoin the queue, I get a 3001 error.
Was able to create a new character on one of the JP servers, and logged in with out any problems (no queue at all).
-
Primal-Ultros here. 3001 as well. I also noticed that NA in general is blocked off completely for character creation atm. Hopefully, some communication comes down the line soon
https://na.finalfantasyxiv.com/lodestone/worldstatus/
-
Same thing on Gilgamesh. Cannot join the queue. 3001 error.
-
I've made it into Q now but I have been stuck a 673 for over 30 minutes. Which was also my starting position when I was able to queue.
-
was in game. 90002 error. 3001 trying to rejoin in midgardsormr
-
Got through the Que... then got slapped with the 3001 error... Not even letting me get back in que no Leviathan...
-
Queued up for a couple hours and made it all the way to the zone loading screen when I was 3001'd and now I can't even get in the queue at all again. "The world is currently full"
-
Primal - Leviathan is borked too. 3 hours in queue to get to like 84, then 10105 error, then 3001s ever since. I can't even get back into queue, just 3001s.
-
Same here, would be nice to get an official response or update
-
Must be something going on with primal right now. I'm Hyperion. DC'd and now just getting 3001
-
I queued for 2.5 hours starting at 2580 and got in. Played a little over an hour and then kicked out with this 3001. After several 3001 trying to get back in, I'm now 787 in queue so there must have been a DDOS for me to get queue number this low. Still probably another hour of waiting to get back in.
-
Well, back in queue now at 1149. Glad I spent 3 hours waiting to hit right as a massive server problem that still hasn't been announced or acknowledged hit, wasting another hour.
Seriously, if I get on and those AFKers are in Limsa on Leviathan (SeeD's naked cowboy catboi and those dang male roes who all line up), I'm gonna scream. XD
-
I've been trying to get back in for the past 40 mins and still can't even queue - I HAVE seen the zone loading screen (with the moogle) twice, that made me think I was about to get in, but instead of loading the world I get 3001'd. I wish I could just queue so I don't have to keep babysitting the computer..
-
Well thought I got lucky with a 787 queue position but guess not. It hasn't moved at all in 20 minutes...
Edit: Still no movement in queue in 40min. Appears frozen....how wonderful.
-
surprise surprise 3001 for over an hour, and once queue finally opens back up I go from 4k to 1500 over the course of 2 hours just to get another 3001. Guess NA is having some severe issues right now if I can't even log in with my character in Midgardsormr.