I was in que to login started at 458 made it to 43 got 90002 now 2002 - this sucks!

I was in que to login started at 458 made it to 43 got 90002 now 2002 - this sucks!
Going into the Waking Sands on Gilgamesh .::sad panda face::.
Same on Cerberus. 90002 followed by constant 2002
Why did we pay extra money for pre-order.. if we can't get in. If this didn't happen for the 2013 re-release then it would be different.. but come on SE you knew it was going to be busy.. ever hear of being Pro-Active?
Well of course it's the US and EU servers, Gotta get the JP servers up perfect first.
I'm having the same issue. Aether Data Center (Sargatanas). Hope this gets fixed very soon.
Last edited by Seffer; 06-21-2015 at 06:23 AM.
I resolved 2002 error by running the following in command prompt
ipconfig /flushdns
Looks like this may be related to a DNS caching error?
It is not a DNS caching error else all data center would not work for those getting the 2002 errors. This is purely a server side issue that the devs have already been working on. Everyone just needs to exercise some patience. I believe it is a domino effect that started with Balming. Supposedly it is the most popular server on Aether DC and the extensive login rush crashed it and then it trickled its way down.
And for the record, this is nothing compared to original launch and ARR launch.
Patience is a virtue.
I just was able to get back in.
Suggestion. Take your younger sibling for a walk, your niece/nephew, son/daughter. By the time you get back, you will be able to get back in.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.
Reply With Quote



