Printable View
I'm getting fed up with the 5 hours of constant lag spikes ever since the follow up maintenance to fix somethings from another follow up maintenance. As much as I enjoy playing this I'm not really wanting to throw my money at you just so I spend a couple of hours attempting to Atma farm to have to spend majority of that time lagging because you lot can't understand how much more easier it would be to have the EU servers in the dammed EU!!!!
I pity the fool who doesn't STFU.
/thread
In a very large portion of cases, once diagnosed properly, it has come out that there are issues in route to the server that are at least compounding the inherent lag if not being the actual lag spikes themselves. The servers can have hiccups that might otherwise be manageable, but if you have a 400ms spike in Nova Scotia on the way to Montreal it can be enough to render things unplayable. This type of problem has been identified for the majority of those that have more properly investigated their routes. Basically, it typically boils down to issues with the agreements with the routing partners connecting you to Montreal--those peering agreements are managed by your ISP, not SE. In the case of consoles, there have also been problems with the PSN network that adversely impact stability as well--that is Sony's problem (and sometimes our ISP) and not SE.
Have you identified the IP your client is using while logged fully in the game (via resmon from start/search box or running netstat in a CMD window while logged fully into the game) and then run a series of tracert/traceroute style reports both during good and bad lag conditions and compared the results? This will help identify the source(s) of your lag spikes/packet loss so you know who to contact to investigate and address the problem. If you are on a console, you may be able to get this information by viewing the connections through your router's management interface (provided it has an app for doing so). The addresses you need will start with 199 and will show an active/connected state. Idle_wait statuses are no longer currently in use.
If you don't have a means to track down the actual IP, you can use the IP listed for your server at the arrstatus.com page. Even though it may not be your actual server, it is an IP within the same subnet and will still give a reasonable enough picture that may identify if there is a routing problem.
I haven't had any lag spikes in the past month but today I had a few, if it helps >
Code:C:\Windows\System32>tracert 124.150.157.30
Tracing route to 124.150.157.30 over a maximum of 30 hops
1 1 ms 1 ms <1 ms 10.0.0.138
2 25 ms 27 ms 25 ms ***.18.210.15
3 25 ms 25 ms 25 ms ***.18.68.133
4 26 ms 25 ms 25 ms bundle-ether4.lon-edge902.melbourne.telstra.net
[203.50.76.12]
5 26 ms 27 ms 25 ms bundle-ether11.exi-core1.melbourne.telstra.net [
203.50.11.113]
6 27 ms 27 ms 26 ms bundle-ether13.exi-core10.melbourne.telstra.net
[203.50.11.135]
7 40 ms 41 ms 39 ms bundle-ether12.chw-core10.sydney.telstra.net [20
3.50.11.124]
8 41 ms 41 ms 40 ms bundle-ether19.chw-core2.sydney.telstra.net [203
.50.11.130]
9 40 ms 41 ms 39 ms bundle-ether1.oxf-gw2.sydney.telstra.net [203.50
.6.90]
10 41 ms 38 ms 39 ms 203.50.13.38
11 188 ms 187 ms 186 ms i-0-4-0-3.paix-core01.bx.telstraglobal.net [202.
84.140.70]
12 225 ms 227 ms 226 ms i-0-2-0-7.eqnx-core01.bi.telstraglobal.net [202.
40.149.38]
13 230 ms 230 ms 230 ms unknown.telstraglobal.net [202.40.149.81]
14 * * * Request timed out.
15 251 ms 259 ms 251 ms po4-0-0.cr1.nrt1.asianetcom.net [202.147.0.33]
16 252 ms 251 ms 251 ms squareco.asianetcom.net [203.192.149.210]
17 251 ms 251 ms 250 ms 61.195.56.129
18 227 ms 226 ms 226 ms 219.117.144.66
19 227 ms 226 ms 226 ms 219.117.144.53
20 315 ms 254 ms 226 ms 219.117.144.41
21 230 ms 313 ms 313 ms 219.117.147.190
22 228 ms 225 ms 228 ms 124.150.157.30
Trace complete.
C:\Windows\System32>ping 124.150.157.30
Pinging 124.150.157.30 with 32 bytes of data:
Reply from 124.150.157.30: bytes=32 time=226ms TTL=233
Reply from 124.150.157.30: bytes=32 time=227ms TTL=233
Reply from 124.150.157.30: bytes=32 time=230ms TTL=233
Reply from 124.150.157.30: bytes=32 time=227ms TTL=233
Ping statistics for 124.150.157.30:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 226ms, Maximum = 230ms, Average = 227ms