Results -9 to 0 of 4

Threaded View

  1. #3
    Player
    Raist's Avatar
    Join Date
    Aug 2013
    Posts
    2,457
    Character
    Raist Soulforge
    World
    Midgardsormr
    Main Class
    Thaumaturge Lv 60
    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.
    (1)
    Last edited by Raist; 06-20-2014 at 07:29 AM.