Error 900002

[Stokely93]

Constantly getting this error message a few mins after i log in. It's beginning to become really frustrating, i can't play at the moment tried everything to try and stop the error but nothing works

[Nischa]

Replying here because I am getting the exact same issue atm. I have been playing all day without problems and now I get this error 90002 every few minutes or so. Checked my internet connection but there don't seem to be any problems on my end. It's quite impossible to play the game decently atm. I already filed a bug report as well. Btw, we're playing on the same world, coincidence?

[Livilda]

I'm getting the same issue here, Balmung. Happened right after I finished Keeper of the Lake.

[Gaiko]

I got booted from ST run a few minutes ago, tried to relogin and got stuck in the loading screen, i heard the sounds on the backgroud (like the party formation sound) and after 30 seconds i got dced again with the same error, ran all day today without this and now im pooped.

[Raist]

Internet is knackered up pretty bad in general across some of the main corridors leading to Montreal. May be a contributing factor for some of you guys. May be worth checking to see if you (or your ISP) can spot anything out of sorts along your routes to SE's ISP in Canada (Ormuco).

neolobby02.ffxiv.com
neolobby04.ffxiv.com
neolobby06.ffxiv.com

Those are the current DNS names for the lobby serves in Canada (Japan servers are currently using 1, 3, and 5 in their names).

To get a sort of visual of things, here are some images I linked to in another post the other night. You can see similar maps, statistics, and support posts for a long list of web services and ISP's at the main site: https://downdetector.com/companies. The images get updated periodically throughout the day, so you may see them change a bit after a while. You may notice patterns forming amongst them... likely because they are running into problems along the same routing points:


Source: https://downdetector.com/status/time-warner-cable


https://downdetector.com/status/att


https://downdetector.com/status/comcast-xfinity


https://downdetector.com/status/verizon-communications


https://downdetector.com/status/netflix


https://downdetector.com/status/playstation-network


https://downdetector.com/status/xbox-live


https://downdetector.com/status/call-of-duty

[featal]

I'm posting here because I am having the same problem. I never had a problem until this newest patch. I was curious if anyone had found a solution to this problem or is there not really anything we can do about it?

[Godric-Artemis]

same as everyone here, got 2002 too on ragnarok

[Stokely93]

Interesting to see i'm not the only one with these issues. Seriously annoying as it has become unplayable

[Raist]

Aside from the usual odd bits of lag spiking I see crop up in specific regions, haven't seen anything out of the ordinary. We have been wrangling with a 20-40ms injection that happens getting through our gateways to Columbia, then the odd spike up to around 180-200 that show up in different regions from time to time: Atlanta, Ashburne/DC, Chicago, New Jersey, or New York. So long as it is only one section of the route having the high lag spikes, it hardly impacts game play... but when they start stacking you can really feel it. But, it hasn't been bad enough to cause wide scale disconnects in a really long time... like, since almost a year ago when I got Tier3 involved and they fixed our local CMTS and other overloaded gateway problems (they split us up onto neighboring nodes).

Midgardsormr
Time Warner Cable/Road Runner service (15/1, internet only service--no broadcast TV)
from Florence, South Carolina

Currently goes through Columbia then either Charlotte or Raleigh (sometimes both), then to Atlanta where I get switched to Cogentco out of Atlanta to get to Montreal. For the most part, things are pretty tight until I hit Atlanta. If it isn't an issue getting out of the gate to Columbia, it is always something happening between the hand-off to Cogentco in Atlanta and the hand-off to Ormuco in Montreal.

Just saying... you may want to look at your routes. There may be something there your ISP needs to address. It may not be the end-all fix, but if you are hitting high enough congestion along the way it can compound a problem that might otherwise be recoverable by the TCP/IP protocol the game is using. Here's a recent trace I ran... aside from local gateway weirdness, it's solid and so is my game play for the most part (until about 10:00 or so, starts lagging as we come through the north east--can ping some hops directly and get bad spikes and occasional packet loss, a strong indication of congestion overloading those hops):

C:\Windows\System32>tracert 199.91.189.30

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    41 ms    19 ms    24 ms  cpe-075-176-160-001.sc.res.rr.com [75.176.160.1]
  3    15 ms    24 ms    17 ms  cpe-024-031-198-009.sc.res.rr.com [24.31.198.9]
  4    20 ms    20 ms    20 ms  24.31.196.212
  5    23 ms    34 ms    22 ms  be33.chrcnctr01r.southeast.rr.com [24.93.64.182]
  6    30 ms    29 ms    31 ms  bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]
  7    26 ms    24 ms    28 ms  107.14.19.99
  8    26 ms    27 ms    28 ms  te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
  9    27 ms    27 ms    25 ms  be2050.ccr41.atl01.atlas.cogentco.com [154.54.0.165]
 10    32 ms    34 ms    37 ms  be2168.ccr21.dca01.atlas.cogentco.com [154.54.31.94]
 11    39 ms    40 ms    41 ms  be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31.118]
 12    45 ms    42 ms    45 ms  be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.50]
 13    50 ms    49 ms    51 ms  be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
 14    64 ms    65 ms    66 ms  38.122.42.34
 15    47 ms    49 ms    50 ms  192.34.76.10
 16    47 ms    51 ms    48 ms  199.91.189.242
 17    48 ms    48 ms    49 ms  199.91.189.30

Trace complete.

[BlaiseArath]

Constantly getting this error message a few mins after i log in. It's beginning to become really frustrating, i can't play at the moment tried everything to try and stop the error but nothing works

i was getting this quite often in WoD last night... ruined the entire experience because i was DCing almost the entire time, with lots of latency too