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

Heavy Lag in STO

azurianstarazurianstar Member Posts: 6,985 Arc User
edited October 2013 in Windows and General: PC, Network, and Other Technical Issues
It started about 2 Hours ago and ever since STO has been getting worse and worse with the lag and rubberbanding that it's become impossible to play.


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 192.168.0.1
2 93 ms 78 ms 94 ms fl-184-4-144-1.dhcp.embarqhsd.net [184.4.144.1]

3 108 ms 71 ms 71 ms fl-64-45-223-249.dhcp.embarqhsd.net [64.45.223.2
49]
4 244 ms 87 ms 316 ms host138.embarqservices.net [207.30.14.138]
5 * * 36 ms host42.embarqservices.net [209.26.9.42]
6 51 ms 51 ms 54 ms 173-248-66-236.centurylink.net [173.248.66.236]

7 33 ms 35 ms 32 ms bb-wnpkflxe-jx9-02-ae0.core.centurytel.net [208.
110.248.94]
8 61 ms 36 ms 37 ms 208-110-248-193.centurylink.net [208.110.248.193
]
9 36 ms 46 ms 42 ms bb-miauflws-jx9-01-ae0.core.centurytel.net [208.
110.248.101]
10 86 ms 58 ms 56 ms nap-edge-04.inet.qwest.net [67.129.170.101]
11 46 ms 50 ms 47 ms atx-brdr-01.inet.qwest.net [67.14.14.134]
12 195 ms 206 ms 192 ms te0-0-0-16.ccr21.atl02.atlas.cogentco.com [154.5
4.10.61]
13 * 204 ms 203 ms be2053.mpd22.atl01.atlas.cogentco.com [154.54.3.
145]
14 191 ms 189 ms 197 ms te0-3-0-2.ccr21.dca01.atlas.cogentco.com [154.54
.2.46]
15 213 ms 211 ms * te0-7-0-2.ccr22.jfk02.atlas.cogentco.com [154.54
.26.1]
16 217 ms 222 ms 218 ms te0-4-0-7.ccr22.bos01.atlas.cogentco.com [154.54
.5.249]
17 407 ms 226 ms 307 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
18 224 ms * * 38.111.40.114
19 223 ms 210 ms * 208.95.185.41
20 220 ms 222 ms 224 ms 208.95.185.41

Trace complete.
Post edited by Unknown User on
«1

Comments

  • lucho80lucho80 Member Posts: 6,600 Bug Hunter
    edited September 2013
    No problems here, then again, I'm a 2 hour car ride away from Boston which in internet terms is next door.
  • azurianstarazurianstar Member Posts: 6,985 Arc User
    edited September 2013
    Afraid not everyone lives in Boston or near Boston.
  • casperdudesdcasperdudesd Member Posts: 0 Arc User
    edited September 2013
    no their is a very very heavy lagg in the game i sat loading a map for 3 hrs on fioz
  • casperdudesdcasperdudesd Member Posts: 0 Arc User
    edited September 2013
    how ever my lagg is not that bad...
    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:

    1 3 ms 3 ms 2 ms dslrouter [192.168.1.1]
    2 27 ms 26 ms 26 ms 10.41.15.1
    3 30 ms 27 ms 28 ms P0-0-1-2.BFLONY-LCR-21.verizon-gni.net [130.81.4
    4.232]
    4 51 ms 81 ms 38 ms xe-1-1-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.
    209.34]
    5 48 ms 48 ms 48 ms 0.ge-4-0-0.XL3.BOS4.ALTER.NET [152.63.17.30]
    6 47 ms 47 ms 48 ms 0.xe-8-0-0.GW15.BOS4.ALTER.NET [152.63.24.26]
    7 50 ms 52 ms 51 ms internap-gw.customer.alter.net [152.179.134.214]

    8 49 ms 50 ms 50 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
    04]
    9 56 ms 52 ms 54 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
    61.78]
    10 100 ms 97 ms 99 ms 208.95.185.41

    Trace complete.
  • tekehdtekehd Member Posts: 2,032 Arc User
    edited September 2013
    Same here:
    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 25 ms 19 ms 28 ms 76.104.103.1
    3 11 ms 11 ms 11 ms te-1-3-ur01.robinsrd.va.richmond.comcast.net [68
    .85.71.225]
    4 19 ms 18 ms 15 ms xe-6-1-2-0-ar02.charlvilleco.va.richmond.comcast
    .net [68.86.172.57]
    5 20 ms 22 ms 22 ms pos-1-3-0-0-cr01.ashburn.va.ibone.comcast.net [6
    8.86.91.57]
    6 20 ms 20 ms 21 ms be-13-pe04.ashburn.va.ibone.comcast.net [68.86.8
    4.214]
    7 33 ms 33 ms 32 ms as174.ashburn.va.ibone.comcast.net [66.208.229.1
    42]
    8 58 ms 56 ms 30 ms be2112.mpd22.dca01.atlas.cogentco.com [154.54.5.
    234]
    9 76 ms 76 ms 78 ms te0-0-0-14.mpd21.jfk02.atlas.cogentco.com [154.5
    4.42.34]
    10 83 ms 84 ms 83 ms te0-4-0-7.ccr21.bos01.atlas.cogentco.com [154.54
    .25.114]
    11 82 ms 82 ms * te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
    4]
    12 129 ms 127 ms 139 ms 38.111.40.114
    13 130 ms 129 ms 128 ms 208.95.185.41

    Trace complete.

    the router at 38.111.40.114 is screwed.
  • mattmiraclemattmiracle Member Posts: 0 Arc User
    edited September 2013
    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms CISCOE3000
    2 * * * Request timed out.
    3 12 ms 11 ms 11 ms ae0-1121.cr02.clmcohib.midohio.rr.com [184.59.243.211]
    4 15 ms 16 ms 19 ms network-065-029-001-038.midwest.rr.com [65.29.1.38]
    5 38 ms 27 ms 23 ms 107.14.19.58
    6 25 ms 24 ms 24 ms so-1-1-1.a0.alb75.tbone.rr.com [66.109.1.49]
    7 62 ms 61 ms 62 ms te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
    8 28 ms 25 ms 25 ms be2176.ccr21.dca01.atlas.cogentco.com [154.54.41.54]
    9 32 ms 34 ms 48 ms te0-7-0-8.ccr21.jfk02.atlas.cogentco.com [154.54.41.2]
    10 78 ms 40 ms 79 ms te0-6-0-5.ccr22.bos01.atlas.cogentco.com [154.54.44.26]
    11 77 ms 78 ms 79 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
    12 * 137 ms 143 ms 38.111.40.114
    13 * 132 ms 133 ms 208.95.185.41

    Trace complete.
    Matt Miracle

    Fleet Commander in Chief [Rank 7] for Covenant of Honor; a FED T5 Starbase
    House Leader [Rank 7] for Honorable House of Mor'gue; a KDF T3 Starbase
    Find us at CovenantofHonor.com.  My Twitter handle; @jmattmiracle
  • o1derfull1o1derfull1 Member Posts: 294
    edited September 2013
    I concur, bad lag/rubberbanding and escalating over the last 2 days. Similar complaints from some, but not all fleetmates.

    My tracert couldn't even complete. The first time. See two tracerts below.


    Tracing route to patchserver.cryticstudios.com [92.242.140.2]
    over a maximum of 30 hops:

    1 2 ms <1 ms <1 ms 192.168.1.1
    2 * 7 ms 11 ms 10.125.80.1
    3 9 ms 10 ms * 68.11.12.110
    4 11 ms 39 ms 11 ms 68.11.14.149
    5 9 ms 10 ms 13 ms 68.11.14.98
    6 20 ms 22 ms 23 ms 68.1.2.121
    7 37 ms 38 ms * 70.167.150.130
    8 25 ms 21 ms 21 ms ae0-60g.cr1.dfw1.us.nlayer.net [69.31.63.125]
    9 38 ms 47 ms 88 ms xe-3-3-1.cr1.atl1.us.nlayer.net [69.22.142.24]
    10 38 ms 46 ms 39 ms 208.84.49.30
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    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 * * * 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.



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

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 20 ms 10 ms 9 ms 10.125.80.1
    3 36 ms 24 ms 11 ms 68.11.12.110
    4 14 ms 79 ms 10 ms 68.11.14.149
    5 9 ms 44 ms 8 ms 68.11.14.98
    6 81 ms 21 ms 21 ms 68.1.2.109
    7 40 ms 23 ms 23 ms 68.105.30.22
    8 34 ms 23 ms 22 ms xe-0-1-0.cr2.dfw2.us.above.net [64.125.27.81]
    9 * 26 ms 116 ms xe-7-0-0.cr2.iah1.us.above.net [64.125.21.138]
    10 210 ms * 63 ms xe-2-1-0.cr2.dca2.us.above.net [64.125.28.49]
    11 65 ms 64 ms 66 ms xe-1-3-0.mpr4.bos2.us.above.net [64.125.24.113]

    12 204 ms 121 ms 120 ms xe-1-0-0.mpr3.bos2.us.above.net [64.125.25.65]
    13 120 ms 76 ms 77 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [20
    8.184.110.70]
    14 68 ms 65 ms 67 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
    04]
    15 68 ms 65 ms 74 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
    61.78]
    16 66 ms 77 ms 64 ms 208.95.185.41

    Trace complete.
    _________________________________________________

    ::WARNING:: This game is not intended for use as a source of self-esteem.
  • twamtwam Member Posts: 0 Arc User
    edited September 2013
    Same here, it's getting so bad the game is basically unplayable at times. Which isn't necessarily a bad thing, as I'm getting more work done now, but I can't imagine that being the company's intentions.

    My tracert:
    Traceren van de route naar patchserver.crypticstudios.com [208.95.185.41]
    via maximaal 30 hops:

    1 1 ms <1 ms <1 ms *.*.*.*
    2 12 ms 12 ms 10 ms *.*.*.*.nl [*.*.*.*]
    3 12 ms 8 ms 11 ms *.*.*.*
    4 10 ms 12 ms 11 ms asd-lc0006-cr101-ae6-0.core.as9143.net [213.51.1
    58.78]
    5 9 ms 11 ms 11 ms adm-b7-link.telia.net [80.239.135.165]
    6 13 ms 12 ms 10 ms adm-bb3-link.telia.net [213.155.133.36]
    7 12 ms 23 ms 14 ms adm-b5-link.telia.net [80.91.253.171]
    8 14 ms 11 ms 11 ms cogent-ic-140551-adm-b5.c.telia.net [213.248.93.
    90]
    9 13 ms 11 ms 11 ms te0-7-0-3.ccr22.ams03.atlas.cogentco.com [154.54
    .36.129]
    10 20 ms 39 ms 21 ms te0-0-0-7.ccr22.lpl01.atlas.cogentco.com [154.54
    .37.106]
    11 88 ms 87 ms 89 ms te0-4-0-2.ccr22.bos01.atlas.cogentco.com [154.54
    .44.185]
    12 86 ms 91 ms 89 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
    134]
    13 101 ms 89 ms 91 ms 38.111.40.114
    14 92 ms 86 ms 84 ms 208.95.185.41

    De trace is voltooid.

    [redacted personal IP info for security]

    I'm inclined to say the problem is probably not at my end - these are average results for me, for these kinds of tests. I'm also blessed with an extremely stable internet connection and good ISP. Euro player, here, Dutch. Been bad for a couple of days now, getting worse - doesn't really matter what time of day.
  • azurianstarazurianstar Member Posts: 6,985 Arc User
    edited September 2013
    Any word on when we might have a fix?


    EDIT: Nope, still busted. Lagging so hard, almost feel like a vinyl record at a rapper DJ booth.
  • ashstorm1ashstorm1 Member Posts: 679 Arc User
    edited September 2013
    I have the same problem. The game started getting laggy in the middle of a Fleet Alert, and it got so bad that i could no longer control my ship. Now i seem to have problems logging back, too.

    I hope we get a fix very soon. Thank you.
  • UnknownUnknown
    edited September 2013
    This content has been removed.
  • skyranger1414skyranger1414 Member Posts: 1,785 Arc User
    edited September 2013
    I get choppy graphics and lag spikes. Its far worse than I've experienced before In STO. It was working great, there would be the occasional disconnect but graphics ran smoothly. Since two patches ago its practically unplayable.
  • twamtwam Member Posts: 0 Arc User
    edited September 2013
    Same or worse after patch day.

    Still getting 10-15 second's worth of stuckness, followed by chaos and death, generally.
  • megtrekkiemegtrekkie Member Posts: 85 Arc User
    edited September 2013
    Im From The Uk And Tbh I Don't Think It Our Pcs Or Laptops I Think Its The Fact Star Trek Online Servers And Never Winter For That Matter Are Very Limited They Need To Improve That Coz Before Lor I Was Playing This Game On High Graphic On My Laptop Now I Have To Result In Low Graphic And I Tend To Lag More On Stfs That Why I Never Play Then But They Doo Need To Bring More Hardware In So Other Wise Its Gonna Annoy Every One
  • capemike4capemike4 Member Posts: 394 Arc User
    edited September 2013
    Only started playing yesterday, and haven't noticed any connection issues at all here from Chattanooga, Tennessee(home of the fastest internet connections in the country) aside from one brief episode of a map taking about a minute to load...no other performance issues worth mentioning, but I'll keep an eye out!
    When in doubt...Gravity Well TO THE FACE!! :D
  • kpg1usakpg1usa Member Posts: 190 Arc User
    edited September 2013
    I am also seeing network lag and CPU spikes when STO accesses sound and texture files.
  • xsharpexxsharpex Member Posts: 0 Arc User
    edited September 2013
    blame the redshirt shard. they reallocate network bandwidth and server resources to have all three shards up at the same time. people always experience abnormal lag and network issues whenever cryptic rolls it out.

    they can tell you to upload trace reports and to reset your modem and routers; flush your dns and all that jazz. it's still not going to solve the issue, but you are more than welcome to waste your time and try it.
  • legetdumarlegetdumar Member Posts: 263
    edited September 2013
    Well this is interesting...note where some of the worst numbers are coming from...

    racing route to us1.proxy.crypticstudios.com [208.95.184.152]
    over a maximum of 30 hops:

    1 <1 ms 1 ms <1 ms 192.168.1.254
    2 7 ms 10 ms 6 ms 10.139.176.1
    3 140 ms 75 ms 114 ms chcgildtgr00.bb.telus.com [154.11.11.30]
    4 101 ms 63 ms 92 ms 173.182.200.2
    5 108 ms 90 ms 102 ms be2005.ccr21.ord01.atlas.cogentco.com [66.28.4.7
    3]
    6 116 ms 124 ms 74 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43
    .194]
    7 104 ms 64 ms 134 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
    134]
    8 139 ms 123 ms 145 ms 38.111.40.114
    9 253 ms 311 ms 319 ms us1.proxy.crypticstudios.com [208.95.184.152]

    Trace complete.

    C:\Windows\System32>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 192.168.1.254
    2 7 ms 6 ms 50 ms 10.139.176.1
    3 40 ms 40 ms 40 ms chcgildtgr00.bb.telus.com [154.11.11.30]
    4 92 ms 117 ms 91 ms 173.182.200.2
    5 41 ms 41 ms 56 ms be2005.ccr21.ord01.atlas.cogentco.com [66.28.4.7
    3]
    6 174 ms 133 ms 120 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43
    .186]
    7 206 ms 352 ms 223 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
    134]
    8 232 ms 217 ms 230 ms 38.111.40.114
    9 190 ms 191 ms 204 ms 208.95.185.41

    Hmmmm.....
    Criticism, while never agreeable, is necessary. It is like pain in the body. It brings attention to an unhealthy state of things---Winston Churchill
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited September 2013
    legetdumar wrote: »
    Well this is interesting...note where some of the worst numbers are coming from...
    Hmmmm.....

    You should post these results in the Network section of the PWE Tech Support Forum so their network techs are aware of the problem...

    http://techsupport.perfectworld.com/
  • ellandhorellandhor Member Posts: 8 Arc User
    edited September 2013
    I noticed that around 5+pm GMT, I'm also getting insane lag. One thing that I can't seem to understand is the single player missions. They are supposed to be separate instances, but still I find myself running and then "teleporting" a dozen meters back due to lag.

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 28 ms 26 ms 26 ms 80.106.108.36
    3 25 ms 25 ms 25 ms 79.128.244.117
    4 25 ms 25 ms 26 ms trip-gsra-trip7609a-1.backbone.otenet.net [79.128.232.5]
    5 30 ms 31 ms 31 ms athe-crsb-trip-gsra-1.backbone.otenet.net [79.128.224.209]
    6 30 ms 30 ms 31 ms ten0-2-2-0-crs01.ath.OTEGlobe.net [62.75.3.29]
    7 63 ms 28 ms 29 ms 62.75.4.170
    8 76 ms 80 ms 80 ms 62.75.4.154
    9 74 ms 76 ms 74 ms er1.ams1.nl.above.net [195.69.144.122]
    10 70 ms 71 ms 70 ms xe-0-1-0.er1.ams5.nl.above.net [64.125.25.174]
    11 130 ms 126 ms 122 ms xe-0-2-1.cr1.ams5.nl.above.net [64.125.22.61]
    12 227 ms 235 ms 219 ms so-2-1-0.mpr2.lga5.us.above.net [64.125.31.182]
    13 256 ms 220 ms 218 ms xe-1-0-0.cr1.lga5.us.above.net [64.125.29.45]
    14 324 ms 318 ms 316 ms xe-2-1-0.mpr3.bos2.us.above.net [64.125.24.105]
    15 225 ms 226 ms 222 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
    16 225 ms 225 ms 227 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
    17 237 ms 232 ms 233 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    18 229 ms 231 ms 233 ms 208.95.185.41

    Trace complete.

    One thing I also wonder about is how come and from the EU I log into the US?
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited September 2013
    ellandhor wrote: »
    I noticed that around 5+pm GMT, I'm also getting insane lag. One thing that I can't seem to understand is the single player missions. They are supposed to be separate instances, but still I find myself running and then "teleporting" a dozen meters back due to lag.

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 28 ms 26 ms 26 ms 80.106.108.36
    3 25 ms 25 ms 25 ms 79.128.244.117
    4 25 ms 25 ms 26 ms trip-gsra-trip7609a-1.backbone.otenet.net [79.128.232.5]
    5 30 ms 31 ms 31 ms athe-crsb-trip-gsra-1.backbone.otenet.net [79.128.224.209]
    6 30 ms 30 ms 31 ms ten0-2-2-0-crs01.ath.OTEGlobe.net [62.75.3.29]
    7 63 ms 28 ms 29 ms 62.75.4.170
    8 76 ms 80 ms 80 ms 62.75.4.154
    9 74 ms 76 ms 74 ms er1.ams1.nl.above.net [195.69.144.122]
    10 70 ms 71 ms 70 ms xe-0-1-0.er1.ams5.nl.above.net [64.125.25.174]
    11 130 ms 126 ms 122 ms xe-0-2-1.cr1.ams5.nl.above.net [64.125.22.61]
    12 227 ms 235 ms 219 ms so-2-1-0.mpr2.lga5.us.above.net [64.125.31.182]
    13 256 ms 220 ms 218 ms xe-1-0-0.cr1.lga5.us.above.net [64.125.29.45]
    14 324 ms 318 ms 316 ms xe-2-1-0.mpr3.bos2.us.above.net [64.125.24.105]
    15 225 ms 226 ms 222 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
    16 225 ms 225 ms 227 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
    17 237 ms 232 ms 233 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    18 229 ms 231 ms 233 ms 208.95.185.41

    Trace complete.

    One thing I also wonder about is how come and from the EU I log into the US?

    Rubberbanding occurs when your Client thinks you're at point Y, but the Server tells the Client you're at Point X, because it never received the message you were moving to point Y. Single or shared instance has little to do with this...

    It looks like your issue is being caused by the above.net backbone, which appears to be a trans-Atlantic cable provider. You could try using the Europe Proxy option in the Launcher, as this could move your connection path to different trans-Atlantic cable connection. (which could have less or more network congestion, so doing this may or may not improve your connection issue...)

    And STO only has a single centralized sever located in Boston, so ALL the STO connection around the world connect to this single location. This makes it possible for people from around the world to be able to play and interact in the same STF...
  • ellandhorellandhor Member Posts: 8 Arc User
    edited September 2013
    It looks like your issue is being caused by the above.net backbone, which appears to be a trans-Atlantic cable provider. You could try using the Europe Proxy option in the Launcher, as this could move your connection path to different trans-Atlantic cable connection. (which could have less or more network congestion, so doing this may or may not improve your connection issue...)
    We're in agreement there. I tried the EU proxy, but didn't get past the login screen. The patcher started normally, but couldn't log into the game as it keeps on timing out. Seems my two options are either play with worse than dialup lag or not be able to log in at all. Now this is a bad business model for this type of franchise. :(

    And below you get the picture (I had to stop the extra time outs, but you get the idea):

    Tracing route to eu1.proxy.crypticstudios.com [79.125.3.30] over a maximum of 30 hops:
    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 26 ms 26 ms 26 ms 80.106.108.36
    3 25 ms 26 ms 25 ms 79.128.244.121
    4 26 ms 25 ms 25 ms trip-gsra-trip7609b-1.backbone.otenet.net [79.128.232.9]
    5 30 ms 31 ms 31 ms athe-crsb-trip-gsra-1.backbone.otenet.net [79.128.224.209]
    6 31 ms 30 ms 30 ms ten0-8-5-0-crs01.ath.OTEGlobe.net [62.75.3.85]
    7 28 ms 28 ms 29 ms 62.75.4.170
    8 73 ms 80 ms 72 ms 62.75.4.106
    9 74 ms 76 ms 73 ms amsix01-ams1.amazon.com [195.69.146.100]
    10 196 ms 190 ms 188 ms 178.236.3.39
    11 96 ms 99 ms 96 ms 178.236.3.10
    12 93 ms 95 ms 97 ms 176.32.106.29
    13 95 ms 95 ms 127 ms 178.236.0.179
    14 92 ms 91 ms 91 ms 178.236.0.68
    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 ^C
  • legetdumarlegetdumar Member Posts: 263
    edited September 2013
    grouchyotaku wrote: »
    You should post these results in the Network section of the PWE Tech Support Forum so their network techs are aware of the problem...

    http://techsupport.perfectworld.com/

    On it.:cool:
    Criticism, while never agreeable, is necessary. It is like pain in the body. It brings attention to an unhealthy state of things---Winston Churchill
  • legetdumarlegetdumar Member Posts: 263
    edited September 2013
    The last patch hasn't helped much..the numbers are bad all around, but the one's of interest to PWE will be hilighted in green:

    racing route to patchserver.crypticstudios.com [208.95.185.41]
    ver a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.254
    2 50 ms 6 ms 31 ms 10.139.176.1
    3 57 ms 57 ms 57 ms chcgildtgr00.bb.telus.com [154.11.11.30]
    4 69 ms 57 ms 57 ms 173.182.200.2
    5 180 ms 58 ms 58 ms be2006.mpd21.ord01.atlas.cogentco.com [154.54.5.
    7]
    6 81 ms 81 ms 122 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43
    186]
    7 383 ms 343 ms 254 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
    34]
    8 99 ms 143 ms 143 ms 38.111.40.114
    9 101 ms 115 ms 101 ms 208.95.185.41

    race complete.

    :\Windows\system32>tracert us1.proxy.crypticstudios.com

    racing route to us1.proxy.crypticstudios.com [208.95.184.152]
    ver a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.254
    2 6 ms 6 ms 12 ms 10.139.176.1
    3 253 ms 75 ms 162 ms chcgildtgr00.bb.telus.com [154.11.11.30]
    4 58 ms 57 ms 57 ms 173.182.200.2
    5 58 ms 58 ms 58 ms be2004.mpd22.ord01.atlas.cogentco.com [154.54.5.
    ]
    6 87 ms 172 ms 99 ms be2139.ccr21.bos01.atlas.cogentco.com [154.54.43
    178]
    7 81 ms 83 ms 86 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
    34]
    8 152 ms 197 ms 183 ms 38.111.40.114
    9 389 ms 81 ms 81 ms us1.proxy.crypticstudios.com [208.95.184.152]

    race complete.

    :\Windows\system32>
    :rolleyes:

    Posted at PWE's tech support forum as well...hope someone sees it
    Criticism, while never agreeable, is necessary. It is like pain in the body. It brings attention to an unhealthy state of things---Winston Churchill
  • legetdumarlegetdumar Member Posts: 263
    edited September 2013
    Another tracer conducted a few minutes ago...again bad numbers across the board, including PWE

    icrosoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>tracert us1.proxy.crypticstudios.com

    Tracing route to us1.proxy.crypticstudios.com [208.95.184.152]
    over a maximum of 30 hops:

    1 1 ms <1 ms 1 ms 192.168.1.254
    2 14 ms 7 ms 14 ms 10.139.176.1
    3 221 ms 285 ms 129 ms chcgildtgr00.bb.telus.com [154.11.11.30]
    4 77 ms 85 ms 84 ms 173.182.200.2
    5 287 ms 244 ms 108 ms be2005.ccr21.ord01.atlas.cogentco.com [66.28.4.7
    3]
    6 371 ms 221 ms 105 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43
    .194]
    7 306 ms 251 ms 310 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
    134]
    8 382 ms 287 ms 268 ms 38.111.40.114
    9 271 ms 181 ms 116 ms us1.proxy.crypticstudios.com [208.95.184.152]

    Trace complete.

    C:\Windows\system32>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 192.168.1.254
    2 9 ms 6 ms 6 ms 10.139.176.1
    3 201 ms 129 ms 155 ms chcgildtgr00.bb.telus.com [154.11.11.30]
    4 198 ms 245 ms 207 ms 173.182.200.2
    5 162 ms 249 ms 305 ms be2005.ccr21.ord01.atlas.cogentco.com [66.28.4.7
    3]
    6 413 ms 331 ms 180 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43
    .186]
    7 210 ms 187 ms 156 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
    ]
    8 102 ms 215 ms 125 ms 38.111.40.114
    9 124 ms 182 ms 98 ms 208.95.185.41

    Trace complete.

    Posting this in tech support as well..if anybody even reads these things! :rolleyes:
    Criticism, while never agreeable, is necessary. It is like pain in the body. It brings attention to an unhealthy state of things---Winston Churchill
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited September 2013
    legetdumar wrote: »
    Another tracer conducted a few minutes ago...again bad numbers across the board, including PWE

    icrosoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>tracert us1.proxy.crypticstudios.com

    Tracing route to us1.proxy.crypticstudios.com [208.95.184.152]
    over a maximum of 30 hops:

    1 1 ms <1 ms 1 ms 192.168.1.254
    2 14 ms 7 ms 14 ms 10.139.176.1
    3 221 ms 285 ms 129 ms chcgildtgr00.bb.telus.com [154.11.11.30]
    ...

    Now I wonder... 192.168.1.x is obviously a 'private address' range and represents your gateway router. 10.x.x.x is also a 'private address' range, but is less commonly used. If this address belongs to your ISP, then this would indicate your ISP has some serious issues routing traffic onto the 'public' Internet...
  • jbmonroejbmonroe Member Posts: 809 Arc User
    edited September 2013
    legetdumar wrote: »
    The last patch hasn't helped much..the numbers are bad all around, but the one's of interest to PWE will be hilighted in green:

    racing route to patchserver.crypticstudios.com [208.95.185.41]
    ver a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.254
    2 50 ms 6 ms 31 ms 10.139.176.1
    3 57 ms 57 ms 57 ms chcgildtgr00.bb.telus.com [154.11.11.30]
    4 69 ms 57 ms 57 ms 173.182.200.2
    5 180 ms 58 ms 58 ms be2006.mpd21.ord01.atlas.cogentco.com [154.54.5.
    7]
    6 81 ms 81 ms 122 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43
    186]
    7 383 ms 343 ms 254 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
    34]
    8 99 ms 143 ms 143 ms 38.111.40.114
    9 101 ms 115 ms 101 ms 208.95.185.41

    race complete.

    :\Windows\system32>tracert us1.proxy.crypticstudios.com

    racing route to us1.proxy.crypticstudios.com [208.95.184.152]
    ver a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.254
    2 6 ms 6 ms 12 ms 10.139.176.1
    3 253 ms 75 ms 162 ms chcgildtgr00.bb.telus.com [154.11.11.30]
    4 58 ms 57 ms 57 ms 173.182.200.2
    5 58 ms 58 ms 58 ms be2004.mpd22.ord01.atlas.cogentco.com [154.54.5.
    ]
    6 87 ms 172 ms 99 ms be2139.ccr21.bos01.atlas.cogentco.com [154.54.43
    178]
    7 81 ms 83 ms 86 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
    34]
    8 152 ms 197 ms 183 ms 38.111.40.114
    9 389 ms 81 ms 81 ms us1.proxy.crypticstudios.com [208.95.184.152]

    race complete.

    :\Windows\system32>
    :rolleyes:

    Posted at PWE's tech support forum as well...hope someone sees it

    What I see when I trace is CogentCo's Atlas cluster has two nodes that are having trouble carrying the traffic. WOW players are making the same complaint. It may not be that there's a specific problem with STO--more that a lot of games are trying to push packets "in the same direction" so to speak, and it's causing problems for everyone as a whole.
    boldly-watched.png
  • kimonykimony Member Posts: 571 Arc User
    edited September 2013
    I don't know if it's the case above but "10.x.x.x" internet addresses are used by some internet resellers to ensure enough address space:

    192.168.x.x is a Private Internet address Class C that support 65534 hosts

    BUT

    10.x.x.x is a Private Internet address Class A that support 16777214 hosts

    Such is the case with my ISP, DSLExtreme. I am assigned a 10.x.x.x address

    Verizon has recently talked about switching to 10.x.x.x addresses in the future.

    #SaucersForever #TrianglesCutDeep #TeamBeta #ShipOneisNumberOne
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited September 2013
    kimony wrote: »
    I don't know if it's the case above but "10.x.x.x" internet addresses are used by some internet resellers to ensure enough address space:

    192.168.x.x is a Private Internet address Class C that support 65534 hosts

    BUT

    10.x.x.x is a Private Internet address Class A that support 16777214 hosts

    Such is the case with my ISP, DSLExtreme. I am assigned a 10.x.x.x address

    Verizon has recently talked about switching to 10.x.x.x addresses in the future.

    And of course, some college campuses use the 10.x.x.x as well. These address are considered 'private' because their not legal address for use with DNS lookup and are not route-able on the public Internet. The official Internet Standards Document RFC 1918 (which is easily found on GOOGLE) describes its use and limitations.

    'Private Address' space was originally developed as a response for the Internet running out of IPv4 addresses. Originally, every computer connected to the Internet was suppose to have a unique Internet address. Now there are too many computers to do this, so...

    Though if Verizon is talking about using the 10.x.x.x address space, (which huge potential pitfalls as far as DNS is concerned), it sounds like they want to avoid the expense of upgrading to IPv6 address space, which would completely solve the address space issue, as IPv6 address space is so large, it has enough to provide 6 or 7 unique address for every square meter on planet earth...
  • legetdumarlegetdumar Member Posts: 263
    edited October 2013
    grouchyotaku wrote: »
    Now I wonder... 192.168.1.x is obviously a 'private address' range and represents your gateway router. 10.x.x.x is also a 'private address' range, but is less commonly used. If this address belongs to your ISP, then this would indicate your ISP has some serious issues routing traffic onto the 'public' Internet...

    Oh, believe me, our ISP got an earful today, lol. I noticed that as well. ;)

    But also, pointing out PWE's numbers was meant to prod them to at least look into things on their end, since expecting them fix the internet is a little much. :P
    Criticism, while never agreeable, is necessary. It is like pain in the body. It brings attention to an unhealthy state of things---Winston Churchill
Sign In or Register to comment.