Random 90k errors - Leviathan

The game will be playing just fine, and all of a sudden, everything stops, and I get the "unable to establish connection with the server" 900002 error. Has only been happening today, but the internet is working fine. Any ideas?

I am having this same issue on Midgardsomr. I have disconnected with this issue upwards of 6-10 times in the last 4 hours.

Myself and a friend on Leviathan have had the same issue today. It has happened to me four times. 90002 and 2002. My internet connection is fine, and I have run all the troubleshooting on it.

Same over here on Famfrit, it seems to commonly occur before a boss pull. It only started happening recently and has never been an issue up until recently, I don't get disconnected from other programs such as Skype when I experience one of these errors.

looks like the problems in the Ashburn/DC area earlier this week never cleared up...my ISP switched me over to Cogent (was on TATA's as6453 hops) and I'm now going down to Atlanta instead. Also no more bypass to Toronto--goes to Albany then straight into Montreal. Still get the odd hiccup here and there in Time Warner's localized segments with spikes breaking 100ms now and then (something we are still working on addressing), but otherwise responses are hovering around the 50ms mark and have smooth gameplay.

May be worth taking a look at your routes.

Code:

Tracing route to 199.91.189.30 over a maximum of 30 hops 1 1 ms <1 ms <1 ms LPTSRV [10.10.100.1] 2 34 ms 26 ms 38 ms cpe-75-176-160-1.sc.res.rr.com [75.176.160.1] 3 26 ms 29 ms 19 ms cpe-024-031-198-009.sc.res.rr.com [24.31.198.9] 4 17 ms 18 ms 18 ms 24.31.196.212 5 24 ms 24 ms 21 ms be33.chrcnctr01r.southeast.rr.com [24.93.64.182] 6 24 ms 26 ms 26 ms bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82] 7 25 ms 26 ms 26 ms 0.ae5.pr0.atl20.tbone.rr.com [107.14.19.99] 8 27 ms 38 ms 25 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109] 9 29 ms 26 ms 28 ms be2050.ccr41.atl01.atlas.cogentco.com [154.54.0.165] 10 34 ms 35 ms 34 ms be2168.ccr41.dca01.atlas.cogentco.com [154.54.31.94] 11 40 ms 41 ms 41 ms be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31.118] 12 42 ms 42 ms 44 ms be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.50] 13 49 ms 49 ms 50 ms be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17] 14 65 ms 64 ms 64 ms 38.122.42.34 15 46 ms 49 ms 48 ms 192.34.76.10 16 49 ms 47 ms 49 ms 199.91.189.242 17 48 ms 50 ms 47 ms 199.91.189.30 Ping statistics for 199.91.189.30: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 46ms, Maximum = 52ms, Average = 48ms

**note these were taken across wireless too while streaming video to a Roku downstairs...which has it's own flakiness issues, and it is still smooth

Same thing is happening to me as well over on Exodus. I connect, see people stopping and running, stopping and running, then eventually "Error 90002".
I can get on for maybe...2-3 minutes before i'm kicked.

Quote:

Originally Posted by Raist

looks like the problems in the Ashburn/DC area earlier this week never cleared up...my ISP switched me over to Cogent (was on TATA's as6453 hops) and I'm now going down to Atlanta instead. Also no more bypass to Toronto--goes to Albany then straight into Montreal. Still get the odd hiccup here and there in Time Warner's localized segments with spikes breaking 100ms now and then (something we are still working on addressing), but otherwise responses are hovering around the 50ms mark and have smooth gameplay.

May be worth taking a look at your routes.

Code:

Tracing route to 199.91.189.30 over a maximum of 30 hops 1 1 ms <1 ms <1 ms LPTSRV [10.10.100.1] 2 34 ms 26 ms 38 ms cpe-75-176-160-1.sc.res.rr.com [75.176.160.1] 3 26 ms 29 ms 19 ms cpe-024-031-198-009.sc.res.rr.com [24.31.198.9] 4 17 ms 18 ms 18 ms 24.31.196.212 5 24 ms 24 ms 21 ms be33.chrcnctr01r.southeast.rr.com [24.93.64.182] 6 24 ms 26 ms 26 ms bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82] 7 25 ms 26 ms 26 ms 0.ae5.pr0.atl20.tbone.rr.com [107.14.19.99] 8 27 ms 38 ms 25 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109] 9 29 ms 26 ms 28 ms be2050.ccr41.atl01.atlas.cogentco.com [154.54.0.165] 10 34 ms 35 ms 34 ms be2168.ccr41.dca01.atlas.cogentco.com [154.54.31.94] 11 40 ms 41 ms 41 ms be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31.118] 12 42 ms 42 ms 44 ms be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.50] 13 49 ms 49 ms 50 ms be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17] 14 65 ms 64 ms 64 ms 38.122.42.34 15 46 ms 49 ms 48 ms 192.34.76.10 16 49 ms 47 ms 49 ms 199.91.189.242 17 48 ms 50 ms 47 ms 199.91.189.30 Ping statistics for 199.91.189.30: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 46ms, Maximum = 52ms, Average = 48ms

**note these were taken across wireless too while streaming video to a Roku downstairs...which has it's own flakiness issues, and it is still smooth

Hello Raist! You seem to be a bit of an expert on the subject judging from your other posts on this particular topic, I've of course ran a trace route but they each come back as request timed out, except for one or two. But what baffles me is that I don't get disconnected from other services or games in the same way. The only way I'll be booted off another game online is because my internet legitimately went down. If you could give any insight to this I'd greatly appreciate it, thank you and take care.

A common cause for 90k error is old routers. Routers have a 2 year life cycle after which they start dropping the connection long enough for a dc.

Confirm it is not the router by using another one or by connecting computer/modem for about the time you would need to disconnect.

Just got a brand new router put in so all is good from my area. Must be the weird congestion from earlier. Just wondered if it was a data center issue.