Lag east servers

Xaoziq - Raging Tide
Xaoziq - Raging Tide Posts: 4 Arc User
edited February 2015 in Support Desk
Since about 2-3 weeks I've been having lag issues on Raging Tide server when connecting from the Netherlands.

This lag also seems to be connected to the 'Server error' message when logging in.

The lag seems to start in the evening for some reason, random times mostly after 19:00 CET (1:00 PM EST). :/

It's not just high ping all the time, I get freezes where nothing moves for 10-60 seconds and then everything speeds up for a bit and then freezes again, after it shows pings like 6k+.

Did a traceroute and it shows the following:
Traceren van de route naar pwieast3.perfectworld.com [198.49.243.17]
via maximaal 30 hops:

1 <1 ms <1 ms <1 ms 1.0.168.192.in-addr.arpa [192.168.0.1]
2 6 ms 6 ms 5 ms PC [0.0.0.0]
3 7 ms 7 ms 10 ms 169.61.142.212.in-addr.arpa [212.142.61.169]
4 8 ms 8 ms 7 ms 41.244.116.84.in-addr.arpa [84.116.244.41]
5 8 ms 7 ms 13 ms nl-ams04a-ri2-xe-2-3-0.aorta.net [84.116.134.89]
6 6 ms 8 ms 7 ms 18.182.46.213.in-addr.arpa [213.46.182.18]
7 96 ms 96 ms 93 ms xe-3-0-0.bos10.ip4.gtt.net [141.136.109.138]
8 106 ms 93 ms 95 ms internap-gw.ip4.gtt.net [77.67.77.54]
9 95 ms 96 ms 120 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
10 99 ms 103 ms 110 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
11 * * * Time-out bij opdracht.
12 98 ms 95 ms 102 ms 17.243.49.198.in-addr.arpa [198.49.243.17]

De trace is voltooid.

It seems that there is an issue after hop 10 'perfectworldent-4.border11.bsn.pnap.net'.

Does anyone have an idea on what the problem may be? Seems to be in PWI network from my point of view.
Post edited by Xaoziq - Raging Tide on

Comments

  • SylenThunder - Twilight Temple
    SylenThunder - Twilight Temple Posts: 7,908
    edited February 2015
    That would be right around where PWE's ISP is, but since the Following hop does not have a massive spike, it's most likely just not returning ping requests. Overall the route looks pretty clean, but your hops are kind of funky.

    What kind of setup do you have with the network connection there? All of it looks like an internal network until you get to hop 7, and then there's suddenly a huge spike.

    i'm at work, so I don't have all the tools to directly analyze those hops from here, but it's definitely a strange trace.
    [SIGPIC][/SIGPIC]
  • Xaoziq - Raging Tide
    Xaoziq - Raging Tide Posts: 4 Arc User
    edited February 2015
    This might be because I just set up a new DNS server, I put it back to auto-detect now and this is the traceroute:

    Traceren van de route naar pwieast3.perfectworld.com [198.49.243.17]
    via maximaal 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 6 ms 5 ms 5 ms PC [0.0.0.0]
    3 7 ms 7 ms 7 ms 212.142.61.169
    4 7 ms 7 ms 6 ms 84.116.244.41
    5 8 ms 7 ms 7 ms nl-ams04a-ri2-xe-2-3-0.aorta.net [84.116.134.89]

    6 8 ms 7 ms 8 ms 213.46.182.18
    7 127 ms 97 ms 94 ms xe-3-0-0.bos10.ip4.gtt.net [141.136.109.138]
    8 97 ms 97 ms 100 ms internap-gw.ip4.gtt.net [77.67.77.54]
    9 98 ms 96 ms 99 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
    04]
    10 106 ms 108 ms 104 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
    61.78]
    11 * * * Time-out bij opdracht.
    12 99 ms 98 ms 98 ms 198.49.243.17

    De trace is voltooid.

    Maybe I should also mention that when I use the service WTFast the lag and server error messages don't occur. This service reroutes the connections through a faster network to lower latency. Using this isn't an option though since PWI doesn't seem to like me using it.
  • SylenThunder - Twilight Temple
    SylenThunder - Twilight Temple Posts: 7,908
    edited February 2015
    Xaoziq - Raging Tide wrote: »
    This might be because I just set up a new DNS server, I put it back to auto-detect now and this is the traceroute:

    Traceren van de route naar pwieast3.perfectworld.com [198.49.243.17]
    via maximaal 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 6 ms 5 ms 5 ms PC [0.0.0.0]
    3 7 ms 7 ms 7 ms 212.142.61.169
    4 7 ms 7 ms 6 ms 84.116.244.41
    5 8 ms 7 ms 7 ms nl-ams04a-ri2-xe-2-3-0.aorta.net [84.116.134.89]

    6 8 ms 7 ms 8 ms 213.46.182.18
    7 127 ms 97 ms 94 ms xe-3-0-0.bos10.ip4.gtt.net [141.136.109.138]
    8 97 ms 97 ms 100 ms internap-gw.ip4.gtt.net [77.67.77.54]
    9 98 ms 96 ms 99 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
    04]
    10 106 ms 108 ms 104 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
    61.78]
    11 * * * Time-out bij opdracht.
    12 99 ms 98 ms 98 ms 198.49.243.17

    De trace is voltooid.

    Maybe I should also mention that when I use the service WTFast the lag and server error messages don't occur. This service reroutes the connections through a faster network to lower latency. Using this isn't an option though since PWI doesn't seem to like me using it.

    Yeah, using WTFast will get your account auto-banned for a year really quick by the server bots.

    The route is still a bit odd with Hop 2-4, then it looks more like I would expect at hop 5. Then at hop 7, you have a huge spike. With hops 1-6 being so low, they appear to be an internal network. It's very rare to see anything lower than 25ms after you hit the CO for your ISP. The spikes are a bit high, but not overly so. It's still a pretty weird route overall.
    [SIGPIC][/SIGPIC]

Categories