90000, 3 minutes of 3102, 90000, and 1015 in a row.

[Bluevann]

Anyone else been experiencing this? This is the second time it happens to me in 2 days, though I've been getting 90000 alone several times since 2.1 already, whereas I wouldn't never get it before unless it was my router messing up (and this time, it isn't cause I fixed it).

I was FATEing in Costa del Sol when I got the first 90000 today. After two minutes of 3102, it took me to the loading screen (without popping up the queue log), and before it'd load up I got 90000 again. I repeat the log in, and the same happens again, this time getting error 1015. At the last attempt I finally get in, WITH the queue window popping. I wonder if the fact that the first two errors occurred when there was no Log In Queue pop up is just a coincidence, or has to do with the error.

[NeruMew]

The numbers sound fun!

(not any more than before, I have not been getting them... just a couple of randoms 90k, but they stopped... they never were usual for me)

I wonder why some people get 90ked all the time... Is it package loss in a bad connection?

off topic again: /wave fellow Balmung'er!

edit: I doubt the queue had anything to do with this. More likely was the server being unstable at the moment for whatever reason. It would be nice to have more light on this topic though, so we can know why we are getting these errors.

[Jennika]

I hardly ever have problems like that. I wonder if the problem is with certain ISPs?

[LaralnKornera]

There was one night where a friend of mine, someone else on the server, and myself were constantly getting 90k and all 3 of us have the same ISP. After a while it fixed itself, so I think it might of been a fault on the ISP at the time not connecting right to some services rather then it being the fault of SE's server since everyone else was playing perfectly fine.

[Bluevann]

I doubt the queue had anything to do with this. More likely was the server being unstable at the moment for whatever reason. It would be nice to have more light on this topic though, so we can know why we are getting these errors.

Hello to you too!

It wasn't just the queue log not popping what aroused my suspicions. The lobby server has been acting weird since 2.1 (See all the "29,593 players in queue" or "-49,429 players in queue" reports). I think something was messed up when the patch was implemented. I hope SE is working on it >_<

[NeruMew]

Hello to you too!

It wasn't just the queue log not popping what aroused my suspicions. The lobby server has been acting weird since 2.1 (See all the "29,593 players in queue" or "-49,429 players in queue" reports). I think something was messed up when the patch was implemented. I hope SE is working on it >_<

Yeah that's funny, I wonder if it's how many people are online in the server, or in the "datacenter" division, or what... xDDD

But yeah I still don't think that caused it. x_x

[Teon]

It's SE fault since the last servers' update. They implemented new hardware.
Except the connection between them and us sucks. This 90k crap happens on random victims on every single raid (8 men) content ingame.
I experienced it on every single raid i joined at least once.
It's fun (but rarer) when happens on CT and 23 players have to wait one single guy relogging, it happened on my last CT run when we lost the tank.
Priceless when the MT suddendly disappear and the party wipe haha
This game is freefalling , seriously. Total unplayable crap.