lobby server error

last Thursday I tried to Log in. I got passed the log in screen but when went to start the game it gave me a lobby server error 2002. I get the same every time I try to log in now. I have tried powering down the computer, and reconnecting to the router. Still can't get in. Can you help me.

Quote:

---

Originally Posted by amovita9

last Thursday I tried to Log in. I got passed the log in screen but when went to start the game it gave me a lobby server error 2002. I get the same every time I try to log in now. I have tried powering down the computer, and reconnecting to the router. Still can't get in. Can you help me.

---

I've been having the same issues since this afternoon. I'm probably going to check another data center to see if its just the one I'm on or not.

Just got a 90k error followed by this error nonstop on Brynhildr server.

Same.. 90k followed by lobby error repeatedly...

Fix the game.

Same

/10char

changed data centers, no problem (JP data center)
went back to my data center, took 5 years but got back in.

Same thing just happened to me. First got kicked out and when I tried to log back in, Error 2002.

at 7:41 pm on Gilgamesh, I was kicked out of the gamed and have received Lobby 2002 Errors since (I have rebooted my machine twice). Would appreciate if someone would take a look at the issue.

Thanks

about 15 minutes ago on Coeurl, booted straight out of Darkhold after massive lag spikes

tried several times to log back in, no success

about 15mins ago me and a friend on faerie got booted off...now its stuck on the error to log in screen..

Happened again after getting back in- Coil run. This is very aggravating.

Again, 90k'd while waiting in que to do the dungeon i was so rudely disconnected from, after having to wait at least 20 minutes to log back into the game.

I guess I don't get to play the game tonight, since the server (and lobby) are being flat out stupid.

Same thing happening on Diabolos server.

Non-stop disconnects while playing Crystal Tower on Bahamut server due to disconnection to the lobby server. Finally reconnected and kicked off from the CT instance...