If you have purchased a Legacy or Starter Pack, please see this thread for instructions on how to claim your items in-game. (Please see the yellow text in the linked thread for instructions on creating a Reman.) (Not seeing your pack in-game? Please see the lime-green text in the linked thread above for information.)
If you have additional questions about the Legacy or Starter pack, please read this FAQ.
Thanks SO MUCH for all your support, and we'll see you in-game!
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 15 ms 15 ms 15 ms tl12sj.wp.shawcable.net [64.59.177.98]
3 15 ms 15 ms 15 ms rc1nr-tge0-2-5-0.wp.shawcable.net [66.163.73.193
]
4 31 ms 35 ms 35 ms rc1so-ge2-0-0-1.cg.shawcable.net [66.163.77.202]
5 25 ms 27 ms 24 ms xe-9-2-0.edge4.Chicago3.Level3.net [4.53.98.49]
6 25 ms 29 ms 25 ms vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]
7 32 ms 24 ms 40 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
8 24 ms 27 ms 25 ms ae-14-51.car4.Chicago1.Level3.net [4.69.138.6]
9 27 ms 26 ms 24 ms te0-3-0-1.ccr22.ord03.atlas.cogentco.com [154.54
.13.9]
10 25 ms 25 ms 25 ms te0-3-0-5.ccr22.ord01.atlas.cogentco.com [154.54
.43.233]
11 47 ms 55 ms 47 ms te0-3-0-1.ccr22.bos01.atlas.cogentco.com [154.54
.24.57]
12 50 ms 60 ms 49 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
13 47 ms 49 ms 52 ms 38.111.40.114
14 46 ms 51 ms 57 ms 208.95.185.41
Trace complete.
C:\Windows\system32>
My ISP is Shaw Cable and I'm in Winnipeg , Manitoba , Canada
Contact your ISP as in the example above yours. Those nettest numbers are atrocious.
As also outlined in the OP of this thread, try releasing and renewing your IP.
Open a command prompt, type ipconfig /release Wait a few seconds, then at the next prompt, type ipconfig /renew. You may also have to contact your ISP to obtain a new IP address. (especially if your IP is static).
Normal for columns 1-3 should be 300-500KB/s and column 2 should be about 20 KB/s.
What gets me is that even your port 80 (standard HTTP) port is a little off. Whatever the hell it's pinging, too, as bolded above...it's taking a stupidly long time to get there...
Also, as a commonsensical security precaution, black out your local IP.
I'm having exactly the same problem. It started on Friday. Sometimes the game will be fine but then it gets into a setup where it basically stops responding to commands. I (generally) seem to still be receiving data from the server regarding my environment (i.e. other players and NPCs keep moving on my screen) and the chat system continues to work fine but any commands I send take several minutes to show a response.
I ran the tests in the OP and the tracert was fine the nettest results were similar to those reported by others.
I don't think that this is an ISP problem unless we're all on the same ISP, I'm using Comcast Cable in California.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms
2 47 ms 25 ms 29 ms
3 11 ms 10 ms 11 ms te-8-3-ur06.pleasanton.ca.sfba.comcast.net [68.8
7.196.101]
4 22 ms 21 ms 22 ms te-0-2-0-7-ar01.oakland.ca.sfba.comcast.net [69.
139.198.30]
5 17 ms 23 ms 25 ms te-0-1-0-5-cr01.seattle.wa.ibone.comcast.net [68
.86.90.121]
6 25 ms 22 ms 19 ms pos-0-6-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.86.202]
7 17 ms 18 ms 19 ms pos-0-5-0-0-pe01.529bryant.ca.ibone.comcast.net
[68.86.88.2]
8 64 ms 65 ms 64 ms te0-7-0-0.ccr21.sjc04.atlas.cogentco.com [154.54
.11.185]
9 66 ms 66 ms 71 ms te0-0-0-6.ccr21.sfo01.atlas.cogentco.com [154.54
.7.173]
10 62 ms * 65 ms te0-4-0-3.mpd22.mci01.atlas.cogentco.com [154.54
.45.85]
11 79 ms * 74 ms te0-3-0-7.mpd22.ord01.atlas.cogentco.com [154.54
.84.86]
12 106 ms 132 ms 103 ms te0-1-0-1.ccr22.bos01.atlas.cogentco.com [154.54
.6.21]
13 104 ms 104 ms 112 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
14 125 ms 124 ms 122 ms 38.111.40.114
15 109 ms 104 ms 108 ms 208.95.185.41
I'm having the same issues here. The game will just be completely unresponsive or have massive rubberbanding. By the end of it, I usually just get disconnected. It's making the game pretty much unplayable.
The results of the two tests are below.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
3 8 ms 9 ms * te-6-7-ur08.sacramento.ca.ccal.comcast.net [69.1
39.197.245]
4 8 ms 9 ms 10 ms te-0-2-0-0-ar03.sacramento.ca.sacra.comcast.net
[68.87.200.189]
5 10 ms 10 ms 11 ms pos-0-1-0-0-cr01.sacramento.ca.ibone.comcast.net
[68.86.90.133]
6 16 ms 15 ms 15 ms pos-0-9-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.85.181]
7 15 ms 13 ms 13 ms pos-0-2-0-0-pe01.529bryant.ca.ibone.comcast.net
[68.86.87.6]
8 55 ms 55 ms 54 ms te0-7-0-12.ccr21.sjc04.atlas.cogentco.com [154.5
4.11.109]
9 63 ms 47 ms 48 ms te0-0-0-6.ccr21.sfo01.atlas.cogentco.com [154.54
.7.173]
10 56 ms 64 ms 60 ms te0-3-0-1.ccr22.mci01.atlas.cogentco.com [154.54
.6.41]
11 71 ms 69 ms 70 ms te0-3-0-7.mpd22.ord01.atlas.cogentco.com [154.54
.84.86]
12 100 ms 103 ms 94 ms te0-1-0-6.ccr21.bos01.atlas.cogentco.com [154.54
.43.190]
13 165 ms 216 ms 207 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
14 94 ms 107 ms 91 ms 38.111.40.114
15 91 ms 95 ms 91 ms 208.95.185.41
I'm having the same issues here. The game will just be completely unresponsive or have massive rubberbanding. By the end of it, I usually just get disconnected. It's making the game pretty much unplayable.
The results of the two tests are below.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
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 7 ms 23 ms 8 ms 96.120.14.113
3 8 ms 9 ms * te-6-7-ur08.sacramento.ca.ccal.comcast.net [69.1
39.197.245]
4 8 ms 9 ms 10 ms te-0-2-0-0-ar03.sacramento.ca.sacra.comcast.net
[68.87.200.189]
5 10 ms 10 ms 11 ms pos-0-1-0-0-cr01.sacramento.ca.ibone.comcast.net
[68.86.90.133]
6 16 ms 15 ms 15 ms pos-0-9-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.85.181]
7 15 ms 13 ms 13 ms pos-0-2-0-0-pe01.529bryant.ca.ibone.comcast.net
[68.86.87.6]
8 55 ms 55 ms 54 ms te0-7-0-12.ccr21.sjc04.atlas.cogentco.com [154.5
4.11.109]
9 63 ms 47 ms 48 ms te0-0-0-6.ccr21.sfo01.atlas.cogentco.com [154.54
.7.173]
10 56 ms 64 ms 60 ms te0-3-0-1.ccr22.mci01.atlas.cogentco.com [154.54
.6.41]
11 71 ms 69 ms 70 ms te0-3-0-7.mpd22.ord01.atlas.cogentco.com [154.54
.84.86]
12 100 ms 103 ms 94 ms te0-1-0-6.ccr21.bos01.atlas.cogentco.com [154.54
.43.190] 13 165 ms 216 ms 207 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
14 94 ms 107 ms 91 ms 38.111.40.114
15 91 ms 95 ms 91 ms 208.95.185.41
Bolded hop in your traceroute has been shown to be problematic on several traces by several players (I['ve posted this after having run more than a dozen traces over several times of day on the global forums). Sandy hit right before S7 went live, so I wouldn't be the least bit surprised to be shown there was a major bottleneck in that relay.
Also, your nettest is extremely spotty on many ports. A hardware reset might clear that up, if you get those same nettest results after a full hardware reset/power cycle, a talk with your ISP may be in order.
If you installed via the website (as opposed to having had a boxed copy of the game some time ago), make sure PMB is not installed/not running on your PC. PMB runs as a limited P2P client, and will allow other users to download the STO installer from your PC, as well as any other game installer that utilizes PMB for downloading, which will in turn eat up bandwidth like Pac-Man eating pellets.
And for the sake of security, hide your local IP in your nettest results....
Quote:
Originally Posted by adeonhawkwood
I'm having exactly the same problem. It started on Friday. Sometimes the game will be fine but then it gets into a setup where it basically stops responding to commands. I (generally) seem to still be receiving data from the server regarding my environment (i.e. other players and NPCs keep moving on my screen) and the chat system continues to work fine but any commands I send take several minutes to show a response.
I ran the tests in the OP and the tracert was fine the nettest results were similar to those reported by others.
I don't think that this is an ISP problem unless we're all on the same ISP, I'm using Comcast Cable in California.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.1.1
2 47 ms 25 ms 29 ms 24.5.136.1
3 11 ms 10 ms 11 ms te-8-3-ur06.pleasanton.ca.sfba.comcast.net [68.8
7.196.101]
4 22 ms 21 ms 22 ms te-0-2-0-7-ar01.oakland.ca.sfba.comcast.net [69.
139.198.30]
5 17 ms 23 ms 25 ms te-0-1-0-5-cr01.seattle.wa.ibone.comcast.net [68
.86.90.121]
6 25 ms 22 ms 19 ms pos-0-6-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.86.202]
7 17 ms 18 ms 19 ms pos-0-5-0-0-pe01.529bryant.ca.ibone.comcast.net
[68.86.88.2]
8 64 ms 65 ms 64 ms te0-7-0-0.ccr21.sjc04.atlas.cogentco.com [154.54
.11.185]
9 66 ms 66 ms 71 ms te0-0-0-6.ccr21.sfo01.atlas.cogentco.com [154.54
.7.173]
10 62 ms * 65 ms te0-4-0-3.mpd22.mci01.atlas.cogentco.com [154.54
.45.85]
11 79 ms * 74 ms te0-3-0-7.mpd22.ord01.atlas.cogentco.com [154.54
.84.86]
12 106 ms 132 ms 103 ms te0-1-0-1.ccr22.bos01.atlas.cogentco.com [154.54
.6.21]
13 104 ms 104 ms 112 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
14 125 ms 124 ms 122 ms 38.111.40.114
15 109 ms 104 ms 108 ms 208.95.185.41
You've got a couple of partial misses in your trace (indicated by the asterisks, each hop on the trace receives three packets). That might explain the bit of lag time in your commands, but I can't be completely sure. The last few hops are a little high but not completely problematic.
Same as the above poster too: Unless you wish to unwittingly invite hackers into your PC, block out your local IP in your nettest results
Also, your nettest is extremely spotty on many ports. A hardware reset might clear that up, if you get those same nettest results after a full hardware reset/power cycle, a talk with your ISP may be in order.
I'm pretty confident that it's not my hardware. Mostly because STO is the only game where I'm having this issue. I've been playing a number of other online games today (since STO is virtually unplayable) and have not been having any lag issues in any of them, it's just STO.
Quote:
If you installed via the website (as opposed to having had a boxed copy of the game some time ago), make sure PMB is not installed/not running on your PC. PMB runs as a limited P2P client, and will allow other users to download the STO installer from your PC, as well as any other game installer that utilizes PMB for downloading, which will in turn eat up bandwidth like Pac-Man eating pellets.
I'll check and disable it on principle but see above comments regarding other games.
Quote:
Originally Posted by lewstelamon01
And for the sake of security, hide your local IP in your nettest results....
Fair enough, mind not quoting it then?
Last edited by adeonhawkwood; 12-08-2012 at 10:26 PM.
I'm pretty confident that it's not my hardware. Mostly because STO is the only game where I'm having this issue. I've been playing a number of other online games today (since STO is virtually unplayable) and have not been having any lag issues in any of them, it's just STO.
I'll check and disable it on principle but see above comments regarding other games.
Fair enough, mind not quoting it then?
Other games aren't nearly as network intensive as STO.
At any rate, those nettest numbers shouldn't be all over the place like that. Those numbers may not be the fault of your hardware, and it's at least worth a call to your ISP to find out why they're nowhere near consistent.
I've edited the IP addresses out of my quotes, but my statement still stands about other users remembering to block out their local IP when they post their nettest results.
NorCal Comcast user here, my husband and I are both having horrible lag/rubberbanding/server disconnects, just since the last patch. Before that everything was fine.
Trace:
Microsoft Windows [Version 6.1.7601]
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 192.168.1.1
2 13 ms 10 ms 9 ms [local IP]
3 11 ms 9 ms 15 ms te-7-8-ur09.sacramento.ca.ccal.comcast.net [68.85.120.129]
4 10 ms 9 ms 11 ms te-9-2-ur08.sacramento.ca.ccal.comcast.net [68.87.221.49]
5 10 ms 11 ms 11 ms te-0-2-0-0-ar03.sacramento.ca.sacra.comcast.net [68.87.200.189]
6 10 ms 11 ms 15 ms pos-0-4-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.90.21]
7 16 ms 16 ms 29 ms pos-0-7-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.85.46]
8 15 ms 15 ms 17 ms pos-0-2-0-0-pe01.529bryant.ca.ibone.comcast.net [68.86.87.6]
9 15 ms 13 ms 15 ms te0-7-0-12.ccr21.sjc04.atlas.cogentco.com [154.54.11.109]
10 15 ms 15 ms 13 ms te0-0-0-6.ccr21.sfo01.atlas.cogentco.com [154.54.7.173]
11 59 ms 59 ms 61 ms te0-1-0-2.ccr21.mci01.atlas.cogentco.com [154.54.24.118]
12 80 ms 71 ms 71 ms te0-5-0-4.ccr22.ord01.atlas.cogentco.com [154.54.45.150]
13 94 ms 93 ms 93 ms te0-1-0-6.ccr22.bos01.atlas.cogentco.com [154.54.43.206]
14 93 ms 93 ms 93 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
15 99 ms 93 ms 103 ms 38.111.40.114
16 93 ms 93 ms 94 ms 208.95.185.41
I am using Cox Communication and here is my results;
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms (My IP)
2 * * * Request timed out.
3 6 ms 5 ms 5 ms ip68-6-12-190.sd.sd.cox.net [68.6.12.190]
4 6 ms 6 ms 5 ms elcnsysc01-tec-141.sd.sd.cox.net [68.6.8.58]
5 6 ms 5 ms 5 ms fed1sysc01-gex0901.sd.sd.cox.net [68.6.8.100]
6 23 ms 23 ms 23 ms 68.1.5.129
7 32 ms 32 ms 32 ms dcr2-ge-7-0-0-292.sanfranciscosfo.savvis.net [208.173.170.1]
8 39 ms 33 ms 33 ms cr1-tenge-0-3-5-0.sanfrancisco.savvis.net [204.70.200.198]
9 72 ms 72 ms 72 ms cr2-bundle-pos-1.newyork.savvis.net [204.70.197.34]
10 70 ms 71 ms 71 ms er1-te-2-1.newyorknyd.savvis.net [204.70.196.70]
11 79 ms 77 ms 76 ms msr1-te-0-3-0-0.bos.savvis.net [206.28.97.205]
12 76 ms 75 ms 76 ms 206.28.97.137
13 176 ms 85 ms 80 ms internap.Boston.savvis.net [208.172.51.230]
14 164 ms 160 ms 166 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
15 77 ms 78 ms 78 ms cryptic-3.border11.bsn.pnap.net [216.52.61.78]
16 77 ms 77 ms 77 ms 208.95.185.41
Trace complete.
The information marked in orange seems to run through the area lewstelamon01 described earlier as running through the area hit by Sandy. I also would like to note that I had no latency issues prior to the season 7 release.