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
Options

Unplayable lag and severe stutter

emphatic83emphatic83 Member Posts: 9 Arc User
in Windows and General: PC, Network, and Other Technical Issues
Its been about a week since this has been happening, CS refuses to help me because they say the can't provide support for people using windows 10. The game is pretty unplayable, anyone experienced this and found a way to correct it?.

Up until this started happening I was lucky I suppose, I got the occasional hiccup or mini stutter during peak times but never anything major, recently it has been unplayable, with regular hands and "server not respondings" of 30 second or more, Running a CCA almost always results in me D/C or stalling out until the End.

Here are some videos to illustrate the problem.

Video 1

Video 2

Video 3

Comments

  • Options
    necriemoonnecriemoon Member Posts: 52 Arc User
    edited August 2015
    Yep.
    It was pretty bad tonight. I thought we just had a slew of fixes to improve lag?
    j/k Cryptic. I know you all are working hard to resolve it.

    I wish I could provide some insight as to what was causing it. Here's a video of the second half of my CCA tonight:
    CCA 8/20/15

    EDIT: Playing The Rubberband Man in the background while I watch this video makes me laugh. Enjoy :) P.S. Thanks to Lootcritter for the idea!


    It was so bad, about halfway through I decided it needed to be recorded in case it could provide some useful info. Most of the time when you see my ship spazzing out and twitching I'm not even trying to steer it. I was able to eventually go back towards the CE with mouse steering, but as soon as I got close, I'd loose control. You may also be able to notice about 1 minute in my Tac Team, APO, B:F@W, and EP2W3 were "eaten" i.e. put on cool down, but not used, or at the very least, extremely delayed.

    I'm sad to say that between that and the lag I experienced just trying to move around ESD, it made me close the game for the night. Its been this way since the start of the CE event, though some days are better than others.

    Here's a Trace Route I ran immediately after closing the game (with the formatting cleaned up a bit).
    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  DD-WRT [192.168.1.1]
  2    38 ms    28 ms    20 ms  67.181.72.1
  3    11 ms    10 ms     9 ms  68.87.203.73
  4    13 ms    13 ms    13 ms  68.87.221.61
  5    22 ms    21 ms    20 ms  68.86.94.189
  6     *        *        *     Request timed out.
  7    49 ms    46 ms    47 ms  he-0-15-0-0-cr01.denverqwest.co.ibone.comcast.net [68.86.89.138]
  8    49 ms    48 ms    48 ms  he-0-2-0-3-cr02.denver.co.ibone.comcast.net [68.86.89.29]
  9    50 ms    46 ms    49 ms  ae-13-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.84.30]
 10    48 ms    46 ms    46 ms  te0-0-0-0.rcr11.b006467-1.den01.atlas.cogentco.com [154.54.10.33]
 11    49 ms    48 ms    54 ms  te0-1-0-3.ccr22.den01.atlas.cogentco.com [154.54.83.33]
 12    65 ms    72 ms    64 ms  be2130.ccr22.mci01.atlas.cogentco.com [154.54.26.122]
 13    71 ms    70 ms    82 ms  be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.118]
 14    77 ms    78 ms    79 ms  be2185.ccr22.cle04.atlas.cogentco.com [154.54.43.178]
 15    92 ms    92 ms    92 ms  be2189.ccr22.alb02.atlas.cogentco.com [154.54.43.185]
 16    93 ms    96 ms    94 ms  be2302.ccr22.bos01.atlas.cogentco.com [154.54.43.13]
 17    96 ms    94 ms    95 ms  te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
 18    95 ms    92 ms    93 ms  38.111.40.114
 19    93 ms    95 ms    94 ms  198.49.243.253
 20     *        *        *     Request timed out.
 21    94 ms    96 ms    92 ms  patchserver2.crypticstudios.com [208.95.185.41]


Trace complete.

    My ISP is Comcast. I get 30/12 Mbps speeds, average, though I've seen much higher at times.
    My CPU is an i7 3.4GHz. I'm running Windows 7 with 16 GB or RAM, and using a GTX 760. I don't think it wouldn't be a video card issue, because I was able to record that at 60 FPS.
    To the best of my knowledge, my system stats and bandwidth can not account for the lag shown in the above linked video. All my other network activity tonight, such as streaming video, online gaming with other games, etc. has been smooth as silk.
  • Options
    nyxadrillnyxadrill Member Posts: 1,242 Arc User
    edited August 2015
    I know the guys at Cryptic are working hard on this. Each patch seems to have something relating to it (power changes, etc) and I know they have the added headache of network routing, however it doesn't help peoples attitude towards them when PWE support keep blaming Windows 10 !!!

    That's a pure and simple cop out used by many support desks lately and it doesn't wash with me.

    I honestly think that PWE support doesn't do Bort and his hard working team (or anyone at Cryptic for that matter) any favours.
    server_hamster6.png
  • Options
    necriemoonnecriemoon Member Posts: 52 Arc User
    Tonight I ran CCA at about 8:30 PM Pacific. It was smooth as silk. No stuttering, no eaten abilities, and very fast. Took about 2:40 to complete. Great run. The only think I can figure is there may still be some powers people are using that are causing silly amounts of lag. I can U/L the vid if it would be helpful for comparison against my previous one.
  • Options
    willamsheridanwillamsheridan Member Posts: 1,189 Arc User
    I am having the exact same problem several times a day. But i am pretty sure its not my PC. Tracrer and pingtests don't work. My Hybrid router blocks them and i cant unblock them. But everything else works fine, my connection is up to 29Mbit/
    The long SnRs start around 8-9pm (German time) and go on until around midnight.

    But i don t think the stutter has anything to do with the SnRs. I just played some PvEs and noticed in KSA that it usually happened when some players activated all their abilities to kill the cube.. one on cube was destroyed i didn't have any problem. Until the next cube arrived. And the problems always started when 2 players attacked the Cube with all their skills on.

    So i expect that its a BOff or captain skill and it must be somethng new, a few Months old or so. Maybe Overwhelming Force, mabye Kemocite maybe something else but i think if its a trait, skill or ability its one from the last 2 lockboxes or the recent FEs.

  • Options
    internetonsetaddinternetonsetadd Member Posts: 98 Arc User
    Same issue almost constantly since yesterday. Was only periodic over the last couple of weeks. Similar or better trace numbers than those posted above. Also Comcast. CCA stutters to the point of unplayability. If I don't get disconnected, for all intents and purposes I'm basically AFKing, because I'm contributing nothing, because I can't even steer my ship. I stopped playing for a couple months due to all the ability lag and server problems, and only came back for the event. If this persists I probably won't stick around. Promotions and new content don't outweigh unplayability.
  • Options
    shurato2099shurato2099 Member Posts: 588 Arc User
    I'm in the same boat. Lag and latency started building last night and today I can barely navigate in CCA let alone get any weapons to fire or abilities to activate. Service provider is also Comcast.
  • Options
    stuntpilotstuntpilot Member Posts: 76 Arc User
    Comcast here. Constant SNRs, massive lag. Cannot move character in game more than a few meters ... only to be snapped back to where I was. This all seems very familiar. :(
  • Options
    shurato2099shurato2099 Member Posts: 588 Arc User
    A tracert shows two spikes at cogentco and then a timeout right before reaching the patchserver.
  • Options
    paxfederaticapaxfederatica Member Posts: 1,496 Arc User
    edited August 2015
    I use Comcast too, but have had no issues until tonight. The trace data suggests the issue is closer to Cryptic's end than it is to mine. Here's my tracert data:
    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  10.0.0.1
  2    15 ms    13 ms    13 ms  96.120.48.145
  3     9 ms    19 ms    18 ms  68.85.164.57
  4    19 ms    17 ms    19 ms  69.139.176.222
  5    23 ms    18 ms    18 ms  68.87.174.1
  6    34 ms    31 ms    31 ms  be-13367-cr02.denver.co.ibone.comcast.net [68.86.94.5]
  7    30 ms    28 ms    32 ms  ae-12-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.84.26]
  8    30 ms    42 ms    43 ms  te0-0-0-0.rcr11.b006467-1.den01.atlas.cogentco.com [154.54.10.33]
  9    33 ms    28 ms    30 ms  te0-1-0-3.ccr22.den01.atlas.cogentco.com [154.54.83.33]
 10    50 ms    48 ms    53 ms  be2130.ccr22.mci01.atlas.cogentco.com [154.54.26.122]
 11    39 ms    39 ms    39 ms  be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.118]
 12    48 ms    47 ms    47 ms  be2185.ccr22.cle04.atlas.cogentco.com [154.54.43.178]
 13    58 ms    58 ms    66 ms  be2189.ccr22.alb02.atlas.cogentco.com [154.54.43.185]
 14    64 ms    61 ms    63 ms  be2302.ccr22.bos01.atlas.cogentco.com [154.54.43.13]
 15    71 ms    61 ms    76 ms  te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
 16    71 ms    66 ms    78 ms  38.111.40.114
 17    62 ms    63 ms    63 ms  198.49.243.253
 18     *        *        *     Request timed out.
 19    63 ms    61 ms    68 ms  patchserver2.crypticstudios.com [208.95.185.41]


Trace complete.

    Nettest was completely useless:
    contacting nettest server..timed out
hit return to exit

    Pathping hit a brick wall in the same spot as tracert:
    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
  0  10.0.0.241
  1  10.0.0.1
  2  96.120.48.145
  3  68.85.164.57
  4  69.139.176.222
  5  68.87.174.1
  6  be-13367-cr02.denver.co.ibone.comcast.net [68.86.94.5]
  7  ae-12-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.84.26]
  8  te0-0-0-0.rcr11.b006467-1.den01.atlas.cogentco.com [154.54.10.33]
  9  te0-1-0-3.ccr22.den01.atlas.cogentco.com [154.54.83.33]
 10  be2130.ccr22.mci01.atlas.cogentco.com [154.54.26.122]
 11  be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.118]
 12  be2185.ccr22.cle04.atlas.cogentco.com [154.54.43.178]
 13  be2189.ccr22.alb02.atlas.cogentco.com [154.54.43.185]
 14  be2302.ccr22.bos01.atlas.cogentco.com [154.54.43.13]
 15  te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
 16  38.111.40.114
 17  198.49.243.253
 18     *        *        *
Computing statistics for 425 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           10.0.0.241                                                           0/ 100 =  0%
  1    2ms     0/ 100 =  0%     0/ 100 =  0%  10.0.0.1                                                             0/ 100 =  0%
  2   14ms     0/ 100 =  0%     0/ 100 =  0%  96.120.48.145                                                        0/ 100 =  0%
  3   14ms     0/ 100 =  0%     0/ 100 =  0%  68.85.164.57                                                         0/ 100 =  0%
  4   17ms     0/ 100 =  0%     0/ 100 =  0%  69.139.176.222                                                       0/ 100 =  0%
  5   16ms     0/ 100 =  0%     0/ 100 =  0%  68.87.174.1                                                          0/ 100 =  0%
  6   41ms     0/ 100 =  0%     0/ 100 =  0%  be-13367-cr02.denver.co.ibone.comcast.net [68.86.94.5]               0/ 100 =  0%
  7   43ms     0/ 100 =  0%     0/ 100 =  0%  ae-12-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.84.26]         0/ 100 =  0%
  8   32ms     0/ 100 =  0%     0/ 100 =  0%  te0-0-0-0.rcr11.b006467-1.den01.atlas.cogentco.com [154.54.10.33]    0/ 100 =  0%
  9   40ms     0/ 100 =  0%     0/ 100 =  0%  te0-1-0-3.ccr22.den01.atlas.cogentco.com [154.54.83.33]              0/ 100 =  0%
 10   46ms     0/ 100 =  0%     0/ 100 =  0%  be2130.ccr22.mci01.atlas.cogentco.com [154.54.26.122]                0/ 100 =  0% 
 11  ---     100/ 100 =100%   100/ 100 =100%  be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.118]                 0/ 100 =  0%
 12   32ms     0/ 100 =  0%     0/ 100 =  0%  be2185.ccr22.cle04.atlas.cogentco.com [154.54.43.178]                0/ 100 =  0%
 13   45ms     0/ 100 =  0%     0/ 100 =  0%  be2189.ccr22.alb02.atlas.cogentco.com [154.54.43.185]                0/ 100 =  0%
 14   49ms     0/ 100 =  0%     0/ 100 =  0%  be2302.ccr22.bos01.atlas.cogentco.com [154.54.43.13]                 0/ 100 =  0%
 15   49ms     0/ 100 =  0%     0/ 100 =  0%  te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]   0/ 100 =  0%
 16   48ms     0/ 100 =  0%     0/ 100 =  0%  38.111.40.114                                                        0/ 100 =  0%
 17   65ms     0/ 100 =  0%     0/ 100 =  0%  198.49.243.253

Trace complete.
    ​​
    Post edited by paxfederatica on
    STAR TREK ONLINE: THE PEACEMAKERS
    My Foundry missions | My STO Wiki page | My Twitter home page
  • Options
    kane53kane53 Member Posts: 108 Arc User
    the server lagg is so bad i cant even move my ship
  • Options
    rekurzionrekurzion Member Posts: 697 Arc User
    edited August 2015
    i'm really curious, I see a lot of Comcast (not that there is much of choice anymore), but have you folks upgraded to their newest modem?

    The reason I ask is I have a sneaking suspicion that comcast is throttling their speeds for users still on their docsis 2.0 modems and forcing them to upgrade. it is technically EOL this year
  • Options
    skyylar3skyylar3 Member Posts: 3 Arc User
    I have Comcast but am using my own third-party modem. Anybody having this issue that is not on Comcast?
  • Options
    paxfederaticapaxfederatica Member Posts: 1,496 Arc User
    edited August 2015
    It's not a Comcast issue. As shown in the data posted above, the problem was (and as of now, still is) occurring at the last hop before reaching Cryptic's server, which is long past the Comcast stretch of the trace. Also, my other Internet activities are unaffected. I did a connection speed test and it came back as fast as it's ever been. STO is the only thing that's affected.

    UPDATE: And yet...

    Somehow, in spite of that apparent roadblock, I was able to log in and play this morning with no connection issues whatsoever. I even did an Advanced CE run without any trouble. Afterward, while still logged in, I did another tracert and it still shows the block at the last hop before the Cryptic server. Nettest is also still timing out without producing any data.

    So, it would seem that either tracert and nettest are both somehow producing a "false positive", or STO traffic is now being rerouted around the problem node.​​
    Post edited by paxfederatica on
    STAR TREK ONLINE: THE PEACEMAKERS
    My Foundry missions | My STO Wiki page | My Twitter home page
  • Options
    duncanidaho11duncanidaho11 Member Posts: 7,973 Arc User
    edited August 2015
    paxfederatica wrote: »

    Somehow, in spite of that apparent roadblock, I was able to log in and play this morning with no connection issues whatsoever. I even did an Advanced CE run without any trouble. Afterward, while still logged in, I did another tracert and it still shows the block at the last hop before the Cryptic server. Nettest is also still timing out without producing any data.​​

    Some users are reporting no problems (and the fact that the general forum isn't being clogged with a dozen redundant "the game is down!" messages seems to indicate the same.) You may have just graduated into that category.

    Me, the game still doesn't work and the symptoms are identical to those other users are experiencing. The last time something like this happened, I'll also point out, the second to last hop was also timing out for all affected users. It could be a false positive, but this is the only context I've seen it show up.

    It would probably require networking engineer to adequately explain the problem, but to my dirt-encrusted peasant mind part of a system involved with handling player connections may not be working properly. Maybe its just one piece of hardware, and if you get forced onto it then you're in for an absolutely terrible time. I really don't know, but I can say that this hasn't been fixed yet.
    Bipedal mammal and senior Foundry author.
    Notable missions: Apex [AEI], Gemini [SSF], Trident [AEI], Evolution's Smile [SSF], Transcendence
    Looking for something new to play? I've started building Foundry missions again in visual novel form!
  • Options
    liverwurstliverwurst Member Posts: 4 Arc User
    Having connection issues with STO (and NeverWinter) like the others.

    Per forum instructions:

    Comcast internet service.

    http://www.speedtest.net/my-result/4620464493

    ============

    PS C:\Users\Liver> tracert patchserver.crypticstudios.com

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

    1 <1 ms <1 ms <1 ms 10.0.0.1
    2 10 ms 9 ms 8 ms 96.120.52.181
    3 8 ms 8 ms 9 ms xe-7-1-0-0-sr01.pennington.tn.nash.comcast.net [68.86.150.5]
    4 10 ms 10 ms 9 ms xe-1-1-1-0-ar01.goodslettvll.tn.nash.comcast.net [162.151.9.126]
    5 18 ms 16 ms 18 ms he-1-1-0-7-cr02.56marietta.ga.ibone.comcast.net [68.86.94.69]
    6 36 ms 38 ms 38 ms be-11314-cr01.dallas.tx.ibone.comcast.net [68.86.85.21]
    7 47 ms 49 ms 46 ms be-11317-cr02.denver.co.ibone.comcast.net [68.86.84.230]
    8 46 ms 47 ms 48 ms ae-16-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.84.122]
    9 48 ms 46 ms 47 ms te0-0-1-0.rcr11.b006467-1.den01.atlas.cogentco.com [154.54.13.5]
    10 46 ms 48 ms 46 ms te0-1-0-3.ccr22.den01.atlas.cogentco.com [154.54.83.33]
    11 53 ms 53 ms 53 ms be2130.ccr22.mci01.atlas.cogentco.com [154.54.26.122]
    12 48 ms 47 ms 49 ms be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.118]
    13 61 ms 75 ms 72 ms be2185.ccr22.cle04.atlas.cogentco.com [154.54.43.178]
    14 69 ms 74 ms 71 ms be2189.ccr22.alb02.atlas.cogentco.com [154.54.43.185]
    15 71 ms 72 ms 71 ms be2302.ccr22.bos01.atlas.cogentco.com [154.54.43.13]
    16 72 ms 72 ms 73 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
    17 71 ms 87 ms 71 ms 38.111.40.114
    18 71 ms 71 ms 74 ms 198.49.243.253
    19 * * * Request timed out.
    20 72 ms 71 ms 72 ms patchserver2.crypticstudios.com [208.95.185.41]

    Trace complete.

    ============

    PS C:\Users\Liver> pathping patchserver.crypticstudios.com

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 Orion.homenet.lan [10.0.0.13]
    1 10.0.0.1
    2 96.120.52.181
    3 xe-7-1-0-0-sr01.pennington.tn.nash.comcast.net [68.86.150.5]
    4 xe-1-1-1-0-ar01.goodslettvll.tn.nash.comcast.net [162.151.9.126]
    5 he-1-1-0-7-cr02.56marietta.ga.ibone.comcast.net [68.86.94.69]
    6 be-11314-cr01.dallas.tx.ibone.comcast.net [68.86.85.21]
    7 be-11317-cr02.denver.co.ibone.comcast.net [68.86.84.230]
    8 ae-16-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.84.122]
    9 te0-0-1-0.rcr11.b006467-1.den01.atlas.cogentco.com [154.54.13.5]
    10 te0-1-0-3.ccr22.den01.atlas.cogentco.com [154.54.83.33]
    11 be2130.ccr22.mci01.atlas.cogentco.com [154.54.26.122]
    12 be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.118]
    13 be2185.ccr22.cle04.atlas.cogentco.com [154.54.43.178]
    14 be2189.ccr22.alb02.atlas.cogentco.com [154.54.43.185]
    15 be2302.ccr22.bos01.atlas.cogentco.com [154.54.43.13]
    16 te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
    17 38.111.40.114
    18 198.49.243.253
    19 * * *
    Computing statistics for 450 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Orion.homenet.lan [10.0.0.13]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
    0/ 100 = 0% |
    2 9ms 0/ 100 = 0% 0/ 100 = 0% 96.120.52.181
    0/ 100 = 0% |
    3 12ms 0/ 100 = 0% 0/ 100 = 0% xe-7-1-0-0-sr01.pennington.tn.nash.comcast.net [68.86.150.5]
    0/ 100 = 0% |
    4 17ms 0/ 100 = 0% 0/ 100 = 0% xe-1-1-1-0-ar01.goodslettvll.tn.nash.comcast.net [162.151.9.126]
    0/ 100 = 0% |
    5 18ms 0/ 100 = 0% 0/ 100 = 0% he-1-1-0-7-cr02.56marietta.ga.ibone.comcast.net [68.86.94.69]
    0/ 100 = 0% |
    6 38ms 0/ 100 = 0% 0/ 100 = 0% be-11314-cr01.dallas.tx.ibone.comcast.net [68.86.85.21]
    0/ 100 = 0% |
    7 49ms 0/ 100 = 0% 0/ 100 = 0% be-11317-cr02.denver.co.ibone.comcast.net [68.86.84.230]
    0/ 100 = 0% |
    8 50ms 0/ 100 = 0% 0/ 100 = 0% ae-16-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.84.122]
    0/ 100 = 0% |
    9 53ms 0/ 100 = 0% 0/ 100 = 0% te0-0-1-0.rcr11.b006467-1.den01.atlas.cogentco.com [154.54.13.5]
    0/ 100 = 0% |
    10 52ms 0/ 100 = 0% 0/ 100 = 0% te0-1-0-3.ccr22.den01.atlas.cogentco.com [154.54.83.33]
    0/ 100 = 0% |
    11 47ms 0/ 100 = 0% 0/ 100 = 0% be2130.ccr22.mci01.atlas.cogentco.com [154.54.26.122]
    0/ 100 = 0% |
    12 --- 100/ 100 =100% 100/ 100 =100% be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.118]
    0/ 100 = 0% |
    13 36ms 0/ 100 = 0% 0/ 100 = 0% be2185.ccr22.cle04.atlas.cogentco.com [154.54.43.178]
    0/ 100 = 0% |
    14 49ms 0/ 100 = 0% 0/ 100 = 0% be2189.ccr22.alb02.atlas.cogentco.com [154.54.43.185]
    0/ 100 = 0% |
    15 45ms 0/ 100 = 0% 0/ 100 = 0% be2302.ccr22.bos01.atlas.cogentco.com [154.54.43.13]
    0/ 100 = 0% |
    16 45ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
    0/ 100 = 0% |
    17 45ms 0/ 100 = 0% 0/ 100 = 0% 38.111.40.114
    0/ 100 = 0% |
    18 73ms 0/ 100 = 0% 0/ 100 = 0% 198.49.243.253

    Trace complete.
    PS C:\Users\Liver>

    ============

    nettest:

    contacting nettest server..timed out
    hit return to exit
  • Options
    giannicampanellagiannicampanella Member Posts: 424 Arc User
    Yo, leave the basement for a sec, and allow your eyes to adjust to the sunlight. Level3 ISP of ISPs jengaed. The interwebz broke this time, not Cryptic servers. There's a first time for everything.
    Greenbird
  • Options
    nukem001nukem001 Member Posts: 19 Arc User
    I got in to the selection screen and I am being disconnected or timed out by Cryptic servers. There is no issues to reach them. 10 minutes I get in and get booted. This is proof that cryptic really needs to pull down the servers and attempt a reboot to see if it clears what ever is happening. Since they wont then what cryptic actually needs to do today is provide all users 1 crystal entity for the event since we cannot log in due to a issue on there end. If they don't then then we have our answer that they really don't care about the players.
  • Options
    ovrkylovrkyl Member Posts: 309 Arc User
    STO%20technical%20difficulties%20MEME.png
    characters
    This is my signature. There are many like it, but this one is mine.
  • Options
    janack42janack42 Member Posts: 8 Arc User
    Found this thread over on the Neverwinter side of Cryptic. Disseminating information for others.

    http://www.arcgames.com/en/forums/neverwinter/#/discussion/1203025/connection-issues-read-this-please
  • Options
    ovrkylovrkyl Member Posts: 309 Arc User
    Started getting repeating lag/rubberbanding surges during the crystal event tonight. Had noticed earlier this week that the 'net seemed to have a repeating lag spike every 4 seconds or so, and a fresh reboot of computer and modem fixed it. Tried that again, then did this ping series and tracert immediately afterward without the game or browser running (completely clean fresh restarts on both modem and computer and have not started the game back up yet). Still showing lag spikes in repetition even with no game running.

    Ping was done as a series of 100 to get a nice noticeable trend and even percentage on results.

    Tracert shows the suspected culprit(s).

    Times in red and yellow are relative to Cryptic's stated thresholds for pings as per these forums.
    Microsoft Windows [Version 10.0.10240]
    (c) 2015 Microsoft Corporation. All rights reserved.

    C:\Users\█████>ping -n 100 patchserver.crypticstudios.com

    Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=363ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=161ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=366ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=156ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=253ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=190ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=95ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=95ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=114ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=254ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=193ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=99ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=94ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=255ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=190ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=97ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=93ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=255ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=192ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=106ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=89ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=315ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=95ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=315ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=95ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=222ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=98ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=362ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=111ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=98ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=273ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=93ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=174ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=283ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=95ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=89ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=105ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=289ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=93ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=94ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=315ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=125ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=121ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=98ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=95ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=330ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=123ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=101ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=208ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=236ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=89ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=268ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=108ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=93ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=175ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=119ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=94ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=135ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=299ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=89ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=221ms TTL=45

    Ping statistics for 208.95.185.41:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 89ms, Maximum = 366ms, Average = 139ms

    C:\Users\█████>tracert patchserver.crypticstudios.com

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

    1 1 ms 1 ms 2 ms ██.█.█.█
    2 * * * Request timed out.
    3 8 ms 8 ms 76 ms xe-2-3-0-0-sur04.longview.wa.bverton.comcast.net [162.151.125.141]
    4 13 ms 10 ms 14 ms ae-56-0-ar03.troutdale.or.bverton.comcast.net [68.87.222.209]
    5 52 ms 18 ms 70 ms he-0-4-0-4-cr02.seattle.wa.ibone.comcast.net [68.86.94.121]
    6 21 ms 16 ms 15 ms he-0-12-0-1-pe04.seattle.wa.ibone.comcast.net [68.86.82.230]
    7 16 ms 17 ms 15 ms as174.seattle.wa.ibone.comcast.net [66.208.228.110]
    8 44 ms 44 ms 45 ms be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.198]
    9 45 ms 202 ms 202 ms be2126.ccr21.den01.atlas.cogentco.com [154.54.25.65]
    10 67 ms 67 ms 67 ms be2128.ccr21.mci01.atlas.cogentco.com [154.54.25.174]
    11 67 ms 71 ms 68 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
    12 77 ms 79 ms 73 ms be2351.ccr21.cle04.atlas.cogentco.com [154.54.44.86]
    13 91 ms 119 ms 95 ms be2009.ccr21.alb02.atlas.cogentco.com [154.54.25.89]
    14 676 ms 557 ms 566 ms be2299.ccr21.bos01.atlas.cogentco.com [154.54.43.9]
     15 92 ms 98 ms 97 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.134]
    16 206 ms 236 ms 104 ms 38.111.40.114
    17 90 ms 261 ms 226 ms 198.49.243.253
    18 * * * Request timed out.
    19 186 ms 205 ms 201 ms patchserver2.crypticstudios.com [208.95.185.41]

    Trace complete.
    There you have it. Straight through the Valley of the Shadow of Death right up to the Gates of Hell (and not a damn thing to do with Comcast this time).

    FFS Cryptic/PWE, will you please get rid of that PoS Cogent already?
    This is my signature. There are many like it, but this one is mine.
  • Options
    dalolorndalolorn Member Posts: 3,655 Arc User
    ovrkyl wrote: »
    Started getting repeating lag/rubberbanding surges during the crystal event tonight. Had noticed earlier this week that the 'net seemed to have a repeating lag spike every 4 seconds or so, and a fresh reboot of computer and modem fixed it. Tried that again, then did this ping series and tracert immediately afterward without the game or browser running (completely clean fresh restarts on both modem and computer and have not started the game back up yet). Still showing lag spikes in repetition even with no game running.

    Ping was done as a series of 100 to get a nice noticeable trend and even percentage on results.

    Tracert shows the suspected culprit(s).

    Times in red and yellow are relative to Cryptic's stated thresholds for pings as per these forums.
    Microsoft Windows [Version 10.0.10240]
    (c) 2015 Microsoft Corporation. All rights reserved.

    C:\Users\█████>ping -n 100 patchserver.crypticstudios.com

    Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=363ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=161ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=366ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=156ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=253ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=190ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=95ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=95ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=114ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=254ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=193ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=99ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=94ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=255ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=190ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=97ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=93ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=255ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=192ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=106ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=89ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=315ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=95ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=315ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=95ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=222ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=98ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=362ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=111ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=98ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=273ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=93ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=174ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=283ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=95ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=89ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=105ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=289ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=93ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=94ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=315ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=125ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=121ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=98ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=95ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=330ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=123ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=101ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=208ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=236ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=89ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=268ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=108ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=93ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=175ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=119ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=94ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=135ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=299ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=90ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=89ms TTL=45
    Reply from 208.95.185.41: bytes=32 time=221ms TTL=45

    Ping statistics for 208.95.185.41:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 89ms, Maximum = 366ms, Average = 139ms

    C:\Users\█████>tracert patchserver.crypticstudios.com

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

    1 1 ms 1 ms 2 ms ██.█.█.█
    2 * * * Request timed out.
    3 8 ms 8 ms 76 ms xe-2-3-0-0-sur04.longview.wa.bverton.comcast.net [162.151.125.141]
    4 13 ms 10 ms 14 ms ae-56-0-ar03.troutdale.or.bverton.comcast.net [68.87.222.209]
    5 52 ms 18 ms 70 ms he-0-4-0-4-cr02.seattle.wa.ibone.comcast.net [68.86.94.121]
    6 21 ms 16 ms 15 ms he-0-12-0-1-pe04.seattle.wa.ibone.comcast.net [68.86.82.230]
    7 16 ms 17 ms 15 ms as174.seattle.wa.ibone.comcast.net [66.208.228.110]
    8 44 ms 44 ms 45 ms be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.198]
    9 45 ms 202 ms 202 ms be2126.ccr21.den01.atlas.cogentco.com [154.54.25.65]
    10 67 ms 67 ms 67 ms be2128.ccr21.mci01.atlas.cogentco.com [154.54.25.174]
    11 67 ms 71 ms 68 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
    12 77 ms 79 ms 73 ms be2351.ccr21.cle04.atlas.cogentco.com [154.54.44.86]
    13 91 ms 119 ms 95 ms be2009.ccr21.alb02.atlas.cogentco.com [154.54.25.89]
    14 676 ms 557 ms 566 ms be2299.ccr21.bos01.atlas.cogentco.com [154.54.43.9]
     15 92 ms 98 ms 97 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.134]
    16 206 ms 236 ms 104 ms 38.111.40.114
    17 90 ms 261 ms 226 ms 198.49.243.253
    18 * * * Request timed out.
    19 186 ms 205 ms 201 ms patchserver2.crypticstudios.com [208.95.185.41]

    Trace complete.
    There you have it. Straight through the Valley of the Shadow of Death right up to the Gates of Hell (and not a damn thing to do with Comcast this time).

    FFS Cryptic/PWE, will you please get rid of that PoS Cogent already?

    Well, having experienced severe connection problems a few minutes ago, I ran a tracert of my own. Almost everything had a ping of 200-300 ms, with a few exceptions. (This might have something to do with me being in Europe.)

    The only hops to exceed this were Cogent or anonymous post-Cogent hops, which timed out on one ping, once timed out on two pings, and (much like your own) timed out on all three pings in the last pre-Cryptic hop. Mind you, the first half of the Cogent section went fairly well.
    Infinite possibilities have implications that could not be completely understood if you turned this entire universe into a giant supercomputer.p3OEBPD6HU3QI.jpg
Sign In or Register to comment.