error 90000 since 2/23

[Solnaya]

Same issue, getting 90k'd trying to get past character login screen. I have Verizon FiOS and live in Texas. Problems started on Mon, Feb 24th, 2014. I download the WTFast 30 day free trial and have been able to login using that, though I'll be a sad panda if problems continue to persist after trial ends.

[Maku]

The 90k error is happening to us in Japan too. I can't go into or leave an ID without getting 90k. It started today after the hot "fix"

[Aenerb]

Still happening here. DFW Verizon. I was able to get around it by lowering the mtu on my machine, but that's not a solution, only a band-aid. I would like to see this fixed, but it seems SE needs to have a talk with Level3 and Verizon to get something done.

[Rubicon]

I was able to log in after patching last night's hotfix.

[cearka]

a bit better since maintenance, but I've been having tons of DCs since 2/23 as well. can't help but wonder if ps4 beta is putting more load on the network or something.

[ReplicaX]

a bit better since maintenance, but I've been having tons of DCs since 2/23 as well. can't help but wonder if ps4 beta is putting more load on the network or something.

The PS4 Beta Phase 1 is all on the Japanese Datacenter with its own worlds and not the NA/EU Datacenter.
Phase 2 of the Beta will be on Public worlds aka both Datacenters.

This info is in the Lodestone Topics section.

[Marishi-Ten]

FOR TEXAS USES AFFECTED BY 90K:

Testing a work around right now. We were able to make it work for one of our FC members that was affected by the 90k/Verizon issue:

Change the MTU values to 999 or lower.

He is on the PS3, but this worked for him. 1000 MTU he would 90k, 999 he wouldn't. You can change the MTU values on the PS3 itself.

PC Users have to use elevated command lines in the command prompt (run as admin)

For hardline:
netsh interface ipv4 set subinterface "Local Area Connection" mtu=999 store=persistent

For WiFi:
netsh interface ipv4 set subinterface "Wireless Network Connection" mtu=999 store=persistent

You can change it back to 1500 (default) by the same command line just change mtu=999 to mtu=1500. It's something to try and obviously I don't know if this will work for everyone. It is an option though and if people try this out, please post detailed results to see if our FC member was a one off or if this can be a standard work around.

BE ADVISED - This is only tested for one user to combat the specific Texas/Verizon 90k issue. IF YOU DO NOT LIVE IN TEXAS AND YOUR ISP IS NOT VERIZON, DO NOT ATTEMPT as it will likely not work.

[Ma_Ge]

..and still am getting the 90k error WAY too often..especially in CT! Everything was fine before the last maintenance -- and the recent hotfix didn't help anything! Twenty minutes at a time being stuck in 90k oblivion with -11,980 people in queue (yes NEGATIVE!). Lag, lag, lag, like I've never had before then...woops! 90k again!

Yes, I use a PS3, but it wasn't a problem before (and I've been here since Beta Phase 3). The game is no fun now..and it's pissing me off. I give them until March 12 to fix it...I'm not buying another month if this doesn't get better soon.

[yangusis]

Tried MTU fix, didn't work. I even looked up a guide to find the perfect MTU setting, and that did not work either. I was having this issue before the hotfix, and after as well. It worked real nice like directly after the hotfix.

I'm in AZ with Cox Communications, not Texas and Verizon. I run into 2002 and 90k errors, and if I do get in, I'll check signal and it will constantly say receiving 0, so I get all the pretty ping lag.

[Wettsaufer]

Im in the same boat. Im in Las vegas, and I 90k'd 7 times within 2 hours. No Verizon . Its getting beyond annoying.