test content
  • Games
  • Social
  • Arc News
  • Support
  • Zen
What is the Arc Client?
Install Arc
Forums > Home› Support› PC, Network, and Other Technical Issues› Windows and General: PC, Network, and Other Technical Issues

Unplayable Lag

talekeepertalekeeper Member Posts: 7 Arc User
edited July 2014 in Windows and General: PC, Network, and Other Technical Issues
This has only started happening the past couple of days, possibly because of a recent patch, but there's been unexplainable, massive lag spikes for no apparent reason - I was doing a STF and I literally lag for minutes at a time. I'd like some sort of explanation for this, since I ran a speedtest to check if it's my connection (It's not. I'm getting 10 ping, 20 mb down, 20 mb up).

Can someone please explain why the servers can't handle 10 people in a STF?
Post edited by talekeeper on

Comments

  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited July 2014
    talekeeper wrote: »
    ...
    Can someone please explain why the servers can't handle 10 people in a STF?

    So did you check if your ISP can handle the connection to the STO Servers ??? Take a look at this thread, then post some network diagnostic results... http://sto-forum.perfectworld.com/showthread.php?t=225155
  • talekeepertalekeeper Member Posts: 7 Arc User
    edited July 2014
    Tracert:

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:

    1 2 ms 2 ms 2 ms fnbnij31.asahi-net.or.jp [202.224.33.143]
    2 2 ms 2 ms 5 ms tkybi1-v5.asahi-net.or.jp [202.224.33.129]
    3 3 ms 3 ms 3 ms tkyni91.asahi-net.or.jp [202.224.32.91]
    4 3 ms 3 ms 3 ms xe-0-2-0-30.r00.tokyjp05.jp.bb.gin.ntt.net [61.1
    20.146.29]
    5 4 ms 5 ms 3 ms ae-10.r20.tokyjp05.jp.bb.gin.ntt.net [129.250.4.
    108]
    6 98 ms 100 ms 106 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.3.1
    2]
    7 109 ms 109 ms 109 ms ae-1.r05.sttlwa01.us.bb.gin.ntt.net [129.250.5.4
    7]
    8 101 ms 100 ms 101 ms be3048.ccr21.sea02.atlas.cogentco.com [154.54.11
    .9]
    9 123 ms 125 ms 123 ms be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.
    198]
    10 134 ms 133 ms 134 ms be2127.ccr22.den01.atlas.cogentco.com [154.54.25
    .69]
    11 150 ms 150 ms 150 ms be2130.ccr22.mci01.atlas.cogentco.com [154.54.26
    .122]
    12 164 ms 163 ms 163 ms be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.
    118]
    13 185 ms 184 ms 184 ms be2138.ccr22.bos01.atlas.cogentco.com [154.54.43
    .202]
    14 186 ms 186 ms 186 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
    130]
    15 197 ms 197 ms 196 ms 38.111.40.114
    16 179 ms 189 ms 186 ms patchserver2.crypticstudios.com [208.95.185.41]


    Nettest Flat out fails. Pings at 176.9, Times out port 80, 443, and stalls on port 7255.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited July 2014
    talekeeper wrote: »
    ...

    Nettest Flat out fails. Pings at 176.9, Times out port 80, 443, and stalls on port 7255.

    If 'Net Test' fails, thats very bad. And since you're connecting from Japan, and the majority of the Trans-Pacific cable links are over subscribed for Internet traffic, this implies what the problem might be...

    Try using the 'pathping' command (which uses the same syntax as the 'tracert' command) to see if you have a problem with 'packet drop', either lost or thrown away by the ISP and Internet Backbone provider...
  • talekeepertalekeeper Member Posts: 7 Arc User
    edited July 2014
    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 Icewind [110.4.205.201]
    1 fnbnij2.asahi-net.or.jp [211.13.148.15]
    2 fnbnip-ge0.asahi-net.or.jp [211.13.148.30]
    3 tkybi1-v5.asahi-net.or.jp [202.224.33.129]
    4 tkyni91.asahi-net.or.jp [202.224.32.91]
    5 xe-0-2-0-30.r00.tokyjp05.jp.bb.gin.ntt.net [61.120.146.29]
    6 ae-10.r20.tokyjp05.jp.bb.gin.ntt.net [129.250.4.108]
    7 ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.3.12]
    8 ae-1.r05.sttlwa01.us.bb.gin.ntt.net [129.250.5.47]
    9 be3048.ccr21.sea02.atlas.cogentco.com [154.54.11.9]
    10 be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.198]
    11 be2127.ccr22.den01.atlas.cogentco.com [154.54.25.69]
    12 be2130.ccr22.mci01.atlas.cogentco.com [154.54.26.122]
    13 * te8-8.ccr01.stl03.atlas.cogentco.com [154.54.6.254]
    14 te0-1-0-28.ccr42.ord01.atlas.cogentco.com [154.54.27.29]
    15 be2138.ccr22.bos01.atlas.cogentco.com [154.54.43.202]
    16 te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
    17 38.111.40.114
    18 208.95.185.41

    Computing statistics for 450 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Icewind [110.4.205.201]
    0/ 100 = 0% |
    1 3ms 0/ 100 = 0% 0/ 100 = 0% fnbnij2.asahi-net.or.jp [211.13.14
    8.15]
    0/ 100 = 0% |
    2 2ms 0/ 100 = 0% 0/ 100 = 0% fnbnip-ge0.asahi-net.or.jp [211.13
    .148.30]
    0/ 100 = 0% |
    3 3ms 0/ 100 = 0% 0/ 100 = 0% tkybi1-v5.asahi-net.or.jp [202.224
    .33.129]
    0/ 100 = 0% |
    4 4ms 0/ 100 = 0% 0/ 100 = 0% tkyni91.asahi-net.or.jp [202.224.3
    2.91]
    0/ 100 = 0% |
    5 4ms 0/ 100 = 0% 0/ 100 = 0% xe-0-2-0-30.r00.tokyjp05.jp.bb.gin
    .ntt.net [61.120.146.29]
    0/ 100 = 0% |
    6 9ms 0/ 100 = 0% 0/ 100 = 0% ae-10.r20.tokyjp05.jp.bb.gin.ntt.n
    et [129.250.4.108]
    0/ 100 = 0% |
    7 103ms 4/ 100 = 4% 4/ 100 = 4% ae-2.r20.sttlwa01.us.bb.gin.ntt.ne
    t [129.250.3.12]
    0/ 100 = 0% |
    8 109ms 0/ 100 = 0% 0/ 100 = 0% ae-1.r05.sttlwa01.us.bb.gin.ntt.ne
    t [129.250.5.47]
    0/ 100 = 0% |
    9 96ms 0/ 100 = 0% 0/ 100 = 0% be3048.ccr21.sea02.atlas.cogentco.
    com [154.54.11.9]
    0/ 100 = 0% |
    10 --- 100/ 100 =100% 100/ 100 =100% be2085.ccr21.slc01.atlas.cogentco.
    com [154.54.2.198]
    0/ 100 = 0% |
    11 148ms 0/ 100 = 0% 0/ 100 = 0% be2127.ccr22.den01.atlas.cogentco.
    com [154.54.25.69]
    0/ 100 = 0% |
    12 143ms 0/ 100 = 0% 0/ 100 = 0% be2130.ccr22.mci01.atlas.cogentco.
    com [154.54.26.122]
    5/ 100 = 5% |
    13 --- 100/ 100 =100% 95/ 100 = 95% te8-8.ccr01.stl03.atlas.cogentco.c
    om [154.54.6.254]
    0/ 100 = 0% |
    14 154ms 6/ 100 = 6% 1/ 100 = 1% te0-1-0-28.ccr42.ord01.atlas.cogen
    tco.com [154.54.27.29]
    0/ 100 = 0% |
    15 191ms 5/ 100 = 5% 0/ 100 = 0% be2138.ccr22.bos01.atlas.cogentco.
    com [154.54.43.202]
    0/ 100 = 0% |
    16 --- 100/ 100 =100% 95/ 100 = 95% te4-2.ccr01.bos06.atlas.cogentco.c
    om [66.28.4.254]
    0/ 100 = 0% |
    17 192ms 5/ 100 = 5% 0/ 100 = 0% 38.111.40.114
    1/ 100 = 1% |
    18 179ms 6/ 100 = 6% 0/ 100 = 0% 208.95.185.41


    It fixed itself a little earlier during the day, and now it's back. And I see it's dropping packets on a couple of the jumps, though I'm not entirely sure what this means.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited July 2014
    talekeeper wrote: »
    ...

    It fixed itself a little earlier during the day, and now it's back. And I see it's dropping packets on a couple of the jumps, though I'm not entirely sure what this means.

    In short, 'dropped packets' will cause lag (due to the Client sending a request to resend the missing data packet, then waiting for the replacement data to arrive) and broken connections (if too many request to resend data attempt fail, the socket is declared dead and is closed)

    'dropped packets' are usually associated with excessive network load, though failing hardware can also trigger this. And this is why the problem is intermittent, as network load will vary from hour to hour and minute to minute...

    The only solution that you could really try, is the 'Euro Proxy' option in the Launcher Option Menu, and see if the Network Path around the other side of the world is any better then the Trans-Pacific links...(Probably won't work, but it doesn't hurt to try, as you can always change it back...)
  • originalboodahoriginalboodah Member Posts: 30 Arc User
    edited July 2014
    I've been noticing crippling lag spikes for the last month. Today, I have some information for anyone reading this.

    2 sequential tracerts to the patch server yielded this result:

    4 52 ms 49 ms 48 ms ge-4-1-0.mpr1.iad10.us.mfnx.net [206.126.236.86]
    5 50 ms 51 ms 54 ms ae11.cr1.dca2.us.above.net [64.125.30.65]
    6 51 ms 50 ms 49 ms ae5.cr2.dca2.us.above.net [64.125.20.190]
    7 88 ms 61 ms 60 ms ae8.mpr4.bos2.us.above.net.29.125.64.in-addr.arpa [64.125.29.33]
    8 61 ms * 63 ms ae2.mpr3.bos2.us.above.net [64.125.25.41]
    9 63 ms 62 ms 62 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
    10 61 ms 63 ms 63 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
    11 64 ms 69 ms 70 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    12 57 ms 57 ms 61 ms patchserver2.crypticstudios.com [208.95.185.41]



    4 49 ms 48 ms 49 ms ge-4-1-0.mpr1.iad10.us.mfnx.net [206.126.236.86]
    5 61 ms 50 ms 56 ms ae11.cr1.dca2.us.above.net [64.125.30.65]
    6 73 ms 66 ms 69 ms ae5.cr2.dca2.us.above.net [64.125.20.190]
    7 61 ms 64 ms 61 ms ae8.mpr4.bos2.us.above.net.29.125.64.in-addr.arpa [64.125.29.33]
    8 62 ms 60 ms 62 ms ae2.mpr3.bos2.us.above.net [64.125.25.41]
    9 * * * Request timed out.
    10 66 ms 66 ms 63 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
    11 63 ms 72 ms 69 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    12 69 ms 61 ms 67 ms patchserver2.crypticstudios.com [208.95.185.41]


    You'll notice that one of the links in the chain went MIA in the second run.
    A simple google search for the name of the offending link yielded some interesting results

    http://us.battle.net/wow/en/forum/topic/13019162177 - Battle.net
    http://forums.na.leagueoflegends.com/board/showthread.php?t=4664008 - League of Legends
    http://nw-forum.perfectworld.com/showthread.php?185612-Feedback-Lag-and-Rubberbanding/page54 - Neverwinter

    During subsequent tracerts, the same link occasionally went missing.

    Just stuff I've noticed from my own machine.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited July 2014
    originalboodah wrote: »
    I've been noticing crippling lag spikes for the last month. Today, I have some information for anyone reading this.

    2 sequential tracerts to the patch server yielded this result:

    ....

    Though the latency values are well below the recommended upper limit of 180ms, so that, by itself, is not the issue...

    Now if you were to post the 'Path Ping' results, that would check for 'dropped packets' on your connection, that would provide much more useful information...
  • tanthotantho Member Posts: 10 Arc User
    edited July 2014
    grouchyotaku wrote: »
    So did you check if your ISP can handle the connection to the STO Servers ??? Take a look at this thread, then post some network diagnostic results... http://sto-forum.perfectworld.com/showthread.php?t=225155

    Well I did these 2 tests and everything was well below the minimums. In the last 3 weeks I have dc'd more than I have in 3 years of playing this game.

    The very last suggestion:

    Sporadic ISP Issue Fix:
    The below is not guaranteed to work but might help solve some issues with your ISP. Using the Post Office analogy, this is like getting a new address and having mail delivered there.
    Renew IP Address
    Go to Start Menu
    Search for cmd
    Right-click and "Run as Administrator"
    Type the following: ipconfig /release
    Hit Enter
    Now, type ipconfig /renew
    Hit Enter

    I did this and for 3 hours I experienced not a bit of lag, rubberbanding, dc'ing.
    I hope this was the fix I needed. Otherwise I have been told by several folks that a full uninstall / reinstall might be the only other solution.
    Thanks OP.
Sign In or Register to comment.