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.10.1
2 8 ms 7 ms 7 ms 73.165.176.1
3 7 ms 7 ms 7 ms te-9-1-ur02.exeter.nh.boston.comcast.net [68.87.
152.53]
4 8 ms 6 ms 7 ms po-20-ur01.exeter.nh.boston.comcast.net [68.87.1
45.106]
5 14 ms 15 ms 15 ms be-64-ar01.needham.ma.boston.comcast.net [68.85.
69.149]
6 28 ms 23 ms 23 ms he-2-5-0-0-cr01.newyork.ny.ibone.comcast.net [68
.86.94.201]
7 19 ms 22 ms 18 ms pos-0-1-0-0-pe01.111eighthave.ny.ibone.comcast.n
et [68.86.87.170]
8 18 ms 21 ms 18 ms te0-0-0-2.ccr22.jfk05.atlas.cogentco.com [154.54
.11.209]
9 20 ms 20 ms 18 ms te0-3-0-5.ccr22.jfk02.atlas.cogentco.com [154.54
.26.65]
10 25 ms 24 ms 25 ms te0-4-0-3.ccr22.bos01.atlas.cogentco.com [154.54
.44.66] 11 128 ms 208 ms 203 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
12 35 ms 35 ms 35 ms 38.111.40.114
13 24 ms 23 ms 25 ms 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 5 ms 4 ms 5 ms gw2-no149.tbcn.telia.com [81.224.251.1]
3 13 ms 13 ms 13 ms kbn-b3.telia.net [80.91.253.70]
4 31 ms 31 ms 31 ms te4-7.ccr01.cph01.atlas.cogentco.com [130.117.14.33]
5 28 ms 28 ms 29 ms te0-0-0-6.ccr22.ham01.atlas.cogentco.com [154.54.62.117]
6 29 ms 29 ms 29 ms te0-5-0-7.ccr22.ams03.atlas.cogentco.com [154.54.73.105]
7 41 ms 41 ms 41 ms te0-2-0-7.ccr22.lpl01.atlas.cogentco.com [154.54.37.122]
8 108 ms 107 ms 109 ms te0-0-0-3.ccr22.bos01.atlas.cogentco.com [154.54.42.101]
9 111 ms 111 ms 111 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
10 126 ms 128 ms 126 ms 38.111.40.114
11 107 ms 116 ms 108 ms 208.95.185.41
Trace complete.
Possible problem:
"Some of you might also experience a slower connection to one of our games or services. This is most probably due to several fiber cables being destroyed by the storm in the US east coast area."
Traza a la direcci?n patchserver.crypticstudios.com [208.95.185.41]
sobre un m?ximo de 30 saltos:
1 11 ms 6 ms 7 ms 10.112.128.1
2 9 ms 8 ms 7 ms 10.119.240.1
3 13 ms 11 ms 13 ms 10.119.240.101
4 15 ms 13 ms 11 ms 10.254.1.141
5 13 ms 13 ms 11 ms 10.254.4.170
6 19 ms 21 ms 19 ms te1-7.ccr02.vlc01.atlas.cogentco.com [149.6.83.6
9]
7 19 ms 23 ms 19 ms te4-7.ccr02.abc02.atlas.cogentco.com [154.54.58.
57]
8 19 ms 17 ms 17 ms te0-1-0-1.ccr22.mad05.atlas.cogentco.com [154.54
.36.149]
9 36 ms 37 ms 35 ms te0-7-0-14.mpd22.par01.atlas.cogentco.com [130.1
17.49.97]
10 44 ms 44 ms 52 ms te0-4-0-6.mpd22.lon13.atlas.cogentco.com [154.54
.37.189]
11 * * * Tiempo de espera agotado para esta solicitud.
12 * * * Tiempo de espera agotado para esta solicitud.
13 * * * Tiempo de espera agotado para esta solicitud.
14 * * * Tiempo de espera agotado para esta solicitud.
That's what i'm getting from Spain (Europe) lately... and the same result directly from my router so... somethings wrong on ALL the servers... because... there was servers on Europe, wasn't there?
I have been dealing with annoying lag times and 'pauses' for the past week.
I thought it was just the season 7 traffic slowing everything down.
But... In several events today I was the only one that was having lag time problems.
So my question to all of you is: Are you having lag time issues?
PS: Here are my tracert and nettest results:
1 <1 ms <1 ms <1 ms 1.1.168.192.in-addr.arpa [192.168.1.1]
2 35 ms 28 ms 19 ms 1.204.5.107.in-addr.arpa [107.5.204.1]
3 9 ms 10 ms 8 ms te-5-1-ur02.pontiac.mi.michigan.comcast.net [68.87.185.45]
4 10 ms 10 ms 9 ms te-9-3-ur03.pontiac.mi.michigan.comcast.net [68.87.191.138]
5 11 ms 12 ms 10 ms te-0-5-0-1-ar01.pontiac.mi.michigan.comcast.net [68.87.191.142]
6 26 ms 23 ms 23 ms he-4-5-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.221]
7 17 ms 15 ms 17 ms pos-1-5-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.87.126]
8 15 ms 15 ms 17 ms te0-4-0-7.ccr22.ord03.atlas.cogentco.com [154.54.12.129]
9 16 ms 15 ms 16 ms te0-4-0-0.ccr22.ord01.atlas.cogentco.com [154.54.1.97]
10 38 ms 37 ms 37 ms te0-3-0-1.ccr22.bos01.atlas.cogentco.com [154.54.24.57]
11 39 ms 37 ms 36 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
12 53 ms 38 ms 36 ms 114.40.111.38.in-addr.arpa [38.111.40.114]
13 37 ms 67 ms 37 ms 41.185.95.208.in-addr.arpa [208.95.185.41]
I have problems in logging in and if ever I was able to login... My game play is being rubberbanding really bad... So far with my observation, I experience this issue when I am to the Sol system.
See my test result below.
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 12 ms 3 ms 5 ms 192.168.0.254
2 5 ms 4 ms 3 ms 192.168.254.1
3 31 ms 29 ms 162 ms 180.191.3.1
4 30 ms 31 ms 31 ms 10.109.9.65
5 31 ms 30 ms 42 ms 120.28.0.193
6 33 ms 32 ms 31 ms 120.28.4.86
7 256 ms 204 ms 201 ms 120.28.0.78
8 171 ms 171 ms 195 ms te0-7-0-10.1108.ccr22.lax04.atlas.cogentco.com [38.104.210.241]
9 175 ms 190 ms 171 ms te0-4-0-7.ccr22.lax01.atlas.cogentco.com [154.54.84.121]
10 211 ms 208 ms 206 ms te0-2-0-3.ccr22.iah01.atlas.cogentco.com [154.54.45.1]
11 256 ms 306 ms 225 ms te0-0-0-2.ccr22.atl01.atlas.cogentco.com [154.54.5.93]
12 247 ms 232 ms 232 ms te0-5-0-7.ccr22.dca01.atlas.cogentco.com [154.54.42.201]
13 292 ms 238 ms 239 ms te0-7-0-14.ccr21.jfk02.atlas.cogentco.com [154.54.41.6]
14 245 ms 248 ms 245 ms te0-2-0-1.ccr22.bos01.atlas.cogentco.com [154.54.44.94]
15 279 ms 248 ms 245 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
16 253 ms 260 ms 252 ms 38.111.40.114
17 246 ms 245 ms 257 ms 208.95.185.41
Trace complete.
C:\Users\Administrator>
contacting nettest server..
timed out
hit return to exit
I have problems in logging in and if ever I was able to login... My game play is being rubberbanding really bad... So far with my observation, I experience this issue when I am to the Sol system.
See my test result below.
ISP: Globe Tattoo Broadband (Manila, Philippines)
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 12 ms 3 ms 5 ms 192.168.0.254
2 5 ms 4 ms 3 ms 192.168.254.1
3 31 ms 29 ms 162 ms 180.191.3.1
4 30 ms 31 ms 31 ms 10.109.9.65
5 31 ms 30 ms 42 ms 120.28.0.193
6 33 ms 32 ms 31 ms 120.28.4.86
7 256 ms 204 ms 201 ms 120.28.0.78
8 171 ms 171 ms 195 ms te0-7-0-10.1108.ccr22.lax04.atlas.cogentco.com [38.104.210.241]
9 175 ms 190 ms 171 ms te0-4-0-7.ccr22.lax01.atlas.cogentco.com [154.54.84.121]
10 211 ms 208 ms 206 ms te0-2-0-3.ccr22.iah01.atlas.cogentco.com [154.54.45.1]
11 256 ms 306 ms 225 ms te0-0-0-2.ccr22.atl01.atlas.cogentco.com [154.54.5.93]
12 247 ms 232 ms 232 ms te0-5-0-7.ccr22.dca01.atlas.cogentco.com [154.54.42.201]
13 292 ms 238 ms 239 ms te0-7-0-14.ccr21.jfk02.atlas.cogentco.com [154.54.41.6]
14 245 ms 248 ms 245 ms te0-2-0-1.ccr22.bos01.atlas.cogentco.com [154.54.44.94]
15 279 ms 248 ms 245 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
16 253 ms 260 ms 252 ms 38.111.40.114
17 246 ms 245 ms 257 ms 208.95.185.41
Trace complete.
C:\Users\Administrator>
contacting nettest server..
timed out
hit return to exit
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms kotiboksi.Elisa [192.168.100.1]
2 69 ms 34 ms 33 ms kerker1.fi.elisa.net [88.112.64.1]
3 30 ms 27 ms 23 ms ge1-1-0.helso-p1.fi.elisa.net [139.97.9.37]
4 26 ms 21 ms 30 ms ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
5 36 ms 28 ms 29 ms ae1-10.bbr1.hel2.fi.eunetip.net [213.192.191.53]
6 30 ms 90 ms 51 ms so7-0-0-0.bbr1.sto1.se.eunetip.net [213.192.191.210]
7 69 ms 65 ms 40 ms xe-10-2-1.bar1.Stockholm1.Level3.net [213.242.110.169]
8 32 ms 29 ms 31 ms te0-0-0-4.ccr21.sto01.atlas.cogentco.com [130.117.15.229]
9 81 ms 31 ms 44 ms te0-2-0-4.ccr21.sto03.atlas.cogentco.com [154.54.58.202]
10 74 ms 68 ms 78 ms te0-3-0-5.ccr21.ham01.atlas.cogentco.com [154.54.38.29]
11 60 ms 64 ms 81 ms te0-0-0-3.ccr21.ams03.atlas.cogentco.com [130.117.50.41]
12 74 ms 73 ms 79 ms te0-4-0-7.ccr22.lpl01.atlas.cogentco.com [154.54.58.70]
13 139 ms 193 ms 170 ms te0-3-0-3.ccr22.bos01.atlas.cogentco.com [154.54.1.157]
14 160 ms 207 ms 384 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
15 175 ms 165 ms 175 ms 38.111.40.114
16 150 ms 199 ms 138 ms 208.95.185.41
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 28 ms 30 ms 26 ms 10.100.32.1
2 27 ms 27 ms 29 ms 68.13.10.105
3 29 ms 29 ms 27 ms 68.13.8.253
4 65 ms 26 ms 27 ms mtc1dsrj01-ae4.0.rd.om.cox.net [68.13.14.5]
5 43 ms 45 ms 43 ms 68.1.5.140
6 * * 181 ms dpr1-ge-3-0-0-298.dallasequinix.savvis.net [208.173.178.177]
7 87 ms 53 ms 56 ms dpr1-ge-2-0-0.dallasequinix.savvis.net [204.70.204.146]
8 47 ms 43 ms 42 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196.29]
9 91 ms 91 ms 93 ms cr2-tengig-0-15-0-0.NewYork.savvis.net [204.70.196.118]
10 91 ms 93 ms 90 ms er1-te-2-1.newyorknyd.savvis.net [204.70.196.70]
11 98 ms 97 ms 101 ms msr1-te-0-3-0-0.bos.savvis.net [206.28.97.205]
12 97 ms 99 ms 100 ms 206.28.97.137
13 97 ms 99 ms 97 ms internap.Boston.savvis.net [208.172.51.230]
14 100 ms 104 ms 101 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
15 101 ms 108 ms 107 ms cryptic-3.border11.bsn.pnap.net [216.52.61.78]
16 98 ms 97 ms 99 ms 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 homeportal [192.168.1.254]
2 48 ms 26 ms 25 ms 99-69-110-3.lightspeed.tulsok.sbcglobal.net [99.
69.110.3]
3 * * * Request timed out.
4 * * * Request timed out.
5 27 ms 26 ms 29 ms 12.83.46.5
6 36 ms 38 ms 39 ms ggr3.dlstx.ip.att.net [12.122.139.17]
7 82 ms 80 ms 81 ms 192.205.36.194
8 79 ms 79 ms 80 ms te0-4-0-3.ccr22.dfw01.atlas.cogentco.com [154.54
.82.29]
9 93 ms 92 ms 94 ms te0-3-0-0.mpd22.mci01.atlas.cogentco.com [154.54
.25.206]
10 * 67 ms 67 ms te0-4-0-3.mpd22.ord01.atlas.cogentco.com [154.54
.30.177]
11 76 ms 76 ms 76 ms te0-1-0-6.ccr21.bos01.atlas.cogentco.com [154.54
.43.190]
12 77 ms 74 ms 76 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
13 83 ms 89 ms 88 ms 38.111.40.114
14 76 ms 77 ms 76 ms 208.95.185.41
I have problems in logging in and if ever I was able to login... My game play is being rubberbanding really bad... So far with my observation, I experience this issue when I am to the Sol system.
See my test result below.
ISP: Globe Tattoo Broadband (Manila, Philippines)
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 12 ms 3 ms 5 ms 192.168.0.254
2 5 ms 4 ms 3 ms 192.168.254.1
3 31 ms 29 ms 162 ms 180.191.3.1
4 30 ms 31 ms 31 ms 10.109.9.65
5 31 ms 30 ms 42 ms 120.28.0.193
6 33 ms 32 ms 31 ms 120.28.4.86 7 256 ms 204 ms 201 ms 120.28.0.78
8 171 ms 171 ms 195 ms te0-7-0-10.1108.ccr22.lax04.atlas.cogentco.com [38.104.210.241]
9 175 ms 190 ms 171 ms te0-4-0-7.ccr22.lax01.atlas.cogentco.com [154.54.84.121]
10 211 ms 208 ms 206 ms te0-2-0-3.ccr22.iah01.atlas.cogentco.com [154.54.45.1]
11 256 ms 306 ms 225 ms te0-0-0-2.ccr22.atl01.atlas.cogentco.com [154.54.5.93]
12 247 ms 232 ms 232 ms te0-5-0-7.ccr22.dca01.atlas.cogentco.com [154.54.42.201]
13 292 ms 238 ms 239 ms te0-7-0-14.ccr21.jfk02.atlas.cogentco.com [154.54.41.6]
14 245 ms 248 ms 245 ms te0-2-0-1.ccr22.bos01.atlas.cogentco.com [154.54.44.94]
15 279 ms 248 ms 245 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
16 253 ms 260 ms 252 ms 38.111.40.114
17 246 ms 245 ms 257 ms 208.95.185.41
Trace complete.
C:\Users\Administrator>
contacting nettest server..
timed out
hit return to exit
Holy hell at those bolded hop times. Anything over 100 is not good, those numbers are horrid. There's an issue along the way there, I'd be surprised your data is getting to the server intact at all.
ok how is this Im not sure what Im looking at here
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 homeportal [192.168.1.254]
2 48 ms 26 ms 25 ms 99-69-110-3.lightspeed.tulsok.sbcglobal.net [99.
69.110.3]
3 * * * Request timed out.
4 * * * Request timed out.
5 27 ms 26 ms 29 ms 12.83.46.5
6 36 ms 38 ms 39 ms ggr3.dlstx.ip.att.net [12.122.139.17]
7 82 ms 80 ms 81 ms 192.205.36.194
8 79 ms 79 ms 80 ms te0-4-0-3.ccr22.dfw01.atlas.cogentco.com [154.54
.82.29]
9 93 ms 92 ms 94 ms te0-3-0-0.mpd22.mci01.atlas.cogentco.com [154.54
.25.206]
10 * 67 ms 67 ms te0-4-0-3.mpd22.ord01.atlas.cogentco.com [154.54
.30.177]
11 76 ms 76 ms 76 ms te0-1-0-6.ccr21.bos01.atlas.cogentco.com [154.54
.43.190]
12 77 ms 74 ms 76 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
13 83 ms 89 ms 88 ms 38.111.40.114
14 76 ms 77 ms 76 ms 208.95.185.41
Trace complete.
Don't know either, you're getting some hops that are completely timing out, but otherwise, those numbers look fine, if borderline in a couple places.
can you explain what a hop time is sorry Im a dumb marine lol not very pc wise but youhand me a nade launcher and a rifle Ill kill a towelhead
Using the traceroute you provided as an example...
1 1 ms 1 ms 1 ms homeportal [192.168.1.254]
2 48 ms 26 ms 25 ms 99-69-110-3.lightspeed.tulsok.sbcglobal.net [99.
69.110.3] 3 * * * Request timed out.
4 * * * Request timed out.
5 27 ms 26 ms 29 ms 12.83.46.5
6 36 ms 38 ms 39 ms ggr3.dlstx.ip.att.net [12.122.139.17]
7 82 ms 80 ms 81 ms 192.205.36.194
8 79 ms 79 ms 80 ms te0-4-0-3.ccr22.dfw01.atlas.cogentco.com [154.54
.82.29]
9 93 ms 92 ms 94 ms te0-3-0-0.mpd22.mci01.atlas.cogentco.com [154.54
.25.206]
10 * 67 ms 67 ms te0-4-0-3.mpd22.ord01.atlas.cogentco.com [154.54
.30.177]
11 76 ms 76 ms 76 ms te0-1-0-6.ccr21.bos01.atlas.cogentco.com [154.54
.43.190]
12 77 ms 74 ms 76 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
13 83 ms 89 ms 88 ms 38.111.40.114
14 76 ms 77 ms 76 ms 208.95.185.41
Each entry in your trace (the ones marked as 1, 2, and so on) is called a "hop". Think of it as a postal route and those are the stops along the way. The ones I've highlighted in yellow are your problem points. Also, in any hop where you see an asterisk, that's a partial timeout--which means a significant lag in response time.
I've made a thread about the lag I'm getting, I figured I'd post in here as well:
I've been getting a huge amount of lag, I checked the ping using netgraph and it is fluctuating wildly from 100-3000 ping. Here is a Tracert to the patchserver:
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 8 ms 10.14.8.1
3 8 ms 8 ms 8 ms 10.1.1.9
4 61 ms 201 ms 198 ms 209.221.47.61
5 108 ms 103 ms 113 ms atl-bb1-geth0-0-0-15.telia.net [213.248.90.29]
6 118 ms 119 ms 137 ms ash-bb1-link.telia.net [80.91.252.213]
7 123 ms 116 ms 121 ms te0-7-0-6.mpd21.iad02.atlas.cogentco.com [154.54
.10.57]
8 130 ms 125 ms 122 ms te0-2-0-4.mpd21.dca01.atlas.cogentco.com [154.54
.26.113]
9 58 ms 63 ms * te0-7-0-2.mpd21.jfk02.atlas.cogentco.com [154.54
.3.46]
10 * 60 ms 51 ms te0-0-0-1.ccr21.bos01.atlas.cogentco.com [154.54
.6.1]
11 47 ms 45 ms 49 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
12 62 ms 70 ms 57 ms 38.111.40.114
13 47 ms 61 ms 48 ms 208.95.185.41
I've tried bypassing the router and switching the routers, no luck. I've got STO installed on a Desktop and a Laptop and the lag is happening on both.
Anyone got any ideas of what could be going on?
Before Season 7 I was not having any issues with lag, ever since it began its been horrible a lot of the time. Every once in a while I get some time to play when there's no lag, but it seems those times are coming less and less often.
Well After talking with Tech support at RR Tampabay, They saw errors and reset things on there end along with me doing a full power/remove battery reset of the modem on my end now am getting the following number.
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
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....
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.
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.
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.
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.
Brian
True, but those numbers aren't completely problematic there, except in hop 14. I'll point out, though, that I'd run several traces over a period of time when I posted that commentary and got wildly variable results...but yes, they were in that zone.
Comments
Hmmm... where have we seen this name before? >:-(
Second time... 9min later
ISP: TELIA (SWEDEN)
Local IP: TRIBBLE.TRIBBLE.TRIBBLE.TRIBBLE
Ping: 107.2 msec
Port: 80: 27 KB/sec 5 KB/sec 206 KB/sec 500
Port: 80: 17 KB/sec 4 KB/sec 158 KB/sec 500
Port: 443: 30 KB/sec 4 KB/sec 130 KB/sec 500
Port: 443: 19 KB/sec 4 KB/sec 167 KB/sec 500
Port: 7255: 20 KB/sec 6 KB/sec 273 KB/sec 500
Port: 7255: 23 KB/sec 5 KB/sec 209 KB/sec 500
Port: 7003: 29 KB/sec 4 KB/sec 170 KB/sec 500
Port: 7003: 20 KB/sec 4 KB/sec 137 KB/sec 500
Port: 7202: 21 KB/sec 4 KB/sec 152 KB/sec 500
Port: 7202: 16 KB/sec 4 KB/sec 158 KB/sec 500
Port: 7499: 20 KB/sec 5 KB/sec 241 KB/sec 500
Port: 7499: 19 KB/sec 5 KB/sec 226 KB/sec 500
Port: 80: 28 KB/sec 5 KB/sec 191 KB/sec 500
Idle NIC bandwidth Send: 3 KB/sec Recv: 201 KB/sec
hit return to exit
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 5 ms 4 ms 5 ms gw2-no149.tbcn.telia.com [81.224.251.1]
3 13 ms 13 ms 13 ms kbn-b3.telia.net [80.91.253.70]
4 31 ms 31 ms 31 ms te4-7.ccr01.cph01.atlas.cogentco.com [130.117.14.33]
5 28 ms 28 ms 29 ms te0-0-0-6.ccr22.ham01.atlas.cogentco.com [154.54.62.117]
6 29 ms 29 ms 29 ms te0-5-0-7.ccr22.ams03.atlas.cogentco.com [154.54.73.105]
7 41 ms 41 ms 41 ms te0-2-0-7.ccr22.lpl01.atlas.cogentco.com [154.54.37.122]
8 108 ms 107 ms 109 ms te0-0-0-3.ccr22.bos01.atlas.cogentco.com [154.54.42.101]
9 111 ms 111 ms 111 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
10 126 ms 128 ms 126 ms 38.111.40.114
11 107 ms 116 ms 108 ms 208.95.185.41
Trace complete.
Possible problem:
"Some of you might also experience a slower connection to one of our games or services. This is most probably due to several fiber cables being destroyed by the storm in the US east coast area."
sobre un m?ximo de 30 saltos:
1 11 ms 6 ms 7 ms 10.112.128.1
2 9 ms 8 ms 7 ms 10.119.240.1
3 13 ms 11 ms 13 ms 10.119.240.101
4 15 ms 13 ms 11 ms 10.254.1.141
5 13 ms 13 ms 11 ms 10.254.4.170
6 19 ms 21 ms 19 ms te1-7.ccr02.vlc01.atlas.cogentco.com [149.6.83.6
9]
7 19 ms 23 ms 19 ms te4-7.ccr02.abc02.atlas.cogentco.com [154.54.58.
57]
8 19 ms 17 ms 17 ms te0-1-0-1.ccr22.mad05.atlas.cogentco.com [154.54
.36.149]
9 36 ms 37 ms 35 ms te0-7-0-14.mpd22.par01.atlas.cogentco.com [130.1
17.49.97]
10 44 ms 44 ms 52 ms te0-4-0-6.mpd22.lon13.atlas.cogentco.com [154.54
.37.189]
11 * * * Tiempo de espera agotado para esta solicitud.
12 * * * Tiempo de espera agotado para esta solicitud.
13 * * * Tiempo de espera agotado para esta solicitud.
14 * * * Tiempo de espera agotado para esta solicitud.
That's what i'm getting from Spain (Europe) lately... and the same result directly from my router so... somethings wrong on ALL the servers... because... there was servers on Europe, wasn't there?
I thought it was just the season 7 traffic slowing everything down.
But... In several events today I was the only one that was having lag time problems.
So my question to all of you is: Are you having lag time issues?
PS: Here are my tracert and nettest results:
1 <1 ms <1 ms <1 ms 1.1.168.192.in-addr.arpa [192.168.1.1]
2 35 ms 28 ms 19 ms 1.204.5.107.in-addr.arpa [107.5.204.1]
3 9 ms 10 ms 8 ms te-5-1-ur02.pontiac.mi.michigan.comcast.net [68.87.185.45]
4 10 ms 10 ms 9 ms te-9-3-ur03.pontiac.mi.michigan.comcast.net [68.87.191.138]
5 11 ms 12 ms 10 ms te-0-5-0-1-ar01.pontiac.mi.michigan.comcast.net [68.87.191.142]
6 26 ms 23 ms 23 ms he-4-5-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.221]
7 17 ms 15 ms 17 ms pos-1-5-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.87.126]
8 15 ms 15 ms 17 ms te0-4-0-7.ccr22.ord03.atlas.cogentco.com [154.54.12.129]
9 16 ms 15 ms 16 ms te0-4-0-0.ccr22.ord01.atlas.cogentco.com [154.54.1.97]
10 38 ms 37 ms 37 ms te0-3-0-1.ccr22.bos01.atlas.cogentco.com [154.54.24.57]
11 39 ms 37 ms 36 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
12 53 ms 38 ms 36 ms 114.40.111.38.in-addr.arpa [38.111.40.114]
13 37 ms 67 ms 37 ms 41.185.95.208.in-addr.arpa [208.95.185.41]
Trace complete.
contacting nettest server..
Local IP: 107.5.207.92
Ping: 40.6 msec
Port: 80: 1521 KB/sec 49 KB/sec 1601 KB/sec 500
Port: 80: 1584 KB/sec 51 KB/sec 1668 KB/sec 500
Port: 443: 1628 KB/sec 51 KB/sec 1712 KB/sec 500
Port: 443: 1633 KB/sec 53 KB/sec 1718 KB/sec 500
Port: 7255: 1606 KB/sec 51 KB/sec 1688 KB/sec 500
Port: 7255: 1631 KB/sec 51 KB/sec 1716 KB/sec 500
Port: 7003: 1488 KB/sec 46 KB/sec 1564 KB/sec 500
Port: 7003: 1651 KB/sec 53 KB/sec 1736 KB/sec 500
Port: 7202: 1622 KB/sec 52 KB/sec 1705 KB/sec 500
Port: 7202: 1560 KB/sec 49 KB/sec 1640 KB/sec 500
Port: 7499: 1689 KB/sec 54 KB/sec 1777 KB/sec 500
Port: 7499: 1610 KB/sec 52 KB/sec 1693 KB/sec 500
Port: 80: 1623 KB/sec 52 KB/sec 1709 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 1 KB/sec
See my test result below.
Microsoft Windows [Version 6.1.7601]
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 12 ms 3 ms 5 ms 192.168.0.254
2 5 ms 4 ms 3 ms 192.168.254.1
3 31 ms 29 ms 162 ms 180.191.3.1
4 30 ms 31 ms 31 ms 10.109.9.65
5 31 ms 30 ms 42 ms 120.28.0.193
6 33 ms 32 ms 31 ms 120.28.4.86
7 256 ms 204 ms 201 ms 120.28.0.78
8 171 ms 171 ms 195 ms te0-7-0-10.1108.ccr22.lax04.atlas.cogentco.com [38.104.210.241]
9 175 ms 190 ms 171 ms te0-4-0-7.ccr22.lax01.atlas.cogentco.com [154.54.84.121]
10 211 ms 208 ms 206 ms te0-2-0-3.ccr22.iah01.atlas.cogentco.com [154.54.45.1]
11 256 ms 306 ms 225 ms te0-0-0-2.ccr22.atl01.atlas.cogentco.com [154.54.5.93]
12 247 ms 232 ms 232 ms te0-5-0-7.ccr22.dca01.atlas.cogentco.com [154.54.42.201]
13 292 ms 238 ms 239 ms te0-7-0-14.ccr21.jfk02.atlas.cogentco.com [154.54.41.6]
14 245 ms 248 ms 245 ms te0-2-0-1.ccr22.bos01.atlas.cogentco.com [154.54.44.94]
15 279 ms 248 ms 245 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
16 253 ms 260 ms 252 ms 38.111.40.114
17 246 ms 245 ms 257 ms 208.95.185.41
Trace complete.
C:\Users\Administrator>
contacting nettest server..
timed out
hit return to exit
See my test result below.
ISP: Globe Tattoo Broadband (Manila, Philippines)
Microsoft Windows [Version 6.1.7601]
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 12 ms 3 ms 5 ms 192.168.0.254
2 5 ms 4 ms 3 ms 192.168.254.1
3 31 ms 29 ms 162 ms 180.191.3.1
4 30 ms 31 ms 31 ms 10.109.9.65
5 31 ms 30 ms 42 ms 120.28.0.193
6 33 ms 32 ms 31 ms 120.28.4.86
7 256 ms 204 ms 201 ms 120.28.0.78
8 171 ms 171 ms 195 ms te0-7-0-10.1108.ccr22.lax04.atlas.cogentco.com [38.104.210.241]
9 175 ms 190 ms 171 ms te0-4-0-7.ccr22.lax01.atlas.cogentco.com [154.54.84.121]
10 211 ms 208 ms 206 ms te0-2-0-3.ccr22.iah01.atlas.cogentco.com [154.54.45.1]
11 256 ms 306 ms 225 ms te0-0-0-2.ccr22.atl01.atlas.cogentco.com [154.54.5.93]
12 247 ms 232 ms 232 ms te0-5-0-7.ccr22.dca01.atlas.cogentco.com [154.54.42.201]
13 292 ms 238 ms 239 ms te0-7-0-14.ccr21.jfk02.atlas.cogentco.com [154.54.41.6]
14 245 ms 248 ms 245 ms te0-2-0-1.ccr22.bos01.atlas.cogentco.com [154.54.44.94]
15 279 ms 248 ms 245 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
16 253 ms 260 ms 252 ms 38.111.40.114
17 246 ms 245 ms 257 ms 208.95.185.41
Trace complete.
C:\Users\Administrator>
contacting nettest server..
timed out
hit return to exit
ISP: Elisa (Finland)
contacting nettest server..
Local IP: XX.TRIBBLE.XX.TRIBBLE
Ping: 150.0 msec
Port: 80: 280 KB/sec 77 KB/sec 303 KB/sec 500
Port: 80: 142 KB/sec 93 KB/sec 159 KB/sec 500
Port: 443: 389 KB/sec 95 KB/sec 421 KB/sec 500
Port: 443: 386 KB/sec 94 KB/sec 416 KB/sec 500
Port: 7255: 429 KB/sec 98 KB/sec 463 KB/sec 500
Port: 7255: 424 KB/sec 80 KB/sec 458 KB/sec 500
Port: 7003: 443 KB/sec 77 KB/sec 478 KB/sec 500
Port: 7003: 392 KB/sec 96 KB/sec 427 KB/sec 500
Port: 7202: 401 KB/sec 92 KB/sec 436 KB/sec 500
Port: 7202: 391 KB/sec 79 KB/sec 424 KB/sec 500
Port: 7499: 455 KB/sec 44 KB/sec 485 KB/sec 500
Port: 7499: 94 KB/sec 99 KB/sec 114 KB/sec 500
Port: 80: 133 KB/sec 78 KB/sec 152 KB/sec 500
Idle NIC bandwidth Send: 45 KB/sec Recv: 9 KB/sec
hit return to exit
C:\Users\kurre>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 kotiboksi.Elisa [192.168.100.1]
2 69 ms 34 ms 33 ms kerker1.fi.elisa.net [88.112.64.1]
3 30 ms 27 ms 23 ms ge1-1-0.helso-p1.fi.elisa.net [139.97.9.37]
4 26 ms 21 ms 30 ms ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
5 36 ms 28 ms 29 ms ae1-10.bbr1.hel2.fi.eunetip.net [213.192.191.53]
6 30 ms 90 ms 51 ms so7-0-0-0.bbr1.sto1.se.eunetip.net [213.192.191.210]
7 69 ms 65 ms 40 ms xe-10-2-1.bar1.Stockholm1.Level3.net [213.242.110.169]
8 32 ms 29 ms 31 ms te0-0-0-4.ccr21.sto01.atlas.cogentco.com [130.117.15.229]
9 81 ms 31 ms 44 ms te0-2-0-4.ccr21.sto03.atlas.cogentco.com [154.54.58.202]
10 74 ms 68 ms 78 ms te0-3-0-5.ccr21.ham01.atlas.cogentco.com [154.54.38.29]
11 60 ms 64 ms 81 ms te0-0-0-3.ccr21.ams03.atlas.cogentco.com [130.117.50.41]
12 74 ms 73 ms 79 ms te0-4-0-7.ccr22.lpl01.atlas.cogentco.com [154.54.58.70]
13 139 ms 193 ms 170 ms te0-3-0-3.ccr22.bos01.atlas.cogentco.com [154.54.1.157]
14 160 ms 207 ms 384 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
15 175 ms 165 ms 175 ms 38.111.40.114
16 150 ms 199 ms 138 ms 208.95.185.41
Trace complete.
:rolleyes:
ISP - Cox Communications - Omaha, NE, USA.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\TRIBBLE>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 28 ms 30 ms 26 ms 10.100.32.1
2 27 ms 27 ms 29 ms 68.13.10.105
3 29 ms 29 ms 27 ms 68.13.8.253
4 65 ms 26 ms 27 ms mtc1dsrj01-ae4.0.rd.om.cox.net [68.13.14.5]
5 43 ms 45 ms 43 ms 68.1.5.140
6 * * 181 ms dpr1-ge-3-0-0-298.dallasequinix.savvis.net [208.173.178.177]
7 87 ms 53 ms 56 ms dpr1-ge-2-0-0.dallasequinix.savvis.net [204.70.204.146]
8 47 ms 43 ms 42 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196.29]
9 91 ms 91 ms 93 ms cr2-tengig-0-15-0-0.NewYork.savvis.net [204.70.196.118]
10 91 ms 93 ms 90 ms er1-te-2-1.newyorknyd.savvis.net [204.70.196.70]
11 98 ms 97 ms 101 ms msr1-te-0-3-0-0.bos.savvis.net [206.28.97.205]
12 97 ms 99 ms 100 ms 206.28.97.137
13 97 ms 99 ms 97 ms internap.Boston.savvis.net [208.172.51.230]
14 100 ms 104 ms 101 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
15 101 ms 108 ms 107 ms cryptic-3.border11.bsn.pnap.net [216.52.61.78]
16 98 ms 97 ms 99 ms 208.95.185.41
Trace complete.
contacting nettest server..
Local IP: xx.xx.xx.TRIBBLE
Ping: 96.8 msec
Port: 80: 338 KB/sec 8 KB/sec 358 KB/sec 500
Port: 80: 131 KB/sec 3 KB/sec 140 KB/sec 500
Port: 443: 534 KB/sec 10 KB/sec 564 KB/sec 500
Port: 443: 195 KB/sec 5 KB/sec 208 KB/sec 500
Port: 7255: 475 KB/sec 8 KB/sec 503 KB/sec 500
Port: 7255: 487 KB/sec 9 KB/sec 515 KB/sec 500
Port: 7003: 486 KB/sec 9 KB/sec 514 KB/sec 500
Port: 7003: 231 KB/sec 5 KB/sec 245 KB/sec 500
Port: 7202: 461 KB/sec 7 KB/sec 486 KB/sec 500
Port: 7202: 460 KB/sec 6 KB/sec 486 KB/sec 500
Port: 7499: 486 KB/sec 8 KB/sec 514 KB/sec 500
Port: 7499: 529 KB/sec 8 KB/sec 558 KB/sec 500
Port: 80: 112 KB/sec 2 KB/sec 120 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 2 KB/sec
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\jason>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 homeportal [192.168.1.254]
2 48 ms 26 ms 25 ms 99-69-110-3.lightspeed.tulsok.sbcglobal.net [99.
69.110.3]
3 * * * Request timed out.
4 * * * Request timed out.
5 27 ms 26 ms 29 ms 12.83.46.5
6 36 ms 38 ms 39 ms ggr3.dlstx.ip.att.net [12.122.139.17]
7 82 ms 80 ms 81 ms 192.205.36.194
8 79 ms 79 ms 80 ms te0-4-0-3.ccr22.dfw01.atlas.cogentco.com [154.54
.82.29]
9 93 ms 92 ms 94 ms te0-3-0-0.mpd22.mci01.atlas.cogentco.com [154.54
.25.206]
10 * 67 ms 67 ms te0-4-0-3.mpd22.ord01.atlas.cogentco.com [154.54
.30.177]
11 76 ms 76 ms 76 ms te0-1-0-6.ccr21.bos01.atlas.cogentco.com [154.54
.43.190]
12 77 ms 74 ms 76 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
13 83 ms 89 ms 88 ms 38.111.40.114
14 76 ms 77 ms 76 ms 208.95.185.41
Trace complete.
Holy hell at those bolded hop times. Anything over 100 is not good, those numbers are horrid. There's an issue along the way there, I'd be surprised your data is getting to the server intact at all.
Don't know either, you're getting some hops that are completely timing out, but otherwise, those numbers look fine, if borderline in a couple places.
ROLL TIDE ROLL
Using the traceroute you provided as an example...
Each entry in your trace (the ones marked as 1, 2, and so on) is called a "hop". Think of it as a postal route and those are the stops along the way. The ones I've highlighted in yellow are your problem points. Also, in any hop where you see an asterisk, that's a partial timeout--which means a significant lag in response time.
ROLL TIDE ROLL
I've been getting a huge amount of lag, I checked the ping using netgraph and it is fluctuating wildly from 100-3000 ping. Here is a Tracert to the patchserver:
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 8 ms 10.14.8.1
3 8 ms 8 ms 8 ms 10.1.1.9
4 61 ms 201 ms 198 ms 209.221.47.61
5 108 ms 103 ms 113 ms atl-bb1-geth0-0-0-15.telia.net [213.248.90.29]
6 118 ms 119 ms 137 ms ash-bb1-link.telia.net [80.91.252.213]
7 123 ms 116 ms 121 ms te0-7-0-6.mpd21.iad02.atlas.cogentco.com [154.54
.10.57]
8 130 ms 125 ms 122 ms te0-2-0-4.mpd21.dca01.atlas.cogentco.com [154.54
.26.113]
9 58 ms 63 ms * te0-7-0-2.mpd21.jfk02.atlas.cogentco.com [154.54
.3.46]
10 * 60 ms 51 ms te0-0-0-1.ccr21.bos01.atlas.cogentco.com [154.54
.6.1]
11 47 ms 45 ms 49 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
12 62 ms 70 ms 57 ms 38.111.40.114
13 47 ms 61 ms 48 ms 208.95.185.41
Trace complete.
Here are the Nettest results:
contacting nettest server..
Local IP: ******* - I'm hiding this
Ping: 130.5 msec
Port: 80: 13 KB/sec 8 KB/sec 15 KB/sec 500
Port: 80: 32 KB/sec 2 KB/sec 36 KB/sec 500
Port: 443: 28 KB/sec 10 KB/sec 110 KB/sec 500
Port: 443: 24 KB/sec 6 KB/sec 57 KB/sec 500
Port: 7255: 28 KB/sec 4 KB/sec 32 KB/sec 500
Port: 7255: timed out
Port: 7003: 29 KB/sec 3 KB/sec 49 KB/sec 500
Port: 7003: 30 KB/sec 2 KB/sec 35 KB/sec 500
Port: 7202: timed out
Port: 7202: 21 KB/sec 3 KB/sec 34 KB/sec 500
Port: 7499: 33 KB/sec 2 KB/sec 37 KB/sec 500
Port: 7499: 36 KB/sec 3 KB/sec 41 KB/sec 500
Port: 80: 38 KB/sec 2 KB/sec 41 KB/sec 500
Idle NIC bandwidth Send: 1 KB/sec Recv: 0 KB/sec
hit return to exit
My ISP is Northland Cable and I'm located near Savannah, GA.
Here is a Pingtest from pingtest.net:
http://www.pingtest.net/result/73275626.png
Here is a Speedtest:
http://www.speedtest.net/result/2347373763.png
I've tried bypassing the router and switching the routers, no luck. I've got STO installed on a Desktop and a Laptop and the lag is happening on both.
Anyone got any ideas of what could be going on?
Before Season 7 I was not having any issues with lag, ever since it began its been horrible a lot of the time. Every once in a while I get some time to play when there's no lag, but it seems those times are coming less and less often.
Here are the results, if I understand the original post this is bad...I believe.
If someone could confirm. My ISP is Road Runner Bright House Tampa.
contacting nettest server..
Local IP: 70.127.35.95
Ping: 176.5 msec
Port: 80: 22 KB/sec 3 KB/sec 102 KB/sec 500
Port: 80: timed out
Port: 443: 19 KB/sec 2 KB/sec 59 KB/sec 500
Port: 443: 19 KB/sec 3 KB/sec 65 KB/sec 500
Port: 7255: 20 KB/sec 2 KB/sec 32 KB/sec 500
Port: 7255: 26 KB/sec 2 KB/sec 38 KB/sec 500
Port: 7003: 26 KB/sec 2 KB/sec 39 KB/sec 500
Port: 7003: 33 KB/sec 2 KB/sec 45 KB/sec 500
Port: 7202: 29 KB/sec 2 KB/sec 41 KB/sec 500
Port: 7202: 30 KB/sec 2 KB/sec 42 KB/sec 500
Port: 7499: 21 KB/sec 2 KB/sec 32 KB/sec 500
Port: 7499: 23 KB/sec 2 KB/sec 34 KB/sec 500
Port: 80: 30 KB/sec 2 KB/sec 43 KB/sec 500
Idle NIC bandwidth Send: 2 KB/sec Recv: 10 KB/sec
hit return to exit
Eww...RR Tampa Bay...been there done that, I'm afraid.
Anyway, yeah, those numbers are terribad. Might wanna have a talk and make sure they aren't massively throttling your connection.
ROLL TIDE ROLL
Thanks to all who responded.
contacting nettest server..
Local IP: ##.##.##.##
Ping: 68.2 msec
Port: 80: 643 KB/sec 23 KB/sec 697 KB/sec 500
Port: 80: 635 KB/sec 21 KB/sec 684 KB/sec 500
Port: 443: 665 KB/sec 17 KB/sec 713 KB/sec 500
Port: 443: 658 KB/sec 20 KB/sec 709 KB/sec 500
Port: 7255: 716 KB/sec 15 KB/sec 769 KB/sec 500
Port: 7255: 718 KB/sec 24 KB/sec 774 KB/sec 500
Port: 7003: 742 KB/sec 23 KB/sec 809 KB/sec 500
Port: 7003: 670 KB/sec 21 KB/sec 730 KB/sec 500
Port: 7202: 765 KB/sec 25 KB/sec 838 KB/sec 500
Port: 7202: 553 KB/sec 17 KB/sec 602 KB/sec 500
Port: 7499: 790 KB/sec 24 KB/sec 873 KB/sec 500
Port: 7499: 653 KB/sec 22 KB/sec 728 KB/sec 500
Port: 80: 761 KB/sec 24 KB/sec 842 KB/sec 500
Idle NIC bandwidth Send: 2 KB/sec Recv: 3 KB/sec
hit return to exit
Copyright (c) 2009 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 * * * 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
and my nettest
unable to allocate performance buffer
contacting nettest server..
Local IP: 24.78.228.225
Ping: 428.7 msec
Port: 80: 265 KB/sec 0 KB/sec 0 KB/sec 500
Port: 80: 147 KB/sec 0 KB/sec 0 KB/sec 500
Port: 443: 137 KB/sec 0 KB/sec 0 KB/sec 500
Port: 443: 127 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7255: 187 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7255: 420 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7003: 168 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7003: 4 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7202: 76 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7202: 305 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7499: 175 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7499: 142 KB/sec 0 KB/sec 0 KB/sec 500
Port: 80: 479 KB/sec 0 KB/sec 0 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
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.
ROLL TIDE ROLL
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
Trace complete.
contacting nettest server..
Local IP:
Ping: 96.8 msec
Port: 80: 123 KB/sec 0 KB/sec 0 KB/sec 500
Port: 80: 371 KB/sec 0 KB/sec 0 KB/sec 500
Port: 443: 389 KB/sec 0 KB/sec 0 KB/sec 500
Port: 443: 427 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7255: 382 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7255: 446 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7003: 484 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7003: 413 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7202: 496 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7202: 419 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7499: 375 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7499: 403 KB/sec 0 KB/sec 0 KB/sec 500
Port: 80: 368 KB/sec 0 KB/sec 0 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
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
contacting nettest server..
Local IP:
Ping: 176.5 msec
Port: 80: 155 KB/sec 10 KB/sec 167 KB/sec 500
Port: 80: 377 KB/sec 17 KB/sec 399 KB/sec 500
Port: 443: 39 KB/sec 6 KB/sec 131 KB/sec 500
Port: 443: 177 KB/sec 10 KB/sec 196 KB/sec 500
Port: 7255: 474 KB/sec 30 KB/sec 1333 KB/sec 500
Port: 7255: 528 KB/sec 29 KB/sec 556 KB/sec 500
Port: 7003: 109 KB/sec 11 KB/sec 117 KB/sec 500
Port: 7003: 155 KB/sec 11 KB/sec 168 KB/sec 500
Port: 7202: timed out
Port: 7202: 474 KB/sec 20 KB/sec 503 KB/sec 500
Port: 7499: 462 KB/sec 37 KB/sec 1561 KB/sec 500
Port: 7499: 573 KB/sec 24 KB/sec 606 KB/sec 500
Port: 80: 507 KB/sec 15 KB/sec 537 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
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....
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
ROLL TIDE ROLL
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.
ROLL TIDE ROLL
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
Trace complete.
And the nettest:
contacting nettest server..
Local IP: [redacted]
Ping: 90.9 msec
Port: 80: 341 KB/sec 12 KB/sec 359 KB/sec 500
Port: 80: 77 KB/sec 4 KB/sec 83 KB/sec 500
Port: 443: 465 KB/sec 18 KB/sec 490 KB/sec 500
Port: 443: 385 KB/sec 17 KB/sec 406 KB/sec 500
Port: 7255: 302 KB/sec 15 KB/sec 323 KB/sec 500
Port: 7255: 302 KB/sec 15 KB/sec 320 KB/sec 500
Port: 7003: 422 KB/sec 19 KB/sec 448 KB/sec 500
Port: 7003: 114 KB/sec 7 KB/sec 122 KB/sec 500
Port: 7202: 144 KB/sec 7 KB/sec 153 KB/sec 500
Port: 7202: 381 KB/sec 17 KB/sec 408 KB/sec 500
Port: 7499: 123 KB/sec 8 KB/sec 131 KB/sec 500
Port: 7499: 254 KB/sec 8 KB/sec 271 KB/sec 500
Port: 80: 301 KB/sec 15 KB/sec 318 KB/sec 500
Idle NIC bandwidth Send: 2 KB/sec Recv: 3 KB/sec
hit return to exit
Then maybe the STO people can sort their **** out instead of giving us all this hoop-jumping and useless "solutions."
:mad:
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.
Brian
True, but those numbers aren't completely problematic there, except in hop 14. I'll point out, though, that I'd run several traces over a period of time when I posted that commentary and got wildly variable results...but yes, they were in that zone.
ROLL TIDE ROLL