Quote Originally Posted by VegaNovus View Post
I've not experienced these server problems?

Do you assume that because it affects you and other posters in here that it affects EVERYBODY?

No.


I'd just like to point out in this particular topic that 90002 is a client disconnect error - this means that your client closed the connection because of a local network failure.

Now, this could be your ISP.
Anybody with 90002 error, I would recommend rebooting your router, switch from wifi to wired and/or calling your ISP.

Don't be such an SE apologist, it's not an issue on our end, there's too many different routers and ISPs affected for that. It's SE's problem and one they've refused to acknowledge never mind fix.

I've had this issue since 3.2's launch and I've sent tickets (Which got ignored, not even a single automated response) and I've posted in the correct threads to no avail. There's no SE presence on the issue, there's been no updates and SE are leaving people in the dark because as long as they get out sub money then they don't care. Anybody suffering this issue needs to unsubscribe and send a message to SE that this is unacceptable because they won't care until it affects their profits.

SE's customer service is the worst I've ever seen. It's basically nonexistent.