test content
What is the Arc Client?
Install Arc

Very Bad Lag Patcher Site Reports As Down

leadme2kirkleadme2kirk Member Posts: 1,273 Arc User
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Admin>tracert crypticstudios.com

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

1 39 ms 37 ms

2 23 ms 18 ms
3 10 ms 12 ms

4 14 ms 15 ms

5 22 ms 19 ms 18 ms ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]
6 17 ms 18 ms 18 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 20 ms 18 ms 18 ms be3021.ccr41.iad02.atlas.cogentco.com [154.54.10
.209]
8 18 ms 19 ms 18 ms be2112.mpd22.dca01.atlas.cogentco.com [154.54.5.
234]
9 28 ms 31 ms 24 ms be2151.ccr42.jfk02.atlas.cogentco.com [154.54.40
.74]
10 35 ms 31 ms 31 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
11 31 ms 30 ms 31 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
12 30 ms 34 ms 35 ms 38.111.40.114
13 31 ms 31 ms 32 ms sitedown.crypticstudios.com [208.95.185.46]

Trace complete.

Previous tracert was going through gtt.net instead on congentco
Post edited by Unknown User on

Comments

  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited December 2014
    ...
    Trace complete.

    Previous tracert was going through gtt.net instead on congentco

    Though in reality, the 'Trace Route' is showing excellent network latency values. So what ever is causing your problems, its not a network latency issue...

    Now if we only had the 'Net Test' diagnostic results (which test for open network ports and sustained network throughput) and the 'Path Ping' results (which checks for lost or thrown away data packets along your connection route) ...
  • shaunmanxshaunmanx Member Posts: 3 Arc User
    edited December 2014
    The servers are down again this morning as well
  • edited December 2014
    This content has been removed.
  • edited December 2014
    This content has been removed.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited December 2014
    Forgot about Net test cause my antivirus quarantined it.

    Net test results:

    contacting nettest server..
    Local IP:
    Ping: 29.5 msec
    Port: 80: 1183 KB/sec 42 KB/sec 1250 KB/sec 500
    Port: 80: 1174 KB/sec 41 KB/sec 1239 KB/sec 500
    Port: 443: 1206 KB/sec 43 KB/sec 1273 KB/sec 500
    Port: 443: 1188 KB/sec 42 KB/sec 1254 KB/sec 500
    Port: 7255: 343 KB/sec 13 KB/sec 362 KB/sec 500
    Port: 7255: 1145 KB/sec 40 KB/sec 1208 KB/sec 500
    Port: 7003: 932 KB/sec 38 KB/sec 982 KB/sec 500
    Port: 7003: 497 KB/sec 20 KB/sec 524 KB/sec 500
    Port: 7202: 571 KB/sec 23 KB/sec 604 KB/sec 500
    Port: 7202: 922 KB/sec 39 KB/sec 973 KB/sec 500
    Port: 7499: 712 KB/sec 29 KB/sec 751 KB/sec 500
    Port: 7499: 1166 KB/sec 41 KB/sec 1231 KB/sec 500
    Port: 80: 1094 KB/sec 47 KB/sec 1155 KB/sec 500
    Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
    hit return to exit

    So 'Net Test' shows that you can't maintain a consistent sustained network connection throughput, which hints at a intermittent connection quality issue of some kind, possibly network load based...

    And the pathping:

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

    C:\Users\Admin>pathping patchserver.crypticstudios.com

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0
    1
    2
    3 cpe-024-025-062-022.ec.res.rr.com [24.25.62.22]
    4 be31.drhmncev01r.southeast.rr.com [24.93.64.184]
    5 107.14.19.42
    6 ae-0-0.pr0.dca20.tbone.rr.com [66.109.6.183]
    7 be3021.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
    8 be2112.mpd22.dca01.atlas.cogentco.com [154.54.5.234]
    9 be2151.ccr42.jfk02.atlas.cogentco.com [154.54.40.74]
    10 be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
    11 te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
    12 38.111.40.114
    13 patchserver2.crypticstudios.com [208.95.185.41]

    Computing statistics for 325 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0
    0/ 100 = 0% |
    1 19ms 0/ 100 = 0% 0/ 100 = 0%
    0/ 100 = 0% |
    2 24ms 0/ 100 = 0% 0/ 100 = 0%
    0/ 100 = 0% |
    3 12ms 0/ 100 = 0% 0/ 100 = 0%
    0/ 100 = 0% |
    4 14ms 0/ 100 = 0% 0/ 100 = 0% be31.drhmncev01r.southeast.rr.com
    [24.93.64.184]
    0/ 100 = 0% |
    5 20ms 0/ 100 = 0% 0/ 100 = 0% 107.14.19.42
    0/ 100 = 0% |
    6 22ms 0/ 100 = 0% 0/ 100 = 0% ae-0-0.pr0.dca20.tbone.rr.com [66.
    109.6.183]
    0/ 100 = 0% |
    7 19ms 0/ 100 = 0% 0/ 100 = 0% be3021.ccr41.iad02.atlas.cogentco.
    com [154.54.10.209]
    0/ 100 = 0% |
    8 --- 100/ 100 =100% 100/ 100 =100% be2112.mpd22.dca01.atlas.cogentco.
    com [154.54.5.234]
    0/ 100 = 0% |
    9 26ms 0/ 100 = 0% 0/ 100 = 0% be2151.ccr42.jfk02.atlas.cogentco.
    com [154.54.40.74]
    0/ 100 = 0% |
    10 32ms 0/ 100 = 0% 0/ 100 = 0% be2096.ccr22.bos01.atlas.cogentco.
    com [154.54.30.42]
    0/ 100 = 0% |
    11 59ms 0/ 100 = 0% 0/ 100 = 0% te3-2.ccr01.bos06.atlas.cogentco.c
    om [154.54.46.130]
    0/ 100 = 0% |
    12 36ms 0/ 100 = 0% 0/ 100 = 0% 38.111.40.114
    0/ 100 = 0% |
    13 31ms 0/ 100 = 0% 0/ 100 = 0% patchserver2.crypticstudios.com [2
    08.95.185.41]

    Trace complete.

    C:\Users\Admin>

    Now a 100% Packet loss could be caused by the backbone router being configured not to support the network protocol that 'Path Ping' uses, but if this was the case, you would normally expect this behavior on all the nodes of the Cogent Backbone, and this is not the case...

    So assuming that the issue is being caused by traffic congestion on the Cogent Backbone, you should open a Ticket with Cryptic with the 'Net Test' and 'Path Ping' information, so that Cryptic/PWE can kick Cogent a few more times to try to get this addressed...

    You can also try the 'Proxy' setting in the Launcher Option Menu to see if this setting will let you bypass the suspected network congestion... It may, or may not work, but it doesn't hurt to try, as you can always change the settings back later...
  • edited December 2014
    This content has been removed.
Sign In or Register to comment.