Printable View
Run a trace route while your in game on the end point IP. Where is the latency occurring? What are the stats on the pings and hop tables? Depending on how you're being routed, it may not be an issue on your end. Are you hardlined into your router or using wifi? If the latter, does hardlining your connection stabilize the connection?
Same issues.
Was in a duty and DC'd like 3 times in 90 mins.
I just made a similar thread, here is what i've said:
Upon that last maintenance, those Errors were fixed for me. I'm playing on a desktop connected to a router via Ethernet; however, my wife is using a laptop and she's connecting through the same router via wireless, she still gets these errors! I used a broadband to find out if it will fix the issue, and yeah it was fixed! but I cannot use the broadband all the time. I have to use the router, anyway to fix these 90000 and 2002 errors she has been getting for days now?
:/
What's the latency between the NIC on the laptop and the connection out? What's odd to me is that even though from the NIC to the router is a hop and will cause latency, my own route path shows next to no jitter from my NIC to me router via wireless (see below). Does the lag happen all the time, or when you're hardlined and she is on the wifi? Does the issue clear up when you are not connected? Anything else running on the network? Phones, Netflix, Laptops, etc?
The largest jump for me is from Seattle to Chicago. The latency almost doubles. I have historical trace routes and pings that show much much higher lag times. I pulled this trace route more as a reference point than anything else.
traceroute to 199.91.189.38 (199.91.189.38), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 2.459 ms 3.245 ms 3.822 ms
2 192.168.0.1 (192.168.0.1) 6.275 ms 1.202 ms 2.429 ms
3 184.99.64.199 (184.99.64.199) 23.813 ms 23.147 ms 25.731 ms
4 184-99-65-49.boid.qwest.net (184.99.65.49) 23.719 ms 42.811 ms 31.405 ms
5 sea-brdr-02.inet.qwest.net (67.14.41.18) 49.715 ms 41.207 ms 38.921 ms
6 ix-1-0-0-0.tcore1.00s-seattle.as6453.net (64.86.123.77) 38.378 ms 42.517 ms 83.059 ms
7 if-1-0-0-3.core1.00s-seattle.as6453.net (64.86.123.6) 55.198 ms 36.625 ms
if-0-0-0-2.core1.00s-seattle.as6453.net (64.86.123.2) 37.021 ms
8 if-8-2-3-0.tcore2.ct8-chicago.as6453.net (64.86.124.30) 109.835 ms 113.097 ms 101.895 ms
9 if-3-2.tcore1.w6c-montreal.as6453.net (66.198.96.45) 113.080 ms 101.879 ms 104.395 ms
10 66.198.96.50 (66.198.96.50) 120.111 ms 121.201 ms 123.035 ms
11 192.34.76.2 (192.34.76.2) 106.506 ms 107.071 ms 106.427 ms
Omg I can't do anything at all with this constantly happening! Never had the issue before and now it's like a kiss of death every 5 min.
I tried playing directly connected and still got kicked out with a 90k after a while.
So, I called Square on this. I got told its congestion and to try again later. Load of bs seems how Ive been playing since the start of beta, early access and so forth, with no issues until yesterday morning.
Hi Everyone, I was having this issues for a while until i read a bunch of threads about this on these forums. This goes back to before the big maintenance they did a week or so ago. You're IP was in a list to use a specific SE server IP, this server IP was causing these problems, which get worse and worse until the game is unplayable. SE fixed the root cause, but unless you have a new IP since then, you will still see this issue.
Call your ISP and get them to reset your IP
With a new IP, you will never have this problem again, due to SE fixing the original server issue.
I couldnt stay logged in for more than 30 seconds. I called my ISP, they reset my IP, I restarted my modem, and I haven't been booted since.
Just got off the phone with my isp and did as you suggested. Still a no go for me. Soon as I get on its major lag then 90k.
well, i'm sorry to hear that. I was SoL for almost 2 weeks before I did this and I have been great since. Hope you guys can get this fixed somehow.