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

Lagging since yesterday's patch

sovereign010sovereign010 Member Posts: 641 Arc User
edited November 2014 in Windows and General: PC, Network, and Other Technical Issues
I don't know what you guys did, but ever since yesterday's update my game has been lagging to the point of utter uselessness, even a complete reinstall of 10GB worth of data has done nothing to resolve the problem.

Already did a speed test, results are here: http://www.speedtest.net/my-result/3891433812

Tracert:

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

1 2 ms 2 ms 5 ms BTHUB4 [192.168.x.TRIBBLE]
2 71 ms 57 ms 59 ms 217.41.165.186
3 25 ms 24 ms 24 ms 217.41.165.193
4 32 ms 25 ms 25 ms 213.1.69.198
5 * * 28 ms 213.120.162.69
6 83 ms 93 ms 62 ms 31.55.165.109
7 28 ms 31 ms 27 ms acc2.10GigE-7-2-0.mr.21cn-ipp.bt.net [109.159.20.224]
8 40 ms 43 ms 46 ms core1-te0-13-0-15.ilford.ukcore.bt.net [109.159.250.164]
9 62 ms 62 ms 68 ms peer3-te0-3-0-1.telehouse.ukcore.bt.net [62.172.102.9]
10 33 ms 34 ms 35 ms 166-49-211-244.eu.bt.net [166.49.211.244]
11 34 ms 34 ms 34 ms be3035.ccr21.lon01.atlas.cogentco.com [130.117.4.169]
12 37 ms 36 ms 40 ms be2398.ccr22.lon01.atlas.cogentco.com [130.117.1.210]
13 34 ms 34 ms 44 ms be2494.ccr42.lon13.atlas.cogentco.com [154.54.3.130]
14 115 ms 115 ms 116 ms be2493.ccr22.bos01.atlas.cogentco.com [154.54.4.97]
15 113 ms 112 ms 112 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.24]
16 128 ms 137 ms 137 ms 38.111.40.114
17 116 ms 143 ms 125 ms patchserver2.crypticstudios.com [208.95.185.41]


Trace complete.

Nettest:

contacting nettest server..
Local IP: 81.135.68.196
Ping: 115.4 msec
Port: 80: 418 KB/sec 15 KB/sec 442 KB/sec 500
Port: 80: 422 KB/sec 15 KB/sec 446 KB/sec 500
Port: 443: 400 KB/sec 15 KB/sec 424 KB/sec 500
Port: 443: 412 KB/sec 15 KB/sec 436 KB/sec 500
Port: 7255: 422 KB/sec 15 KB/sec 447 KB/sec 500
Port: 7255: 415 KB/sec 15 KB/sec 439 KB/sec 500
Port: 7003: 398 KB/sec 15 KB/sec 421 KB/sec 500
Port: 7003: 417 KB/sec 15 KB/sec 441 KB/sec 500
Port: 7202: 407 KB/sec 15 KB/sec 430 KB/sec 500
Port: 7202: 414 KB/sec 15 KB/sec 438 KB/sec 500
Port: 7499: timed out
Port: 7499: 252 KB/sec 21 KB/sec 692 KB/sec 500
Port: 80: 172 KB/sec 19 KB/sec 804 KB/sec 500
Idle NIC bandwidth Send: 16 KB/sec Recv: 817 KB/sec
hit return to exit
Post edited by sovereign010 on

Comments

  • eurialoeurialo Member Posts: 667 Arc User
    edited November 2014
    same for me

    Traccia instradamento verso patchserver.crypticstudios.com [208.95.185.41]
    su un massimo di 30 punti di passaggio:

    1 1 ms 1 ms 1 ms 192.168.0.1
    2 24 ms 25 ms 33 ms 10.20.224.1
    3 26 ms 25 ms 25 ms 10.7.104.206
    4 30 ms 30 ms 31 ms 10.250.18.24
    5 30 ms 30 ms 30 ms 10.250.19.1
    6 25 ms 25 ms 24 ms 10.247.126.129
    7 36 ms 37 ms 37 ms 10.250.23.186
    8 42 ms 41 ms 41 ms 10.7.8.149
    9 42 ms 41 ms 41 ms 10.7.0.13
    10 47 ms 46 ms 46 ms 10.254.2.209
    11 57 ms 54 ms 58 ms 10.254.0.125
    12 56 ms 58 ms 57 ms 10.254.12.21
    13 162 ms 63 ms 57 ms 10.254.12.6
    14 67 ms 71 ms 68 ms 89.97.200.186
    15 67 ms 74 ms 70 ms 89.97.200.254
    16 77 ms 72 ms 76 ms 89.96.200.18
    17 120 ms 115 ms 120 ms te0-6-0-2.rcr21.mil01.atlas.cogentco.com [149.6.152.209]
    18 119 ms 121 ms 118 ms be2043.ccr21.zrh01.atlas.cogentco.com [154.54.38.101]
    19 119 ms 119 ms 115 ms be2023.ccr21.muc01.atlas.cogentco.com [130.117.0.249]
    20 131 ms 133 ms 130 ms be2228.ccr41.fra03.atlas.cogentco.com [154.54.38.49]
    21 133 ms 132 ms 134 ms be2261.ccr41.ams03.atlas.cogentco.com [154.54.37.29]
    22 146 ms 152 ms 151 ms be2182.ccr21.lpl01.atlas.cogentco.com [154.54.77.246]
    23 218 ms 220 ms 221 ms be2386.ccr21.bos01.atlas.cogentco.com [154.54.44.161]
    24 215 ms 210 ms 228 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
    25 223 ms 214 ms 218 ms 38.111.40.114
    26 218 ms 218 ms 223 ms patchserver2.crypticstudios.com [208.95.185.41]

    Traccia completata.
    [SIGPIC][/SIGPIC]

    Playing STO spamming FAW is like playing chess using always the computer's suggested moves
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited November 2014
    sovereign010 wrote: »
    I don't know what you guys did, but ever since yesterday's update my game has been lagging to the point of utter uselessness, even a complete reinstall of 10GB worth of data has done nothing to resolve the problem.

    Already did a speed test, results are here: http://www.speedtest.net/my-result/3891433812

    ...

    Though in reality, the Speed Test connects to a diagnostic Server that has nothing to do with the network where the STO Servers are located, which makes the results invalid for solving your problem...

    'Net Test' is much more useful, as the diagnostic Server it uses is located on the same network as the STO Servers... The inconsistent sustained throughput results of 'Net Test' shows that you can't maintain a reliable network connection quality to the network where the STO Servers are located. And since the 'Net Test' uses a simple diagnostic server, (so the STO Servers are out of the picture with the Net Test results) this shows that the problem is a connection quality issue and not a STO Server issue...

    The 'Trace Route' isn't showing anything particularly bad, as far as network latency is concerned. But network latency isn't everything needed to maintain a quality connection, and there's probably some other issue present that 'Trace Route' won't pick up...

    Now what we really need here are the 'Path Ping' diagnostic results, as this will provided a more detailed result on connection quality issue on the path your ISP is using to reach the STO Servers...
  • sovereign010sovereign010 Member Posts: 641 Arc User
    edited November 2014
    Pathping:

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 Steve-PC.home [192.168.x.TRIBBLE]
    1 BTHUB4 [192.168.x.TRIBBLE]
    2 217.41.165.186
    3 217.41.165.193
    4 213.1.69.198
    5 213.120.162.69
    6 31.55.165.109
    7 acc2.10GigE-7-2-0.mr.21cn-ipp.bt.net [109.159.250.224]
    8 core1-te0-13-0-15.ilford.ukcore.bt.net [109.159.250.164]
    9 peer3-te0-3-0-1.telehouse.ukcore.bt.net [62.172.102.9]
    10 166-49-211-244.eu.bt.net [166.49.211.244]
    11 be3035.ccr21.lon01.atlas.cogentco.com [130.117.14.169]
    12 be2398.ccr22.lon01.atlas.cogentco.com [130.117.51.210]
    13 be2494.ccr42.lon13.atlas.cogentco.com [154.54.39.130]
    14 be2493.ccr22.bos01.atlas.cogentco.com [154.54.42.97]
    15 te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
    16 38.111.40.114
    17 patchserver2.crypticstudios.com [208.95.185.41]

    Computing statistics for 425 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Steve-PC.home [192.168.x.TRIBBLE] 0/ 100 = 0% |
    1 4ms 0/ 100 = 0% 0/ 100 = 0% BTHUB4 [192.168.x.TRIBBLE] 0/ 100 = 0% |
    2 29ms 0/ 100 = 0% 0/ 100 = 0% 217.41.165.186 0/ 100 = 0% |
    3 --- 100/ 100 =100% 100/ 100 =100% 217.41.165.193 0/ 100 = 0% |
    4 31ms 38/ 100 = 38% 38/ 100 = 38% 213.1.69.198 0/ 100 = 0% |
    5 29ms 32/ 100 = 32% 32/ 100 = 32% 213.120.162.69 0/ 100 = 0% |
    6 28ms 0/ 100 = 0% 0/ 100 = 0% 31.55.165.109 0/ 100 = 0% |
    7 34ms 20/ 100 = 20% 20/ 100 = 20% acc2.10GigE-7-2-0.mr.21cn-ipp.bt.net [109.159.250.224] 0/ 100 = 0% |
    8 43ms 21/ 100 = 21% 21/ 100 = 21% core1-te0-13-0-15.ilford.ukcore.bt
    .net [109.159.250.164] 0/ 100 = 0% |
    9 35ms 0/ 100 = 0% 0/ 100 = 0% peer3-te0-3-0-1.telehouse.ukcore.bt.net [62.172.102.9] 0/ 100 = 0% |
    10 37ms 0/ 100 = 0% 0/ 100 = 0% 166-49-211-244.eu.bt.net [166.49.211.244] 0/ 100 = 0% |
    11 36ms 0/ 100 = 0% 0/ 100 = 0% be3035.ccr21.lon01.atlas.cogentco.com [130.117.14.169] 0/ 100 = 0% |
    12 42ms 0/ 100 = 0% 0/ 100 = 0% be2398.ccr22.lon01.atlas.cogentco.com [130.117.51.210] 0/ 100 = 0% |
    13 36ms 0/ 100 = 0% 0/ 100 = 0% be2494.ccr42.lon13.atlas.cogentco.
    com [154.54.39.130] 0/ 100 = 0% |
    14 121ms 0/ 100 = 0% 0/ 100 = 0% be2493.ccr22.bos01.atlas.cogentco.
    com [154.54.42.97] 0/ 100 = 0% |
    15 --- 100/ 100 =100% 100/ 100 =100% te4-2.ccr01.bos06.atlas.cogentco.c
    om [66.28.4.254] 0/ 100 = 0% |
    16 130ms 0/ 100 = 0% 0/ 100 = 0% 38.111.40.114 0/ 100 = 0% |
    17 126ms 0/ 100 = 0% 0/ 100 = 0% patchserver2.crypticstudios.com [208.95.185.41]

    Trace complete.

    I'm gonna have to do some serious reading up in order to make heads or tails of this! :D
  • sovereign010sovereign010 Member Posts: 641 Arc User
    edited November 2014
    PS, forgot to say I was located in the UK.
  • chiapetzorz1988chiapetzorz1988 Member Posts: 2 Arc User
    edited November 2014
    Sorry to step in, but I am apparently not allowed to post new threads.

    I've been having some serious issues that last little while, and running the trace and net test today, has revealed this.


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

    C:\Users\Gene CO>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 TRIBBLE.TRIBBLE.TRIBBLE.TRIBBLE
    2 * * * Request timed out.
    3 8 ms 10 ms 11 ms 69.63.254.73
    4 13 ms 10 ms 10 ms 69.63.251.41
    5 15 ms 15 ms 16 ms 69.63.251.45
    6 * * * Request timed out.
    7 29 ms 29 ms 28 ms be3056.ccr21.jfk05.atlas.cogentco.com [154.54.13
    .33]
    8 29 ms 28 ms 27 ms be2063.mpd22.jfk02.atlas.cogentco.com [154.54.47
    .57]
    9 34 ms 33 ms 33 ms be2097.ccr22.bos01.atlas.cogentco.com [154.54.30
    .118]
    10 34 ms 34 ms 33 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
    4]
    11 46 ms 34 ms 35 ms 38.111.40.114
    12 35 ms 35 ms 35 ms patchserver2.crypticstudios.com [208.95.185.41]


    Trace complete.


    And the net test shows this.

    contacting nettest server..
    Local IP: 99.251.112.217
    Ping: 34.5 msec
    Port: 80: 913 KB/sec 22 KB/sec 963 KB/sec 500
    Port: 80: 819 KB/sec 20 KB/sec 863 KB/sec 500
    Port: 443: 755 KB/sec 19 KB/sec 796 KB/sec 500
    Port: 443:

    At which time it hangs indefinitely.

    running Pingplotter to the patchserver also shows me an unresponsive router at the hop 2, with 100% packet loss. Hop 6, 69.63.248.89, also goes from being perfectly fine, to unresponsive with 100% packet loss.

    I've already had rogers cable come out and install a new line to my apartment yesterday, So I'm not sure what exactly is going on.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited November 2014
    sovereign010 wrote: »
    Pathping:

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 Steve-PC.home [192.168.x.TRIBBLE]
    1 BTHUB4 [192.168.x.TRIBBLE]
    2 217.41.165.186
    3 217.41.165.193
    4 213.1.69.198
    5 213.120.162.69
    6 31.55.165.109
    7 acc2.10GigE-7-2-0.mr.21cn-ipp.bt.net [109.159.250.224]
    8 core1-te0-13-0-15.ilford.ukcore.bt.net [109.159.250.164]
    9 peer3-te0-3-0-1.telehouse.ukcore.bt.net [62.172.102.9]
    10 166-49-211-244.eu.bt.net [166.49.211.244]
    11 be3035.ccr21.lon01.atlas.cogentco.com [130.117.14.169]
    12 be2398.ccr22.lon01.atlas.cogentco.com [130.117.51.210]
    13 be2494.ccr42.lon13.atlas.cogentco.com [154.54.39.130]
    14 be2493.ccr22.bos01.atlas.cogentco.com [154.54.42.97]
    15 te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
    16 38.111.40.114
    17 patchserver2.crypticstudios.com [208.95.185.41]

    Computing statistics for 425 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Steve-PC.home [192.168.x.TRIBBLE] 0/ 100 = 0% |
    1 4ms 0/ 100 = 0% 0/ 100 = 0% BTHUB4 [192.168.x.TRIBBLE] 0/ 100 = 0% |
    2 29ms 0/ 100 = 0% 0/ 100 = 0% 217.41.165.186 0/ 100 = 0% |
    3 --- 100/ 100 =100% 100/ 100 =100% 217.41.165.193 0/ 100 = 0% |
    4 31ms 38/ 100 = 38% 38/ 100 = 38% 213.1.69.198 0/ 100 = 0% |
    5 29ms 32/ 100 = 32% 32/ 100 = 32% 213.120.162.69 0/ 100 = 0% |
    6 28ms 0/ 100 = 0% 0/ 100 = 0% 31.55.165.109 0/ 100 = 0% |
    7 34ms 20/ 100 = 20% 20/ 100 = 20% acc2.10GigE-7-2-0.mr.21cn-ipp.bt.net [109.159.250.224] 0/ 100 = 0% |
    8 43ms 21/ 100 = 21% 21/ 100 = 21% core1-te0-13-0-15.ilford.ukcore.bt
    .net [109.159.250.164] 0/ 100 = 0% |
    9 35ms 0/ 100 = 0% 0/ 100 = 0% peer3-te0-3-0-1.telehouse.ukcore.bt.net [62.172.102.9] 0/ 100 = 0% |
    10 37ms 0/ 100 = 0% 0/ 100 = 0% 166-49-211-244.eu.bt.net [166.49.211.244] 0/ 100 = 0% |
    11 36ms 0/ 100 = 0% 0/ 100 = 0% be3035.ccr21.lon01.atlas.cogentco.com [130.117.14.169] 0/ 100 = 0% |
    12 42ms 0/ 100 = 0% 0/ 100 = 0% be2398.ccr22.lon01.atlas.cogentco.com [130.117.51.210] 0/ 100 = 0% |
    13 36ms 0/ 100 = 0% 0/ 100 = 0% be2494.ccr42.lon13.atlas.cogentco.
    com [154.54.39.130] 0/ 100 = 0% |
    14 121ms 0/ 100 = 0% 0/ 100 = 0% be2493.ccr22.bos01.atlas.cogentco.
    com [154.54.42.97] 0/ 100 = 0% |
    15 --- 100/ 100 =100% 100/ 100 =100% te4-2.ccr01.bos06.atlas.cogentco.c
    om [66.28.4.254] 0/ 100 = 0% |
    16 130ms 0/ 100 = 0% 0/ 100 = 0% 38.111.40.114 0/ 100 = 0% |
    17 126ms 0/ 100 = 0% 0/ 100 = 0% patchserver2.crypticstudios.com [208.95.185.41]

    Trace complete.

    I'm gonna have to do some serious reading up in order to make heads or tails of this! :D

    Now this explains why you have connection quality issues to the STO Servers. To have a reliable TCP/IP connection you should be having ZERO PACKET LOSS for the connection and you have...

    Now a 100% loss could be caused the node configuration not supporting the protocol that 'Path Ping' uses, but values that are not 100% are real. And any measurable packet loss will cause issues with time synced networked applications, such as the STO Client...

    Dropped Packets (which are either lost or thrown away by the network) starts at Hop #3, which appears to be in the domain of your ISP. Sounds like you need to contact your ISP technical support and have them look into a dropped packet issue occurring in their networks...
  • sovereign010sovereign010 Member Posts: 641 Arc User
    edited November 2014
    It gets worse:

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 Steve-PC.home [192.168.x.TRIBBLE]
    1 BTHUB4 [192.168.1.254]
    2 217.41.165.186
    3 217.41.165.193
    4 213.1.69.198
    5 213.120.162.69
    6 31.55.165.109
    7 acc2.10GigE-7-2-0.mr.21cn-ipp.bt.net [109.159.250.224]
    8 * core1-te0-13-0-15.ilford.ukcore.bt.net [109.159.250.164]
    9 peer3-te0-3-0-1.telehouse.ukcore.bt.net [62.172.102.9]
    10 166-49-211-244.eu.bt.net [166.49.211.244]
    11 be3035.ccr21.lon01.atlas.cogentco.com [130.117.14.169]
    12 be2398.ccr22.lon01.atlas.cogentco.com [130.117.51.210]
    13 be2494.ccr42.lon13.atlas.cogentco.com [154.54.39.130]
    14 be2493.ccr22.bos01.atlas.cogentco.com [154.54.42.97]
    15 te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
    16 38.111.40.114
    17 patchserver2.crypticstudios.com [208.95.185.41]

    Computing statistics for 425 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Steve-PC.home [192.168.1.213] 0/ 100 = 0% |
    1 3ms 0/ 100 = 0% 0/ 100 = 0% BTHUB4 [192.168.x.TRIBBLE] 0/ 100 = 0% |
    2 29ms 0/ 100 = 0% 0/ 100 = 0% 217.41.165.186 0/ 100 = 0% |
    3 --- 100/ 100 =100% 100/ 100 =100% 217.41.165.193 0/ 100 = 0% |
    4 29ms 38/ 100 = 38% 38/ 100 = 38% 213.1.69.198 0/ 100 = 0% |
    5 30ms 37/ 100 = 37% 37/ 100 = 37% 213.120.162.69 0/ 100 = 0% |
    6 27ms 0/ 100 = 0% 0/ 100 = 0% 31.55.165.109 0/ 100 = 0% |
    7 32ms 33/ 100 = 33% 33/ 100 = 33% acc2.10GigE-7-2-0.mr.21cn-ipp.bt.net [109.159.250.224] 0/ 100 = 0% |
    8 42ms 34/ 100 = 34% 34/ 100 = 34% core1-te0-13-0-15.ilford.ukcore.bt.net [109.159.250.164] 0/ 100 = 0% |
    9 36ms 0/ 100 = 0% 0/ 100 = 0% peer3-te0-3-0-1.telehouse.ukcore.bt.net [62.172.102.9] 0/ 100 = 0% |
    10 37ms 0/ 100 = 0% 0/ 100 = 0% 166-49-211-244.eu.bt.net [166.49.211.244] 0/ 100 = 0% |
    11 36ms 0/ 100 = 0% 0/ 100 = 0% be3035.ccr21.lon01.atlas.cogentco.com [130.117.14.169] 0/ 100 = 0% |
    12 44ms 0/ 100 = 0% 0/ 100 = 0% be2398.ccr22.lon01.atlas.cogentco.com [130.117.51.210] 0/ 100 = 0% |
    13 36ms 0/ 100 = 0% 0/ 100 = 0% be2494.ccr42.lon13.atlas.cogentco.com [154.54.39.130] 0/ 100 = 0% |
    14 123ms 0/ 100 = 0% 0/ 100 = 0% be2493.ccr22.bos01.atlas.cogentco.com [154.54.42.97] 0/ 100 = 0% |
    15 --- 100/ 100 =100% 100/ 100 =100% te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254] 0/ 100 = 0% |
    16 132ms 0/ 100 = 0% 0/ 100 = 0% 38.111.40.114 0/ 100 = 0% |
    17 124ms 0/ 100 = 0% 0/ 100 = 0% patchserver2.crypticstudios.com [208.95.185.41]

    Trace complete.

    Seems there's losses at several points in the chain.
  • aoax10aoax10 Member Posts: 271 Arc User
    edited November 2014
    They are having issues right now with account login. Server goes red, green, red, green. :)
  • sovereign010sovereign010 Member Posts: 641 Arc User
    edited November 2014
    aoax10 wrote: »
    They are having issues right now with account login. Server goes red, green, red, green. :)

    I noticed my client was going up and down, it was doing the same thing yesterday. Glad it's not just mine :)

    To quote Howard from the Big Bang Theory:
    "(Pushing button on elevator) Nah, that baby's broken"
  • aoax10aoax10 Member Posts: 271 Arc User
    edited November 2014
    Would you mind running another tracert in cmd?

    tracert patchserver.crypticstudios.com

    Mine isn't showing up any anomalies even though the STO server is down.
  • aoax10aoax10 Member Posts: 271 Arc User
    edited November 2014
    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 7 ms 7 ms 5 ms 10.104.106.145
    3 6 ms 7 ms 8 ms dtr01yakmwa-tge-0-1-0-15.yakm.wa.charter.com [96.34.106.112]
    4 8 ms 15 ms 12 ms bbr01yakmwa-bue-1.yakm.wa.charter.com [96.34.105.230]
    5 38 ms 31 ms 32 ms bbr02snjsca-bue-3.snjs.ca.charter.com [96.34.2.148]
    6 31 ms 33 ms 31 ms te0-4-0-8.ccr21.sjc03.atlas.cogentco.com [38.104.138.157]
    7 30 ms 31 ms 31 ms be2000.ccr21.sjc01.atlas.cogentco.com [154.54.6.105]
    8 32 ms 32 ms 32 ms be2164.ccr21.sfo01.atlas.cogentco.com [154.54.28.33]
    9 66 ms 65 ms 67 ms be2132.ccr21.mci01.atlas.cogentco.com [154.54.30.54]
    10 72 ms 72 ms 73 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
    11 99 ms 97 ms 96 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43.194]
    12 95 ms 95 ms 96 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
    13 100 ms 110 ms 104 ms 38.111.40.114
    14 98 ms 96 ms 95 ms patchserver2.crypticstudios.com [208.95.185.41]
  • garakfan84garakfan84 Member Posts: 0 Arc User
    edited November 2014
    I keep getting disconnected, server not responding and login time out. Can barely play.
    [SIGPIC][/SIGPIC]
  • imcguigaimcguiga Member Posts: 44 Arc User
    edited November 2014
    I'm getting the same problem, I keep getting disconnected. I started at 2:00 and I've been disconnected 3 times now. I don't understand why this isn't treated as the highest priority issue since it prevents any form of playing. Who cares if a mission is too easy or too tough if you can't stay connected logn enough to start or finish it?
  • sovereign010sovereign010 Member Posts: 641 Arc User
    edited November 2014
    Here it is:

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

    1 2 ms 2 ms 2 ms BTHUB4 [192.168.x.TRIBBLE]
    2 24 ms 25 ms 24 ms 217.41.165.186
    3 25 ms 24 ms 25 ms 217.41.165.193
    4 33 ms 28 ms * 213.1.69.198
    5 28 ms 27 ms 27 ms 213.120.162.69
    6 25 ms 26 ms 26 ms 31.55.165.109
    7 28 ms * * acc2.10GigE-7-2-0.mr.21cn-ipp.bt.net [109.159.250.224]
    8 37 ms 34 ms 34 ms core1-te0-13-0-15.ilford.ukcore.bt.net [109.159.250.164]
    9 33 ms 33 ms 32 ms peer3-te0-3-0-1.telehouse.ukcore.bt.net [62.172.102.9]
    10 35 ms 31 ms 31 ms 166-49-211-244.eu.bt.net [166.49.211.244]
    11 31 ms 31 ms 31 ms be3035.ccr21.lon01.atlas.cogentco.com [130.117.14.169]
    12 37 ms 37 ms 38 ms be2398.ccr22.lon01.atlas.cogentco.com [130.117.51.210]
    13 34 ms 34 ms 34 ms be2494.ccr42.lon13.atlas.cogentco.com [154.54.39.130]
    14 116 ms 116 ms 112 ms be2493.ccr22.bos01.atlas.cogentco.com [154.54.42.97]
    15 117 ms 113 ms 112 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
    16 135 ms 135 ms 137 ms 38.111.40.114
    17 126 ms 124 ms 138 ms patchserver2.crypticstudios.com [208.95.185.41]

    Trace complete.
  • imcguigaimcguiga Member Posts: 44 Arc User
    edited November 2014
    And again.
  • garakfan84garakfan84 Member Posts: 0 Arc User
    edited November 2014
    imcguiga wrote: »
    I'm getting the same problem, I keep getting disconnected. I started at 2:00 and I've been disconnected 3 times now. I don't understand why this isn't treated as the highest priority issue since it prevents any form of playing. Who cares if a mission is too easy or too tough if you can't stay connected logn enough to start or finish it?

    Very true.
    [SIGPIC][/SIGPIC]
  • truewarpertruewarper Member Posts: 930 Arc User
    edited November 2014
    Through PingPlotter, out of 14 hops, three gateway servers are down, with 100% package loss. Two of them, their IP number is even not registering.

    The third --- 208.95.185.225. comes after this one --216.52.61.78/perfectworldent-4border 11.bsn.pnap.net is showing package loss as well, but still able to show its address.

    It is a bad day being a server, somewhere.
    52611496918_3c42b8bab8.jpg
    Departing from Sol *Earth* by Carlos A Smith,on Flickr
    SPACE---The Last and Great Frontier. A 14th-year journey
    Vna res, una mens, unum cor et anima una. Cetera omnia, somnium est.
  • aoax10aoax10 Member Posts: 271 Arc User
    edited November 2014
    sovereign010 wrote: »
    Here it is:

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

    1 2 ms 2 ms 2 ms BTHUB4 [192.168.x.TRIBBLE]
    2 24 ms 25 ms 24 ms 217.41.165.186
    3 25 ms 24 ms 25 ms 217.41.165.193
    4 33 ms 28 ms * 213.1.69.198
    5 28 ms 27 ms 27 ms 213.120.162.69
    6 25 ms 26 ms 26 ms 31.55.165.109
    7 28 ms * * acc2.10GigE-7-2-0.mr.21cn-ipp.bt.net [109.159.250.224]
    8 37 ms 34 ms 34 ms core1-te0-13-0-15.ilford.ukcore.bt.net [109.159.250.164]
    9 33 ms 33 ms 32 ms peer3-te0-3-0-1.telehouse.ukcore.bt.net [62.172.102.9]
    10 35 ms 31 ms 31 ms 166-49-211-244.eu.bt.net [166.49.211.244]
    11 31 ms 31 ms 31 ms be3035.ccr21.lon01.atlas.cogentco.com [130.117.14.169]
    12 37 ms 37 ms 38 ms be2398.ccr22.lon01.atlas.cogentco.com [130.117.51.210]
    13 34 ms 34 ms 34 ms be2494.ccr42.lon13.atlas.cogentco.com [154.54.39.130]
    14 116 ms 116 ms 112 ms be2493.ccr22.bos01.atlas.cogentco.com [154.54.42.97]
    15 117 ms 113 ms 112 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
    16 135 ms 135 ms 137 ms 38.111.40.114
    17 126 ms 124 ms 138 ms patchserver2.crypticstudios.com [208.95.185.41]

    Trace complete.



    7 28 ms * * acc2.10GigE-7-2-0.mr.21cn-ipp.bt.net [109.159.250.224]

    This should not be there. This usually means something is not routing properly through the ISP.
  • geckoisalizardgeckoisalizard Member Posts: 80 Arc User
    edited November 2014
    EDIT: EDT Canada.

    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 8 ms 9 ms 22 ms 10.110.227.129
    3 15 ms 11 ms 11 ms van58-6-240-93.dynamic.rogerstelecom.net [209.148.240.93]
    4 15 ms 15 ms 15 ms 69.63.253.194
    5 10 ms 11 ms 14 ms be4066.ccr22.yyz02.atlas.cogentco.com [38.122.69.117]
    6 19 ms 19 ms 20 ms be2437.ccr22.alb02.atlas.cogentco.com [66.28.4.197]
    7 24 ms 25 ms 26 ms be2302.ccr22.bos01.atlas.cogentco.com [154.54.43.13]
    8 23 ms 23 ms 24 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
    9 26 ms 36 ms 35 ms 38.111.40.114
    10 23 ms 23 ms 25 ms patchserver2.crypticstudios.com [208.95.185.41]


    Trace complete.

    And pingpath.


    Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 Hitokiri-DT [192.168.1.100]
    1 192.168.1.1
    2 10.110.227.129
    3 van58-6-240-93.dynamic.rogerstelecom.net [209.148.240.93]
    4 69.63.253.194
    5 be4066.ccr22.yyz02.atlas.cogentco.com [38.122.69.117]
    6 be2437.ccr22.alb02.atlas.cogentco.com [66.28.4.197]
    7 be2302.ccr22.bos01.atlas.cogentco.com [154.54.43.13]
    8 te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
    9 38.111.40.114
    10 patchserver2.crypticstudios.com [208.95.185.41]

    Computing statistics for 250 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Hitokiri-DT [192.168.1.100]
    0/ 100 = 0% |
    1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
    0/ 100 = 0% |
    2 --- 100/ 100 =100% 100/ 100 =100% 10.110.227.129
    0/ 100 = 0% |
    3 --- 100/ 100 =100% 100/ 100 =100% van58-6-240-93.dynamic.rogerstelecom.net [209.148.240.93]
    0/ 100 = 0% |
    4 --- 100/ 100 =100% 100/ 100 =100% 69.63.253.194
    0/ 100 = 0% |
    5 12ms 0/ 100 = 0% 0/ 100 = 0% be4066.ccr22.yyz02.atlas.cogentco.com [38.122.69.117]
    0/ 100 = 0% |
    6 20ms 0/ 100 = 0% 0/ 100 = 0% be2437.ccr22.alb02.atlas.cogentco.com [66.28.4.197]
    0/ 100 = 0% |
    7 25ms 0/ 100 = 0% 0/ 100 = 0% be2302.ccr22.bos01.atlas.cogentco.com [154.54.43.13]
    0/ 100 = 0% |
    8 54ms 0/ 100 = 0% 0/ 100 = 0% te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
    0/ 100 = 0% |
    9 30ms 0/ 100 = 0% 0/ 100 = 0% 38.111.40.114
    0/ 100 = 0% |
    10 23ms 0/ 100 = 0% 0/ 100 = 0% patchserver2.crypticstudios.com [208.95.185.41]

    Trace complete.
  • scipunk1973scipunk1973 Member Posts: 6 Arc User
    edited November 2014
    My traceroute:

    Microsoft Windows [Version 6.3.9600]
    (c) 2013 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 <1 ms <1 ms <1 ms 192.168.1.1
    2 * * * Request timed out.
    3 17 ms 14 ms 14 ms te-0-1-0-2-sur01.springfield.ma.boston.comcast.n
    et [68.87.158.185]
    4 17 ms 19 ms 17 ms be-49-ar01.needham.ma.boston.comcast.net [68.85.
    69.13]
    5 24 ms 24 ms 22 ms he-2-5-0-0-cr01.newyork.ny.ibone.comcast.net [68
    .86.94.201]
    6 23 ms 24 ms 22 ms te-0-1-0-2-pe04.ashburn.va.ibone.comcast.net [68
    .86.84.242]
    7 24 ms 23 ms 22 ms be7922.ccr21.jfk10.atlas.cogentco.com [154.54.13
    .161]
    8 22 ms 21 ms 23 ms be2057.ccr22.jfk02.atlas.cogentco.com [154.54.80
    .177]
    9 29 ms 28 ms 29 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
    .42]
    10 130 ms 204 ms 211 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
    4]
    11 47 ms 34 ms 52 ms 38.111.40.114
    12 34 ms 32 ms 32 ms patchserver2.crypticstudios.com [208.95.185.41]


    Trace complete.

    C:\Windows\system32>
  • zztopperszztoppers Member Posts: 0 Arc User
    edited November 2014
    Mine says connection with the server timed out. But it does not even connect with the server. It never get to the point where I cna even select a character.

    Very Frustrating. I reinstalled the game as well. Still nothing!
  • tetryontetryon Member Posts: 1 Arc User
    edited November 2014
    Hello,

    same problem here, very laggy. Im from Bucharest and made those 2 tests:

    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 [192.168.1.1]
    2 1 ms 1 ms <1 ms 10.0.x.x [10.0.x.x]
    3 2 ms 1 ms 2 ms 10.30.x.x [10.30.x.x]
    4 4 ms 2 ms 2 ms cr01.bucuresti.rdsnet.ro [213.154.128.59]
    5 34 ms 33 ms 35 ms xr01.frankfurt.rdsnet.ro [213.154.125.41]
    6 33 ms 33 ms 33 ms ge-3-0.ir1.frankfurt-he.de.xo.net [80.81.192.182
    ]
    7 52 ms 90 ms 51 ms 207.88.15.77.ptr.us.xo.net [207.88.15.77]
    8 129 ms 132 ms 131 ms vb1042.rar3.nyc-ny.us.xo.net [207.88.13.202]
    9 135 ms 135 ms 132 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]

    10 136 ms 136 ms 134 ms ae1d0.mcr2.cambridge-ma.us.xo.net [216.156.1.14]

    11 123 ms 123 ms 121 ms 209.117.103.10
    12 125 ms 124 ms 123 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
    04]
    13 138 ms 126 ms 125 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
    61.78]
    14 * * * Request timed out.
    15 120 ms 121 ms 121 ms patchserver2.crypticstudios.com [208.95.185.41]


    Trace complete.


    and the second one:

    contacting nettest server..
    Local IP: 188.27.122.11
    Ping: 143.0 msec
    Port: 80: 284 KB/sec 9 KB/sec 299 KB/sec 500
    Port: 80: 252 KB/sec 8 KB/sec 264 KB/sec 500
    Port: 443: 379 KB/sec 11 KB/sec 398 KB/sec 500
    Port: 443: 294 KB/sec 9 KB/sec 308 KB/sec 500
    Port: 7255: 501 KB/sec 14 KB/sec 526 KB/sec 500
    Port: 7255: 491 KB/sec 15 KB/sec 517 KB/sec 500
    Port: 7003: 428 KB/sec 10 KB/sec 449 KB/sec 500
    Port: 7003: 325 KB/sec 8 KB/sec 341 KB/sec 500
    Port: 7202: 460 KB/sec 14 KB/sec 483 KB/sec 500
    Port: 7202: 382 KB/sec 10 KB/sec 401 KB/sec 500
    Port: 7499: 448 KB/sec 14 KB/sec 471 KB/sec 500
    Port: 7499: 311 KB/sec 9 KB/sec 326 KB/sec 500
    Port: 80: 408 KB/sec 13 KB/sec 428 KB/sec 500
    Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
    hit return to exit

    From what I understand ( 14 * * * Request timed out.) the problem is with your ISP Cryptic, the ethernet seems to be really bad in the US. The game started to be so laggy since DR came up.

    I do have a FiberLink Gb connection, a very good one, tested in other games with no problems.
    Pls fix these problems, sometimes the game is unplayable for me.

    Thank you.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited November 2014
    tetryon wrote: »
    ...

    From what I understand ( 14 * * * Request timed out.) the problem is with your ISP Cryptic, the ethernet seems to be really bad in the US. The game started to be so laggy since DR came up.

    I do have a FiberLink Gb connection, a very good one, tested in other games with no problems.
    Pls fix these problems, sometimes the game is unplayable for me.

    Thank you.

    Hop #14 may be a problem, but the sudden increase in network latency between #7 & #8 also looks suspicious... The 'Net Test' results do show a connection quality issue of some kind, but other then #14 not responding (which could be caused by its network configuration), the latency values aren't bad.

    Whats really needs to be seen is the 'Path Ping' results, to look for issues that won't be noticed by a 'Trace Route' test...
Sign In or Register to comment.