Yea whats the point of doing these tests when you never got an answer for the submitted results, much less any fix?
Why not putting your results on the forum, instead of a new rage thread?
EDIT: Don't forget to put a bit more info, like what specs your rig is, temperature, networking, etc etc. Don't forget to add the list of running programs as well; some people tend to let couple of torrents running while playing STO.
im getting constant server not responding popups over the last 4 days and i dont know why then i saw this thread and followed the instructions and this is what i got enjoy.
p.s. i started playing STO last May and havnt had this much problems aside from pve
p.s.s. i live in kennewick,washington but you didnt hear that from me
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dslrouter.netgear.com [192.168.254.254]
2 269 ms 246 ms 441 ms 50.35.192.1
3 279 ms 264 ms 263 ms 50.34.0.25
4 289 ms 276 ms 292 ms ae0---0.car01.sttl.wa.frontiernet.net [74.42.149
.105]
5 224 ms 233 ms 226 ms xe--9-0-0---0.cor01.sttl.wa.frontiernet.net [74.
40.3.189]
6 295 ms 275 ms 248 ms ae0---0.cbr01.sttl.wa.frontiernet.net [74.40.5.1
22]
7 267 ms 258 ms 382 ms 206.111.7.149.ptr.us.xo.net [206.111.7.149]
8 335 ms 363 ms * vb2000d1.rar3.seattle-wa.us.xo.net [207.88.13.14
2]
9 328 ms 307 ms 314 ms te-4-0-0.rar3.denver-co.us.xo.net [207.88.12.82]
10 375 ms 319 ms 296 ms te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21
]
11 368 ms 296 ms 306 ms ae0d0.mcr2.cambridge-ma.us.xo.net [216.156.0.30]
12 329 ms 294 ms 308 ms 209.117.103.10
13 353 ms 511 ms 482 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
14 343 ms 374 ms 367 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 307 ms 337 ms 362 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Users\Administrator>
ill post the nettest when its done....again, but all the numbers are 1-20kb/500
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 36 ms 36 ms 35 ms fl-71-3-216-1.dhcp.embarqhsd.net [71.3.216.1]
3 36 ms 36 ms 36 ms fl-184-7-223-26.sta.centurylinkservices.net [184
.7.223.26]
4 46 ms 46 ms 48 ms bb-ftmyflxa-jx9-02-ae0.core.centurytel.net [208.
110.248.86]
5 36 ms 38 ms 37 ms bb-ftmyflxa-jx9-01-ae0.core.centurytel.net [208.
110.248.85]
6 42 ms 40 ms 41 ms bb-wnpkflxe-jx9-01-xe-11-1-0.0.core.centurytel.n
et [208.110.248.185]
7 60 ms 58 ms 83 ms bb-rcmtncxa-jx9-02-xe-1-2-0.core.centurytel.net
[208.110.248.157]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 75 ms 78 ms 75 ms bst-edge-05.inet.qwest.net [67.14.30.126]
12 82 ms 83 ms 79 ms 65.120.117.250
13 78 ms 79 ms 80 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
14 207 ms 216 ms 215 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 210 ms 210 ms 210 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Windows\system32>
Better results than as of recent, but still horrid from PWE/Cryptic. :mad:
im getting constant server not responding popups over the last 4 days and i dont know why then i saw this thread and followed the instructions and this is what i got enjoy.
p.s. i started playing STO last ...
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dslrouter.netgear.com [192.168.254.254]
2 269 ms 246 ms 441 ms 50.35.192.1
3 279 ms 264 ms 263 ms 50.34.0.25
...
Over a quarter of a second lag on the first hop? When the recommended upper limit for latency is 180ms ??? You normally would only expect this kind of latency with a satellite link...
Try rebooting both your router and gateway/modem and see if that improves the condition. If it doesn't you may have to contact your ISP Tech Support and have someone take a look at the gateway/modem...
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
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 * 392 ms 369 ms pa-67-235-80-1.dhcp.embarqhsd.net [67.235.80.1]
3 293 ms 300 ms 342 ms crls-agw1.inet.qwest.net [75.160.220.1]
4 430 ms 517 ms 410 ms bst-edge-05.inet.qwest.net [67.14.30.126]
5 297 ms 243 ms 227 ms 65.120.117.250
6 305 ms 270 ms 379 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
7 499 ms 536 ms 525 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
8 382 ms 475 ms 432 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Oh this is a joy, let's try that again
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
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 311 ms 247 ms 480 ms pa-67-235-80-1.dhcp.embarqhsd.net [67.235.80.1]
3 303 ms 167 ms 228 ms crls-agw1.inet.qwest.net [75.160.220.1]
4 540 ms * 365 ms bst-edge-05.inet.qwest.net [67.14.30.126]
5 416 ms 445 ms 593 ms 65.120.117.250
6 449 ms * 373 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
7 420 ms 474 ms * perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
8 428 ms 356 ms 393 ms patchserver2.crypticstudios.com [208.95.185.41]
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 311 ms 247 ms 480 ms pa-67-235-80-1.dhcp.embarqhsd.net [67.235.80.1]
...
I have a feeling this is a BAAAAAD thing.
Over 3 tenths of a second delay on the first hop?!?! When the recommended upper limit for network latency is 180ms ?!?!
Try rebooting both your router and your modem/gateway. If this doesn't correct the problem, then you will need to contact your ISP Tech Support and have them send someone out to take a look at the modem/gateway unit...
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 7 ms 9 ms 27 ms pa-67-235-80-1.dhcp.embarqhsd.net [67.235.80.1]
3 63 ms 43 ms 35 ms crls-agw1.inet.qwest.net [75.160.220.1]
4 412 ms 346 ms 243 ms bst-edge-05.inet.qwest.net [67.14.30.126]
5 313 ms 354 ms 119 ms 65.120.117.250
6 38 ms 37 ms 37 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
7 96 ms 117 ms 149 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
8 450 ms 96 ms 96 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Yeah, I was having a totally horrible day yesterday. Today looks better. Maybe my router/Modem combo doesn't like snow?
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 9 ms 6 ms 10 ms pa-67-235-80-1.dhcp.embarqhsd.net [67.235.80.1]
3 7 ms 6 ms 9 ms crls-agw1.inet.qwest.net [75.160.220.1]
4 296 ms 222 ms 205 ms bst-edge-05.inet.qwest.net [67.14.30.126]
5 61 ms 36 ms 59 ms 65.120.117.250
6 167 ms 217 ms 94 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
7 166 ms 107 ms 106 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
8 140 ms 118 ms 150 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
I'm not getting much love from bst-edge-05.inet.qwest.net though, and the pings are swinging around a bit wild. Anything I can do about that?
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 36 ms 38 ms 35 ms fl-71-3-216-1.dhcp.embarqhsd.net [71.3.216.1]
3 34 ms 34 ms 56 ms fl-184-7-223-26.sta.centurylinkservices.net [184
.7.223.26]
4 52 ms 36 ms 36 ms bb-ftmyflxa-jx9-02-ae0.core.centurytel.net [208.
110.248.86]
5 82 ms 40 ms 37 ms bb-ftmyflxa-jx9-01-ae0.core.centurytel.net [208.
110.248.85]
6 42 ms 40 ms 61 ms bb-wnpkflxe-jx9-01-xe-11-1-0.0.core.centurytel.n
et [208.110.248.185]
7 58 ms 57 ms 64 ms bb-rcmtncxa-jx9-02-xe-1-2-0.core.centurytel.net
[208.110.248.157]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 76 ms 76 ms 75 ms bst-edge-05.inet.qwest.net [67.14.30.126]
12 78 ms 78 ms 78 ms 65.120.117.250
13 77 ms 77 ms 79 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
14 135 ms 130 ms 139 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 129 ms 132 ms 130 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Windows\system32>
Granted I only have a 6m service so I don't expect super speedy connections, but this is totally garbage compared to another MMORPG I play from time to time.
My in game ping rate is pretty much 200ms average, with spikes in the 700's-1000's making for some horrendous lag.
The other MMORPG from my understanding is located up in Boston, while PWE's is in California, and both I connect from the south in Florida.
So while the distance may be further to get to California, the connection rate is 2-3X worse than the Boston based game server's.
Garbage connection each and every time to PWE. :mad:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 21 ms 2 ms 1 ms 192.168.1.1
2 * 15 ms 8 ms 10.235.96.1
3 13 ms 42 ms 13 ms 173-219-247-146-link.sta.suddenlink.net [173.219
.247.146]
4 69 ms 74 ms 66 ms 173-219-236-216-link.sta.suddenlink.net [173.219
.236.216]
5 70 ms 70 ms 77 ms 173-219-236-216-link.sta.suddenlink.net [173.219
.236.216]
6 63 ms 66 ms 73 ms xe-0-0-0-13.r01.dllstx04.us.bb.gin.ntt.net [129.
250.197.125]
7 72 ms 66 ms 64 ms ae-9.r07.dllstx09.us.bb.gin.ntt.net [129.250.2.2
08]
8 69 ms 65 ms 69 ms be3002.ccr21.dfw03.atlas.cogentco.com [154.54.13
.89]
9 103 ms 129 ms 106 ms be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.
45]
10 82 ms 80 ms 78 ms be2012.ccr21.mci01.atlas.cogentco.com [154.54.2.
113]
11 71 ms 64 ms 66 ms be2156.ccr21.ord01.atlas.cogentco.com [154.54.6.
86]
12 90 ms 85 ms 98 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43
.194]
13 84 ms 90 ms 85 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
14 86 ms 84 ms 90 ms 38.111.40.114
15 88 ms 83 ms 87 ms patchserver2.crypticstudios.com [208.95.185.41]
I have been playing for over two years with no problems. Maybe the odd lag that lasted a few seconds but nothing like this.
After the update on February 20, 2014 I was unable to log-in at all. Something about a timeout2 error. I waited a full day and restarted my computer. Now I can log in (although it takes 10 times as long) but once I'm in the game it is lagging and rubberbanding from hell. I have included the requested test results below but like I said I was fine before yesterday.
Tracert:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms GATEWAY [192.168.2.1]
2 17 ms 12 ms 11 ms bas1-woodbridge48_lo0_SYMP.net.bell.ca [64.230.200.180]
3 13 ms 11 ms 11 ms dis2-malton22_4-2-0_100.net.bell.ca [64.230.58.10]
4 26 ms 27 ms 27 ms bx6-chicago23_POS0-3-0-0.net.bell.ca [64.230.186.202]
5 25 ms 25 ms 25 ms cogent_bx6-chicago23 [184.150.181.63]
6 28 ms 23 ms 23 ms te0-7-0-12.mpd22.ord01.atlas.cogentco.com [154.54.40.161]
7 39 ms 39 ms 38 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43.186]
8 40 ms 39 ms 39 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
9 48 ms 50 ms 52 ms 38.111.40.114
10 51 ms 50 ms 48 ms 208.95.185.41
I have been playing for over two years with no problems. Maybe the odd lag that lasted a few seconds but nothing like this.
After the update on February 20, 2014 I was unable to log-in at all. Something about a timeout2 error. I waited a full day and restarted my computer. Now I can log in (although it takes 10 times as long) but once I'm in the game it is lagging and rubberbanding from hell. I have included the requested test results below but like I said I was fine before yesterday.
...
Both your 'Trace Route' and 'Net Test' diagnostics are showing excellent results. So either the problem is intermittent in nature, and you missed it when doing the diagnostics, or the problem isn't network related...
You could try substituting the 'pathping' command for the 'tracert' command (both use the same syntax) to see if you are suffering from silently dropped packets, but this would normally show up in the 'Net Test' results, so this doesn't appear to be the case...
You could also try using the us-game proxy option in the launcher option menu, as sometimes this will improve the connection quality, (if it is a connection issue...) and it doesn't hurt to try...
I took your advice and used the US-proxy option but that didn't solve the problem either. To be safe I even tried the EU proxy but again... no dice.
It's not a network issue as the test have shown... I've run them another three times and the values are always in the same range. I've disabled my firewall and antivirus just to be safe but no luck either. I'm at a loss. I've done nothing different (no new software installs or updates that I know of) since I was last able to play.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms BearNet [192.168.1.1]
2 9 ms 6 ms 5 ms 10.84.160.1
3 20 ms 7 ms 22 ms dtr03mtpkca-tge-0-1-0-4.mtpk.ca.charter.com [96.34.96.114]
4 14 ms 23 ms 15 ms crr01mtpkca-tge-0-4-0-2.mtpk.ca.charter.com [96.34.98.92]
5 9 ms 15 ms 7 ms bbr01mtpkca-bue-2.mtpk.ca.charter.com [96.34.2.24]
6 10 ms 11 ms 11 ms be4016.ccr23.lax05.atlas.cogentco.com [38.104.84.101]
7 11 ms 11 ms 11 ms be2181.mpd21.lax01.atlas.cogentco.com [154.54.41.113]
8 69 ms 70 ms 77 ms be2067.mpd21.iah01.atlas.cogentco.com [154.54.7.161]
9 76 ms 71 ms 71 ms be2173.ccr22.atl01.atlas.cogentco.com [154.54.29.117]
10 77 ms 76 ms 76 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31.110]
11 80 ms 81 ms 81 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31.118]
12 88 ms * 89 ms be2097.ccr22.bos01.atlas.cogentco.com [154.54.30.118]
13 88 ms 257 ms 251 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
14 87 ms 90 ms * 38.111.40.114
15 86 ms * 88 ms patchserver2.crypticstudios.com [208.95.185.41]
Excessive rubberbanding, losing control of ship.. it just turns like its in slipstream and cannot fire weapons or use abilities. other ships can be seen moving normally. similar situation on the ground.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 5 ms 1 ms 1 ms 192.168.1.1
2 100 ms 35 ms 27 ms cpe-70-94-8-1.kc.res.rr.com [70.94.8.1]
3 11 ms 14 ms 14 ms 65.28.16.194
4 17 ms 15 ms 13 ms tge0-8-0-2.ksczmogn01r.kc.rr.com [98.156.42.136]
5 46 ms 25 ms 27 ms ae30.dllatxl3-cr01.kc.rr.com [98.156.42.0]
6 28 ms 49 ms 33 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
7 29 ms 43 ms 28 ms ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
8 33 ms 33 ms 29 ms te0-4-0-17.ccr21.dfw03.atlas.cogentco.com [154.5
4.11.49]
9 46 ms 27 ms 27 ms be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.
53]
10 38 ms 36 ms 39 ms be2141.mpd22.mci01.atlas.cogentco.com [154.54.5.
157]
11 75 ms 107 ms 55 ms be2158.mpd21.ord01.atlas.cogentco.com [154.54.7.
130]
12 77 ms 76 ms 78 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43
.186]
13 78 ms 74 ms 78 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
14 82 ms 71 ms 70 ms 38.111.40.114
15 100 ms 72 ms 90 ms patchserver2.crypticstudios.com [208.95.185.41]
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 5 ms 1 ms 1 ms 192.168.1.1
2 100 ms 35 ms 27 ms cpe-70-94-8-1.kc.res.rr.com [70.94.8.1]
3 11 ms 14 ms 14 ms 65.28.16.194
4 17 ms 15 ms 13 ms tge0-8-0-2.ksczmogn01r.kc.rr.com [98.156.42.136]
5 46 ms 25 ms 27 ms ae30.dllatxl3-cr01.kc.rr.com [98.156.42.0]
6 28 ms 49 ms 33 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
7 29 ms 43 ms 28 ms ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
8 33 ms 33 ms 29 ms te0-4-0-17.ccr21.dfw03.atlas.cogentco.com [154.5
4.11.49]
9 46 ms 27 ms 27 ms be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.
53]
10 38 ms 36 ms 39 ms be2141.mpd22.mci01.atlas.cogentco.com [154.54.5.
157]
11 75 ms 107 ms 55 ms be2158.mpd21.ord01.atlas.cogentco.com [154.54.7.
130]
12 77 ms 76 ms 78 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43
.186]
13 78 ms 74 ms 78 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
14 82 ms 71 ms 70 ms 38.111.40.114
15 100 ms 72 ms 90 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Hop #2 is the only unusual value here, (should be less then 20ms) so a reboot of both your router and your gateway/modem may be in order here...
Everything else is in more or less expected value range, though that doesn't mean its completely problem free. A 'Net Test' results would have been nice to see the quality of your connection throughput.
If the equipment reboot doesn't correct the problem, you should post the 'Net Test' results, and try substituting the 'pathping' command for the 'tracert' command (both use the same syntax) and post those results, as this will show if you are suffering from dropped packets, and where its occurring...
For many, but not necessarily all, this current bout of poor latency, for myself in particular seems to have a culprit by the name of atlas.cogento.com
A "back country" server hub located in Atlanta,GA USA. After a cursory search on the web I've found that other on-line gamers have been suffering from lag also; such as WoW, WoT, PS3, Diablo & so on.
It has been said by some across other forums that Cogent, basically has over subscribed themselves to TOO many ISP's & does'nt have reliable enough server nodes to handle so much traffic, especially for on-line gamers like us.
Here's a bit of a solution that has worked for me, not too dramatically but it has helped
A word of WARNING here for those whom are uninitiated or otherwise not comfortable with editing your system registry, find another avenue to alleviate your problem because one wrong keystroke while inside the system registry can really mess up your OS.
^Thanks for the info, but I couldn't find my ISP in the registry despite following that path, so I guess I'll have to rely on the original post.
I myself have been having an intense amount of lag for the past month now, to the point of rubberbanding into explosions, heavy torpedoes, and even V'ger blasts. I use Comcast in the 60616 zip of Chicago.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 3 ms 3 ms 3 ms 192.168.1.1
2 1317 ms 169 ms 38 ms 50.141.145.1
3 1233 ms 20 ms 678 ms te-0-3-0-11-sur04.area4.il.chicago.comcast.net [
68.85.131.21]
4 104 ms 95 ms 138 ms te-2-8-0-9-ar01.elmhurst.il.chicago.comcast.net
[68.87.232.253]
5 489 ms 48 ms 99 ms he-2-6-0-0-cr01.chicago.il.ibone.comcast.net [68
.86.94.153]
6 851 ms 25 ms 23 ms he-1-4-0-0-cr01.350ecermak.il.ibone.comcast.net
[68.86.88.34]
7 183 ms 58 ms 42 ms pos-1-4-0-0-pe01.350ecermak.il.ibone.comcast.net
[68.86.86.162]
8 577 ms 36 ms 77 ms 23.30.206.134
9 239 ms 47 ms 81 ms be2006.mpd21.ord01.atlas.cogentco.com [154.54.5.
17]
10 133 ms 59 ms 119 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43
.186]
11 201 ms 210 ms 214 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
12 92 ms 581 ms 359 ms 38.111.40.114
13 48 ms 92 ms 112 ms patchserver2.crypticstudios.com [208.95.185.41]
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 3 ms 3 ms 3 ms 192.168.1.1
2 1317 ms 169 ms 38 ms 50.141.145.1
...
A 1.3 SECOND DELAY ON HOP #2, when the expected value should be less then 20ms !?!?
Reboot/Reset both your router, and the Comcast cable modem unit. If that does not improve the performance, then you will need to contact Comcast Tech Support, and have them send someone out to take a look at that unit...
These are the tracert and nettest results after rebooting my modem and router. My ISP is Internet Frontier, and they use AT&T's DSL lines. I'm connecting from Concord, CA.
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 172.16.0.1
2 1040 ms 928 ms 560 ms 76-191-130-33.dsl.dynamic.redshift.net [76.191.130.33]
3 986 ms 929 ms 885 ms 145.at-7-2-0.gw3.200p-sf.sonic.net [70.36.211.125]
4 916 ms 993 ms 1114 ms 0.ae2.gw.200p-sf.sonic.net [70.36.211.53]
5 1007 ms 948 ms 1031 ms as0.gw2.200p-sf.sonic.net [208.106.96.250]
6 784 ms 1102 ms 1054 ms 0.ge-7-2-0.gw.pao1.sonic.net [69.12.211.117]
7 1039 ms 821 ms 809 ms te0-0-0-15.ccr21.sjc04.atlas.cogentco.com [38.104.141.81]
8 955 ms 1146 ms 911 ms be2015.ccr21.sfo01.atlas.cogentco.com [154.54.7.173]
9 893 ms 1139 ms 934 ms be2132.ccr21.mci01.atlas.cogentco.com [154.54.30.54]
10 1148 ms 925 ms 1179 ms be2157.ccr22.ord01.atlas.cogentco.com [154.54.6.118]
11 601 ms 687 ms 890 ms be2139.ccr21.bos01.atlas.cogentco.com [154.54.43.178]
12 745 ms 699 ms 703 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
13 959 ms 735 ms 698 ms 38.111.40.114
14 952 ms 1047 ms 1012 ms patchserver2.crypticstudios.com [208.95.185.41]
I'll call my ISP in the morning. I look forward to learning what you're able to find out on your end. I understand now why I've been lagging so horribly today. These numbers are absolute rubbish.
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 42 ms 18 ms 20 ms 10.139.176.1
3 60 ms 61 ms 89 ms chcgildtgr00.bb.telus.com [154.11.11.30]
4 164 ms 70 ms 70 ms 173.182.200.2
5 70 ms 62 ms 70 ms be2003.ccr22.ord01.atlas.cogentco.com [154.54.29
.21]
6 86 ms 86 ms 86 ms be2139.ccr21.bos01.atlas.cogentco.com [154.54.43
.178]
7 87 ms 171 ms 87 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
8 579 ms 102 ms 574 ms 38.111.40.114
9 86 ms 85 ms 85 ms patchserver2.crypticstudios.com [208.95.185.41]
I see that the numbers on my end aren't great, but the numbers coming up to Cryptic are downright atrocious.
Criticism, while never agreeable, is necessary. It is like pain in the body. It brings attention to an unhealthy state of things---Winston Churchill
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 172.16.0.1
2 1040 ms 928 ms 560 ms 76-191-130-33.dsl.dynamic.redshift.net [76.191.130.33]
...
C:\WINDOWS\system32>
.
Expected values for the 2nd hop should be around 20ms. Yours is over a second. If rebooting/resetting your cable modem/gateway doesn't correct the problem, then you should have your ISP send someone out to take a look at the unit...
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms **********
2 31 ms 19 ms 54 ms 10.139.176.1
3 61 ms 61 ms 62 ms chcgildtgr00.bb.telus.com [154.11.11.30]
4 70 ms 71 ms 70 ms 173.182.200.2
5 62 ms 70 ms 63 ms be2004.mpd22.ord01.atlas.cogentco.com [154.54.5.
9]
6 86 ms 86 ms 86 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43
.186] 7 280 ms 215 ms 215 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
8 90 ms 88 ms 89 ms 38.111.40.114
9 86 ms 105 ms 86 ms patchserver2.crypticstudios.com [208.95.185.41]
Again, not great numbers on my end, but it looks like the Cogentco Boston hub's definitely acting up again... :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
A 1.3 SECOND DELAY ON HOP #2, when the expected value should be less then 20ms !?!?
Reboot/Reset both your router, and the Comcast cable modem unit. If that does not improve the performance, then you will need to contact Comcast Tech Support, and have them send someone out to take a look at that unit...
I've tried rebooting/resetting the router and modem, to no avail. However, I didn't start getting these problems until a couple weeks ago, and other MMOs like Marvel Heroes work fine for me.
I've tried rebooting/resetting the router and modem, to no avail. However, I didn't start getting these problems until a couple weeks ago, and other MMOs like Marvel Heroes work fine for me.
The recommended upper limit for network latency for STO is 180ms... With the abnormal latency values that you posted, its not surprising at all you're having connection issues, and does indicate some kind of problem with the DSL hardware...
Okay, just got booted from the Mirror Event, ran a tracer, first time I've ever seen asterisks :eek:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms 2 ms
2 20 ms 20 ms 24 ms 10.139.176.1
3 61 ms 61 ms 61 ms chcgildtgr00.bb.telus.com [154.11.11.30]
4 70 ms 71 ms 70 ms 173.182.200.2
5 70 ms 61 ms 70 ms be2005.ccr21.ord01.atlas.cogentco.com [66.28.4.7
3]
6 86 ms 87 ms 86 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43
.186]
7 91 ms 86 ms 86 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
8 * * 117 ms 38.111.40.114
9 112 ms * * patchserver2.crypticstudios.com [208.95.185.41]
10 111 ms 111 ms * patchserver2.crypticstudios.com [208.95.185.41]
11 111 ms 111 ms 111 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Criticism, while never agreeable, is necessary. It is like pain in the body. It brings attention to an unhealthy state of things---Winston Churchill
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [********]
2 14 ms 19 ms 8 ms L100.NWRKNJ-VFTTP-113.verizon-gni.net [98.109.36
.1]
3 17 ms 18 ms 18 ms G0-9-2-3.NWRKNJ-LCR-22.verizon-gni.net [130.81.1
33.34]
4 13 ms 18 ms 18 ms 130.81.162.84
5 * * * Request timed out.
6 * * * Request timed out.
7 25 ms 28 ms 16 ms 0.ae2.XL4.BOS4.ALTER.NET [140.222.226.19]
8 18 ms 16 ms 17 ms 0.xe-11-3-0.GW15.BOS4.ALTER.NET [152.63.21.166]
9 25 ms 27 ms 27 ms internap-gw.customer.alter.net [152.179.134.214]
10 19 ms 17 ms 17 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
11 48 ms 47 ms 52 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
12 53 ms 46 ms 47 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Users\XRaiderV1>
I've got exceptionally low latency on all hops bar hops 5 and 6 which time out, and I'm seeing server not responding errors at times here. I'm on the east coast of the us.
Murphy's laws:
1- Murphy’s Law tells us that anything that can go wrong will go wrong.
2- And anything that does go wrong will get progressively worse.
3- And if you survive the first two laws it’s time to panic.
the servers at hops 5 and 6 appear to have had transporter accidents and are buried in tribbles. more than one person on the east coast has had problems as a result.
Murphy's laws:
1- Murphy’s Law tells us that anything that can go wrong will go wrong.
2- And anything that does go wrong will get progressively worse.
3- And if you survive the first two laws it’s time to panic.
Comments
EDIT: Don't forget to put a bit more info, like what specs your rig is, temperature, networking, etc etc. Don't forget to add the list of running programs as well; some people tend to let couple of torrents running while playing STO.
p.s. i started playing STO last May and havnt had this much problems aside from pve
p.s.s. i live in kennewick,washington but you didnt hear that from me
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>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 dslrouter.netgear.com [192.168.254.254]
2 269 ms 246 ms 441 ms 50.35.192.1
3 279 ms 264 ms 263 ms 50.34.0.25
4 289 ms 276 ms 292 ms ae0---0.car01.sttl.wa.frontiernet.net [74.42.149
.105]
5 224 ms 233 ms 226 ms xe--9-0-0---0.cor01.sttl.wa.frontiernet.net [74.
40.3.189]
6 295 ms 275 ms 248 ms ae0---0.cbr01.sttl.wa.frontiernet.net [74.40.5.1
22]
7 267 ms 258 ms 382 ms 206.111.7.149.ptr.us.xo.net [206.111.7.149]
8 335 ms 363 ms * vb2000d1.rar3.seattle-wa.us.xo.net [207.88.13.14
2]
9 328 ms 307 ms 314 ms te-4-0-0.rar3.denver-co.us.xo.net [207.88.12.82]
10 375 ms 319 ms 296 ms te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21
]
11 368 ms 296 ms 306 ms ae0d0.mcr2.cambridge-ma.us.xo.net [216.156.0.30]
12 329 ms 294 ms 308 ms 209.117.103.10
13 353 ms 511 ms 482 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
14 343 ms 374 ms 367 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 307 ms 337 ms 362 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Users\Administrator>
ill post the nettest when its done....again, but all the numbers are 1-20kb/500
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 36 ms 36 ms 35 ms fl-71-3-216-1.dhcp.embarqhsd.net [71.3.216.1]
3 36 ms 36 ms 36 ms fl-184-7-223-26.sta.centurylinkservices.net [184
.7.223.26]
4 46 ms 46 ms 48 ms bb-ftmyflxa-jx9-02-ae0.core.centurytel.net [208.
110.248.86]
5 36 ms 38 ms 37 ms bb-ftmyflxa-jx9-01-ae0.core.centurytel.net [208.
110.248.85]
6 42 ms 40 ms 41 ms bb-wnpkflxe-jx9-01-xe-11-1-0.0.core.centurytel.n
et [208.110.248.185]
7 60 ms 58 ms 83 ms bb-rcmtncxa-jx9-02-xe-1-2-0.core.centurytel.net
[208.110.248.157]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 75 ms 78 ms 75 ms bst-edge-05.inet.qwest.net [67.14.30.126]
12 82 ms 83 ms 79 ms 65.120.117.250
13 78 ms 79 ms 80 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
14 207 ms 216 ms 215 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 210 ms 210 ms 210 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Windows\system32>
Better results than as of recent, but still horrid from PWE/Cryptic. :mad:
Praetor of the -RTS- Romulan Tal Shiar fleet!
Over a quarter of a second lag on the first hop? When the recommended upper limit for latency is 180ms ??? You normally would only expect this kind of latency with a satellite link...
Try rebooting both your router and gateway/modem and see if that improves the condition. If it doesn't you may have to contact your ISP Tech Support and have someone take a look at the gateway/modem...
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
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 * 392 ms 369 ms pa-67-235-80-1.dhcp.embarqhsd.net [67.235.80.1]
3 293 ms 300 ms 342 ms crls-agw1.inet.qwest.net [75.160.220.1]
4 430 ms 517 ms 410 ms bst-edge-05.inet.qwest.net [67.14.30.126]
5 297 ms 243 ms 227 ms 65.120.117.250
6 305 ms 270 ms 379 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
7 499 ms 536 ms 525 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
8 382 ms 475 ms 432 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Oh this is a joy, let's try that again
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
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 311 ms 247 ms 480 ms pa-67-235-80-1.dhcp.embarqhsd.net [67.235.80.1]
3 303 ms 167 ms 228 ms crls-agw1.inet.qwest.net [75.160.220.1]
4 540 ms * 365 ms bst-edge-05.inet.qwest.net [67.14.30.126]
5 416 ms 445 ms 593 ms 65.120.117.250
6 449 ms * 373 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
7 420 ms 474 ms * perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
8 428 ms 356 ms 393 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
I have a feeling this is a BAAAAAD thing.
Over 3 tenths of a second delay on the first hop?!?! When the recommended upper limit for network latency is 180ms ?!?!
Try rebooting both your router and your modem/gateway. If this doesn't correct the problem, then you will need to contact your ISP Tech Support and have them send someone out to take a look at the modem/gateway unit...
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 7 ms 9 ms 27 ms pa-67-235-80-1.dhcp.embarqhsd.net [67.235.80.1]
3 63 ms 43 ms 35 ms crls-agw1.inet.qwest.net [75.160.220.1]
4 412 ms 346 ms 243 ms bst-edge-05.inet.qwest.net [67.14.30.126]
5 313 ms 354 ms 119 ms 65.120.117.250
6 38 ms 37 ms 37 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
7 96 ms 117 ms 149 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
8 450 ms 96 ms 96 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Yeah, I was having a totally horrible day yesterday. Today looks better. Maybe my router/Modem combo doesn't like snow?
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 9 ms 6 ms 10 ms pa-67-235-80-1.dhcp.embarqhsd.net [67.235.80.1]
3 7 ms 6 ms 9 ms crls-agw1.inet.qwest.net [75.160.220.1]
4 296 ms 222 ms 205 ms bst-edge-05.inet.qwest.net [67.14.30.126]
5 61 ms 36 ms 59 ms 65.120.117.250
6 167 ms 217 ms 94 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
7 166 ms 107 ms 106 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
8 140 ms 118 ms 150 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
I'm not getting much love from bst-edge-05.inet.qwest.net though, and the pings are swinging around a bit wild. Anything I can do about that?
Local IP: 50.130.10.61
Ping: 42.3 msec
Port: 80: 645 KB/sec 39 KB/sec 693 KB/sec 500
Port: 80: 575 KB/sec 38 KB/sec 620 KB/sec 500
Port: 443: 838 KB/sec 48 KB/sec 886 KB/sec 500
Port: 443: 744 KB/sec 45 KB/sec 792 KB/sec 500
Port: 7255: 1255 KB/sec 80 KB/sec 1325 KB/sec 500
Port: 7255: 598 KB/sec 36 KB/sec 640 KB/sec 500
Port: 7003: 698 KB/sec 38 KB/sec 750 KB/sec 500
Port: 7003: 822 KB/sec 49 KB/sec 882 KB/sec 500
Port: 7202: 648 KB/sec 40 KB/sec 699 KB/sec 500
Port: 7202: 849 KB/sec 47 KB/sec 898 KB/sec 500
Port: 7499: 608 KB/sec 38 KB/sec 664 KB/sec 500
Port: 7499: 781 KB/sec 44 KB/sec 834 KB/sec 500
Port: 80: 1694 KB/sec 92 KB/sec 1790 KB/sec 500
Idle NIC bandwidth Send: 1 KB/sec Recv: 1 KB/sec
hit return to exit
Comcast
From Huntsville, AL 35805
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 36 ms 38 ms 35 ms fl-71-3-216-1.dhcp.embarqhsd.net [71.3.216.1]
3 34 ms 34 ms 56 ms fl-184-7-223-26.sta.centurylinkservices.net [184
.7.223.26]
4 52 ms 36 ms 36 ms bb-ftmyflxa-jx9-02-ae0.core.centurytel.net [208.
110.248.86]
5 82 ms 40 ms 37 ms bb-ftmyflxa-jx9-01-ae0.core.centurytel.net [208.
110.248.85]
6 42 ms 40 ms 61 ms bb-wnpkflxe-jx9-01-xe-11-1-0.0.core.centurytel.n
et [208.110.248.185]
7 58 ms 57 ms 64 ms bb-rcmtncxa-jx9-02-xe-1-2-0.core.centurytel.net
[208.110.248.157]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 76 ms 76 ms 75 ms bst-edge-05.inet.qwest.net [67.14.30.126]
12 78 ms 78 ms 78 ms 65.120.117.250
13 77 ms 77 ms 79 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
14 135 ms 130 ms 139 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 129 ms 132 ms 130 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Windows\system32>
Granted I only have a 6m service so I don't expect super speedy connections, but this is totally garbage compared to another MMORPG I play from time to time.
My in game ping rate is pretty much 200ms average, with spikes in the 700's-1000's making for some horrendous lag.
The other MMORPG from my understanding is located up in Boston, while PWE's is in California, and both I connect from the south in Florida.
So while the distance may be further to get to California, the connection rate is 2-3X worse than the Boston based game server's.
Garbage connection each and every time to PWE. :mad:
Praetor of the -RTS- Romulan Tal Shiar fleet!
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\David>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 21 ms 2 ms 1 ms 192.168.1.1
2 * 15 ms 8 ms 10.235.96.1
3 13 ms 42 ms 13 ms 173-219-247-146-link.sta.suddenlink.net [173.219
.247.146]
4 69 ms 74 ms 66 ms 173-219-236-216-link.sta.suddenlink.net [173.219
.236.216]
5 70 ms 70 ms 77 ms 173-219-236-216-link.sta.suddenlink.net [173.219
.236.216]
6 63 ms 66 ms 73 ms xe-0-0-0-13.r01.dllstx04.us.bb.gin.ntt.net [129.
250.197.125]
7 72 ms 66 ms 64 ms ae-9.r07.dllstx09.us.bb.gin.ntt.net [129.250.2.2
08]
8 69 ms 65 ms 69 ms be3002.ccr21.dfw03.atlas.cogentco.com [154.54.13
.89]
9 103 ms 129 ms 106 ms be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.
45]
10 82 ms 80 ms 78 ms be2012.ccr21.mci01.atlas.cogentco.com [154.54.2.
113]
11 71 ms 64 ms 66 ms be2156.ccr21.ord01.atlas.cogentco.com [154.54.6.
86]
12 90 ms 85 ms 98 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43
.194]
13 84 ms 90 ms 85 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
14 86 ms 84 ms 90 ms 38.111.40.114
15 88 ms 83 ms 87 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
contacting nettest server..
Local IP: 173.216.99.254
Ping: 100.1 msec
Port: 80: 153 KB/sec 21 KB/sec 701 KB/sec 500
Port: 80: 324 KB/sec 28 KB/sec 776 KB/sec 500
Port: 443: 304 KB/sec 26 KB/sec 885 KB/sec 500
Port: 443: 145 KB/sec 22 KB/sec 768 KB/sec 500
Port: 7255: 348 KB/sec 26 KB/sec 883 KB/sec 500
Port: 7255: 358 KB/sec 24 KB/sec 882 KB/sec 500
Port: 7003: 372 KB/sec 34 KB/sec 737 KB/sec 500
Port: 7003: 290 KB/sec 27 KB/sec 911 KB/sec 500
Port: 7202: 105 KB/sec 17 KB/sec 635 KB/sec 500
Port: 7202: 384 KB/sec 29 KB/sec 844 KB/sec 500
Port: 7499: 193 KB/sec 19 KB/sec 661 KB/sec 500
Port: 7499: 395 KB/sec 22 KB/sec 727 KB/sec 500
Port: 80: 148 KB/sec 19 KB/sec 702 KB/sec 500
Idle NIC bandwidth Send: 22 KB/sec Recv: 978 KB/sec
hit return to exit
Connecting from Suddenlink Cable, Batesville, Arkansas. I'm supposed to have 30Mbps down, 2Mbps up if that matters..
After the update on February 20, 2014 I was unable to log-in at all. Something about a timeout2 error. I waited a full day and restarted my computer. Now I can log in (although it takes 10 times as long) but once I'm in the game it is lagging and rubberbanding from hell. I have included the requested test results below but like I said I was fine before yesterday.
Tracert:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms GATEWAY [192.168.2.1]
2 17 ms 12 ms 11 ms bas1-woodbridge48_lo0_SYMP.net.bell.ca [64.230.200.180]
3 13 ms 11 ms 11 ms dis2-malton22_4-2-0_100.net.bell.ca [64.230.58.10]
4 26 ms 27 ms 27 ms bx6-chicago23_POS0-3-0-0.net.bell.ca [64.230.186.202]
5 25 ms 25 ms 25 ms cogent_bx6-chicago23 [184.150.181.63]
6 28 ms 23 ms 23 ms te0-7-0-12.mpd22.ord01.atlas.cogentco.com [154.54.40.161]
7 39 ms 39 ms 38 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43.186]
8 40 ms 39 ms 39 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
9 48 ms 50 ms 52 ms 38.111.40.114
10 51 ms 50 ms 48 ms 208.95.185.41
Trace complete.
Nettest:
contacting nettest server..
Local IP: 174.89.171.134
Ping: 47.7 msec
Port: 80: 839 KB/sec 32 KB/sec 886 KB/sec 500
Port: 80: 1272 KB/sec 50 KB/sec 1346 KB/sec 500
Port: 443: 997 KB/sec 36 KB/sec 1054 KB/sec 500
Port: 443: 1098 KB/sec 44 KB/sec 1170 KB/sec 500
Port: 7255: 274 KB/sec 16 KB/sec 300 KB/sec 500
Port: 7255: 1129 KB/sec 43 KB/sec 1223 KB/sec 500
Port: 7003: 958 KB/sec 37 KB/sec 1016 KB/sec 500
Port: 7003: 995 KB/sec 36 KB/sec 1054 KB/sec 500
Port: 7202: 1179 KB/sec 44 KB/sec 1248 KB/sec 500
Port: 7202: 1209 KB/sec 44 KB/sec 1284 KB/sec 500
Port: 7499: 1344 KB/sec 49 KB/sec 1427 KB/sec 500
Port: 7499: 1265 KB/sec 45 KB/sec 1334 KB/sec 500
Port: 80: 1235 KB/sec 43 KB/sec 1312 KB/sec 500
Idle NIC bandwidth Send: 1 KB/sec Recv: 1 KB/sec
ISP:
Bell Canada
Both your 'Trace Route' and 'Net Test' diagnostics are showing excellent results. So either the problem is intermittent in nature, and you missed it when doing the diagnostics, or the problem isn't network related...
You could try substituting the 'pathping' command for the 'tracert' command (both use the same syntax) to see if you are suffering from silently dropped packets, but this would normally show up in the 'Net Test' results, so this doesn't appear to be the case...
You could also try using the us-game proxy option in the launcher option menu, as sometimes this will improve the connection quality, (if it is a connection issue...) and it doesn't hurt to try...
I took your advice and used the US-proxy option but that didn't solve the problem either. To be safe I even tried the EU proxy but again... no dice.
It's not a network issue as the test have shown... I've run them another three times and the values are always in the same range. I've disabled my firewall and antivirus just to be safe but no luck either. I'm at a loss. I've done nothing different (no new software installs or updates that I know of) since I was last able to play.
This all started after the update on the 20th.
I'm open to any other ideas anybody might have.
Thanks
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Bear>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 BearNet [192.168.1.1]
2 9 ms 6 ms 5 ms 10.84.160.1
3 20 ms 7 ms 22 ms dtr03mtpkca-tge-0-1-0-4.mtpk.ca.charter.com [96.34.96.114]
4 14 ms 23 ms 15 ms crr01mtpkca-tge-0-4-0-2.mtpk.ca.charter.com [96.34.98.92]
5 9 ms 15 ms 7 ms bbr01mtpkca-bue-2.mtpk.ca.charter.com [96.34.2.24]
6 10 ms 11 ms 11 ms be4016.ccr23.lax05.atlas.cogentco.com [38.104.84.101]
7 11 ms 11 ms 11 ms be2181.mpd21.lax01.atlas.cogentco.com [154.54.41.113]
8 69 ms 70 ms 77 ms be2067.mpd21.iah01.atlas.cogentco.com [154.54.7.161]
9 76 ms 71 ms 71 ms be2173.ccr22.atl01.atlas.cogentco.com [154.54.29.117]
10 77 ms 76 ms 76 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31.110]
11 80 ms 81 ms 81 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31.118]
12 88 ms * 89 ms be2097.ccr22.bos01.atlas.cogentco.com [154.54.30.118]
13 88 ms 257 ms 251 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
14 87 ms 90 ms * 38.111.40.114
15 86 ms * 88 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
contacting nettest server..
Local IP: 24.205.18.178
Ping: 100.0 msec
Port: 80: 540 KB/sec 14 KB/sec 568 KB/sec 500
Port: 80: 630 KB/sec 21 KB/sec 663 KB/sec 500
Port: 443: 0 KB/sec 0 KB/sec 0 KB/sec 58
Port: 443: timed out
Port: 7255: 728 KB/sec 24 KB/sec 767 KB/sec 500
Port: 7255: 634 KB/sec 24 KB/sec 667 KB/sec 500
Port: 7003: 636 KB/sec 22 KB/sec 669 KB/sec 500
Port: 7003: 678 KB/sec 28 KB/sec 716 KB/sec 500
Port: 7202: 618 KB/sec 30 KB/sec 657 KB/sec 500
Port: 7202: 534 KB/sec 20 KB/sec 561 KB/sec 500
Port: 7499: 605 KB/sec 23 KB/sec 637 KB/sec 500
Port: 7499: 592 KB/sec 13 KB/sec 622 KB/sec 500
Port: 80: 428 KB/sec 14 KB/sec 450 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
charter - los angeles.
Excessive rubberbanding, losing control of ship.. it just turns like its in slipstream and cannot fire weapons or use abilities. other ships can be seen moving normally. similar situation on the ground.
C:\WINDOWS\system32>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 5 ms 1 ms 1 ms 192.168.1.1
2 100 ms 35 ms 27 ms cpe-70-94-8-1.kc.res.rr.com [70.94.8.1]
3 11 ms 14 ms 14 ms 65.28.16.194
4 17 ms 15 ms 13 ms tge0-8-0-2.ksczmogn01r.kc.rr.com [98.156.42.136]
5 46 ms 25 ms 27 ms ae30.dllatxl3-cr01.kc.rr.com [98.156.42.0]
6 28 ms 49 ms 33 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
7 29 ms 43 ms 28 ms ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
8 33 ms 33 ms 29 ms te0-4-0-17.ccr21.dfw03.atlas.cogentco.com [154.5
4.11.49]
9 46 ms 27 ms 27 ms be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.
53]
10 38 ms 36 ms 39 ms be2141.mpd22.mci01.atlas.cogentco.com [154.54.5.
157]
11 75 ms 107 ms 55 ms be2158.mpd21.ord01.atlas.cogentco.com [154.54.7.
130]
12 77 ms 76 ms 78 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43
.186]
13 78 ms 74 ms 78 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
14 82 ms 71 ms 70 ms 38.111.40.114
15 100 ms 72 ms 90 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Hop #2 is the only unusual value here, (should be less then 20ms) so a reboot of both your router and your gateway/modem may be in order here...
Everything else is in more or less expected value range, though that doesn't mean its completely problem free. A 'Net Test' results would have been nice to see the quality of your connection throughput.
If the equipment reboot doesn't correct the problem, you should post the 'Net Test' results, and try substituting the 'pathping' command for the 'tracert' command (both use the same syntax) and post those results, as this will show if you are suffering from dropped packets, and where its occurring...
A "back country" server hub located in Atlanta,GA USA. After a cursory search on the web I've found that other on-line gamers have been suffering from lag also; such as WoW, WoT, PS3, Diablo & so on.
It has been said by some across other forums that Cogent, basically has over subscribed themselves to TOO many ISP's & does'nt have reliable enough server nodes to handle so much traffic, especially for on-line gamers like us.
Here's a bit of a solution that has worked for me, not too dramatically but it has helped
http://www.pcadvisor.co.uk/how-to/internet/3427572/how-reduce-your-latency-in-windows-7/
A word of WARNING here for those whom are uninitiated or otherwise not comfortable with editing your system registry, find another avenue to alleviate your problem because one wrong keystroke while inside the system registry can really mess up your OS.
Cheers, i hope this is helpful
I myself have been having an intense amount of lag for the past month now, to the point of rubberbanding into explosions, heavy torpedoes, and even V'ger blasts. I use Comcast in the 60616 zip of Chicago.
C:\windows\system32>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 3 ms 3 ms 3 ms 192.168.1.1
2 1317 ms 169 ms 38 ms 50.141.145.1
3 1233 ms 20 ms 678 ms te-0-3-0-11-sur04.area4.il.chicago.comcast.net [
68.85.131.21]
4 104 ms 95 ms 138 ms te-2-8-0-9-ar01.elmhurst.il.chicago.comcast.net
[68.87.232.253]
5 489 ms 48 ms 99 ms he-2-6-0-0-cr01.chicago.il.ibone.comcast.net [68
.86.94.153]
6 851 ms 25 ms 23 ms he-1-4-0-0-cr01.350ecermak.il.ibone.comcast.net
[68.86.88.34]
7 183 ms 58 ms 42 ms pos-1-4-0-0-pe01.350ecermak.il.ibone.comcast.net
[68.86.86.162]
8 577 ms 36 ms 77 ms 23.30.206.134
9 239 ms 47 ms 81 ms be2006.mpd21.ord01.atlas.cogentco.com [154.54.5.
17]
10 133 ms 59 ms 119 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43
.186]
11 201 ms 210 ms 214 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
12 92 ms 581 ms 359 ms 38.111.40.114
13 48 ms 92 ms 112 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Nettest:
Local IP: 50.141.145.137
Ping: 300.0 msec
Port: 80: 66 KB/sec 3 KB/sec 71 KB/sec 500
Port: 80: 348 KB/sec 12 KB/sec 421 KB/sec 500
Port: 443: 342 KB/sec 13 KB/sec 365 KB/sec 500
Port: 7255: 38 KB/sec 8 KB/sec 230 KB/sec 500
Port: 7255: 31 KB/sec 3 KB/sec 119 KB/sec 500
Port: 7003: 124 KB/sec 4 KB/sec 131 KB/sec 500
Port: 7003: 196 KB/sec 8 KB/sec 205 KB/sec 500
Port: 7202: 254 KB/sec 10 KB/sec 267 KB/sec 500
Port: 7202: 126 KB/sec 4 KB/sec 132 KB/sec 500
Port: 7499: 158 KB/sec 8 KB/sec 186 KB/sec 500
Port: 80: 196 KB/sec 8 KB/sec 206 KB/sec 500
A 1.3 SECOND DELAY ON HOP #2, when the expected value should be less then 20ms !?!?
Reboot/Reset both your router, and the Comcast cable modem unit. If that does not improve the performance, then you will need to contact Comcast Tech Support, and have them send someone out to take a look at that unit...
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 172.16.0.1
2 1040 ms 928 ms 560 ms 76-191-130-33.dsl.dynamic.redshift.net [76.191.130.33]
3 986 ms 929 ms 885 ms 145.at-7-2-0.gw3.200p-sf.sonic.net [70.36.211.125]
4 916 ms 993 ms 1114 ms 0.ae2.gw.200p-sf.sonic.net [70.36.211.53]
5 1007 ms 948 ms 1031 ms as0.gw2.200p-sf.sonic.net [208.106.96.250]
6 784 ms 1102 ms 1054 ms 0.ge-7-2-0.gw.pao1.sonic.net [69.12.211.117]
7 1039 ms 821 ms 809 ms te0-0-0-15.ccr21.sjc04.atlas.cogentco.com [38.104.141.81]
8 955 ms 1146 ms 911 ms be2015.ccr21.sfo01.atlas.cogentco.com [154.54.7.173]
9 893 ms 1139 ms 934 ms be2132.ccr21.mci01.atlas.cogentco.com [154.54.30.54]
10 1148 ms 925 ms 1179 ms be2157.ccr22.ord01.atlas.cogentco.com [154.54.6.118]
11 601 ms 687 ms 890 ms be2139.ccr21.bos01.atlas.cogentco.com [154.54.43.178]
12 745 ms 699 ms 703 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
13 959 ms 735 ms 698 ms 38.111.40.114
14 952 ms 1047 ms 1012 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\WINDOWS\system32>
contacting nettest server..
Local IP: 76.191.130.42
Ping: 1000.2 msec
Port: 80: 48 KB/sec 3 KB/sec 53 KB/sec 500
Port: 80: 39 KB/sec 4 KB/sec 47 KB/sec 500
Port: 443: 53 KB/sec 2 KB/sec 56 KB/sec 500
Port: 443: 62 KB/sec 3 KB/sec 66 KB/sec 500
Port: 7255: 32 KB/sec 1 KB/sec 34 KB/sec 500
Port: 7255: timed out
Port: 7003: 24 KB/sec 1 KB/sec 25 KB/sec 500
Port: 7003: 35 KB/sec 1 KB/sec 38 KB/sec 500
Port: 7202: 31 KB/sec 2 KB/sec 35 KB/sec 500
Port: 7202: 35 KB/sec 2 KB/sec 37 KB/sec 500
Port: 7499: 43 KB/sec 2 KB/sec 47 KB/sec 500
Port: 7499: 23 KB/sec 1 KB/sec 26 KB/sec 500
Port: 80: 97 KB/sec 4 KB/sec 103 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
I'll call my ISP in the morning. I look forward to learning what you're able to find out on your end. I understand now why I've been lagging so horribly today. These numbers are absolute rubbish.
Too bad the lag and rubber banding are deadlier than the Mirror invaders!!!:mad:
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 42 ms 18 ms 20 ms 10.139.176.1
3 60 ms 61 ms 89 ms chcgildtgr00.bb.telus.com [154.11.11.30]
4 164 ms 70 ms 70 ms 173.182.200.2
5 70 ms 62 ms 70 ms be2003.ccr22.ord01.atlas.cogentco.com [154.54.29
.21]
6 86 ms 86 ms 86 ms be2139.ccr21.bos01.atlas.cogentco.com [154.54.43
.178]
7 87 ms 171 ms 87 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
8 579 ms 102 ms 574 ms 38.111.40.114
9 86 ms 85 ms 85 ms patchserver2.crypticstudios.com [208.95.185.41]
I see that the numbers on my end aren't great, but the numbers coming up to Cryptic are downright atrocious.
Expected values for the 2nd hop should be around 20ms. Yours is over a second. If rebooting/resetting your cable modem/gateway doesn't correct the problem, then you should have your ISP send someone out to take a look at the unit...
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms **********
2 31 ms 19 ms 54 ms 10.139.176.1
3 61 ms 61 ms 62 ms chcgildtgr00.bb.telus.com [154.11.11.30]
4 70 ms 71 ms 70 ms 173.182.200.2
5 62 ms 70 ms 63 ms be2004.mpd22.ord01.atlas.cogentco.com [154.54.5.
9]
6 86 ms 86 ms 86 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43
.186]
7 280 ms 215 ms 215 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
8 90 ms 88 ms 89 ms 38.111.40.114
9 86 ms 105 ms 86 ms patchserver2.crypticstudios.com [208.95.185.41]
Again, not great numbers on my end, but it looks like the Cogentco Boston hub's definitely acting up again... :rolleyes:
I've tried rebooting/resetting the router and modem, to no avail. However, I didn't start getting these problems until a couple weeks ago, and other MMOs like Marvel Heroes work fine for me.
The recommended upper limit for network latency for STO is 180ms... With the abnormal latency values that you posted, its not surprising at all you're having connection issues, and does indicate some kind of problem with the DSL hardware...
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms 2 ms
2 20 ms 20 ms 24 ms 10.139.176.1
3 61 ms 61 ms 61 ms chcgildtgr00.bb.telus.com [154.11.11.30]
4 70 ms 71 ms 70 ms 173.182.200.2
5 70 ms 61 ms 70 ms be2005.ccr21.ord01.atlas.cogentco.com [66.28.4.7
3]
6 86 ms 87 ms 86 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43
.186]
7 91 ms 86 ms 86 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
8 * * 117 ms 38.111.40.114
9 112 ms * * patchserver2.crypticstudios.com [208.95.185.41]
10 111 ms 111 ms * patchserver2.crypticstudios.com [208.95.185.41]
11 111 ms 111 ms 111 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Users\XRaiderV1>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 Wireless_Broadband_Router.home [********]
2 14 ms 19 ms 8 ms L100.NWRKNJ-VFTTP-113.verizon-gni.net [98.109.36
.1]
3 17 ms 18 ms 18 ms G0-9-2-3.NWRKNJ-LCR-22.verizon-gni.net [130.81.1
33.34]
4 13 ms 18 ms 18 ms 130.81.162.84
5 * * * Request timed out.
6 * * * Request timed out.
7 25 ms 28 ms 16 ms 0.ae2.XL4.BOS4.ALTER.NET [140.222.226.19]
8 18 ms 16 ms 17 ms 0.xe-11-3-0.GW15.BOS4.ALTER.NET [152.63.21.166]
9 25 ms 27 ms 27 ms internap-gw.customer.alter.net [152.179.134.214]
10 19 ms 17 ms 17 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
11 48 ms 47 ms 52 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
12 53 ms 46 ms 47 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Users\XRaiderV1>
I've got exceptionally low latency on all hops bar hops 5 and 6 which time out, and I'm seeing server not responding errors at times here. I'm on the east coast of the us.
1- Murphy’s Law tells us that anything that can go wrong will go wrong.
2- And anything that does go wrong will get progressively worse.
3- And if you survive the first two laws it’s time to panic.
1- Murphy’s Law tells us that anything that can go wrong will go wrong.
2- And anything that does go wrong will get progressively worse.
3- And if you survive the first two laws it’s time to panic.