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!
http://www.pingtest.net/result/103937412.png
http://www.speedtest.net/result/3685692232.png
Still getting CONSTANT 90k errors
Printable View
-
08-13-2014, 10:32 AMFayyeValentineStill getting CONSTANT 90k errors
-
08-13-2014, 11:44 AMPEANUT
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!
-
08-13-2014, 01:17 PMBeech
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 -
08-13-2014, 04:56 PMLawlite5
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
-
08-13-2014, 05:10 PMKiara1
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
-
08-14-2014, 06:25 AMPEANUT
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 :\
-
08-14-2014, 10:33 AMRaist
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.
Code: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
-
08-15-2014, 11:11 AMiRawrTeddyBearI 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 failQuote:
Originally Posted by Raist
-
08-15-2014, 12:20 PMYimiko
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.
-
08-15-2014, 01:15 PMRaistSE 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.Quote:
Originally Posted by iRawrTeddyBear
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. -
08-16-2014, 09:36 AMPEANUT
Raist! Thank you very much for your advise and information. I am STILL getting dc'ed with an Error 90000 all the time. I called my ISP Tier 1 and of course like you said, they couldn't help me much, but he did advise me even before I read your post on using a tracert to find out where I'm getting latency issues. Here is a post of my tracert, it seems my issue is constantly around #5. I have no idea what or where it is or how I can fix it. I will call up my ISP again and try and speak to a Tier 3 person to help, but in the meantime could I have your opinion or any other advise you can give me, because now I pretty much can't even play because it happens to frequently, and it saddens me because I love this game :"(
Also, this started happening on Tuesday, which was 4 days ago. My ISP is Verizon, I am on Wireless(I know I know, but I have been playing perfectly fine for a whole year -_-) and my speeds are on 50/50 mbps.
tracert 184.107.107.176
Tracing route to 184.107.107.176 over a maximum of 30 hops
1 1 ms 1 ms 1 ms
2 6 ms 5 ms 5 ms L100.NYCMNY-VFTTP-145.verizon-gni.net [98.113.50
.1]
3 10 ms 6 ms 8 ms G101-0-0-0.NYCMNY-LCR-21.verizon-gni.net [100.41
.211.224]
4 * * * Request timed out.
5 9 ms 9 ms 9 ms 0.ae1.BR2.NYC4.ALTER.NET [140.222.229.91]
6 9 ms 9 ms 10 ms 204.255.168.114
7 10 ms 9 ms 9 ms be2061.ccr22.jfk02.atlas.cogentco.com [154.54.3.
69]
8 15 ms 15 ms 15 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
9 20 ms 19 ms 21 ms be2302.ccr21.alb02.atlas.cogentco.com [154.54.43
.14]
10 23 ms 24 ms 25 ms be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43
.17]
11 26 ms 27 ms 26 ms te8-4.cl-core06.cogent.mtl.iweb.com [38.104.154.
202]
12 27 ms 26 ms 27 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
13 24 ms 24 ms 25 ms 72.55.128.44
14 27 ms 26 ms 24 ms 184.107.107.176
Trace complete.
tracert neolobby02.ffxiv.com
Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms
2 7 ms 17 ms 25 ms L100.NYCMNY-VFTTP-145.verizon-gni.net [98.113.50
.1]
3 8 ms 10 ms 6 ms G0-11-0-3.NYCMNY-LCR-21.verizon-gni.net [130.81.
131.76]
4 8 ms 7 ms 14 ms ae3-0.NY325-BB-RTR2.verizon-gni.net [130.81.199.
154]
5 * * * Request timed out.
6 23 ms 6 ms 8 ms 2.ae0.XT2.NYC4.ALTER.NET [140.222.227.27]
7 17 ms 12 ms 12 ms TenGigE0-7-4-0.GW8.NYC4.ALTER.NET [152.63.21.133
]
8 27 ms 26 ms 28 ms tinet-gw.customer.alter.net [152.179.72.122]
9 72 ms 31 ms 29 ms xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106]
10 26 ms 27 ms 26 ms ormuco-gw.ip4.gtt.net [216.221.156.110]
11 29 ms 26 ms 26 ms 192.34.76.2
12 31 ms 29 ms 28 ms 199.91.189.234
13 29 ms 29 ms 30 ms 199.91.189.74
Trace complete.
tracert neolobby04.ffxiv.com
Tracing route to neolobby04.ffxiv.com [199.91.189.93]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms
2 7 ms 5 ms 5 ms L100.NYCMNY-VFTTP-145.verizon-gni.net [98.113.50
.1]
3 8 ms 11 ms 10 ms G0-11-0-3.NYCMNY-LCR-22.verizon-gni.net [130.81.
131.254]
4 * * * Request timed out.
5 8 ms 8 ms 8 ms 2.ae0.XT2.NYC4.ALTER.NET [140.222.227.27]
6 13 ms 12 ms 13 ms TenGigE0-5-2-0.GW8.NYC4.ALTER.NET [152.63.16.125
]
7 21 ms 20 ms 19 ms tinet-gw.customer.alter.net [152.179.72.122]
8 37 ms 51 ms 32 ms xe-4-2-0.mtl10.ip4.gtt.net [141.136.107.125]
9 28 ms 30 ms 31 ms ormuco-gw.ip4.gtt.net [216.221.156.110]
10 28 ms 27 ms 26 ms 192.34.76.2
11 25 ms 26 ms 32 ms 199.91.189.234
12 29 ms 28 ms 28 ms 199.91.189.93
Trace complete.
tracert neolobby06.ffxiv.com
Tracing route to neolobby06.ffxiv.com [199.91.189.106]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms
2 5 ms 10 ms 6 ms L100.NYCMNY-VFTTP-145.verizon-gni.net [98.113.50
.1]
3 9 ms 7 ms 8 ms G0-11-0-3.NYCMNY-LCR-21.verizon-gni.net [130.81.
131.76]
4 14 ms 82 ms 25 ms ae0-0.NY325-BB-RTR1.verizon-gni.net [130.81.209.
102]
5 * * * Request timed out.
6 49 ms 118 ms 6 ms 3.ae1.XT1.NYC4.ALTER.NET [140.222.228.121]
7 8 ms 10 ms 11 ms TenGigE0-4-2-0.GW8.NYC4.ALTER.NET [152.63.16.73]
8 22 ms 20 ms 20 ms tinet-gw.customer.alter.net [152.179.72.122]
9 31 ms 30 ms 30 ms xe-1-3-0.mtl10.ip4.gtt.net [89.149.184.74]
10 26 ms 26 ms 25 ms ormuco-gw.ip4.gtt.net [216.221.156.110]
11 29 ms 24 ms 24 ms 192.34.76.2
12 32 ms * 31 ms 199.91.189.234
13 27 ms 26 ms 26 ms 199.91.189.106
Trace complete. -
08-16-2014, 03:08 PMRaist
@ Peanut:
Please, don't test against that 184.107.107.176 IP address. That is in no way connected to the game servers. It is a webserver hosted on i-web in a different section of town. The neolobby's though are on Ormuco lines and are in the subnet of the servers used for the game. If you want to test against your specific game server, you can get the IP by running netstat in a CMD prompt or loading Resource Monitor (resmon) and looking for the IP in the Network or TCP sections. All the servers in Canada that the game uses will start with 199 (the ones in JP that it uses periodically start with 124 for the most part).
It looks like alter.net may be one for them to look at. It was periodically getting a wide variance in response times:
6 23 ms 6 ms 8 ms 2.ae0.XT2.NYC4.ALTER.NET [140.222.227.27]
6 49 ms 118 ms 6 ms 3.ae1.XT1.NYC4.ALTER.NET [140.222.228.121]
This is more the kind of thing you want to look for... very erratic results happening at the same areas in your route(s). Those triple star events are not necessarily a sign of a problem, so long as they consistently show * * *. This usually means they have a policy to always drop ICMP ECHO requests. However, if that hop sometimes responds with a time, and then *'s at others--this means traffic shaping rules are kicking in to try to manage high congestion--that would definitely be something for them to investigate if it is happening often enough to be causing noticeable packet loss or delays (skip/pause, rubber-banding, excessive buffering for Netflix/Hulu/Roku/etc.).
Looks like there may be some issues on the other side of the alter.net peering section of your route as well when it is trying to hand off into Ormuco (SE's ISP). So yeah... your traces to the neolobby's may give them something they can work with at Tier3.
Verizon may have some work they need to do internally as well. There were a couple hops that were also getting a little weird within their segments. You may want to run some traces to something like google/youtube, netflix, or hulu as well because there may be some hiccups within the Verizon segments that may show up better against a busier streaming content provider.
Bear in mind, you aren't necessarily trying to diagnose this yourself. It is more a test for smoke before getting someone else to look for the fire. The traces can demonstrate that there may be a problem within their network or their partners, and gives them specific details so they can do additional testing on their own to make sure if/where/who they need to get involved. -
08-16-2014, 03:36 PMRindali
I too am using Verizon and have been getting frequent errors of the same sort in the past couple of days. I've noticed Verizon having issues with a number of other things (Youtube for one) as well in the same time span, but it seems very selective on what it'll cause problems for and what runs fine uninterrupted. I'll work on getting some tracers done, just adding to the pile.
-
08-17-2014, 10:41 AMPEANUT
Thanks so much for reply and taking the time to type that all out. It was very informative. However, I have been running tons of tracert tests for the past 2 or 3 days, figuring out what exactly the problem might be. Both from my cmd and from a software called PingPlotter to help. I also called and explained this to a Tier 1 tech. representative who then is sending the information to a Verizon Technician who should be contacting me by Monday and hopefully will be able to solve this.
But yes, I am getting constant * * * Request timed out, from Alter.net(#5) and occasionally from Verizon(#4), so I truly believe that is what is causing the issue with my frequent Error 90000's. -
08-17-2014, 10:42 AMPEANUT
I have noticed that too with Youtube, a lot of videos will stop at a certain point then take forever to load, then I have to refresh and fast forward for them to start working again, even ran some tests from Youtube and am getting latency results.
-
08-18-2014, 10:09 PMkram
Same problem here, always disconnected after 3-5mins then when connecting it takes so much time that I decided to let it go. LOL!
To make the story short, my internet is working fine with other games except FFXIV and found out about this thread http://forum.square-enix.com/ffxiv/t...P2P-throttling
During prime time hours I experienced this errors and lags, but after that it's fine. However, during Fridays and Saturdays FFXIV is completely fine.
What seems to be the problem?