Is the 2002 error fixed?

[Kryptoghost]

Where you in a queue for more than 5 minutes in the last 7 months? 2002 is related to the login server itself (not the queues for a realm server). When the login server gets too many people, it gets unstable. It's been like that since 2.0 release. It's like this every time there is an expansion release. We have large queues, some people get kicked mid queue. This time it worse than any before because of the large amount of people due to the wow exodus.

How long does this last after an expansion? i feel like i was playing during heavenward release and never experienced this? but other than that ive always been late to expansions.

[Itsgigglez]

How long does this last after an expansion? i feel like i was playing during heavenward release and never experienced this? but other than that ive always been late to expansions.

I've been around for all the launches so far (Except ARR). I have to say Stormblood and EW has been awful so far, but both for entirely different reasons.

Stormblood: Couldnt handle the load and no one could get into instances. (Ala: Rauban EX and Pipen Savage)

EW: Login Queue Ultimate and Login Screen Savage, where you get 2002'd, 4004'd, 3001'd and so on. But everything else in game is alright save for like one or two problems I had when the game imploded on itself and closed me to desktop.

But one thing has always been the same between all the Xpacks and its the login queue. I've had to wait in 3k+ queues before (without the 2002's), Idk whats so different this time around, maybe its all the new players wanting to play ontop of old players wanting to get in and play the new xpack so the login servers are overloaded.

This is the best answer I can give on MY experience with all the xpack launces.

[Jin-]

Had it only at launch couple of times. Zero times in 3+ days

[Darkstride]

See, that's curious because in the 7 months I've been playing prior to this "early access", I've never seen that error before. Now it's coming up persistently.

Clearly, they did something to break things.

The error occurs due to the data center queue maxing out. That's not a common occurrence normally.