Similiar problems, more rubberbanding than actual disconnects. Started to have it when the winter event was on. Since then it has been happening on and off. Somedays we play fine, others we give up. We are in Las Vegas, I tried the US proxy but it failed. I am using STO through steam. Internet with COX.
tracert results
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
Tracing route to patchserver.crypticstudios.com
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * 8 ms 7 ms 10.67.64.1
3 7 ms 9 ms 7 ms 24-234-16-145.ptp.lvcm.net [24.234.16.145]
4 * 9 ms 9 ms 24-234-6-25.ptp.lvcm.net [24.234.6.25]
5 8 ms * 10 ms 24-234-6-218.ptp.lvcm.net [24.234.6.218]
6 35 ms * 33 ms paltbprj01-ae0.0.rd.pt.cox.net [68.1.0.234]
7 35 ms 35 ms 35 ms dcr2-ge--0-0-292.sanfranciscosfo.savvis.net[208.173.170.1]
8 36 ms 36 ms 57 ms cr1-tenge-0-3-5-0.sanfrancisco.savvis.net [204.70.200.198]
9 100 ms * 97 ms cr2-bundle-pos-1.newyork.savvis.net [204.70.197.34]
10 97 ms 98 ms 97 ms er1-te-2-1.newyorknyd.savvis.net [204.70.196.70]
11 109 ms 107 ms 105 ms msr1-te-0-3-0-0.bos.savvis.net [206.28.97.205]
12 104 ms 103 ms 104 ms 206.28.97.137
13 * 103 ms 103 ms internap.Boston.savvis.net [208.172.51.230]
14 103 ms 104 ms 104 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
15 * 105 ms * cryptic-3.border11.bsn.pnap.net [216.52.61.78]
16 * 104 ms 105 ms 208.95.185.41
Seems to alot of USA people with this problem?
I brief explaination of my results would be great, just so I can tell the wife something (yes she palys too)
Thank you for your time and effort
...
Tracing route to patchserver.crypticstudios.com
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * 8 ms 7 ms 10.67.64.1
3 7 ms 9 ms 7 ms 24-234-16-145.ptp.lvcm.net [24.234.16.145]
4 * 9 ms 9 ms 24-234-6-25.ptp.lvcm.net [24.234.6.25]
5 8 ms * 10 ms 24-234-6-218.ptp.lvcm.net [24.234.6.218]
6 35 ms * 33 ms paltbprj01-ae0.0.rd.pt.cox.net [68.1.0.234]
7 35 ms 35 ms 35 ms dcr2-ge--0-0-292.sanfranciscosfo.savvis.net[208.173.170.1] 8 36 ms 36 ms 57 ms cr1-tenge-0-3-5-0.sanfrancisco.savvis.net [204.70.200.198]
9 100 ms * 97 ms cr2-bundle-pos-1.newyork.savvis.net [204.70.197.34]
10 97 ms 98 ms 97 ms er1-te-2-1.newyorknyd.savvis.net [204.70.196.70]
11 109 ms 107 ms 105 ms msr1-te-0-3-0-0.bos.savvis.net [206.28.97.205]
12 104 ms 103 ms 104 ms 206.28.97.137
13 * 103 ms 103 ms internap.Boston.savvis.net [208.172.51.230]
14 103 ms 104 ms 104 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
15 * 105 ms * cryptic-3.border11.bsn.pnap.net [216.52.61.78]
16 * 104 ms 105 ms 208.95.185.41
...
Issue here appears to be with the savvis.net backbone. Something you can't do anything about, but your ISP (Cox) may be able to address... Get a copy of the Trace Route to a Cox support rep and tell them about your connection issues with the STO Servers...
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 9 ms 1 ms 192.168.1.1
2 * 11 ms 8 ms 73.171.228.1
3 10 ms 11 ms 11 ms te-4-2-ur02.williston.vt.boston.comcast.net [68.
87.183.237]
4 8 ms 7 ms 14 ms po-51-ur01.williston.vt.boston.comcast.net [68.8
7.146.230]
5 25 ms 33 ms 35 ms be-79-ar01.needham.ma.boston.comcast.net [68.85.
162.45]
6 53 ms 46 ms 46 ms he-2-8-0-0-cr01.newyork.ny.ibone.comcast.net [68
.86.93.185]
7 48 ms 45 ms 43 ms pos-1-0-0-0-pe01.111eighthave.ny.ibone.comcast.n
et [68.86.86.42]
8 49 ms 57 ms 62 ms te0-7-0-15.ccr21.jfk07.atlas.cogentco.com [154.5
4.10.97]
9 83 ms 77 ms 49 ms te0-2-0-0.mpd21.jfk02.atlas.cogentco.com [154.54
.80.181]
10 95 ms 93 ms 91 ms te0-2-0-6.ccr22.bos01.atlas.cogentco.com [154.54
.44.58]
11 85 ms 56 ms 87 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
12 62 ms 58 ms 66 ms 38.111.40.114
13 525 ms 57 ms 55 ms 208.95.185.41
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 9 ms 1 ms 192.168.1.1
2 * 11 ms 8 ms 73.171.228.1
3 10 ms 11 ms 11 ms te-4-2-ur02.williston.vt.boston.comcast.net [68.
87.183.237]
4 8 ms 7 ms 14 ms po-51-ur01.williston.vt.boston.comcast.net [68.8
7.146.230]
5 25 ms 33 ms 35 ms be-79-ar01.needham.ma.boston.comcast.net [68.85.
162.45]
6 53 ms 46 ms 46 ms he-2-8-0-0-cr01.newyork.ny.ibone.comcast.net [68
.86.93.185]
7 48 ms 45 ms 43 ms pos-1-0-0-0-pe01.111eighthave.ny.ibone.comcast.n
et [68.86.86.42]
8 49 ms 57 ms 62 ms te0-7-0-15.ccr21.jfk07.atlas.cogentco.com [154.5
4.10.97]
9 83 ms 77 ms 49 ms te0-2-0-0.mpd21.jfk02.atlas.cogentco.com [154.54
.80.181]
10 95 ms 93 ms 91 ms te0-2-0-6.ccr22.bos01.atlas.cogentco.com [154.54
.44.58]
11 85 ms 56 ms 87 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
12 62 ms 58 ms 66 ms 38.111.40.114
13 525 ms 57 ms 55 ms 208.95.185.41
I would hope that last hop is a typo. Otherwise that's the worst lag I've seen to date in this thread. It's one packet, sure, but if that's happening on more than an occasional basis I can see where you're getting lagged....more than a full half second on that one packet....
It's a lot like a bunch of cars on the interstate being stuck behind a little old lady doing twenty miles an hour. Now, that may or not be happening on a constant basis. Judging by the fact that you've said that you have been experiencing this a while now, I'm inclined to believe that would be more than occasional...but what I can't figure out is why. It's been said that there may be some capacity issues going on...and in your case I'm thinking that may be what's going on. I can't think of another reason why there are packets taking that long to reach the patch server otherwise (that final hop on the trace being the destination: patchserver.crypticstudios.com).
Just my opinion. The rest of your numbers look fine.
I would hope that last hop is a typo. Otherwise that's the worst lag I've seen to date in this thread. It's one packet, sure, but if that's happening on more than an occasional basis I can see where you're getting lagged....more than a full half second on that one packet....
It's a lot like a bunch of cars on the interstate being stuck behind a little old lady doing twenty miles an hour. Now, that may or not be happening on a constant basis. Judging by the fact that you've said that you have been experiencing this a while now, I'm inclined to believe that would be more than occasional...but what I can't figure out is why. It's been said that there may be some capacity issues going on...and in your case I'm thinking that may be what's going on. I can't think of another reason why there are packets taking that long to reach the patch server otherwise (that final hop on the trace being the destination: patchserver.crypticstudios.com).
Just my opinion. The rest of your numbers look fine.
This lag has only been like this since the wonderland update. Otherwise it was just rubberbanding issues.
1 3 ms 3 ms 3 ms 192.168.1.254
2 33 ms 25 ms 27 ms 99-153-24-2.lightspeed.secloh.sbcglobal.net [99.
153.24.2]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 29 ms 32 ms 29 ms 12.83.69.25
7 35 ms 34 ms 39 ms cgcil03jt.ip.att.net [12.122.84.53]
8 36 ms 36 ms 35 ms te0-2-0-2.ccr22.ord03.atlas.cogentco.com [154.54
.12.85]
9 37 ms 36 ms 36 ms te0-3-0-1.ccr21.ord01.atlas.cogentco.com [154.54
.29.17]
10 56 ms 54 ms 57 ms te0-0-0-5.ccr22.bos01.atlas.cogentco.com [154.54
.42.254]
11 53 ms 53 ms 54 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
12 55 ms 54 ms * 38.111.40.114
13 54 ms 53 ms 52 ms 208.95.185.41
1 3 ms 3 ms 3 ms 192.168.1.254
2 33 ms 25 ms 27 ms 99-153-24-2.lightspeed.secloh.sbcglobal.net [99.
153.24.2] 3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 29 ms 32 ms 29 ms 12.83.69.25
7 35 ms 34 ms 39 ms cgcil03jt.ip.att.net [12.122.84.53]
8 36 ms 36 ms 35 ms te0-2-0-2.ccr22.ord03.atlas.cogentco.com [154.54
.12.85]
9 37 ms 36 ms 36 ms te0-3-0-1.ccr21.ord01.atlas.cogentco.com [154.54
.29.17]
10 56 ms 54 ms 57 ms te0-0-0-5.ccr22.bos01.atlas.cogentco.com [154.54
.42.254]
11 53 ms 53 ms 54 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4] 12 55 ms 54 ms * 38.111.40.114
13 54 ms 53 ms 52 ms 208.95.185.41
I know im good with the tracert, but what do I do about the nettest?
I have had this problem ever since I started to play Star Trek back in June of 2012
and all I want is to play the game. T_T
Your traceroute is NOT good. The hops I've highlighted in red have completely or partially timed out. From the looks of the trace, they might well be on your ISP's network, early as they are in the route.
Your nettest results...are, to put it mildly, subpar. I'd contact your ISP (guessing from your trace that it's SBC Global) and see what's going on. Would also suggest power cycling your router and modem (allow at least 30 seconds between turning both off and then on).
Your traceroute is NOT good. The hops I've highlighted in red have completely or partially timed out. From the looks of the trace, they might well be on your ISP's network, early as they are in the route.
Your nettest results...are, to put it mildly, subpar. I'd contact your ISP (guessing from your trace that it's SBC Global) and see what's going on. Would also suggest power cycling your router and modem (allow at least 30 seconds between turning both off and then on).
lewstelamon01, if i contact my ISP what would I say exactly (btw my ISP is AT&T)?
lewstelamon01, if i contact my ISP what would I say exactly (btw my ISP is AT&T)?
Also how would I power cycle my router and modem?
Power cycling is just a fancy pants term for "unplug your router and modem from its power supply and then plug them back in".
Anyway, it would probably be best to explain that you're seeing reduced network speeds and provide them with the results of the tests that you've run.
If you're lucky and get a competent tech support rep (one who is genuinely interested in solving your problem rather than how fast they can get you off the line and on to the next person in queue), you can explain that you've run a traceroute because of network issues you're having and it's timing out early in the trace.
However, I'm going to wager that you'll have to explain that to a senior technical support analyst...most Tier I reps, IMO, are the type that will rush to whatever answer will get you off the line....
Its doing it for me every 10-20mins of game play for me:mad:. I've tryed everything on the forum and double checked everything my end and theres not a problem. I've even spoke to my I.S.P and theres nothing wrong there im with virgin media if that helps you out and my test results.
tracing results
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 6 ms 44 ms 7 ms cpc14-sotn9-2-0-gw.15-1.cable.virginmedia.com [86.3.216.1]
2 6 ms 6 ms 9 ms sotn-core-1b-ae4-3865.network.virginmedia.net [80.4.225.233]
3 10 ms 11 ms 12 ms glfd-bb-1b-ae3-0.network.virginmedia.net [212.43.163.153]
4 12 ms 14 ms 11 ms nrth-bb-1a-as5-0.network.virginmedia.net [212.43.163.182]
5 14 ms 12 ms 14 ms nrth-tmr-1-ae1-0.network.virginmedia.net [213.105.159.30]
6 27 ms 28 ms 27 ms fran-ic-1-as0-0.network.virginmedia.net [62.253.185.81]
7 30 ms 28 ms 28 ms te0-7-0-7.mpd22.fra03.atlas.cogentco.com [130.117.14.133]
8 27 ms 30 ms 29 ms te0-2-0-2.mpd22.ams03.atlas.cogentco.com [130.117.3.85]
9 35 ms 34 ms 33 ms te0-1-0-2.ccr22.lpl01.atlas.cogentco.com [154.54.37.110]
10 101 ms 103 ms 100 ms te0-5-0-4.ccr22.bos01.atlas.cogentco.com [154.54.85.217]
11 224 ms 109 ms 445 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
12 108 ms 105 ms 107 ms 38.111.40.114
13 102 ms 99 ms 99 ms 208.95.185.41
i changed over to use a cryptic proxy, and has fixed the lag, but still getting rubberbanding. although i havent stayed on longer then what it takes to finish the race daily.
Thank you for explaining my results. However, I seem to have gone almost a week without any major or minor issues. I still get the very occasional rubberband but I back to playing happily again. Might have lost a few fleet marks and some snow eppohs but all is well. Happy new year
I have recently came back to the game after about 8 months. Now I have the same issue described above. I can stay logged in for about 20 minutes and then I get disconnected. I have tried:
disabling on demand patching
tried both the US & EU proxies
made sure all my network related drivers are updated
What is also bizarre is that sometimes the issue seems to be that my wifi internet connection is dropped completely. This appears to be the only piece of software that is causing this issue and it was not a problem when I played 8 months ago.
...
What is also bizarre is that sometimes the issue seems to be that my wifi internet connection is dropped completely. This appears to be the only piece of software that is causing this issue and it was not a problem when I played 8 months ago.
This sounds like you're wireless router is getting overwhelmed by the number of simultaneous open network connections... (a issue that STO is known to have compared to most other MMRPG games...) Have you tried a direct cable connection to the router? Besides shutting down all other background network tasks, try disabling the built in Voice Chat in the STO Client...
I've been moaning about this in other sections and didn't see this thread here until mine was moved into this section... lol... should have looked hey!?!?! Anyway I'm glad the issue seems widespread so at least its not because of geographical location etc. (tho I'm sure it doesnt help).
Here's my tracert to patchserver.crypticstudios.com
1 <1 ms <1 ms <1 ms
2 1 ms 1 ms 1 ms
3 17 ms 16 ms 16 ms nexthop.qld.iinet.net.au [203.215.9.250]
4 17 ms 16 ms 17 ms te7-1.bne-pipe-bdr2.iinet.net.au [203.215.8.22]
5 29 ms 31 ms 29 ms xe-0-0-3-0.syd-mas-core1.iinet.net.au [203.215.20.108]
6 30 ms 30 ms 29 ms 32433.chep02.cu.telstraglobal.net [134.159.130.105]
7 29 ms 29 ms 29 ms i-0-6-1-0.sydp-core01.bi.telstraglobal.net [202.84.223.9]
8 181 ms 181 ms 181 ms i-0-5-0-0.1wlt-core01.bx.telstraglobal.net [202.84.140.185]
9 178 ms 177 ms 177 ms i-0-4-0-1.eqla01.bi.telstraglobal.net [202.84.251.154]
10 189 ms 183 ms 183 ms cogent-peer.eqla01.pr.telstraglobal.net [134.159.63.198]
11 177 ms 178 ms 177 ms te0-1-0-5.mpd21.lax01.atlas.cogentco.com [154.54.82.157]
12 213 ms 214 ms 213 ms te0-1-0-3.ccr21.iah01.atlas.cogentco.com [154.54.44.237]
13 228 ms 228 ms 229 ms te0-0-0-7.mpd21.atl01.atlas.cogentco.com [154.54.28.253]
14 239 ms 240 ms 239 ms te0-3-0-2.mpd21.dca01.atlas.cogentco.com [154.54.28.17]
15 245 ms 245 ms 245 ms te0-0-0-2.mpd21.jfk02.atlas.cogentco.com [154.54.41.18]
16 295 ms 278 ms 279 ms te0-1-0-2.ccr22.bos01.atlas.cogentco.com [154.54.44.38]
17 291 ms 280 ms 294 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
18 295 ms 301 ms 305 ms 38.111.40.114
19 296 ms 295 ms 296 ms 208.95.185.41
No anti-virus or firewall programs active & have been playing this game on this connection for the last 9 months without issue until the holidays started.
I've been moaning about this in other sections and didn't see this thread here until mine was moved into this section... lol... should have looked hey!?!?! Anyway I'm glad the issue seems widespread so at least its not because of geographical location etc. (tho I'm sure it doesnt help).
Here's my tracert to patchserver.crypticstudios.com
1 <1 ms <1 ms <1 ms
2 1 ms 1 ms 1 ms
3 17 ms 16 ms 16 ms nexthop.qld.iinet.net.au [203.215.9.250]
4 17 ms 16 ms 17 ms te7-1.bne-pipe-bdr2.iinet.net.au [203.215.8.22]
5 29 ms 31 ms 29 ms xe-0-0-3-0.syd-mas-core1.iinet.net.au [203.215.20.108]
6 30 ms 30 ms 29 ms 32433.chep02.cu.telstraglobal.net [134.159.130.105]
7 29 ms 29 ms 29 ms i-0-6-1-0.sydp-core01.bi.telstraglobal.net [202.84.223.9] 8 181 ms 181 ms 181 ms i-0-5-0-0.1wlt-core01.bx.telstraglobal.net [202.84.140.185]
9 178 ms 177 ms 177 ms i-0-4-0-1.eqla01.bi.telstraglobal.net [202.84.251.154]
10 189 ms 183 ms 183 ms cogent-peer.eqla01.pr.telstraglobal.net [134.159.63.198]
11 177 ms 178 ms 177 ms te0-1-0-5.mpd21.lax01.atlas.cogentco.com [154.54.82.157]
12 213 ms 214 ms 213 ms te0-1-0-3.ccr21.iah01.atlas.cogentco.com [154.54.44.237]
13 228 ms 228 ms 229 ms te0-0-0-7.mpd21.atl01.atlas.cogentco.com [154.54.28.253]
14 239 ms 240 ms 239 ms te0-3-0-2.mpd21.dca01.atlas.cogentco.com [154.54.28.17]
15 245 ms 245 ms 245 ms te0-0-0-2.mpd21.jfk02.atlas.cogentco.com [154.54.41.18]
16 295 ms 278 ms 279 ms te0-1-0-2.ccr22.bos01.atlas.cogentco.com [154.54.44.38]
17 291 ms 280 ms 294 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
18 295 ms 301 ms 305 ms 38.111.40.114
19 296 ms 295 ms 296 ms 208.95.185.41
No anti-virus or firewall programs active & have been playing this game on this connection for the last 9 months without issue until the holidays started.
Provider: iinet Australia.
Your traceroute looks like hell, the highlighted numbers are all well over the problematic level (150 and above)
Your nettest is a complete hash. Optimal numbers are 200 or better for the first and third columns and 20 or better for the middle one. Some ports are timing out entirely. (which could be a firewall issue or your router isn't putting anything out of those ports at all).
A call to your ISP may be in order, or at the very least a reset of your modem. Router could be problematic too. (assuming both aren't one and the same).
Comments
tracert results
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * 8 ms 7 ms 10.67.64.1
3 7 ms 9 ms 7 ms 24-234-16-145.ptp.lvcm.net [24.234.16.145]
4 * 9 ms 9 ms 24-234-6-25.ptp.lvcm.net [24.234.6.25]
5 8 ms * 10 ms 24-234-6-218.ptp.lvcm.net [24.234.6.218]
6 35 ms * 33 ms paltbprj01-ae0.0.rd.pt.cox.net [68.1.0.234]
7 35 ms 35 ms 35 ms dcr2-ge--0-0-292.sanfranciscosfo.savvis.net[208.173.170.1]
8 36 ms 36 ms 57 ms cr1-tenge-0-3-5-0.sanfrancisco.savvis.net [204.70.200.198]
9 100 ms * 97 ms cr2-bundle-pos-1.newyork.savvis.net [204.70.197.34]
10 97 ms 98 ms 97 ms er1-te-2-1.newyorknyd.savvis.net [204.70.196.70]
11 109 ms 107 ms 105 ms msr1-te-0-3-0-0.bos.savvis.net [206.28.97.205]
12 104 ms 103 ms 104 ms 206.28.97.137
13 * 103 ms 103 ms internap.Boston.savvis.net [208.172.51.230]
14 103 ms 104 ms 104 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
15 * 105 ms * cryptic-3.border11.bsn.pnap.net [216.52.61.78]
16 * 104 ms 105 ms 208.95.185.41
net test
contacting nettest server..
Ping: 107.2 msec
Port: 80: 452 KB/sec 17 KB/sec 477 KB/sec 500
Port: 80: 227 KB/sec 8 KB/sec 240 KB/sec 500
Port: 443: 400 KB/sec 14 KB/sec 421 KB/sec 500
Port: 443: 426 KB/sec 15 KB/sec 449 KB/sec 500
Port: 7255: 422 KB/sec 15 KB/sec 444 KB/sec 500
Port: 7255: 243 KB/sec 9 KB/sec 256 KB/sec 500
Port: 7003: 425 KB/sec 15 KB/sec 447 KB/sec 500
Port: 7003: 347 KB/sec 13 KB/sec 367 KB/sec 500
Port: 7202: 304 KB/sec 11 KB/sec 320 KB/sec 500
Port: 7202: 245 KB/sec 9 KB/sec 261 KB/sec 500
Port: 7499: 264 KB/sec 10 KB/sec 279 KB/sec 500
Port: 7499: 209 KB/sec 8 KB/sec 221 KB/sec 500
Port: 80: 387 KB/sec 17 KB/sec 408 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
Seems to alot of USA people with this problem?
I brief explaination of my results would be great, just so I can tell the wife something (yes she palys too)
Thank you for your time and effort
Issue here appears to be with the savvis.net backbone. Something you can't do anything about, but your ISP (Cox) may be able to address... Get a copy of the Trace Route to a Cox support rep and tell them about your connection issues with the STO Servers...
over a maximum of 30 hops:
1 1 ms 9 ms 1 ms 192.168.1.1
2 * 11 ms 8 ms 73.171.228.1
3 10 ms 11 ms 11 ms te-4-2-ur02.williston.vt.boston.comcast.net [68.
87.183.237]
4 8 ms 7 ms 14 ms po-51-ur01.williston.vt.boston.comcast.net [68.8
7.146.230]
5 25 ms 33 ms 35 ms be-79-ar01.needham.ma.boston.comcast.net [68.85.
162.45]
6 53 ms 46 ms 46 ms he-2-8-0-0-cr01.newyork.ny.ibone.comcast.net [68
.86.93.185]
7 48 ms 45 ms 43 ms pos-1-0-0-0-pe01.111eighthave.ny.ibone.comcast.n
et [68.86.86.42]
8 49 ms 57 ms 62 ms te0-7-0-15.ccr21.jfk07.atlas.cogentco.com [154.5
4.10.97]
9 83 ms 77 ms 49 ms te0-2-0-0.mpd21.jfk02.atlas.cogentco.com [154.54
.80.181]
10 95 ms 93 ms 91 ms te0-2-0-6.ccr22.bos01.atlas.cogentco.com [154.54
.44.58]
11 85 ms 56 ms 87 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
12 62 ms 58 ms 66 ms 38.111.40.114
13 525 ms 57 ms 55 ms 208.95.185.41
Port: 80: 760 KB/sec 24 KB/sec 805 KB/sec 500
Port: 80: 465 KB/sec 16 KB/sec 497 KB/sec 500
Port: 443: 874 KB/sec 28 KB/sec 928 KB/sec 500
Port: 443: 144 KB/sec 7 KB/sec 159 KB/sec 500
Port: 7255: 912 KB/sec 29 KB/sec 967 KB/sec 500
Port: 7255: 536 KB/sec 20 KB/sec 576 KB/sec 500
Port: 7003: 809 KB/sec 25 KB/sec 858 KB/sec 500
Port: 7003: 613 KB/sec 20 KB/sec 650 KB/sec 500
Port: 7202: 433 KB/sec 17 KB/sec 462 KB/sec 500
Port: 7202: 928 KB/sec 29 KB/sec 983 KB/sec 500
Port: 7499: 909 KB/sec 27 KB/sec 963 KB/sec 500
Port: 7499: 571 KB/sec 18 KB/sec 605 KB/sec 500
Port: 80: 580 KB/sec 19 KB/sec 616 KB/sec 500
Idle NIC bandwidth Send: 2 KB/sec Recv: 5 KB/sec
I would hope that last hop is a typo. Otherwise that's the worst lag I've seen to date in this thread. It's one packet, sure, but if that's happening on more than an occasional basis I can see where you're getting lagged....more than a full half second on that one packet....
It's a lot like a bunch of cars on the interstate being stuck behind a little old lady doing twenty miles an hour. Now, that may or not be happening on a constant basis. Judging by the fact that you've said that you have been experiencing this a while now, I'm inclined to believe that would be more than occasional...but what I can't figure out is why. It's been said that there may be some capacity issues going on...and in your case I'm thinking that may be what's going on. I can't think of another reason why there are packets taking that long to reach the patch server otherwise (that final hop on the trace being the destination: patchserver.crypticstudios.com).
Just my opinion. The rest of your numbers look fine.
ROLL TIDE ROLL
This lag has only been like this since the wonderland update. Otherwise it was just rubberbanding issues.
1 3 ms 3 ms 3 ms 192.168.1.254
2 33 ms 25 ms 27 ms 99-153-24-2.lightspeed.secloh.sbcglobal.net [99.
153.24.2]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 29 ms 32 ms 29 ms 12.83.69.25
7 35 ms 34 ms 39 ms cgcil03jt.ip.att.net [12.122.84.53]
8 36 ms 36 ms 35 ms te0-2-0-2.ccr22.ord03.atlas.cogentco.com [154.54
.12.85]
9 37 ms 36 ms 36 ms te0-3-0-1.ccr21.ord01.atlas.cogentco.com [154.54
.29.17]
10 56 ms 54 ms 57 ms te0-0-0-5.ccr22.bos01.atlas.cogentco.com [154.54
.42.254]
11 53 ms 53 ms 54 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
12 55 ms 54 ms * 38.111.40.114
13 54 ms 53 ms 52 ms 208.95.185.41
Trace complete.
Ping: 63.8 msec
Port: 80: 19 KB/sec 2 KB/sec 28 KB/sec 500
Port: 80: 21 KB/sec 2 KB/sec 23 KB/sec 500
Port: 443: 18 KB/sec 2 KB/sec 20 KB/sec 500
Port: 443: 19 KB/sec 2 KB/sec 21 KB/sec 500
Port: 7255: 15 KB/sec 2 KB/sec 16 KB/sec 500
Port: 7255: 19 KB/sec 2 KB/sec 21 KB/sec 500
Port: 7003: 21 KB/sec 2 KB/sec 23 KB/sec 500
Port: 7003: 22 KB/sec 3 KB/sec 25 KB/sec 500
Port: 7202: 19 KB/sec 2 KB/sec 21 KB/sec 500
Port: 7202: 18 KB/sec 2 KB/sec 20 KB/sec 500
Port: 7499: 6 KB/sec 8 KB/sec 7 KB/sec 500
Port: 7499: 16 KB/sec 5 KB/sec 18 KB/sec 500
Port: 80: 19 KB/sec 6 KB/sec 28 KB/sec 500
Idle NIC bandwidth Send: 1 KB/sec Recv: 0 KB/sec
I know im good with the tracert, but what do I do about the nettest?
I have had this problem ever since I started to play Star Trek back in June of 2012
and all I want is to play the game. T_T
Your traceroute is NOT good. The hops I've highlighted in red have completely or partially timed out. From the looks of the trace, they might well be on your ISP's network, early as they are in the route.
Your nettest results...are, to put it mildly, subpar. I'd contact your ISP (guessing from your trace that it's SBC Global) and see what's going on. Would also suggest power cycling your router and modem (allow at least 30 seconds between turning both off and then on).
ROLL TIDE ROLL
lewstelamon01, if i contact my ISP what would I say exactly (btw my ISP is AT&T)?
Also how would I power cycle my router and modem?
Power cycling is just a fancy pants term for "unplug your router and modem from its power supply and then plug them back in".
Anyway, it would probably be best to explain that you're seeing reduced network speeds and provide them with the results of the tests that you've run.
If you're lucky and get a competent tech support rep (one who is genuinely interested in solving your problem rather than how fast they can get you off the line and on to the next person in queue), you can explain that you've run a traceroute because of network issues you're having and it's timing out early in the trace.
However, I'm going to wager that you'll have to explain that to a senior technical support analyst...most Tier I reps, IMO, are the type that will rush to whatever answer will get you off the line....
ROLL TIDE ROLL
tracing results
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 6 ms 44 ms 7 ms cpc14-sotn9-2-0-gw.15-1.cable.virginmedia.com [86.3.216.1]
2 6 ms 6 ms 9 ms sotn-core-1b-ae4-3865.network.virginmedia.net [80.4.225.233]
3 10 ms 11 ms 12 ms glfd-bb-1b-ae3-0.network.virginmedia.net [212.43.163.153]
4 12 ms 14 ms 11 ms nrth-bb-1a-as5-0.network.virginmedia.net [212.43.163.182]
5 14 ms 12 ms 14 ms nrth-tmr-1-ae1-0.network.virginmedia.net [213.105.159.30]
6 27 ms 28 ms 27 ms fran-ic-1-as0-0.network.virginmedia.net [62.253.185.81]
7 30 ms 28 ms 28 ms te0-7-0-7.mpd22.fra03.atlas.cogentco.com [130.117.14.133]
8 27 ms 30 ms 29 ms te0-2-0-2.mpd22.ams03.atlas.cogentco.com [130.117.3.85]
9 35 ms 34 ms 33 ms te0-1-0-2.ccr22.lpl01.atlas.cogentco.com [154.54.37.110]
10 101 ms 103 ms 100 ms te0-5-0-4.ccr22.bos01.atlas.cogentco.com [154.54.85.217]
11 224 ms 109 ms 445 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
12 108 ms 105 ms 107 ms 38.111.40.114
13 102 ms 99 ms 99 ms 208.95.185.41
Trace complete.
NETTEST RESULTS
Local IP: ............
Ping: 91.2 msec
Port: 80: 503 KB/sec 18 KB/sec 531 KB/sec 500
Port: 80: 505 KB/sec 18 KB/sec 532 KB/sec 500
Port: 443: 507 KB/sec 18 KB/sec 535 KB/sec 500
Port: 443: 510 KB/sec 19 KB/sec 539 KB/sec 500
Port: 7255: 508 KB/sec 18 KB/sec 537 KB/sec 500
Port: 7255: 508 KB/sec 17 KB/sec 538 KB/sec 500
Port: 7003: 507 KB/sec 16 KB/sec 536 KB/sec 500
Port: 7003: 488 KB/sec 18 KB/sec 515 KB/sec 500
Port: 7202: 494 KB/sec 18 KB/sec 522 KB/sec 500
Port: 7202: 492 KB/sec 16 KB/sec 519 KB/sec 500
Port: 7499: 484 KB/sec 18 KB/sec 512 KB/sec 500
Port: 7499: 507 KB/sec 19 KB/sec 536 KB/sec 500
Port: 80: 509 KB/sec 18 KB/sec 537 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
oh yeah just pointing out im british so its not just a problem hitting america
What is also bizarre is that sometimes the issue seems to be that my wifi internet connection is dropped completely. This appears to be the only piece of software that is causing this issue and it was not a problem when I played 8 months ago.
Here's my tracert to patchserver.crypticstudios.com
1 <1 ms <1 ms <1 ms
2 1 ms 1 ms 1 ms
3 17 ms 16 ms 16 ms nexthop.qld.iinet.net.au [203.215.9.250]
4 17 ms 16 ms 17 ms te7-1.bne-pipe-bdr2.iinet.net.au [203.215.8.22]
5 29 ms 31 ms 29 ms xe-0-0-3-0.syd-mas-core1.iinet.net.au [203.215.20.108]
6 30 ms 30 ms 29 ms 32433.chep02.cu.telstraglobal.net [134.159.130.105]
7 29 ms 29 ms 29 ms i-0-6-1-0.sydp-core01.bi.telstraglobal.net [202.84.223.9]
8 181 ms 181 ms 181 ms i-0-5-0-0.1wlt-core01.bx.telstraglobal.net [202.84.140.185]
9 178 ms 177 ms 177 ms i-0-4-0-1.eqla01.bi.telstraglobal.net [202.84.251.154]
10 189 ms 183 ms 183 ms cogent-peer.eqla01.pr.telstraglobal.net [134.159.63.198]
11 177 ms 178 ms 177 ms te0-1-0-5.mpd21.lax01.atlas.cogentco.com [154.54.82.157]
12 213 ms 214 ms 213 ms te0-1-0-3.ccr21.iah01.atlas.cogentco.com [154.54.44.237]
13 228 ms 228 ms 229 ms te0-0-0-7.mpd21.atl01.atlas.cogentco.com [154.54.28.253]
14 239 ms 240 ms 239 ms te0-3-0-2.mpd21.dca01.atlas.cogentco.com [154.54.28.17]
15 245 ms 245 ms 245 ms te0-0-0-2.mpd21.jfk02.atlas.cogentco.com [154.54.41.18]
16 295 ms 278 ms 279 ms te0-1-0-2.ccr22.bos01.atlas.cogentco.com [154.54.44.38]
17 291 ms 280 ms 294 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
18 295 ms 301 ms 305 ms 38.111.40.114
19 296 ms 295 ms 296 ms 208.95.185.41
Nettest results:
Ping: 273.0 msec
Port: 80: 241 KB/sec 9 KB/sec 255 KB/sec 500
Port: 80: 228 KB/sec 9 KB/sec 241 KB/sec 500
Port: 443: 222 KB/sec 9 KB/sec 236 KB/sec 500
Port: 443: 230 KB/sec 9 KB/sec 245 KB/sec 500
Port: 7255: 4 KB/sec 2 KB/sec 10 KB/sec 500
Port: 7255: timed out
Port: 7003: 4 KB/sec 2 KB/sec 9 KB/sec 500
Port: 7003: timed out
Port: 7202: 5 KB/sec 2 KB/sec 9 KB/sec 500
Port: 7202: timed out
Port: 7499: timed out
Port: 7499: 3 KB/sec 3 KB/sec 21 KB/sec 500
Port: 80: 235 KB/sec 10 KB/sec 250 KB/sec 500
Idle NIC bandwidth Send: 2 KB/sec Recv: 6 KB/sec
No anti-virus or firewall programs active & have been playing this game on this connection for the last 9 months without issue until the holidays started.
Provider: iinet Australia.
Your traceroute looks like hell, the highlighted numbers are all well over the problematic level (150 and above)
Your nettest is a complete hash. Optimal numbers are 200 or better for the first and third columns and 20 or better for the middle one. Some ports are timing out entirely. (which could be a firewall issue or your router isn't putting anything out of those ports at all).
A call to your ISP may be in order, or at the very least a reset of your modem. Router could be problematic too. (assuming both aren't one and the same).
Try one of the proxies as well. That might help.
ROLL TIDE ROLL
Ping: 230.8 msec
Port: 80: 271 KB/sec 10 KB/sec 287 KB/sec 500
Port: 80: 280 KB/sec 11 KB/sec 296 KB/sec 500
Port: 443: 272 KB/sec 11 KB/sec 290 KB/sec 500
Port: 443: 79 KB/sec 4 KB/sec 84 KB/sec 500
Port: 7255: 258 KB/sec 10 KB/sec 273 KB/sec 500
Port: 7255: 274 KB/sec 11 KB/sec 290 KB/sec 500
Port: 7003: 264 KB/sec 10 KB/sec 279 KB/sec 500
Port: 7003: 279 KB/sec 11 KB/sec 296 KB/sec 500
Port: 7202: 274 KB/sec 10 KB/sec 290 KB/sec 500
Port: 7202: 249 KB/sec 9 KB/sec 264 KB/sec 500
Port: 7499: 275 KB/sec 10 KB/sec 291 KB/sec 500
Port: 7499: 271 KB/sec 10 KB/sec 289 KB/sec 500
Port: 80: 264 KB/sec 10 KB/sec 279 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
Game working perfectly fine at the moment & tracert report looks basically like the previous one posted.
Will have a word to my ISP...