test content
What is the Arc Client?
Install Arc
Options

Persistent and recurring problem getting thru to patchserver.crypticstudios.com

First let me post my network tests:

tracert patchserver.crypticstudios.com

1 <1 ms 1 ms <1 ms ***.***.***.*** (purposely hidden)
2 33 ms 33 ms 30 ms 112.211.192.1.pldt.net [112.211.192.1]
3 30 ms 30 ms 31 ms 122.2.135.29.pldt.net [122.2.135.29]
4 30 ms 31 ms 52 ms 210.213.133.82.static.pldt.net [210.213.133.82]
5 30 ms 31 ms 31 ms 210.213.128.29.static.pldt.net [210.213.128.29]
6 29 ms 31 ms 31 ms 210.213.130.170.static.pldt.net [210.213.130.170]
7 192 ms 194 ms 193 ms be4082.ccr21.sea02.atlas.cogentco.com [38.88.253.225]
8 214 ms 212 ms 212 ms be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.198]
9 212 ms 212 ms 211 ms be3037.ccr21.den01.atlas.cogentco.com [154.54.41.146]
10 218 ms 218 ms 217 ms be3035.ccr21.mci01.atlas.cogentco.com [154.54.5.90]
11 231 ms 229 ms 229 ms be2831.ccr41.ord01.atlas.cogentco.com [154.54.42.166]
12 239 ms 237 ms 237 ms be2717.ccr21.cle04.atlas.cogentco.com [154.54.6.222]
13 331 ms 330 ms 330 ms be2878.ccr21.alb02.atlas.cogentco.com [154.54.26.130]
14 332 ms 333 ms 332 ms be2299.ccr31.bos01.atlas.cogentco.com [154.54.43.9]
15 329 ms 329 ms * te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.134]
16 335 ms 335 ms * 38.111.40.114
17 * 330 ms 330 ms 198.49.243.253
18 * * * Request timed out.
19 * * 335 ms patchserver2.crypticstudios.com [208.95.185.41]

pathping patchserver.crypticstudios.com

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
0 ****.****.**** [***.***.***.***] (purposely hidden)
1 ***.***.***.*** (purposely hidden)
2 112.211.192.1.pldt.net [112.211.192.1]
3 122.2.135.29.pldt.net [122.2.135.29]
4 210.213.133.82.static.pldt.net [210.213.133.82]
5 210.213.128.29.static.pldt.net [210.213.128.29]
6 210.213.130.170.static.pldt.net [210.213.130.170]
7 be4082.ccr21.sea02.atlas.cogentco.com [38.88.253.225]
8 be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.198]
9 be3037.ccr21.den01.atlas.cogentco.com [154.54.41.146]
10 be3035.ccr21.mci01.atlas.cogentco.com [154.54.5.90]
11 be2831.ccr41.ord01.atlas.cogentco.com [154.54.42.166]
12 be2717.ccr21.cle04.atlas.cogentco.com [154.54.6.222]
13 be2878.ccr21.alb02.atlas.cogentco.com [154.54.26.130]
14 be2299.ccr31.bos01.atlas.cogentco.com [154.54.43.9]
15 te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.134]
16 * 38.111.40.114
17 198.49.243.253
18 * * *
Computing statistics for 425 seconds...

At this point pathping died. I can only conjecture the cause to be an unresponsive router after 198.49.243.253 or that said router doesn't return ICMP. Since pathping cannot finish, I'll just post ping results instead (for whatever it's worth).

PS C:\Users\****> ping -n 20 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=334ms TTL=48
Reply from 208.95.185.41: bytes=32 time=335ms TTL=48
Reply from 208.95.185.41: bytes=32 time=335ms TTL=48
Reply from 208.95.185.41: bytes=32 time=334ms TTL=48
Reply from 208.95.185.41: bytes=32 time=333ms TTL=48
Reply from 208.95.185.41: bytes=32 time=334ms TTL=48
Reply from 208.95.185.41: bytes=32 time=335ms TTL=48
Request timed out.
Reply from 208.95.185.41: bytes=32 time=334ms TTL=48
Request timed out.
Request timed out.
Reply from 208.95.185.41: bytes=32 time=335ms TTL=48
Reply from 208.95.185.41: bytes=32 time=335ms TTL=48
Reply from 208.95.185.41: bytes=32 time=336ms TTL=48
Reply from 208.95.185.41: bytes=32 time=335ms TTL=48
Reply from 208.95.185.41: bytes=32 time=334ms TTL=48
Reply from 208.95.185.41: bytes=32 time=333ms TTL=48
Request timed out.
Reply from 208.95.185.41: bytes=32 time=334ms TTL=48
Reply from 208.95.185.41: bytes=32 time=334ms TTL=48

Ping statistics for 208.95.185.41:
Packets: Sent = 20, Received = 16, Lost = 4 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 333ms, Maximum = 336ms, Average = 334ms

Nettest server is unresponsive when I tried to connect to it.

The results above is typical of when I cannot connect to the game. The game will typically bring me to the character selection screen (after some laboring trying to get there) and then fail to load the character with a login server timeout error. Other times it just stays at the "Patching" stage of the launcher.

As my title says, this problem is recurring and consistent with no discernible time pattern of its occurence (it can happen at any time of the day). It typically lasts for hours before I can "normally" play the game again. In my limited networking knowledge, I'm guessing that a router between 198.49.243.253 and 208.95.185.41 is overworked and probably underpaid. I am also guessing that these IP addresses suggest "internal" servers/routers within the Cryptic network.

I would appreciate any insights on this recurring problem.

Comments

  • Options
    salvation4salvation4 Member Posts: 1,167 Arc User
    Use cyberghost VPN..I use it whenever I cant get thru directly..And off late I've had to use it a bit too regularly..Ever since the last two patches more precisely..Also I have noticed when there are events this happens alot and more so towards the end of the events..So basically the server isint well equipped to handle high load capacities..
    Adrian-Uss Sovereign NCC-73811 (LVL 65 FED ENG) UR/E MKXV Fleet Intel Assault Cruiser (April 2012) (Main)
    Adu-Uss Firefox NCC-93425-F (LVL 65 FED AoY ENG) UR/VR MKXV Fleet Intel Assault Cruiser (July 2016)
    Jean-Uss Seratoga Ravenna (LVL 60 FED Delta ENG) UC/R MKVI Bajoran Escort (April 2018)
    Dubsa-RRW Mnaudh (LVL 50 FED allied ROM Delta ENG) Warbird (May 2018)
    Marop-IKS Orunthi (LVL 50 KNG Delta ENG) BoP (May 2018)
    Kanak'lan-TRIBBLE (LVL 65 DOM Gamma ENG) TRIBBLE (June 2018)
  • Options
    slycereslycere Member Posts: 30 Arc User
    salvation4 wrote: »
    Use cyberghost VPN..I use it whenever I cant get thru directly..And off late I've had to use it a bit too regularly..Ever since the last two patches more precisely..Also I have noticed when there are events this happens alot and more so towards the end of the events..So basically the server isint well equipped to handle high load capacities..

    Thank you for this tip. Look at my tracert now:

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

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

    1 195 ms 196 ms 195 ms 10.129.0.1
    2 196 ms 197 ms 195 ms vlan19.bb1.lax1.us.m247.com [38.95.109.33]
    3 196 ms 195 ms 197 ms te0-0-1-0.201.nr11.b002695-2.lax04.atlas.cogentco.com [38.140.40.49]
    4 198 ms 196 ms 196 ms te0-0-2-2.agr12.lax04.atlas.cogentco.com [154.24.29.93]
    5 196 ms 195 ms 196 ms te0-9-0-30.ccr41.lax04.atlas.cogentco.com [154.54.45.121]
    6 195 ms 196 ms 199 ms be2964.ccr21.lax01.atlas.cogentco.com [154.54.44.77]
    7 208 ms 207 ms * be2931.ccr21.phx02.atlas.cogentco.com [154.54.44.85]
    8 216 ms 217 ms 216 ms be2929.ccr21.elp01.atlas.cogentco.com [154.54.42.66]
    9 258 ms 259 ms 258 ms be2928.ccr42.iah01.atlas.cogentco.com [154.54.30.161]
    10 258 ms 259 ms 258 ms be2690.ccr42.atl01.atlas.cogentco.com [154.54.28.129]
    11 265 ms 264 ms 264 ms be2113.ccr42.dca01.atlas.cogentco.com [154.54.24.221]
    12 263 ms 263 ms 264 ms be2807.ccr42.jfk02.atlas.cogentco.com [154.54.40.109]
    13 269 ms 268 ms 269 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
    14 270 ms 269 ms 270 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
    15 271 ms 270 ms 268 ms 38.111.40.114
    16 268 ms 269 ms 268 ms 198.49.243.253
    17 271 ms 269 ms 269 ms 10.251.192.21
    18 269 ms 270 ms 269 ms xboxpatchserver.crypticstudios.com [208.95.185.41]

    Trace complete.

    The trace actually completed.

    And i have no dropped packets:

    C:\Users\*****> ping -n 20 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=268ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=269ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=268ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=268ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=269ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=266ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=268ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=269ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=279ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=268ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=269ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=268ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=266ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=269ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=268ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=267ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=268ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=269ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=266ms TTL=52
    Reply from 208.95.185.41: bytes=32 time=268ms TTL=52

    Ping statistics for 208.95.185.41:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 266ms, Maximum = 279ms, Average = 268ms

    My ping was even better than my direct connection posted above. Which begs the question: Is there an IP-based throttling rule on Cryptic servers?
  • Options
    salvation4salvation4 Member Posts: 1,167 Arc User
    Welcome..And yes I suspect there is a throttle issue..Been suspecting it ever since I returned to STO last year..
    Adrian-Uss Sovereign NCC-73811 (LVL 65 FED ENG) UR/E MKXV Fleet Intel Assault Cruiser (April 2012) (Main)
    Adu-Uss Firefox NCC-93425-F (LVL 65 FED AoY ENG) UR/VR MKXV Fleet Intel Assault Cruiser (July 2016)
    Jean-Uss Seratoga Ravenna (LVL 60 FED Delta ENG) UC/R MKVI Bajoran Escort (April 2018)
    Dubsa-RRW Mnaudh (LVL 50 FED allied ROM Delta ENG) Warbird (May 2018)
    Marop-IKS Orunthi (LVL 50 KNG Delta ENG) BoP (May 2018)
    Kanak'lan-TRIBBLE (LVL 65 DOM Gamma ENG) TRIBBLE (June 2018)
  • Options
    ekypyrosekypyros Member Posts: 181 Arc User
    edited March 2017
    The Problem ist on your Side btw your provider
    I have Tracert from me to you first internet node 112.211.192.1.pldt.net [112.211.192.1]
    1     1 ms    <1 ms    <1 ms  TRIBBLE.TRIBBLE.TRIBBLE.TRIBBLE
      2    15 ms    12 ms    14 ms  TRIBBLE.TRIBBLE.TRIBBLE.TRIBBLE
      3    11 ms     *       19 ms  TRIBBLE.TRIBBLE.TRIBBLE.TRIBBLE
      4    24 ms    15 ms    17 ms  84.116.140.190
      5    19 ms    19 ms    18 ms  ae22.r03.frnkge03.de.bb.gin.ntt.net [62.69.146.85]
      6    34 ms    94 ms    14 ms  ae-0.r20.frnkge04.de.bb.gin.ntt.net [129.250.2.13]
      7   115 ms   109 ms   117 ms  ae-8.r22.asbnva02.us.bb.gin.ntt.net [129.250.4.96]
      8   179 ms   186 ms   173 ms  ae-5.r23.lsanca07.us.bb.gin.ntt.net [129.250.3.189]
      9   179 ms   173 ms   174 ms  ae-2.r01.lsanca07.us.bb.gin.ntt.net [129.250.4.107]
     10   320 ms   324 ms   441 ms  ae-0.pldt.lsanca07.us.bb.gin.ntt.net [129.250.201.206]
     11   342 ms   339 ms   339 ms  210.213.133.102.static.pldt.net [210.213.133.102]
     12   345 ms   339 ms   339 ms  210.213.133.77.static.pldt.net [210.213.133.77]
     13   339 ms   347 ms   344 ms  112.211.192.1.pldt.net [112.211.192.1]
    

    Then my Tracert to patchserver.crypticstudios.com
    1     1 ms     1 ms     1 ms  TRIBBLE.TRIBBLE.TRIBBLE.TRIBBLE
      2    16 ms     9 ms    12 ms  TRIBBLE.TRIBBLE.TRIBBLE.TRIBBLE
      3    12 ms    27 ms    16 ms  TRIBBLE.TRIBBLE.TRIBBLE.TRIBBLE
      4    17 ms    16 ms    17 ms  de-fra01b-ri2-ae32-0.aorta.net [84.116.134.190]
      5    19 ms    18 ms    14 ms  213.46.177.138
      6    26 ms    99 ms    19 ms  be2814.ccr42.ams03.atlas.cogentco.com [130.117.0.141]
      7    26 ms    31 ms    26 ms  be12488.ccr42.lon13.atlas.cogentco.com [130.117.51.41]
      8   100 ms    99 ms    99 ms  be2983.ccr22.bos01.atlas.cogentco.com [154.54.1.178]
      9    97 ms    97 ms   106 ms  te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
     10   102 ms   101 ms   104 ms  38.111.40.114
     11   107 ms    99 ms    99 ms  198.49.243.253
     12     *      105 ms     *     198.49.243.253
     13     *        *        *     Zeitüberschreitung der Anforderung.
     14    97 ms    97 ms    98 ms  patchserver2.crypticstudios.com [208.95.185.41]
    

    And Iam in Germany so i have normal latenz 100 ms int to the USA

    The Problem what you have ist not Cryptic Network its Your Internet Provider Routing

    Change Provider or Contact tecnical Service fom you Provider

    greets
    Ekypyros
Sign In or Register to comment.