Question about Latency and Traces

E_3T1ff3
E_3T1ff3 Posts: 4 Spectator
edited October 2023 in Gaming & Gaming Related

Hello. I was recently playing a game called Secret World Legends, and during the game play, I noticed several lag spikes which were affecting performance and overall playability.

at the instruction of Mods on the discord server, I ran several traces to troubleshoot the issue

Trace 1:

 1   <1 ms   <1 ms   <1 ms Cisco01989 [192.168.1.1]

 2   12 ms   13 ms   14 ms cpe-70-119-48-1.tx.res.rr.com [70.119.48.1]

 3    *     102 ms  372 ms lag-61.lvoktxad01h.netops.charter.com [24.28.132.161]

 4   19 ms   14 ms    7 ms lag-20.lvoktxad01r.netops.charter.com [24.175.33.20]

 5   33 ms   23 ms   13 ms lag-21.mcr11snavtxuu.netops.charter.com [24.175.32.144]

 6   15 ms   23 ms   17 ms lag-23.rcr01hstqtx02.netops.charter.com [24.175.32.156]

 7   17 ms   19 ms   15 ms lag-16.hstqtx0209w-bcr00.netops.charter.com [66.109.6.108]

 8    *       *       *    Request timed out.

 9    *      48 ms   46 ms ae6.3506.ear2.Newark1.level3.net [4.69.214.37]

 10   50 ms   45 ms   43 ms 4.28.188.22

 11   46 ms   60 ms   42 ms s1-nj4.game-hosting.com [37.18.192.5]

 12   59 ms   45 ms   44 ms gs022-nj4.ageofconan.com [37.18.193.31]


Trace 2:

1   <1 ms   <1 ms   <1 ms Cisco01989 [192.168.1.1]

 2   14 ms   13 ms   15 ms cpe-70-119-48-1.tx.res.rr.com [70.119.48.1]

3  103 ms  307 ms   32 ms lag-61.lvoktxad01h.netops.charter.com [24.28.132.161]

 4   16 ms    3 ms    7 ms lag-20.lvoktxad01r.netops.charter.com [24.175.33.20]

 5   19 ms    8 ms   10 ms lag-21.mcr11snavtxuu.netops.charter.com [24.175.32.144]

 6   15 ms   14 ms   13 ms lag-23.rcr01hstqtx02.netops.charter.com [24.175.32.156]

 7   16 ms   19 ms   13 ms lag-16.hstqtx0209w-bcr00.netops.charter.com [66.109.6.108]

 8    *       *       *    Request timed out.

 9    *      48 ms   46 ms ae6.3506.ear2.Newark1.level3.net [4.69.214.37]

 10   58 ms   55 ms   48 ms 4.28.188.22

 11   51 ms   45 ms   44 ms s1-nj4.game-hosting.com [37.18.192.5]

 12   47 ms   45 ms   45 ms gs022-nj4.ageofconan.com [37.18.193.31]

and finally, trace 3

1   <1 ms   <1 ms   <1 ms Cisco01989 [192.168.1.1]

 2   14 ms   13 ms   15 ms cpe-70-119-48-1.tx.res.rr.com [70.119.48.1]

 3  354 ms  553 ms  492 ms lag-61.lvoktxad01h.netops.charter.com [24.28.132.161]

 4   16 ms   13 ms   11 ms lag-20.lvoktxad01r.netops.charter.com [24.175.33.20]

 5   13 ms   14 ms   12 ms lag-21.mcr11snavtxuu.netops.charter.com [24.175.32.144]

 6   15 ms   15 ms   14 ms lag-23.rcr01hstqtx02.netops.charter.com [24.175.32.156]

 7   15 ms   14 ms   17 ms lag-16.hstqtx0209w-bcr00.netops.charter.com [66.109.6.108]

 8    *       *       *    Request timed out.

 9   45 ms   45 ms   43 ms ae6.3506.ear2.Newark1.level3.net [4.69.214.37]

 10   47 ms   58 ms   43 ms 4.28.188.22

 11   48 ms   48 ms   46 ms s1-nj4.game-hosting.com [37.18.192.5]

 12   45 ms   47 ms   42 ms gs022-nj4.ageofconan.com [37.18.193.31]

I was told the problem might be between Spectrum and the SWL server, but Im not sure. could someone look into this for me please?

Comments

  • James_M
    James_M Posts: 4,514 ✅ Verified Employee Moderator

    Hi & welcome!

    What troubleshooting have you tried?

  • E_3T1ff3
    E_3T1ff3 Posts: 4 Spectator

    Thank you.


    Ive done the following to rectify the issue with no results:

    decreased the resolution from 1920x1080 to 1280x800 as well as adjusted the following settings (which was on HIGH before)

    Manually Reset the Router,

    checked for outages in my area (we are in texas, so Im not sure how the Maui fires effected us, if at all)


    to help with troubleshooting, here's the current computer specs I'm running. (computer is less than a year old)

    ♥Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz  2.90 GHz

    ♥ Installed RAM: 16.0 GB (15.9 GB usable)

    ♥Windows 11 Home

  • James_M
    James_M Posts: 4,514 ✅ Verified Employee Moderator

    Appreciate the reply -

    Can you provide a couple additional tracerts to neutral IP's to see how the traffic flows to them? Suggestions include target.com, water.com (one is busy, one is less busy) and google.com or just 8.8.8.8. Please post the results.

    Thanks!

  • E_3T1ff3
    E_3T1ff3 Posts: 4 Spectator

    Absolutely

    Google.com

     1   <1 ms   <1 ms   <1 ms 2603-8080-f300-daa9-b675-0eff-fe4f-c2b8.res6.spectrum.com [2603:8080:f300:daa9:b675:eff:fe4f:c2b8]

     2   15 ms   14 ms   15 ms 2603-90c5-0003-0145-0000-0000-0000-0001.inf6.spectrum.com [2603:90c5:3:145::1]

     3   19 ms   11 ms   15 ms lag-61.lvoktxad01h.netops.charter.com [2605:6000:0:4::e:4502]

     4   15 ms    6 ms   11 ms lag-20.lvoktxad01r.netops.charter.com [2605:6000:0:4::4:40]

     5   15 ms   13 ms   12 ms lag-21.mcr11snavtxuu.netops.charter.com [2605:6000:0:4::4:10]

     6    *       *      14 ms lag-23.rcr01hstqtx02.netops.charter.com [2605:6000:0:4::34]

     7   27 ms   29 ms   31 ms 2605:6000:0:8::83

     8   34 ms   38 ms   39 ms 2607:f8b0:80e5::1

     9   30 ms   32 ms   28 ms 2001:4860:0:1::2b7c

     10   41 ms   34 ms   35 ms 2001:4860:0:11e3::2

     11   29 ms   33 ms   31 ms 2001:4860::c:4001:e55b

     12   37 ms   36 ms   38 ms 2001:4860::c:4002:17b1

     13   37 ms   48 ms   39 ms 2001:4860::cc:4002:c2d6

     14   33 ms   33 ms   39 ms 2001:4860:0:1::497d

     15    *       *       *    Request timed out.

     16    *       *       *    Request timed out.

     17    *       *       *    Request timed out.

     18    *       *       *    Request timed out.

     19    *       *       *    Request timed out.

     20    *       *       *    Request timed out.

     21    *       *       *    Request timed out.

     22    *       *       *    Request timed out.

     23    *       *       *    Request timed out.

     24   48 ms   37 ms   34 ms rw-in-f104.1e100.net [2607:f8b0:4023:1006::68]


    Trace complete.


    Target.com

     1   <1 ms   <1 ms   <1 ms Cisco01989 [192.168.1.1]

     2   11 ms   13 ms   13 ms cpe-70-119-48-1.tx.res.rr.com [70.119.48.1]

     3   20 ms   32 ms   31 ms lag-61.lvoktxad01h.netops.charter.com [24.28.132.161]

     4   10 ms   11 ms   11 ms lag-20.lvoktxad01r.netops.charter.com [24.175.33.20]

     5   14 ms   20 ms   14 ms lag-21.mcr11snavtxuu.netops.charter.com [24.175.32.144]

     6   21 ms   17 ms   15 ms lag-23.rcr01hstqtx02.netops.charter.com [24.175.32.156]

     7   13 ms   14 ms   21 ms lag-416.hstqtx0209w-bcr00.netops.charter.com [66.109.9.88]

     8   22 ms   20 ms   27 ms lag-22.dllstx976iw-bcr00.netops.charter.com [107.14.19.49]

     9   27 ms   31 ms   28 ms lag-302.pr3.dfw10.netops.charter.com [209.18.43.77]

     10   27 ms   26 ms   28 ms 23.235.41.28

     11   21 ms   23 ms   19 ms 146.75.106.187


    Water.com

     1   <1 ms   <1 ms   <1 ms Cisco01989 [192.168.1.1]

     2   12 ms   14 ms    9 ms cpe-70-119-48-1.tx.res.rr.com [70.119.48.1]

     3   29 ms   53 ms   30 ms lag-61.lvoktxad01h.netops.charter.com [24.28.132.161]

     4   14 ms   11 ms   12 ms lag-20.lvoktxad01r.netops.charter.com [24.175.33.20]

     5   15 ms   31 ms   19 ms lag-21.mcr11snavtxuu.netops.charter.com [24.175.32.144]

     6   13 ms   13 ms   17 ms lag-23.rcr01hstqtx02.netops.charter.com [24.175.32.156]

     7   15 ms   19 ms   19 ms lag-416.hstqtx0209w-bcr00.netops.charter.com [66.109.9.88]

     8   23 ms   20 ms   23 ms lag-412.dllstx976iw-bcr00.netops.charter.com [66.109.6.90]

     9   23 ms   22 ms   24 ms lag-0.pr3.dfw10.netops.charter.com [66.109.5.121]

     10   23 ms   28 ms   37 ms be-205-pe12.1950stemmons.tx.ibone.comcast.net [50.248.116.101]

     11   23 ms   22 ms   22 ms be-3412-cs04.dallas.tx.ibone.comcast.net [96.110.34.109]

     12   19 ms   19 ms   22 ms be-3401-pe01.1950stemmons.tx.ibone.comcast.net [68.86.85.46]

     13   22 ms   19 ms   29 ms 66.208.229.146

     14   33 ms   35 ms   39 ms be21.bbrt01.dal01.flexential.net [148.66.237.198]

     15   44 ms   35 ms   34 ms be136.bbrt01.atl10.flexential.net [148.66.237.93]

     16   33 ms    *      35 ms be10.bbrt02.atl10.flexential.net [148.66.236.253]

     17   52 ms   33 ms   33 ms be166.bbrt01.atl03.flexential.net [148.66.237.101]

     18   33 ms   37 ms   35 ms be31.crrt01.atl03.flexential.net [66.51.8.134]

     19   33 ms   35 ms   37 ms 148.66.237.161

     20    *       *       *    Request timed out.

     21    *       *       *    Request timed out.

     22    *       *       *    Request timed out.

     23    *       *       *    Request timed out.

     24    *       *       *    Request timed out.

     25    *       *       *    Request timed out.

     26    *       *       *    Request timed out.

     27    *       *       *    Request timed out.

     28    *       *       *    Request timed out.

     29    *       *       *    Request timed out.

     30    *       *       *    Request timed out.


    Trace complete.


    and lastly 8.8.8.8.

     1   <1 ms   <1 ms   <1 ms Cisco01989 [192.168.1.1]

     2   15 ms    4 ms   14 ms cpe-70-119-48-1.tx.res.rr.com [70.119.48.1]

     3   28 ms   32 ms   31 ms lag-61.lvoktxad01h.netops.charter.com [24.28.132.161]

     4   10 ms   12 ms   12 ms lag-20.lvoktxad01r.netops.charter.com [24.175.33.20]

     5   15 ms   12 ms   12 ms lag-21.mcr11snavtxuu.netops.charter.com [24.175.32.144]

     6   18 ms   15 ms   15 ms lag-23.rcr01hstqtx02.netops.charter.com [24.175.32.156]

     7   37 ms   37 ms   36 ms 131-150-063-011.inf.spectrum.com [131.150.63.11]

     8   31 ms   35 ms   37 ms 142.251.77.141

     9   36 ms   34 ms   36 ms 216.239.40.47

     10   35 ms   36 ms   34 ms dns.google [8.8.8.8]


    Trace complete.

  • William_M
    William_M Posts: 964 ✅ Verified Employee Moderator

    I'm not seeing any problems from your traceroutes, however if the issue is only happen intermittently it can be hard to catch with it. Will you please try running just a standard ping test? You can use this with the command "ping 8.8.8.8 -t". The -t will make it continue to run until you use Ctrl+C to end it, let it run for at least a few minutes before ending it. You can ping other IPs like your game servers in another command prompt window at the same time so if one spikes you can check what the other is doing.

  • E_3T1ff3
    E_3T1ff3 Posts: 4 Spectator

    ping test from 8.8.8.8

    Pinging 8.8.8.8 with 32 bytes of data:

    Reply from 8.8.8.8: bytes=32 time=37ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=36ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=37ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=39ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=44ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=37ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=35ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=32ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=40ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=39ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=37ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=35ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=35ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=36ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=35ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=36ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=48ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=34ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=36ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=36ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=37ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=33ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=32ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=40ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=36ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=36ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=38ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=36ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=36ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=33ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=36ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=37ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=46ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=33ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=35ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=34ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=34ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=32ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=35ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=38ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=34ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=35ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=34ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=41ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=35ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=39ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=34ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=44ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=33ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=37ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=34ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=42ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=40ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=36ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=35ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=39ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=35ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=33ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=31ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=32ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=32ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=61ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=38ms TTL=57

    Reply from 8.8.8.8: bytes=32 time=42ms TTL=57


    Ping statistics for 8.8.8.8:

       Packets: Sent = 64, Received = 64, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

       Minimum = 31ms, Maximum = 61ms, Average = 36ms

  • William_M
    William_M Posts: 964 ✅ Verified Employee Moderator

    Thanks. Everything look good. I recommend leaving command prompt windows pinging 8.8.8.8 and 37.18.193.31 running, and then play the game. Once you notice your ping spiking in game, check if the command prompts are showing the same.

This discussion has been closed.