test content
What is the Arc Client?
Install Arc

Latency Investigations

13»

Comments

  • zorander6zorander6 Member Posts: 130 Arc User
    zorander6 wrote: »
    Would wireshark logs help at all? If so I can set some up next time I play and gather logs but would need to know where to send them. I know you are less focused on network now but since this seems to be an amorphous issue it may help.
    If you do, could you privately message that info?

    Sure though the logs can get rather large fairly quickly. I can put them in dropbox or something for you. May be this weekend before I can do it though but if I have time tonight I'll set a run up.
  • jennyward1985jennyward1985 Member Posts: 48 Arc User
    edited January 2016
    Ive been having terrible lag and rubberbanding since the last patch on 14.01.2016. There nothing wrong with my system and ive never had problems with this much lag before. its got to the point that I cant do anything PVE wise with it being that bad.

    I dont know if other people in Europe are having the same issue but im in the UK if its any help.

    Microsoft Windows [Version 10.0.10586]
    (c) 2015 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>tracert patchserver.crypticstudios.com

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

    1 7 ms 19 ms 10 ms cpc1-gran4-2-0-gw.12-1.cable.virginm.net [62.252.166.1]
    2 9 ms 8 ms 10 ms nott-core-2a-ae2-2860.network.virginmedia.net [62.255.214.13]
    3 * * * Request timed out.
    4 11 ms 10 ms 20 ms leed-bb-1b-ae1-0.network.virginmedia.net [62.254.42.122]
    5 26 ms 17 ms 18 ms 213.152.245.53
    6 27 ms 17 ms 19 ms ae6.mpr3.lhr3.uk.zip.zayo.com [64.125.21.21]
    7 119 ms 91 ms 87 ms ae27.cs1.lhr15.uk.eth.zayo.com [64.125.30.234]
    8 90 ms 89 ms 104 ms ae0.cs1.lhr11.uk.eth.zayo.com [64.125.29.118]
    9 117 ms 85 ms 93 ms ae5.cs1.lhr11.uk.eth.zayo.com [64.125.29.126]
    10 88 ms 86 ms 88 ms ae27.cr1.lga5.us.zip.zayo.com [64.125.30.251]
    11 87 ms 87 ms 91 ms ae7.mpr3.bos2.us.zip.zayo.com [64.125.21.225]
    12 87 ms 89 ms 87 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
    13 88 ms 92 ms 90 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
    14 91 ms 89 ms 87 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    15 88 ms 91 ms 105 ms 198.49.243.250
    16 752 ms 852 ms 851 ms 198.49.243.253
    17 * * * Request timed out.
    18 89 ms 87 ms 86 ms patchserver2.crypticstudios.com [208.95.185.41]

    Trace complete.
    Post edited by jennyward1985 on
  • pottsey5gpottsey5g Member Posts: 4,251 Arc User
    edited January 2016
    Update today:

    Investigations don't seem to show network and server side as particularly the source of the "Latency". Latency reports happen in random geo locations and the time is random (specifically indicating that it's not linked to peak time when we have the most players on). We've talked to our Boston team and they've been stable for our 7 day testing period; there hasn't been any congestion.

    We're still keeping an eye on it in terms of network issues, however I'm turning more of my eye towards software side. 19% of our current reports mention that lag happens in STF content which strongly suggests my attention to head towards software.

    ~Morrigan "LaughingTrendy"
    Have you looked at SB24? It used to run smooth now is a lag mess even on low server population times or with few people in the instant. Even a high end PC that used to run SB24 smooth is now a lag mess. I can believe its not congestion as my main play time is when the server numbers are at the lowest. The lag appears to be at random times but daily along with long load times and does not appear to be related to my connection, PC specs or congestion.

    My CPU is 6 full cores (12 threads) running at 4.2ghz with 16GB of ram on a fast SSD with a 330mb connection. Over the past year STO has been getting lower and lower FPS and worse lag. Star Base 24 is where I noticed it the worst what was 60fps+ is now 5fps or worse. Same for loading into Earth Space dock the load screen often sticks in the 90% range.
  • doyouwdoyouw Member Posts: 200 Arc User
    ISP : K-Net
    Geo : Dunkerque (France)
    time : 14:28 (GMT+2)


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

    Détermination de l'itinéraire vers patchserver.crypticstudios.com [208.95.185.41
    ]
    avec un maximum de 30 sauts :

    1 <1 ms <1 ms <1 ms KBOX [192.168.1.1]
    2 <1 ms <1 ms <1 ms 172.16.100.13
    3 <1 ms <1 ms <1 ms 172.16.100.25
    4 2 ms 2 ms 2 ms border1-lyonix.kwaoo.net [178.250.208.21]
    5 12 ms 12 ms 12 ms gi0-0-0-18.328.agr11.lys01.atlas.cogentco.com [1
    49.6.118.145]
    6 12 ms 12 ms 12 ms te0-0-0-7.rcr21.lys01.atlas.cogentco.com [130.11
    7.2.1]
    7 19 ms 20 ms 19 ms be2472.ccr42.par01.atlas.cogentco.com [130.117.4
    9.121]
    8 26 ms 26 ms 26 ms be12489.ccr42.lon13.atlas.cogentco.com [154.54.5
    7.69]
    9 33 ms 33 ms 33 ms be2491.ccr22.lpl01.atlas.cogentco.com [154.54.39
    .117]
    10 99 ms 99 ms 99 ms be2387.ccr22.bos01.atlas.cogentco.com [154.54.44
    .165]
    11 99 ms 99 ms 99 ms te0-0-0-0.rcr12.b002133-1.bos01.atlas.cogentco.c
    om [66.28.4.254]
    12 97 ms 97 ms 97 ms 38.104.252.70
    13 95 ms 95 ms 95 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
    1]
    14 95 ms 95 ms 95 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
    61.78]
    15 98 ms 98 ms 98 ms 198.49.243.250
    16 838 ms 766 ms 851 ms 198.49.243.253
    17 * * * Délai d'attente de la demande dépassé.
    18 94 ms 94 ms 93 ms patchserver2.crypticstudios.com [208.95.185.41]


    Itinéraire déterminé.

    looks like cogentco.com and crypticstudios.com have realy slow servers/network hardware...
    Dark Side (KDF)
    HOUSE OF BORG
    "I am FLATULUS of Borg, Resistance if Futile! Prepare to pull my finger!"

    cube.jpg
  • pwlaughingtrendypwlaughingtrendy Member Posts: 2,966 Arc User
    edited January 2016
    Update for everyone:

    We've adjusted (and making further) changes and 198.49.243.253 should be different in regards to latency. That being said, we're still going to be investigating latency issues as a whole and I am committed to further investigations. I have and always will be your friend, everyone. I'm on your side.

    Morrigan
  • comrademococomrademoco Member Posts: 1,694 Bug Hunter
    Ty ty ty ty ty ty ty ty ty a bunch trendy

    XD

    It means that I might be able to run hours with out crashing or SNR my way across the galaxy .... YAY!
    6tviTDx.png

  • ddesjardinsddesjardins Member Posts: 3,056 Media Corps
    Update for everyone:

    We've adjusted (and making further) changes and 198.49.243.253 should be different in regards to latency. That being said, we're still going to be investigating latency issues as a whole and I am committed to further investigations. I have and always will be your friend, everyone. I'm on your side.

    Morrigan

    Why did I suddenly get the image of you dying from radiation burns behind a glass wall? Oh yeah, wrong use of the quote on my part. Whew! Thank the Gods.

  • primar13primar13 Member Posts: 1,896 Bug Hunter
    edited January 2016
    Update for everyone:

    We've adjusted (and making further) changes and 198.49.243.253 should be different in regards to latency. That being said, we're still going to be investigating latency issues as a whole and I am committed to further investigations. I have and always will be your friend, everyone. I'm on your side.

    Morrigan

    Why did I suddenly get the image of you dying from radiation burns behind a glass wall? Oh yeah, wrong use of the quote on my part. Whew! Thank the Gods.

    Its all that Nasty Nasty Reddit Radiation.... It Burns! It.... BUUUUUUURNS!

    LOLOL
  • pwlaughingtrendypwlaughingtrendy Member Posts: 2,966 Arc User
    edited January 2016
    Update for everyone:

    We've adjusted (and making further) changes and 198.49.243.253 should be different in regards to latency. That being said, we're still going to be investigating latency issues as a whole and I am committed to further investigations. I have and always will be your friend, everyone. I'm on your side.

    Morrigan

    Why did I suddenly get the image of you dying from radiation burns behind a glass wall? Oh yeah, wrong use of the quote on my part. Whew! Thank the Gods.
    Because I care.
  • jdfosterrocksjdfosterrocks Member Posts: 74 Arc User
    so far the fix from today works. i haven't seen .253 have triple digits, even around prime time for the east coast.
  • rebuilthk47rebuilthk47 Member Posts: 94 Arc User
    (The useful stuff is in bold. The rest is for fun/cringing. Read and find out why.)

    Informative: ISP - Ruralcomm (they use Cogent)
    Geo Location - Greenville, Il
    Date + Time of Day - Every day. After 1:00 P.M. on Weekdays (Monday-Friday), all day on Weekends (Saturday and Sunday).

    I get major lag issues in STFs like Crystalline and in both the Borg and Tholian, worse in the Tholian, Red Alerts.


    Useless Information: To be fair, Ruralcomm is staffed by stupid people. Not ignorant, stupid. They believe that the false information about how the internet works are fact (like more speed means better latency) and that it is impossible to use ping -t while doing anything else on a 1.5Mb connection. I was also asked while using VoIP that is using the router to talk to "tech support" to check my router to make sure the internet in wire is in the right port to try and solve latency issues after having informed "tech support" of my talking to them using VoIP that was currently using said router. (Has the definition of "stupid" been met yet?) Those are a few of many examples. And they're losing business.

    Conclusion: Despite this, however, I have noticed a major discrepancy between lag in TOR when these lag spikes hit in STO which leads me to the conclusion that it is not Idiotcomm, but something else.
  • swamarianswamarian Member Posts: 1,506 Arc User
    edited January 2016
    Time 4:44 CST, Sunday January 25 2016
    ISP: Comcast
    Location: Houston, Tx

    I was cycling through my characters, doffing, admiraling, and moving them around maps, until I got to Innozu@swamarian, on DS9#2. Running from the beam in location to the bank repeatedly threw her into the tailor next door. Other characters appeared to be frozen or stuttering as well. I hadn't had any issues until I got to her.

    Also, the forums appeared to be down at the time.
    Post edited by swamarian on
  • supergaminggeeksupergaminggeek Member Posts: 616 Arc User
    ISP - AT&T
    Geo - California
    Date & Time - 16:00-17:00 PST (GMT -08:00)
  • cabldawgcabldawg Member Posts: 18 Arc User
    edited January 2016
    ISP - Charter
    Geo Location - Wenatchee, Wa
    Date + Time of Day - 1/26/2016 5pm (intermittent over the last year)
    Microsoft Windows [Version 10.0.10586]
    (c) 2015 Microsoft Corporation. All rights reserved.

    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 3 ms <1 ms 192.168.1.1
    2 7 ms 6 ms 13 ms 10.106.21.1
    3 15 ms 7 ms 7 ms dtr01wntcwa-tge-0-1-0-3.wntc.wa.charter.com [96.34.106.240]
    4 18 ms 9 ms 9 ms dtr01yakmwa-bue-2.yakm.wa.charter.com [96.34.104.66]
    5 12 ms 11 ms 11 ms bbr01yakmwa-bue-1.yakm.wa.charter.com [96.34.105.230]
    6 40 ms 38 ms 40 ms bbr02snjsca-bue-3.snjs.ca.charter.com [96.34.2.148]
    7 34 ms 35 ms 35 ms te0-7-0-8.ccr21.sjc03.atlas.cogentco.com [38.104.139.113]
    8 32 ms 34 ms 34 ms be2047.ccr22.sjc01.atlas.cogentco.com [154.54.5.113]
    9 35 ms 42 ms 38 ms be2165.ccr22.sfo01.atlas.cogentco.com [154.54.28.65]
    10 68 ms 71 ms 72 ms be2133.ccr22.mci01.atlas.cogentco.com [154.54.30.66]
    11 74 ms 74 ms 76 ms be2832.ccr42.ord01.atlas.cogentco.com [154.54.44.170]
    12 90 ms 89 ms 87 ms be2718.ccr22.cle04.atlas.cogentco.com [154.54.7.130]
    13 99 ms 96 ms 97 ms be2189.ccr22.alb02.atlas.cogentco.com [154.54.43.185]
    14 103 ms 103 ms 100 ms be2302.ccr22.bos01.atlas.cogentco.com [154.54.43.13]
    15 100 ms 99 ms 107 ms te0-0-0-0.rcr12.b002133-1.bos01.atlas.cogentco.com [66.28.4.254]
    16 127 ms 110 ms 110 ms 38.104.252.70
    17 114 ms 110 ms 109 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
    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 * * * 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.

  • mmps1mmps1 Member Posts: 381 Arc User
    Nirett@mmps1
    Btinternet
    Logged in when server came up, been a complete laggy mess since then. It's taken me an hour to do the omega thingy between esd, Vulcan and DS7. Oh and the omega game is busted. Again. Twice immediately timed out, the other time it just skipped the whole way through so hardly any particles registered. Funtimes.

    Been stuck in the loading screen in the Sherman system for 10 mins now, after a nice dc.
    "Mr talks down to the peasants."
  • daveynydaveyny Member Posts: 8,227 Arc User
    Welp, I've got a Craptastic connection today.
    <grumble..., grumble..., grumble...>
    STO Member since February 2009.
    I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born!
    Forever a STO Veteran-Minion
    upside-down-banana-smiley-emoticon.gif
  • darkhorse281darkhorse281 Member Posts: 256 Arc User
    so much for the server upgrades and bug fixes.....Login2_timeout
  • pwlaughingtrendypwlaughingtrendy Member Posts: 2,966 Arc User
    The STO Team is investigating the sudden drop that is preventing players from logging in.
  • pwlaughingtrendypwlaughingtrendy Member Posts: 2,966 Arc User
    Our engineering team is in the process of stabilizing the Warp Core. Your ship should be ready, Captains. We will be monitoring.
  • risingstar1971risingstar1971 Member Posts: 9 Arc User
    edited January 2016
    I'll lock down an issue for you........

    1.Windows 10 updates
    2. ATI 5770 Video Card
    3.Crimson Drivers and You.

    1. Windows 10 will try to force an update to your card, and it WILL do it. ( I have been beta testing 10 since it was a stain on Bill Gates sheets. Trust me. IT WILL DO IT.)
    2. I dont know about other peoples cards, but the 5700 series is NOT compatable with the crimson drivers.
    3. Windows will force it, Steam will force it, the ATI gaming evolved WILL FORCE IT.
    4. Once these updates run, it is not only ARC games that crash. Any modern game WILL CRASH.
    5. SOLUTION. After every game update, after every windows update, do a MANUAL INSTALL of the ATI 14.x drivers.
    6. Reboot and retstart game.

    Suddenly everything works (with the exception of the anny missions, was still having problems with those)

    Carve it in stone, sticky it, whatever. You own what is now vintage equipment? Follow the above directions. Enjoy.
  • centaurianalphacentaurianalpha Member Posts: 1,150 Arc User
    edited February 2016
    I'm not sure if latency is related to game crashes, but the random crashes have become nearly a show-stopper for me. For some reason, these seem to happen with greater frequency while I'm working in the fleet mine, irrespective of whether it's KDF or Fed. 5 CTD's so far today, mostly in the fleet mines.

    My info:

    ISP: Century Link
    Geo: Phoenix, AZ
    Date: 2am-1pm today
    OS: Win7 Pro (fully updated) [ver.6.1.7601]
    CPU: Intel i3 w/integrated graphics 3.4GHz
    RAM: Corsair 4Gb DDR3

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

    1 <1ms <1ms <1ms 192.168.0.1
    2 26ms 21ms 22ms phnx-ds1-gw68.phnx.qwest.net [67.40.227.68]
    3 23ms 51ms 21ms phnx-agw1.inet.qwest.net [75.160.238.25]
    4 80ms 81ms 84ms bst-edge-05.inet.qwest.net [67.14.30.130]
    5 81ms 82ms 81ms 65.120.117.250
    6 81ms 81ms 81ms border11.te8-1-bbnet2.bsn.pnap.net 63.251.128.104]
    7 81ms 80ms 80ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    8 81ms 81ms 81ms 198.49.243.250
    9 81ms 83ms 81ms 198.49.243.253
    10 * * * Request timed out
    11 82ms 82ms 82ms xboxpatchserver.crypticstudios.com [208.195.185.41]

    Trace complete.

    So Cryptic is using an XBox server for STO??
    Expendables Fleet: Andrew - Bajoran Fed Engineer Ken'taura - Rom/Fed Scientist Gwyllim - Human Fed Delta Tac
    Savik - Vulcan Fed Temporal Sci
    Dahar Masters Fleet: Alphal'Fa - Alien KDF Engineer Qun'pau - Rom/KDF Engineer D'nesh - Orion KDF Scientist Ghen'khan - Liberated KDF Tac
    Welcome to StarBug Online - to boldly Bug where no bug has been before!
    STO player since November 2013
  • rck01rck01 Member Posts: 808 Arc User
    edited February 2016
    I've been experiencing INSANE amounts of lag between the hours of roughly 11:00AM to 11:00PM (GMT) every day for the past 7-10 days. The game is utterly unplayable - I'm lucky if I can run the mini-game to gather omega traces.

    Normally, I run with a fairly high PING - in the 250-350ms range - because I'm logging in from Mauritius (Indian Ocean). However, as long as the ping remains steady I can play - I even PvP a bit. But lately, as soon as I enter a PvE map or the action gets going in Ker'rat, my ping goes through the roof. The "/netgraph 1" command shows 3000ms or higher spikes, and the entire map slows to a crawl. Get enough spikes in succession and netgraph gets pegged at 2700-3000ms until the action stops or I move far enough away from other players/NPCs.

    Note: While this is occurring, a continuous "ping xxxx -t" command against the IP addresses in use by gameclient.exe shows the packet round trip holding steady at ~300ms. In other words, wherever the delay is coming from, Windows doesn't see it from a diagnostic perspective.

    It wasn't like this two weeks ago. I've been playing for years from this location without any major issues. And it's not my local connection: I have a 3ms ping to my provider (Orange - Mauritius Telecom - www.orange.mu) over a 20Mbps fiber link. An analysis of traceroute data shows much of the problem seems to stem from the undersea connection between London (my traffic is routed through there) and the U.S. If I ping the outbound hop in the U.K. I can see 1-2% dropped packets over time - not much, and certainly not enough to kill the game experience, but it's my only clue.

    Anyway, here's my relevant diagnostic data (see below). I really hope you guys can sort this out.

    RCK

    Location: Mauritius (Indian Ocean)
    ISP: Orange (Mauritius Telecom)
    PC: Acer Core i5 Laptop w/Intel GMA 3000 Grapics, 8GB RAM, 7200 RPM HDD
    OS: Windows 10 (latest updates installed).
    Dates: Repeatedly for the past 7-10 days - occurs same time-window every day (11:00-23:00 GMT).


    PathPing
    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 DESKTOP-7DVUJE0 [192.168.2.114]
    1 DD-WRT [192.168.2.1]
    2 * * *
    Computing statistics for 25 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 DESKTOP-7DVUJE0 [192.168.2.114]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% DD-WRT [192.168.2.1]

    Trace complete.

    Tracert
    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.2.1]
    2 * * * Request timed out.
    3 3 ms 3 ms 3 ms 41.136.228.1
    4 3 ms 3 ms 2 ms 196.20.254.6
    5 5 ms 4 ms 4 ms tengig4-1-fl.telecomplus.net [196.20.254.173]
    6 209 ms 209 ms 209 ms if-10-1.core4.LDN-London.as6453.net [80.231.76.61]
    7 * 287 ms 285 ms if-2-3-1-0.tcore1.LDN-London.as6453.net [80.231.76.122]
    8 284 ms 285 ms * if-8-2.thar1.NJY-Newark.as6453.net [66.198.70.173]
    9 287 ms 291 ms * if-1-3.thar2.NJY-Newark.as6453.net [216.6.57.2]
    10 282 ms 282 ms 283 ms if-14-14.tcore2.NTO-New-York.as6453.net [66.198.111.126]
    11 285 ms 284 ms 285 ms be3011.ccr21.jfk05.atlas.cogentco.com [154.54.12.17]
    12 285 ms 284 ms 285 ms be2061.ccr42.jfk02.atlas.cogentco.com [154.54.3.69]
    13 296 ms 299 ms 296 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
    14 292 ms 293 ms 290 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
    15 291 ms 290 ms 291 ms 38.111.40.114
    16 290 ms 291 ms 292 ms 198.49.243.253
    17 * * * Request timed out.
    18 298 ms 298 ms 298 ms xboxpatchserver.crypticstudios.com [208.95.185.41]

    Trace complete.

    Nettest
    contacting nettest server..
    Local IP: 41.136.230.36
    Ping: 272.8 msec
    Port: 80: 29 KB/sec 4 KB/sec 38 KB/sec 500
    Port: 80: 22 KB/sec 2 KB/sec 32 KB/sec 500
    Port: 443: 29 KB/sec 3 KB/sec 41 KB/sec 500
    Port: 443: 18 KB/sec 2 KB/sec 26 KB/sec 500
    Port: 7255: 33 KB/sec 3 KB/sec 45 KB/sec 500
    Port: 7255: 20 KB/sec 2 KB/sec 28 KB/sec 500
    Port: 7003: 28 KB/sec 3 KB/sec 39 KB/sec 500
    Port: 7003: 21 KB/sec 2 KB/sec 32 KB/sec 500
    Port: 7202: 25 KB/sec 2 KB/sec 38 KB/sec 500
    Port: 7202: 63 KB/sec 4 KB/sec 75 KB/sec 500
    Port: 7499: 24 KB/sec 2 KB/sec 34 KB/sec 500
    Port: 7499: 21 KB/sec 3 KB/sec 32 KB/sec 500
    Port: 80: 26 KB/sec 3 KB/sec 37 KB/sec 500
    Idle NIC bandwidth Send: 1 KB/sec Recv: 9 KB/sec
    hit return to exit
Sign In or Register to comment.