Error 90000 (90k) and others relating to it

[Donze]

Same issue on Diabolos. Servers are complete shit since shortly after 2.28 patch.

90k and massive duty server lag. Thought we learned better 7-8 months ago.

[Mawk]

Now im getting both the 90000 and the 2002 error. What can I do ?

[MoonAlo]

pathping 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

0 owner-PC
1
2
3 te-0-7-0-14-sur04.hayward.ca.sfba.comcast.net [68.85.190.177]
4 te-1-15-0-11-ar01.oakland.ca.sfba.comcast.net [68.86.143.102]
5 be-90-ar01.sfsutro.ca.sfba.comcast.net [68.85.155.14]
6 he-1-5-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.90.93]
7 pos-0-4-0-0-pe01.529bryant.ca.ibone.comcast.net [68.86.87.146]
8 ix-2-3-0-0.tcore1.PDI-Palo-Alto.as6453.net [66.198.127.17]
9 if-2-2.tcore2.PDI-Palo-Alto.as6453.net [66.198.127.2]
10 if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.144.58]
11 if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
12 66.198.96.58
13 * * *
Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0/ 100 = 0% |
3 8ms 0/ 100 = 0% 0/ 100 = 0% te-0-7-0-14-sur04.hayward.ca.sfba.
comcast.net [68.85.190.177]
0/ 100 = 0% |
4 10ms 0/ 100 = 0% 0/ 100 = 0% te-1-15-0-11-ar01.oakland.ca.sfba.
comcast.net [68.86.143.102]
0/ 100 = 0% |
5 13ms 0/ 100 = 0% 0/ 100 = 0% be-90-ar01.sfsutro.ca.sfba.comcast
.net [68.85.155.14]
0/ 100 = 0% |
6 14ms 0/ 100 = 0% 0/ 100 = 0% he-1-5-0-0-cr01.sanjose.ca.ibone.c
omcast.net [68.86.90.93]
0/ 100 = 0% |
7 16ms 0/ 100 = 0% 0/ 100 = 0% pos-0-4-0-0-pe01.529bryant.ca.ibon
e.comcast.net [68.86.87.146]
0/ 100 = 0% |
8 13ms 0/ 100 = 0% 0/ 100 = 0% ix-2-3-0-0.tcore1.PDI-Palo-Alto.as
6453.net [66.198.127.17]
0/ 100 = 0% |
9 12ms 0/ 100 = 0% 0/ 100 = 0% if-2-2.tcore2.PDI-Palo-Alto.as6453
.net [66.198.127.2]
0/ 100 = 0% |
10 64ms 0/ 100 = 0% 0/ 100 = 0% if-11-3.tcore2.CT8-Chicago.as6453.
net [66.198.144.58]
0/ 100 = 0% |
11 87ms 0/ 100 = 0% 0/ 100 = 0% if-3-2.tcore1.W6C-Montreal.as6453.
net [66.198.96.45]
95/ 100 = 95% |
12 86ms 95/ 100 = 95% 0/ 100 = 0% 66.198.96.58

Trace complete.

[Winelor]

this has been happening to me for about 24 hours mostly in the morning time for me but most of yall are getting 2 servers iam getting 3

1 8ms 0/ 100 = 0% 0/ 100 = 0% 10.34.160.1
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% COX-68-12-9-34-static.coxinet.net
[68.12.9.34]
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% COX-68-12-9-164-static.coxinet.net
[68.12.9.164]
0/ 100 = 0% |
4 19ms 0/ 100 = 0% 0/ 100 = 0% 68.1.2.111
0/ 100 = 0% |
5 16ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-32.ccr21.dfw03.atlas.cogen
tco.com [38.122.38.85]
0/ 100 = 0% |
6 26ms 0/ 100 = 0% 0/ 100 = 0% be2031.ccr21.dfw01.atlas.cogentco.
com [154.54.7.45]
0/ 100 = 0% |
7 36ms 0/ 100 = 0% 0/ 100 = 0% be2012.ccr21.mci01.atlas.cogentco.
com [154.54.2.113]
0/ 100 = 0% |
8 40ms 0/ 100 = 0% 0/ 100 = 0% be2156.ccr41.ord01.atlas.cogentco.
com [154.54.6.86]
0/ 100 = 0% |
9 59ms 0/ 100 = 0% 0/ 100 = 0% be2079.ccr21.yyz02.atlas.cogentco.
com [154.54.27.182]
0/ 100 = 0% |
10 57ms 0/ 100 = 0% 0/ 100 = 0% te0-0-2-0.rcr11.b011027-3.yyz02.at
las.cogentco.com [154.54.6.238]
0/ 100 = 0% |
11 53ms 0/ 100 = 0% 0/ 100 = 0% 38.122.70.182
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% ae21.cr6.mtl.iweb.com [67.205.127.
121]
0/ 100 = 0% |
13 --- 100/ 100 =100% 100/ 100 =100% ae0.cr5.mtl.iweb.com [184.107.1.61
]
0/ 100 = 0% |
14 --- 100/ 100 =100% 100/ 100 =100% te7-4.dr9.mtl.iweb.com [184.107.1.
110]
0/ 100 = 0% |
15 65ms 0/ 100 = 0% 0/ 100 = 0% 72.55.128.44
0/ 100 = 0% |
16 71ms 0/ 100 = 0% 0/ 100 = 0% 184.107.107.176

[DemonFury]

it is the data center and they know about it and they scheduled a maintenance for tonight instead of just doing an emergency one like they normally do now they make us wat 2 days through 90king every 2 minutes instead of just fixing the issue right away so we are essentially paying to get kicked offline every 2 minutes until they fix this nonsense which i believe should be credited to our accounts since we cannot do anything in game when we are getting kicked off for longer than we actually get to paly teh game..

[Burrmanchu]

it is the data center and they know about it and they scheduled a maintenance for tonight instead of just doing an emergency one like they normally do now they make us wat 2 days through 90king every 2 minutes instead of just fixing the issue right away so we are essentially paying to get kicked offline every 2 minutes until they fix this nonsense which i believe should be credited to our accounts since we cannot do anything in game when we are getting kicked off for longer than we actually get to paly teh game..

. <--- This is a period.

as to the first part of your statement.. is there anywhere where they have acknowledged the issue? or linked it to the maintenance officially? This is the problem I'm having with it this time.. It's been 2 days and not so much as a Dev post. I'm gonna go out on a limb and say all the statistical info people are spamming is nothing they don't already have (or care to have). It would be nice to know they give a shit though... Could at least throw us a bone.

[Surkai25]

Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Surkai25-PC.hsd1.co.comcast.net. [192.168.1.122]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% VAULT101 [192.168.1.1]
0/ 100 = 0% |
2 14ms 0/ 100 = 0% 0/ 100 = 0% 107.2.176.1
0/ 100 = 0% |
3 14ms 0/ 100 = 0% 0/ 100 = 0% te-9-6-ur02.englewood.co.denver.comcast.net [68.86.129.165]
0/ 100 = 0% |
4 13ms 0/ 100 = 0% 0/ 100 = 0% te-0-3-0-1-ar02.aurora.co.denver.comcast.net [68.86.128.9]
0/ 100 = 0% |
5 16ms 0/ 100 = 0% 0/ 100 = 0% te-0-1-0-4-cr01.chicago.il.ibone.comcast.net [68.86.95.201]
0/ 100 = 0% |
6 19ms 1/ 100 = 1% 1/ 100 = 1% xe-2-0-0-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.82.2]
0/ 100 = 0% |
7 14ms 0/ 100 = 0% 0/ 100 = 0% 173.167.58.162
0/ 100 = 0% |
8 38ms 0/ 100 = 0% 0/ 100 = 0% if-4-0-1-0.tcore1.CT8-Chicago.as6453.net [209.58.57.130]
0/ 100 = 0% |
9 39ms 0/ 100 = 0% 0/ 100 = 0% if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.1]
0/ 100 = 0% |
10 61ms 0/ 100 = 0% 0/ 100 = 0% if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% 66.198.96.58
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% te7-3.dr9.mtl.iweb.com [67.205.127.214]
0/ 100 = 0% |
13 60ms 0/ 100 = 0% 0/ 100 = 0% 72.55.128.44
0/ 100 = 0% |
14 62ms 0/ 100 = 0% 0/ 100 = 0% 184.107.107.176

Trace complete.

another drop in the confirmed problem bucket.

[Tryp]

The pathping is only proving that iweb's routers are configured to not respond to ping requests. If 100% of traffic through those hops was actually being dropped, it would be impossible to connect to 184.107.107.176 at all.

The results posted in this thread, if anything, prove that the path between us and the game are not the problem at all, unless there is something in the network at the destination preventing traffic from getting to the requested internal address.

For example, try running pathping to google.com, and you're just as likely to get a hop along the way that does not offer a response.

[DemonFury]

Tracing route to ffxiv.com [202.67.53.202]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 35 ms 51 ms 10 ms c-67-184-112-1.hsd1.il.comcast.net [67.184.112.1
]
3 13 ms 9 ms 9 ms te-0-5-0-12-sur03.chicago201.il.chicago.comcast.
net [68.86.118.65]
4 13 ms 11 ms 11 ms te-8-1-ur03.indianapolis.in.indiana.comcast.net
[68.86.184.57]
5 14 ms 16 ms 11 ms he-2-5-0-0-cr01.chicago.il.ibone.comcast.net [68
.86.91.101]
6 14 ms 14 ms 11 ms he-1-2-0-0-cr01.350ecermak.il.ibone.comcast.net
[68.86.88.26]
7 13 ms 11 ms 14 ms he-1-13-0-0-cr01.losangeles.ca.ibone.comcast.net
[68.86.86.2]
8 11 ms 13 ms 12 ms ae-26.r05.chcgil09.us.bb.gin.ntt.net [129.250.66
.65]
9 13 ms 41 ms 12 ms ae-6.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.2
4]
10 61 ms 62 ms 57 ms ae-5.r20.sttlwa01.us.bb.gin.ntt.net [129.250.3.1
90]
11 151 ms 175 ms 149 ms ae-6.r20.tokyjp05.jp.bb.gin.ntt.net [129.250.3.1
3]
12 140 ms 162 ms 146 ms ae-19.r24.tokyjp05.jp.bb.gin.ntt.net [129.250.6.
209]
13 144 ms 147 ms 207 ms ae-5.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.
170]
14 168 ms 161 ms 236 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.
146.94]
15 160 ms 149 ms 158 ms 219.117.144.66
16 163 ms 172 ms 156 ms 219.117.144.53
17 161 ms 170 ms 157 ms 219.117.146.141
18 172 ms 155 ms 158 ms 219.117.146.106
19 155 ms 169 ms 154 ms 202.67.53.202

[Caindris]

Same issue here on Ultros and I'm in Wyoming for what it's worth. PingPlotter is showing me that 4.69.153.86 is having massive packet loss - anywhere from 20-40% all the time. Other hops in level 3's network (Denver and Chicago 1 and 2) are having intermittent packet loss but nowhere on the level of the Montreal hop.

I'm sure Level 3 is well aware of this issue but it would be nice if SE would act as a go between so we can get some kind of update