Still getting CONSTANT 90k errors

[FayyeValentine]

The title says it all. Getting 90k errors every 8-10 minutes. It's heartbreaking to see a company through such an issue that thousands upon thousands of people are having as "resolved" simply because we can log back in afterwards...

We still have to wait for it to kick us from the server before logging back in, and in my case, 90% of the time, im booted from my ST run, or instance, just because i was offline.

This issue is NOT resolved. It's NOT the player ISP.

Join me brethren and post your story!

[PEANUT]

Yea, I have been getting logged out with an Error 90000 message every 2 minutes for the past half hour. Not sure what's causing it, if it's the server or my internet connection?(Although my internet seems perfectly fine). Just figured I'd post and let you know!

[Beech]

yeah, having very frequent error 90000 disconnects from Famfrit server.... it's happening randomly and within every 10 mins or so.... mostly have noticed that it's more prominent during westcoast peak periods, but it's not specific or consistent other than the game is virtually unplayable... fight encounters will just freeze (i can still cast stuff client side) and then the "you have been disconnected from the server error 90000 occurs, then the 2002, and sometimes 3102 upon which when one of those happens the game just completely exits and closes. crashes?
Anyways, has been only really happening the last month or so,,, never been haing much problems til the past 3 weeks or so.... not sure what's going on, but i can't be a dependable party member with this crap happening for sure. anyone have any idea what's going on? i'm not alone i can see

[Lawlite5]

I have been having the same issue for the past two weeks, I have taken several suggestions regarding my internet that may help the situation which include setting up a vpn, forwarding the ports, changing routers, calling my isp to check. I have concluded that the issue is not me as many people have told me. This error is something that has been happening to a lot of people, and honestly I was planning on getting a subscription after my free days were up, but if this keeps happening, count me out. This shouldn't be happening at all to anyone

[Kiara1]

Yeah its crazy how they still havent fixed these things. It was laggy when I first started playing and its beeen on and off for 6 months. To the guy above me^ I wouldnt recommend you to get a subscription this games maintenance and supoort and servers are really bad. The only reason I keep playing is the friends ive met

[PEANUT]

Started happening again to me today just a short while ago. My internet connection is working perfectly fine. Maybe it has something to do with my ping to the server I use? Not sure, any help would be greatly appreciated. However Error 90000 which I keep getting could be anything which is the problem because, I don't know what specifically is causing it, so I can't fix it :\

[Raist]

In many (if not most) cases it is an issue occurring in route to the servers. Your local connection (what gets checked when you call in or a tech comes on site) may be perfectly fine, but that is not likely where the problem is. It is usually out at the pole, down the street... in another city, state, or even country. By default, there can be as many as 62 hops between your system and SE's servers. Every one of those is a potential point of failure.

It may be worth running some tracerts to your server or at least your lobby server to see if there is anything erratic along your route that your ISP needs to look at. Here are the registered DNS names for the lobby servers if you want to use them. Half are in Canada (even numbers), the others in Japan (odd numbers):

neolobby01.ffxiv.com
neolobby02.ffxiv.com
neolobby03.ffxiv.com
neolobby04.ffxiv.com
neolobby05.ffxiv.com
neolobby06.ffxiv.com

Most the time it winds up being an issue between your ISP's peering hand-off to a Tier1 provider, somewhere in that Tier1's own network, or during the hand-off from them into SE's ISP (Ormuco). This CAN be remedied by your ISP either by them reinforcing their peering agreement with that Tier1, or switching you to a different Tier1 provider. Nearly ALL of them have agreements with the big 3 in North America (Level3, TATA, Cogent). Lately, Level3 seems to be the one having the most trouble meeting the demand on their networks.

Important point that needs to be understood, in case some are not aware of just how the internet works. You do NOT have a direct connection to SE, by the way. Your ISP carries you part of the way, then a third party (sometimes even a 4th or 5th) will carry you a large portion of the way (like across the US and into Canada), and then you get handed off to SE's ISP. Your "internet connection" that is getting tested when you call in is your local node---they are in no way checking the complex web of connections that you traverse across the internet to get to this specific server. Note that each site you go to can have a vastly different path at certain portions of your route, so testing against a benchmark site or another game is NOT the same as testing against any of the servers connected to this game. Hence, you need to run a test against an actual server that is used for this game.

If you find something in the traces, forward your findings to your ISP's Tier3 Support for escalation. The help-desk and on-site tech's can't really do anything about this--you NEED to get Tier3 involved as they are the ones that can get the proper people to investigate any potential issues concerning your specific route. But, you will need to provide them the specific data they need to get involved--the bulk of that will be covered in your tracert results.

For a sort of visual of the path, here is the one I am currently using to my actual game server. This is the IP address my client actually communicates with when I am playing. Notice how the ends of the names are similar in groups along the path. That is because I am being handed off to a different company's network along the route. Note the last hop in the TWC/rr.com network where I have an asterisk. This is typically where I start running into trouble--around the hand-off into their peering partner that is taking me from the DC/VA area and up into Canada (it periodically stalls like it did here, and I get shot off to an absurd region's server (this one is reserved for use out west) before heading forward up the East Coast towards Canada). I live in Florence, South Carolina... when I call my local office or even the help desk (which is Tier1), they can't diagnose this as it is further up the chain then they are able to investigate. This calls for Tier3 or higher to address.

Tracing route to 199.91.189.30 over a maximum of 30 hops

  0  MJ14336 [10.10.100.2]
  1  LPTSRV [10.10.100.1]
  2  cpe-066-026-112-001.sc.res.rr.com [66.26.112.1]
  3  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
  5  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
  6  107.14.19.20
  7     *     ae-4-0.a0.lax91.tbone.rr.com [66.109.1.113]
  8  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  9  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
 10  64.86.85.1
 11  if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
 12  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 13  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 14  66.198.96.50
 15  192.34.76.2
 16  199.91.189.234
 17  199.91.189.30

[iRawrTeddyBear]

In many (if not most) cases it is an issue occurring in route to the servers. Your local connection (what gets checked when you call in or a tech comes on site) may be perfectly fine, but that is not likely where the problem is. It is usually out at the pole, down the street... in another city, state, or even country. By default, there can be as many as 62 hops between your system and SE's servers. Every one of those is a potential point of failure.

It may be worth running some tracerts to your server or at least your lobby server to see if there is anything erratic along your route that your ISP needs to look at. Here are the registered DNS names for the lobby servers if you want to use them. Half are in Canada (even numbers), the others in Japan (odd numbers):

neolobby01.ffxiv.com
neolobby02.ffxiv.com
neolobby03.ffxiv.com
neolobby04.ffxiv.com
neolobby05.ffxiv.com
neolobby06.ffxiv.com

Most the time it winds up being an issue between your ISP's peering hand-off to a Tier1 provider, somewhere in that Tier1's own network, or during the hand-off from them into SE's ISP (Ormuco). This CAN be remedied by your ISP either by them reinforcing their peering agreement with that Tier1, or switching you to a different Tier1 provider. Nearly ALL of them have agreements with the big 3 in North America (Level3, TATA, Cogent). Lately, Level3 seems to be the one having the most trouble meeting the demand on their networks.

Important point that needs to be understood, in case some are not aware of just how the internet works. You do NOT have a direct connection to SE, by the way. Your ISP carries you part of the way, then a third party (sometimes even a 4th or 5th) will carry you a large portion of the way (like across the US and into Canada), and then you get handed off to SE's ISP. Your "internet connection" that is getting tested when you call in is your local node---they are in no way checking the complex web of connections that you traverse across the internet to get to this specific server. Note that each site you go to can have a vastly different path at certain portions of your route, so testing against a benchmark site or another game is NOT the same as testing against any of the servers connected to this game. Hence, you need to run a test against an actual server that is used for this game.

If you find something in the traces, forward your findings to your ISP's Tier3 Support for escalation. The help-desk and on-site tech's can't really do anything about this--you NEED to get Tier3 involved as they are the ones that can get the proper people to investigate any potential issues concerning your specific route. But, you will need to provide them the specific data they need to get involved--the bulk of that will be covered in your tracert results.

For a sort of visual of the path, here is the one I am currently using to my actual game server. This is the IP address my client actually communicates with when I am playing. Notice how the ends of the names are similar in groups along the path. That is because I am being handed off to a different company's network along the route. Note the last hop in the TWC/rr.com network where I have an asterisk. This is typically where I start running into trouble--around the hand-off into their peering partner that is taking me from the DC/VA area and up into Canada (it periodically stalls like it did here, and I get shot off to an absurd region's server (this one is reserved for use out west) before heading forward up the East Coast towards Canada). I live in Florence, South Carolina... when I call my local office or even the help desk (which is Tier1), they can't diagnose this as it is further up the chain then they are able to investigate. This calls for Tier3 or higher to address.

Tracing route to 199.91.189.30 over a maximum of 30 hops

  0  MJ14336 [10.10.100.2]
  1  LPTSRV [10.10.100.1]
  2  cpe-066-026-112-001.sc.res.rr.com [66.26.112.1]
  3  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
  5  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
  6  107.14.19.20
  7     *     ae-4-0.a0.lax91.tbone.rr.com [66.109.1.113]
  8  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  9  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
 10  64.86.85.1
 11  if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
 12  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 13  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 14  66.198.96.50
 15  192.34.76.2
 16  199.91.189.234
 17  199.91.189.30

I don't mean to be rude but this is the same response us that have this problem get all the time and quite frankly i don't understand a bit of what you're saying. But what i gather. we have to call tier 3 tech support? so the thousands of players need to all do this complex thing to take to someone else to get it resolved. There is nothing that square can do at all to rectify any of this. for a system that they set up that is obviously faulty to a fail

[Yimiko]

Balmung server, I've been getting disconnected frequently enough that I spend more time waiting for my character to actually get booted offline than I do in game. I'm not sure if my reply to "welcome back" even gets through.

[Raist]

I don't mean to be rude but this is the same response us that have this problem get all the time and quite frankly i don't understand a bit of what you're saying. But what i gather. we have to call tier 3 tech support? so the thousands of players need to all do this complex thing to take to someone else to get it resolved. There is nothing that square can do at all to rectify any of this. for a system that they set up that is obviously faulty to a fail

SE has nothing to do with the infrastructure and network policies put in place by the long list of universities, governments, and private ISP's that have built the massive web of networks over the last 50-60 years. That is all managed by those respective entities. SE can really only reasonably be expected to directly address issues linked to things on their end or their ISP's end after we get handed off into those networks. That would be the last 3 or 4 hops in most cases. Everything else branches out from your devices, to your ISP's devices, then their partner's devices, and so on until it gets to Ormuco, who is SE's ISP.

This has been going on for decades... and for decades the ISP's have gotten away with shoddy maintenance on their networks and agreements with all those involved in providing interconnectivity between the disparate networks that make up the internet. Because their subscribers have been none the wiser about what is going on... they don't understand where the problems stem from, and have continually blamed the wrong people. And the ones actually responsible have been laughing all the way to the bank. For example, back in the fall I managed to track down some details about our CMTS here, and the hardware was from around 2001 and not even DOCSIS 2.0 compliant---but they were pushing 3.0 level plans that required 8 channel DS bonding on hardware that only supported up to 6 but was only giving out 4--and then they started pushing towards the new 3.1 standard that puts even more channels into play. I made a big stink about it through their forums and support chain, and suddenly I was taken off that gateway and sent to an entirely different city all-together and my latency was reduced by nearly half.

So... yes. If you want your internet issues to get cleaned up, you need to lean on your ISP. They are the ones that dictate where your packets get handed off to on the way to their destination. It's not Microsoft, Blizzard, or SE... but your ISP's routing/peering/transit policies manipulating your path to those endpoints.