More people are encountering the problem every single day. It will probably happen to you too soon, and when it does I will be there to "Like" the forum topic you make about lag and 90k errors. It will be right there with the other dozen made every day. The majority of front page technical support non-sticky topics right now are about lag and 90k, btw.
Last edited by Appleh4x; 10-02-2013 at 10:31 PM.
Ya the cable is getting thinner and thinner due to the high load. I'll wait your like when the last wire of copper my router is connected to will burn.
My coffee is cold with coffee bits in it! I'm going to blame the person who poured and served it to me instead of the machine it came from!
It tastes weird anyways.
-sips while reading-
I've spent hours reading, upgrading stuff, talking with my ISP about all of this.... hours. I'm not going to pick sides but I have done everything in my power to figure out if it's on my end with no luck. I am just waiting for anyone to finally post "I FIXED IT!!1" or for squeex to post something, anybody anything. I do not care who wins this stupid argument. "Experts" on both sides of this bridge seem to make valid points and that really sucks.
This is so true, it starts w/ the lag...then the 90k's. I think what comes after that will be the giving up partMore people are encountering the problem every single day. It will probably happen to you too soon, and when it does I will be there to "Like" the forum topic you make about lag and 90k errors. It will be right there with the other dozen made every day. The majority of front page technical support non-sticky topics right now are about lag and 90k, btw.
I live at the east coast and my friend lives in CA. My friend has been telling me about massive lag and disconnects from the game servers. He was blaming SE for these problems like many others was doing. I looked at his routing table from CA to SE servers. I found he was having servere packet loss and problems and other problems with a routing server in Palo Alto, CA (owned by Tata Communications). I researched this routing server and found out people playing WoW, GW2, and many other mmorpgs living in CA are having the same problems.
I told my friend to call Verizon (his ISP) and explain the problem and they need to reroute him. They blew him off at first that it was not a Verizon problem. I called Verizon on his behalf and made this a 3-way call between Verizon, my friend, and I. After the conversation, Verizon did reroute him and now my friend's connection to SE game servers is great. Today he tells me that he doesn't get disconnects and doesn't lag like he use too.
The people giving the advice are correct for solving these problems addressed in this thread.
I had login problems like everyone in early access and at launch. I understood the servers was being overloaded. After the 9/4 maintenance, I don't have anymore problems with the game. My ping is around 30-44ms on peak times.
I am a network administrator/engineer, web hosting engineer, and own a technology company. i have over 20 years XP. I figured on giving my some of my background before someone becomes critical on what I posted.
Oh great.. this means I need to waste my time calling Comcast.
So I ran a tracert on the IP htat I am connecting to while inside the game, got it from the Resource Monitor in windows and here is the result, the is just one of many, and they are always the same result, Request timed out on the 17th, I know people are saying it's i-web, cogentco, and Tata, and in my case Cogentco is one of the routing isp that shows up, but then I ran a whois on the IP before AND after the timeout it brings up this ..38.122.42.34 192.34.76.2 so is it really Cogento/tata/i-web??? or is it Ormuco, what do you network admins think?
Hyperion server
ran trace while I am on a jp server just to see the diffrenceCode:Tracing route to 199.91.189.57 over a maximum of 30 hops 1 1 ms <1 ms <1 ms 10.10.10.1 2 7 ms 1 ms 1 ms ben2gw1.texascellnet.com [63.246.232.254] 3 4 ms 3 ms 1 ms ben2bh.texascellnet.com [63.246.224.105] 4 5 ms 2 ms 3 ms corban1bh.texascellnet.com [63.246.224.33] 5 9 ms 9 ms 6 ms corbanrtr.texascellnet.com [63.246.224.1] 6 14 ms 9 ms 17 ms 216.171.64.1 7 6 ms 5 ms 4 ms xc_45-90-171.216.xcnetworks.com [216.171.90.45] 8 5 ms 5 ms 8 ms ge-8-29.car2.Dallas1.Level3.net [4.71.171.121] 9 * 5 ms 4 ms ae-3-80.edge2.Dallas1.Level3.net [4.69.145.139] 10 10 ms 6 ms 6 ms 4.68.111.102 11 7 ms * 8 ms be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7. 45] 12 20 ms 18 ms 17 ms be2012.ccr21.mci01.atlas.cogentco.com [154.54.2. 113] 13 27 ms 25 ms 34 ms te0-4-0-3.ccr21.ord01.atlas.cogentco.com [154.54 .6.157] 14 44 ms 42 ms 43 ms be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27 .182] 15 83 ms 55 ms 52 ms be2092.ccr21.ymq02.atlas.cogentco.com [154.54.25 .26] 16 52 ms 48 ms 48 ms 38.122.42.34 17 * * * Request timed out. 18 164 ms 56 ms 50 ms 192.34.76.2 19 143 ms * 55 ms 199.91.189.234 20 51 ms 50 ms 51 ms 199.91.189.57 Trace complete.
on Aegis the IP for jp server is 124.150.157.32
surprise... no time outs, and no I don't get the random and constant 90k on JP serverCode:Tracing route to 124.150.157.32 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 10.10.10.1 2 2 ms 1 ms 1 ms ben2gw1.texascellnet.com [63.246.232.254] 3 2 ms 1 ms 1 ms ben2bh.texascellnet.com [63.246.224.105] 4 4 ms 4 ms 3 ms corban1bh.texascellnet.com [63.246.224.33] 5 6 ms 13 ms 2 ms corbanrtr.texascellnet.com [63.246.224.1] 6 5 ms 4 ms 6 ms 216.171.64.1 7 8 ms 3 ms 5 ms xc_45-90-171.216.xcnetworks.com [216.171.90.45] 8 334 ms 25 ms 13 ms ge-8-29.car2.Dallas1.Level3.net [4.71.171.121] 9 41 ms 40 ms 38 ms vlan60.csw1.Dallas1.Level3.net [4.69.145.62] 10 37 ms 41 ms 37 ms ae-63-63.ebr3.Dallas1.Level3.net [4.69.151.134] 11 45 ms 41 ms 38 ms ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77] 12 37 ms 36 ms 39 ms ae-92-92.csw4.LosAngeles1.Level3.net [4.69.137.3 0] 13 38 ms 39 ms 41 ms ae-4-90.edge2.LosAngeles9.Level3.net [4.69.144.2 07] 14 36 ms 35 ms 38 ms 4.53.230.102 15 37 ms 36 ms 37 ms lajbb001.kddnet.ad.jp [59.128.2.101] 16 153 ms 144 ms 150 ms otejbb205.int-gw.kddi.ne.jp [203.181.100.9] 17 149 ms 151 ms 159 ms jc-ote301.int-gw.kddi.ne.jp [118.155.197.42] 18 146 ms 147 ms 152 ms 106.187.28.198 19 148 ms 145 ms 150 ms 61.195.56.133 20 138 ms 134 ms 145 ms 219.117.144.78 21 139 ms 140 ms 137 ms 219.117.144.57 22 145 ms 154 ms 145 ms 219.117.144.41 23 174 ms 183 ms 149 ms 219.117.147.194 24 140 ms 143 ms 133 ms 124.150.157.32 Trace complete.
Last edited by Noah_; 10-03-2013 at 04:06 AM.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.