2002

[Chewzer]

Actually, the problem just cleared itself up. A bunch of friends all just logged in at the same time who have been trying for hours.

[Skivvy]

I was also able to log in (and stay logged in!) about 20 minutes ago.

[Chewzer]

...but now I'm getting crazy bad lag and stuttering, which is highly unusual for me. Anybody else?

[Drakinor]

Yeah I'm getting the same thing. But the people I've been playing with keep saying their internet is fine. I already reset my router but it's still bad.

[asr32123]

Its still bad for me :/ I just played for about 30 mins, got kicked, and now can't get back on.

[EddPaz]

I can login now but after a few minutes the error 90000 appears.

[Raist]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\XXXX>tracert 199.91.189.26
Tracing route to 199.91.189.26 over a maximum of 30 hops

7 18 ms 17 ms 17 ms be4101.ccr21.sea02.atlas.cogentco.com [38.104.127.253]
8 39 ms 38 ms 39 ms be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.198]
9 49 ms 49 ms 47 ms be2126.ccr21.den01.atlas.cogentco.com [154.54.25.65]
10 59 ms 62 ms 60 ms be2129.mpd21.mci01.atlas.cogentco.com [154.54.26.114]
11 72 ms 73 ms 73 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
12 99 ms * 99 ms be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27.182]
13 106 ms 105 ms 105 ms be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30.206]
14 * 109 ms 109 ms 38.122.42.34
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 114 ms 111 ms * 199.91.189.26
19 110 ms * 111 ms 199.91.189.26

Trace complete.

This is a trace from my home to Goblin server. (Left the first 6 jumps out)

Posting this to see if it helps any.
I have the same issue as well.

Looks like more issues with the unholy alliance of Cogent Communications and PsiNet during the handoff into Ormuco (SE's ISP)... they all three have their dirty paw prints on that 38.122.42.34 address, and it looks like others are having issues at that same backbone. The big question is who will get off their butts to fix it.

No issues from Florence, SC getting in, but I've been re-routed along TATA now, so I'm coming in via a different backbone (66.198.96.50). Was on Cogentco last week, but TWC moved me... may have been because there were issues coming in through Cogent.

May be able to get some help if you forward those flaky traces to your ISP's Tier3 support. That's where I've been sending mine and they get me re-routed.

[Tygg]

Same issue here. NA Malboro server using the PS4.

[kaya_suzumiya]

the cause of the drop outs/90k is cogentco seeing as they have from anywhere 15%-60% packet loss on there hops. the issue isnt with servers but its been with cogentco network which u would see if u use winmtr to tracert to server and leave it on for couple hrs it will show u the packetloss so u can easily see problem. issue only effects na/eu servers because of being routed through the bad path/ bad hop which cogentco has

if u look at the 12th jump on the tracert pasted above u will see problem that jump as like 15-50% packet loss which is causing the problem

[Jethred]

I am also having trouble with the 38.122.42.34 address. Symptoms are the 90k / 2002, and now excessive stuttering lag. I'm on a college network, so I'm not sure what to do besides go to IT