The Elder Scrolls Online

999+ latency and insane lag

Leave a Reply
  • synnerman
    synnerman
    ✭✭✭✭
    Kragorn wrote: »
    rdbrown1987 wrote: »
    Virgin media users please comment here
    Given this in the tracert of the OP in that forum shows this:

    9 23 ms 16 ms 14 ms 80.150.170.5
    10 117 ms 121 ms 119 ms 217.239.45.198

    not sure where VM come into this. Not sure what backbone providers those are but those are well out of VM's network as far as I know .. I have VM in Warrington, FYI, and have noticed similar latency (even though I don't know how to see it as per my previous post) and I too have done tracerts and seen the same pattern with 'pings' suddenly leaping to 100+ at that point.

    The jump in latency is when it hops from here to Europe so is expected. We would expect latency in the UK from the Frankfurt server between 70-120 ish but nowhere near the 200+ - 999 that we are getting.

  • pppontus
    pppontus
    ✭✭✭✭✭
    ✭
    The past weeks? This has been happening for months on the EU server, for everyone, and is so easy to reproduce. Here you go:

    1. Log in to the game at some hour that would be moderately busy (weekdays after 7pm, for example)
    2. Travel to a heavily populated zone (DC: Stormhaven)
    3. Wait a bit
    4. Enjoy not being able to interact with anything, zone chat screaming "LAAAAAAAAG" and the latency meter hitting the red 999+

    Happens every single day..
    Edited by pppontus on March 2, 2015 1:53PM
  • Kragorn
    Kragorn
    ✭✭✭✭✭
    Have you done any tracerts?

    Just had another couple of minutes with two DCs and other crap, again this isn't our end it's well on the way to ZOS:

    First is a good one ...

    c:\ >tracert 159.100.230.103

    Tracing route to 159.100.230.103 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms 10.0.0.250
    2 6 ms 7 ms 5 ms 10.93.144.1
    3 8 ms 7 ms 7 ms bagu-core-2b-xe-132-0.network.virginmedia.net [80.5.167.253]
    4 * * * Request timed out.
    5 * * * Request timed out.
    6 * * * Request timed out.
    7 * * * Request timed out.
    8 17 ms 14 ms 13 ms popl-bb-1b-ae0-0.network.virginmedia.net [62.254.42.90]
    9 14 ms 15 ms 19 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
    10 14 ms 13 ms 13 ms 80.150.170.5
    11 29 ms 29 ms 29 ms 217.239.44.62
    12 30 ms 30 ms 29 ms 193.159.226.18
    13 30 ms 30 ms 29 ms ns99.rookdns.com [195.122.154.4]
    14 31 ms 30 ms 30 ms 159.100.230.103

    Trace complete.

    this is when it was pear-shaped ...

    c:\ >tracert 159.100.230.103

    Tracing route to 159.100.230.103 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms 10.0.0.250
    2 6 ms 8 ms 6 ms 10.93.144.1
    3 7 ms 7 ms 7 ms bagu-core-2b-xe-132-0.network.virginmedia.net [80.5.167.253]
    4 * * * Request timed out.
    5 * * * Request timed out.
    6 * * * Request timed out.
    7 * * * Request timed out.
    8 27 ms 13 ms 23 ms popl-bb-1b-ae0-0.network.virginmedia.net [62.254.42.90]
    9 13 ms 13 ms 13 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
    10 16 ms 13 ms 13 ms 80.150.170.5
    11 28 ms 29 ms 29 ms 217.239.44.62
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * 450 ms * 159.100.230.103
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20 31 ms 33 ms 33 ms 159.100.230.103

    Trace complete.

    In comparison my BT connection ends up ...

    C:\>tracert 159.100.230.103

    Tracing route to 159.100.230.103 over a maximum of 30 hops

    12 27 ms 27 ms 27 ms 217.239.45.198
    13 27 ms 27 ms 27 ms 193.159.226.18
    14 27 ms 26 ms 27 ms ns99.rookdns.com [195.122.154.3]
    15 26 ms 26 ms 26 ms 159.100.230.103

    Trace complete.


    My conclusion is that at least some of the problems we're having is whatever that 193 subnet is and that would affect a large number of players I suspect.
    Edited by Kragorn on March 2, 2015 6:41PM
  • Kragorn
    Kragorn
    ✭✭✭✭✭
    synnerman wrote: »
    Kragorn wrote: »
    rdbrown1987 wrote: »
    Virgin media users please comment here
    Given this in the tracert of the OP in that forum shows this:

    9 23 ms 16 ms 14 ms 80.150.170.5
    10 117 ms 121 ms 119 ms 217.239.45.198

    not sure where VM come into this. Not sure what backbone providers those are but those are well out of VM's network as far as I know .. I have VM in Warrington, FYI, and have noticed similar latency (even though I don't know how to see it as per my previous post) and I too have done tracerts and seen the same pattern with 'pings' suddenly leaping to 100+ at that point.

    The jump in latency is when it hops from here to Europe so is expected. We would expect latency in the UK from the Frankfurt server between 70-120 ish but nowhere near the 200+ - 999 that we are getting.
    Sorry, no, there's no way a jump across the Channel should go to >100ms, I get that going to the US. No way would I expect >100 to Germany, look at the 'good' trace I listed above and the BT one from below here, that's what I expect to see over only a few hundred mile!

    Got another example right now .. but this time I'm doing a tracert using my BT ISP and I get this:

    C:>tracert 159.100.230.103

    Tracing route to 159.100.230.103 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms 10.0.0.248
    2 5 ms 5 ms 5 ms 217.32.142.0
    3 5 ms 5 ms 5 ms 217.32.142.46
    4 6 ms 6 ms 6 ms host109-159-245-138.range109-159.btcentralplus.c
    om [109.159.245.138]
    5 6 ms 5 ms 5 ms 31.55.165.171
    6 6 ms 6 ms 6 ms 31.55.165.109
    7 5 ms 5 ms 5 ms acc2-10GigE-0-3-0.mr.21cn-ipp.bt.net [109.159.25
    0.210]
    8 15 ms 16 ms 23 ms core1-te0-4-0-0.ilford.ukcore.bt.net [109.159.25
    0.129]
    9 12 ms 12 ms 13 ms peer6-te0-9-0-12.telehouse.ukcore.bt.net [109.15
    9.254.165]
    10 16 ms 15 ms 15 ms 166-49-211-236.eu.bt.net [166.49.211.236]
    11 12 ms 12 ms 12 ms 193.159.165.81
    12 27 ms 27 ms 27 ms 217.239.45.198
    13 35 ms 27 ms 27 ms 193.159.226.18
    14 27 ms 27 ms 27 ms ns99.rookdns.com [195.122.154.3]
    15 26 ms 26 ms 26 ms 159.100.230.103

    Trace complete.

    I got that while my VM connection is reporting total pack loss at the 193.159.226.18 node .. so packets from VM are being dropped but those from BT aren't.

    Edited by Kragorn on March 2, 2015 7:16PM
  • Kragorn
    Kragorn
    ✭✭✭✭✭
    And now we're back to normal except for noticeable increase at hops 11 and 13.

    c:\ >tracert 159.100.230.103

    Tracing route to 159.100.230.103 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms 10.0.0.250
    2 7 ms 6 ms 5 ms 10.93.144.1
    3 7 ms 7 ms 7 ms bagu-core-2b-xe-132-0.network.virginmedia.net [80.5.167.253]
    4 * * * Request timed out.
    5 * * * Request timed out.
    6 * * * Request timed out.
    7 * * * Request timed out.
    8 13 ms 15 ms 13 ms popl-bb-1b-ae0-0.network.virginmedia.net [62.254.42.90]
    9 13 ms 13 ms 15 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
    10 14 ms 14 ms 14 ms 80.150.170.5
    11 74 ms 77 ms 81 ms 217.239.44.62
    12 33 ms 33 ms 34 ms 193.159.226.18
    13 80 ms 78 ms 80 ms ns99.rookdns.com [195.122.154.4]
    14 30 ms 31 ms 30 ms 159.100.230.103

    Trace complete.
    Edited by Kragorn on March 2, 2015 7:23PM
  • rsciw
    rsciw
    ✭✭✭
    I've posted my traceroutes in this thread ->
    http://forums.elderscrollsonline.com/en/discussion/comment/1593908/#Comment_1593908

    But for posterity here are the same:

    traceroute to 159.100.232.107 (159.100.232.107), 30 hops max, 60 byte packets
    1 192.168.1.254 (192.168.1.254) 0.575 ms 1.000 ms 1.311 ms
    2 cpc3-tilb8-2-0-gw.basl.cable.virginm.net (77.101.113.1) 12.628 ms 12.816 ms 13.080 ms
    3 basl-core-2a-ae11-613.network.virginmedia.net (81.96.1.73) 11.092 ms 12.156 ms 12.420 ms
    4 brnt-bb-1a-ae10-0.network.virginmedia.net (81.96.0.145) 27.968 ms 26.957 ms 28.196 ms
    5 * * *
    6 popl-bb-1b-ae4-0.network.virginmedia.net (62.252.2.110) 19.670 ms 12.386 ms 52.615 ms
    7 m674-mp2.cvx1-b.lis.dial.ntli.net (62.254.42.162) 15.835 ms 21.121 ms 21.282 ms
    8 193.159.224.57 (193.159.224.57) 20.092 ms 80.150.170.5 (80.150.170.5) 19.628 ms 19.914 ms
    9 217.239.44.46 (217.239.44.46) 104.336 ms 111.324 ms 112.286 ms
    10 193.159.226.18 (193.159.226.18) 113.348 ms 113.758 ms 113.569 ms
    11 ns99.rookdns.com (195.122.154.4) 116.156 ms 115.992 ms ns99.rookdns.com (195.122.154.3) 115.816 ms
    12 159.100.232.107 (159.100.232.107) 99.115 ms 99.695 ms 102.823 ms

    and the one ending with 116 is:

    traceroute to 159.100.232.116 (159.100.232.116), 30 hops max, 60 byte packets
    1 192.168.1.254 (192.168.1.254) 0.936 ms 1.350 ms 1.661 ms
    2 cpc3-tilb8-2-0-gw.basl.cable.virginm.net (77.101.113.1) 10.377 ms 11.214 ms 28.032 ms
    3 basl-core-2b-ae11-710.network.virginmedia.net (81.96.1.217) 16.959 ms 17.947 ms 18.185 ms
    4 popl-bb-1b-ae11-0.network.virginmedia.net (81.96.0.149) 19.124 ms 19.287 ms 19.425 ms
    5 m674-mp2.cvx1-b.lis.dial.ntli.net (62.254.42.162) 24.790 ms 25.753 ms 25.989 ms
    6 80.150.170.5 (80.150.170.5) 29.327 ms 193.159.224.57 (193.159.224.57) 17.950 ms 16.456 ms
    7 217.239.44.22 (217.239.44.22) 89.590 ms 90.549 ms 94.136 ms
    8 193.159.226.18 (193.159.226.18) 95.573 ms 95.834 ms 95.971 ms
    9 ns99.rookdns.com (195.122.154.3) 97.132 ms 96.917 ms ns99.rookdns.com (195.122.154.4) 96.678 ms
    10 159.100.232.116 (159.100.232.116) 96.065 ms 96.201 ms 96.337 ms

    That 193.159.226.18 IP belongs to Germany's DTAG, comparable to BT in UK, its whois sates "for IP-Transit", whereas the IP in pos#11 on your traceroute doesn't state IP transit, but is also part of DTAG's range.

    In comparison to that, one traceroute starting within peer1 network:

    traceroute to 159.100.232.107 (159.100.232.107), 50 hops max, 60 byte packets
    1 * * *
    2 10ge.por-5ltp1ops-dis-2.peer1.net (216.187.112.186) 0.379 ms 0.313 ms 0.255 ms
    3 10ge.xe-0-0-0.ldn-eqx-cor-1.peer1.net (216.187.115.225) 3.415 ms 3.337 ms 3.320 ms
    4 10ge.xe-0-0-0.ldn-telehw-cor-1.peer1.net (216.187.112.181) 6.267 ms 6.199 ms 6.116 ms
    5 ix-0-2-2-0.tcore1.LDN-London.as6453.net (66.110.8.37) 3.681 ms 3.679 ms 3.705 ms
    6 195.219.83.102 (195.219.83.102) 5.771 ms 5.713 ms 4.402 ms
    7 * * *
    8 * * *
    9 212.162.9.150 (212.162.9.150) 17.969 ms 17.934 ms 17.952 ms
    10 ns99.rookdns.com (195.122.154.4) 18.633 ms ns99.rookdns.com (195.122.154.3) 18.169 ms ns99.rookdns.com (195.122.154.4) 18.478 ms
    11 159.100.232.107 (159.100.232.107) 17.994 ms 18.109 ms 18.015 ms

    one starting out via flexiant network

    traceroute to 159.100.232.107 (159.100.232.107), 30 hops max, 60 byte packets
    1 109.231.71.209 (109.231.71.209) 0.169 ms 0.069 ms 0.150 ms
    2 ge1-3-0-545.br1.blsq.flexiant.net (109.231.64.149) 0.206 ms 0.136 ms 0.145 ms
    3 109.231.64.218 (109.231.64.218) 0.309 ms 0.235 ms 0.204 ms
    4 v220.core1.lon1.he.net (216.66.80.117) 8.083 ms 9.703 ms 2.462 ms
    5 ldn-b5-link.telia.net (213.248.93.81) 2.546 ms 2.517 ms 2.549 ms
    6 ldn-bb1-link.telia.net (80.91.246.144) 2.521 ms ldn-bb1-link.telia.net (80.91.246.96) 11.912 ms ldn-bb1-link.telia.net (80.91.247.91) 87.638 ms
    7 ldn-b7-link.telia.net (62.115.138.153) 1.811 ms ldn-b7-link.telia.net (62.115.141.151) 2.662 ms ldn-b7-link.telia.net (62.115.141.149) 1.802 ms
    8 level3-ic-143383-ldn-b5.c.telia.net (213.248.96.38) 1.668 ms 1.696 ms 1.654 ms
    9 * * *
    10 * * *
    11 212.162.9.150 (212.162.9.150) 12.475 ms 13.163 ms 13.129 ms
    12 ns99.rookdns.com (195.122.154.4) 13.247 ms 13.215 ms 13.451 ms
    13 159.100.232.107 (159.100.232.107) 13.108 ms 13.062 ms 13.363 ms

    and one starting out via AWS network in Dublin

    1 ec2-79-125-0-132.eu-west-1.compute.amazonaws.com (79.125.0.132) 0.707 ms 0.657 ms 0.607 ms
    2 178.236.0.124 (178.236.0.124) 0.853 ms 1.766 ms 1.000 ms
    3 178.236.0.131 (178.236.0.131) 1.052 ms 178.236.0.129 (178.236.0.129) 0.866 ms 178.236.0.127 (178.236.0.127) 1.095 ms
    4 213.242.106.85 (213.242.106.85) 1.099 ms 195.16.170.101 (195.16.170.101) 1.497 ms 213.242.106.85 (213.242.106.85) 1.257 ms
    5 * * *
    6 * * *
    7 212.162.9.150 (212.162.9.150) 25.716 ms 25.889 ms 25.846 ms
    8 ns99.rookdns.com (195.122.154.3) 26.827 ms 26.795 ms 26.759 ms
    9 159.100.232.107 (159.100.232.107) 25.487 ms 25.441 ms 25.631 ms


    Their traceroutes are much faster, and notably don't go through that 193.x IP

    At this stage I reckon it's just random guesswork what went haywire and where, from mine/our side at least. Incorrectly configured BGP? Forgot to allow some firewall routes? Cleaner pulled a plug off a switch?
  • Kragorn
    Kragorn
    ✭✭✭✭✭
    I just had another case where my VM connection was broken at the 193. hop while at the same time my BT one was getting through just fine, the tracerts looked just like those I already posted.

    BGP maybe, it's about the only thing I can think of but it seems to be breaking repeatedly every hour or so (though not in any obvious pattern).

    I've not switched to my BT broadband and will see what happens while monitoring the VM connection.
  • icemere
    icemere
    ✭
    I would like to thank ZoS for what-ever they have done behind the scenes, Since mid-yesterday my latency has stabalised back down to normal, And has remained so through-out today, Thanks for the fast fix!
    "It's better to be hated for who you are, Than to be loved, for who you are not"
    "life is for living, Not regretting"
  • Lyrander
    Lyrander
    ✭✭✭
    icemere wrote: »
    I would like to thank ZoS for what-ever they have done behind the scenes, Since mid-yesterday my latency has stabalised back down to normal, And has remained so through-out today, Thanks for the fast fix!


    whatever they did...now i have the worst pings!
  • shiningfury
    shiningfury
    Soul Shriven
    The issue still remains as of today 2015-03-07. Multiple people in zone chat reporting 999+ latency, rubberbanding, and disconnections. The game becomes unplayable and if this is happening now with current population I can only imagine how bad it will be after Tamriel Unlimited is launched.
    Edited by shiningfury on March 8, 2015 12:06AM
  • Mpcolson
    Mpcolson
    ✭✭✭
    I have been experiencing this issues since the patch. My FPS rate dropped into the 20's from running in the 40's since I started this game in BETA.

    I have issues with rubber banding, LAG to beat the band, latency showing 999 in red and then dropping to double digits for a time then back to the red numbers.

    I have issues with audio/video sync when I talk to NPCs and I have so much lag issues the fights I have do not even show what is happening on screen. I do my first attack and by the time the game catches up to my actions the next thing I see is a dead NPC... I can perform 5 moves and never see one animation ... just poof the bad guy is dead.

    This has got to be a ZOS issue... I can play SWTOR with out all these problems. I can watch streaming video in HD without issues so I cannot accept this to be a ISP or router issue. It's coming from ZOS and the new patch.
  • mr_runaway_666b16_ESO
    mr_runaway_666b16_ESO
    ✭✭
    this issues was entirely different to what's happening now, I'm only getting weapon slot lockups and other lag but it doesn't spike and disconnect me. I think this is just new 1.6 lag we are having.

    hoping they can fix it all as fast as they nerf xp grinds.
    Beardeddraggonborn Stam Templar
    Beardeddragonborn mag DK shelved
    Beardie Stam NB
    Eve Bearegard Mag Sorc

Sign In or Register to comment.