Now I connect from the Silicon Valley using Comcast, and was suffering from severe lag and server connection issues since last friday. As a temporary solution, I've found that setting the STO Client to use the US Proxy has greatly reduced the lag issue, enough so that once again STO is playable....
(Though the fact that using the US Proxy improves the issue shows that there is a serious peering issue between Comcast and Cogent Communications that needs to be addressed)
Same, except that I'm in Sacramento. But I'm also using Comcast, and once I set it to use the US proxy the game became playable again, I haven't had any appreciable lag/rubberbanding/crashes since.
For all you other NorCal Comcast people, I have had success with using the US proxy setting in the launcher options as a workaround for now. I set it up yesterday and haven't had any appreciable lag/rubberbanding/crashing since.
Glad to see this thread; I am having the same problems as everyone here (with Comcast in the Bay Area as well). These problems started after the latest patch (12/6/12) and has made playing a living hell. I had no lag issues till then.
I will definitely try the US proxy setting in the launcher and see if this alleviates the problem. Thanks for the suggestion.
Since the Season 7 patch the game has been unplayable for me. I am also in NorCal and have Xfinity internet. Other games run fine. Has anyone from Cryptic addressed the issue aside from telling us to ping their servers?
Now I connect from the Silicon Valley using Comcast, and was suffering from severe lag and server connection issues since last friday. As a temporary solution, I've found that setting the STO Client to use the US Proxy has greatly reduced the lag issue, enough so that once again STO is playable....
(Though the fact that using the US Proxy improves the issue shows that there is a serious peering issue between Comcast and Cogent Communications that needs to be addressed)
Thanks, it's working better, but still kinda laggy. It's a playable game! Small victories.
Since the Season 7 patch the game has been unplayable for me. I am also in NorCal and have Xfinity internet. Other games run fine. Has anyone from Cryptic addressed the issue aside from telling us to ping their servers?
They "address" it by blaming everyone but themselves. :rolleyes:
im in the Ca bay area and im getting the same thing, is was ok at 1st but over the past 2 days i cant even play and when i do log in i cant even log out... im hoping its just a patch thing that will be fixed but that means no free ship for me
0
isomorphismMember, Cryptic DevelopersPosts: 0Arc User
edited December 2012
Cryptic and PWE can confirm that this issue is occurring, and it is being investigated by our technical personnel to try to track down where the problem is. It's not yet clear if this is an issue on Cryptic's side, Comcast's side, or some intermediate provider.
To restate what other people said in the thread, traffic sourced from Comcast in California to our Boston data center seems to be afflicted by some network issue that causes intermittent gameplay glitches.
I really appreciate you guys taking the time to come to the forums and report this issue, and I'm sorry that you're having this disruption. I hope that we can offer some sort of resolution soon, but it may become the case that this is an issue outside of our immediate control; in that case, we'll have to decide what we can do.
In the near term, enabling one of the proxy settings in the Launcher may temporarily improve the gameplay experience. Note that you don't usually want to use proxies once the issue has been resolved, since they tend to be somewhat slower than connecting directly to our servers.
I too have been having disconnection and time out problems.
Sounds Like you guys know about the problem already. If it helps, I'm playing from Australia.
Will try the proxy thing in options tonight and see how it goes.
How will we know when to turn proxy off?
I'm in southern California and don't use Comcast and I'm having all kinds of lagging and disconnect issues. I tried the proxy server thing and it got much worse. I didn't make it 15 seconds before I got kicked off.
Just to follow up. Switching on the US proxy option in the launcher seems to have helped things for me. Occasionally still lags, but is far less problematic.
Many of my fleet members from around the world have all been commenting on connectivity issues.. Most off which probably do not have Comcast, although I do and will be checking the proxy settings to see if I don't get disconnected ever 5-10 minutes..
0
isomorphismMember, Cryptic DevelopersPosts: 0Arc User
edited December 2012
At approximately 1 AM PST today (9 AM UTC December 12, 2012), Cryptic made a routing change that may work around this issue.
Our networking experts have done some analysis and, while the source of the Internet connectivity disruption is not known, they have made a change to route affected traffic by a different path. Our internal tests confirm that this resolves the issue for all cases we have access to.
For all individuals who were affected, we recommend checking again at this time if you are still experiencing disruption. Please disable any proxy, if you have enabled (in the Launcher) it to work around this issue; using the proxy unnecessarily may cause suboptimal performance.
I empathsize with anyone who has experienced this very disruptive issue. We really appreciate the help of everyone who has taken the time to report this issue.
We would very much appreciate any reports from customers who experienced this issue saying that their issue has been resolved.
For anyone still experiencing this issue, a report with the following information would also be very helpful:
1. Date and time that the problem began occurring, as precisely as you can tell (with time zone)
2. A quick description of exactly what sort of problem you observe (lag, rubberbanding, disconnects, etc), and when it occurs (beaming up, logging in, sitting on Earth spacedock, etc.)
3. If you have tried using a proxy in the Launcher, and if so, if it made things better.
4. Optional but helpful: The output of tracert to nettest.crypticstudios.com and the Cryptic 'nettest' program.
1. Today at 8:20-8:28
2. Go to Qs wonderland for daily and snowball digging. Lag rubberbanding server not responding. got Dc'd 5 times in a row.
3.Dont use proxy
so is there any reason why this is the only online game i play that lags to hell and back?
Cryptic and PWE can confirm that this issue is occurring, and it is being investigated by our technical personnel to try to track down where the problem is. It's not yet clear if this is an issue on Cryptic's side, Comcast's side, or some intermediate provider.
To restate what other people said in the thread, traffic sourced from Comcast in California to our Boston data center seems to be afflicted by some network issue that causes intermittent gameplay glitches.
I really appreciate you guys taking the time to come to the forums and report this issue, and I'm sorry that you're having this disruption. I hope that we can offer some sort of resolution soon, but it may become the case that this is an issue outside of our immediate control; in that case, we'll have to decide what we can do.
In the near term, enabling one of the proxy settings in the Launcher may temporarily improve the gameplay experience. Note that you don't usually want to use proxies once the issue has been resolved, since they tend to be somewhat slower than connecting directly to our servers.
Is Comcast a service Cryptic uses to connect players? I use Cox Communication in southern California and I am still having the lagging issues. I have started using the proxy as a temprorary measure and it helps but does not fix the issue.
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 be the area where the problem really takes over. I also would like to note that I had no latency issues prior to the season 7 release.
Bay Area Comcast user here. Issue does not appear to be resolved for me, though it does not seem quite as bad as Friday and Saturday. Still rubberbanding and disconnect this morning. Still gets better stability/performance when using the proxy though.
1. Issue began last Friday. Despite popular belief I'm not actually constantly on STO to know exactly when this started
2. Rubberband and disconnects are the most common symptoms. Also, occasionally the entire interface is unresponsive (you can click buttons, but they don't work, not even Logout). Some instance servers behave better than others. Switching zones or characters may trigger the use of one of these problematic servers. Pinging the server specifically (using the log data from clientservercomm.log) reports about 10% packet loss, occurring in bursts. This does not occur when using a properly functional route.
3. Using the Cryptic US proxy works around the issue. Similarly, using my corporate VPN based out of Dallas, TX also works around the issue.
4.
$ tracert nettest.crypticstudios.com
Tracing route to nettest.crypticstudios.com [208.95.184.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms sthelena [10.0.1.1]
2 28 ms 30 ms 29 ms 50.131.236.1
3 42 ms 9 ms 9 ms te-5-8-ur04.pinole.ca.sfba.comcast.net [68.85.100.69]
4 20 ms 11 ms 23 ms te-0-2-0-13-ar01.oakland.ca.sfba.comcast.net [68.86.143.38]
5 21 ms 23 ms 23 ms he-2-15-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.91.225]
6 16 ms 19 ms 19 ms pos-0-9-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.85.181]
7 17 ms 17 ms 16 ms pos-0-7-0-0-pe01.529bryant.ca.ibone.comcast.net [68.86.88.202]
8 16 ms 16 ms 17 ms te0-0-0-12.ccr21.sjc04.atlas.cogentco.com [154.54.13.17]
9 17 ms 18 ms 16 ms te0-0-0-6.mpd21.sfo01.atlas.cogentco.com [154.54.2.165]
10 60 ms 59 ms 61 ms te0-3-0-1.ccr22.mci01.atlas.cogentco.com [154.54.6.41]
11 72 ms 73 ms 71 ms te0-4-0-3.ccr21.ord01.atlas.cogentco.com [154.54.6.157]
12 97 ms 95 ms 96 ms te0-5-0-6.ccr22.bos01.atlas.cogentco.com [154.54.45.242]
13 94 ms 95 ms 95 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
14 95 ms 108 ms 107 ms 38.111.40.114
15 104 ms 95 ms 97 ms nettest.crypticstudios.com [208.95.184.10]
We would very much appreciate any reports from customers who experienced this issue saying that their issue has been resolved.
For anyone still experiencing this issue, a report with the following information would also be very helpful:
1. Date and time that the problem began occurring, as precisely as you can tell (with time zone)
2. A quick description of exactly what sort of problem you observe (lag, rubberbanding, disconnects, etc), and when it occurs (beaming up, logging in, sitting on Earth spacedock, etc.)
3. If you have tried using a proxy in the Launcher, and if so, if it made things better.
4. Optional but helpful: The output of tracert to nettest.crypticstudios.com and the Cryptic 'nettest' program.
I'd have to say that the problems have been reduced, but not completely resolved.
Without the US Proxy Setting, I'm experiencing some rubber-banding at ESD, Sol System, and Q's Winter Wonderland. I'm also still having issues with the Doff Assignment menus being populated, and claiming 'complete' on the finished ones. At least I no longer have the issue of being a bodiless entity stuck on the transporter pad waiting to beam in...
Starting having some connection issues on the 6th of this month, but got very bad on the morning of the 7th, through out the weekend. Started using the US Proxy on the 9th (which has some minor rubber-banding)
This mornings Trace route output...
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 25 ms 20 ms 30 ms 76.21.124.1
2 10 ms 9 ms 9 ms te-0-0-0-1-ur13.sanjose.ca.sfba.comcast.net [68.85.190.217]
3 23 ms 12 ms 11 ms te-1-13-0-1-ar01.sfsutro.ca.sfba.comcast.net [69.139.198.66]
4 17 ms 23 ms 23 ms he-1-6-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.90.157]
5 14 ms 14 ms 13 ms pos-0-1-0-0-pe01.529bryant.ca.ibone.comcast.net [68.86.87.2]
6 14 ms 13 ms 15 ms te0-7-0-12.ccr21.sjc04.atlas.cogentco.com [154.54.11.109]
7 13 ms 14 ms 14 ms te0-1-0-7.ccr21.sfo01.atlas.cogentco.com [154.54.5.113]
8 57 ms 57 ms 56 ms te0-1-0-2.ccr22.mci01.atlas.cogentco.com [154.54.30.70] 9 71 ms 69 ms 69 ms te0-3-0-7.ccr21.ord01.atlas.cogentco.com [154.54.84.74]
10 92 ms 93 ms 110 ms te0-1-0-6.ccr22.bos01.atlas.cogentco.com [154.54.43.206]
11 130 ms 100 ms 92 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
12 94 ms 93 ms 102 ms 38.111.40.114
13 91 ms 98 ms 92 ms 208.95.185.41
Add my voice to all the rest. Using Comcast Xfinity Extreme 50 out of SF Bay Area (Alameda). Since Winter Wonderland, I am getting terrible intermittent lag, causing rubber banding, game to freeze up, disconnects, etc. Seems worse (often begins) immediately after switching back to game window after checking another window. ISP connection tests as perfect. Graphics drivers are up-to-date. Repeated verifying of game files and re-installing game did not help.
So far getting really good performance with US proxy server option set. Either that option did it, something else changed, or it was some temporary fluke and the lag will return -- but the feel is good so far.
As far as the Northern California Comcast/Cogent Communication issue is concerned, after this mornings patch, I disabled the US Proxy Setting to see if the issue has resolved, and apparently it has. Other then the slow (but steady) loading of some of the Foundry scenes, (which is probably unrelated...) I have not encountered any issues.
Other Northern California Comcast users should disable the use of the US Proxy setting and go back to a direct connect for a cleaner as faster connection to the STO servers...
sigh.... 3 weeks.... still the same problem and i am located in the philippines.... damn can't youi guys in cryptic do something.... PWE tech supports recommendations are not working....
At approximately 1 AM PST today (9 AM UTC December 12, 2012), Cryptic made a routing change that may work around this issue.
Our networking experts have done some analysis and, while the source of the Internet connectivity disruption is not known, they have made a change to route affected traffic by a different path. Our internal tests confirm that this resolves the issue for all cases we have access to.
For all individuals who were affected, we recommend checking again at this time if you are still experiencing disruption. Please disable any proxy, if you have enabled (in the Launcher) it to work around this issue; using the proxy unnecessarily may cause suboptimal performance.
...
We would very much appreciate any reports from customers who experienced this issue saying that their issue has been resolved.
Just letting you know I disabled the proxy last night and I did not have any lag or disconnection problems.
So for me at least it seems to be resolved. Thanks.
Comments
Same, except that I'm in Sacramento. But I'm also using Comcast, and once I set it to use the US proxy the game became playable again, I haven't had any appreciable lag/rubberbanding/crashes since.
Glad to see this thread; I am having the same problems as everyone here (with Comcast in the Bay Area as well). These problems started after the latest patch (12/6/12) and has made playing a living hell. I had no lag issues till then.
I will definitely try the US proxy setting in the launcher and see if this alleviates the problem. Thanks for the suggestion.
Thanks, it's working better, but still kinda laggy. It's a playable game! Small victories.
They "address" it by blaming everyone but themselves. :rolleyes:
To restate what other people said in the thread, traffic sourced from Comcast in California to our Boston data center seems to be afflicted by some network issue that causes intermittent gameplay glitches.
I really appreciate you guys taking the time to come to the forums and report this issue, and I'm sorry that you're having this disruption. I hope that we can offer some sort of resolution soon, but it may become the case that this is an issue outside of our immediate control; in that case, we'll have to decide what we can do.
In the near term, enabling one of the proxy settings in the Launcher may temporarily improve the gameplay experience. Note that you don't usually want to use proxies once the issue has been resolved, since they tend to be somewhat slower than connecting directly to our servers.
would freezeze at gateway and tactical cube
My STOwiki page | Reachable in-game @PhyrexianHero
Fed Armada: Section 31 (level 730, 2700+ members)
KDF Armada: Klingon Intelligence (level 699, 2100+ members)
Sounds Like you guys know about the problem already. If it helps, I'm playing from Australia.
Will try the proxy thing in options tonight and see how it goes.
How will we know when to turn proxy off?
Same for me I'm worrying each time I beam down to the planet for fear of having to restart the game.
#2311#2700#2316#2500
Our networking experts have done some analysis and, while the source of the Internet connectivity disruption is not known, they have made a change to route affected traffic by a different path. Our internal tests confirm that this resolves the issue for all cases we have access to.
For all individuals who were affected, we recommend checking again at this time if you are still experiencing disruption. Please disable any proxy, if you have enabled (in the Launcher) it to work around this issue; using the proxy unnecessarily may cause suboptimal performance.
I empathsize with anyone who has experienced this very disruptive issue. We really appreciate the help of everyone who has taken the time to report this issue.
We would very much appreciate any reports from customers who experienced this issue saying that their issue has been resolved.
For anyone still experiencing this issue, a report with the following information would also be very helpful:
1. Date and time that the problem began occurring, as precisely as you can tell (with time zone)
2. A quick description of exactly what sort of problem you observe (lag, rubberbanding, disconnects, etc), and when it occurs (beaming up, logging in, sitting on Earth spacedock, etc.)
3. If you have tried using a proxy in the Launcher, and if so, if it made things better.
4. Optional but helpful: The output of tracert to nettest.crypticstudios.com and the Cryptic 'nettest' program.
2. Go to Qs wonderland for daily and snowball digging. Lag rubberbanding server not responding. got Dc'd 5 times in a row.
3.Dont use proxy
so is there any reason why this is the only online game i play that lags to hell and back?
Is Comcast a service Cryptic uses to connect players? I use Cox Communication in southern California and I am still having the lagging issues. I have started using the proxy as a temprorary measure and it helps but does not fix the issue.
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 be the area where the problem really takes over. I also would like to note that I had no latency issues prior to the season 7 release.
Brian
1. Issue began last Friday. Despite popular belief I'm not actually constantly on STO to know exactly when this started
2. Rubberband and disconnects are the most common symptoms. Also, occasionally the entire interface is unresponsive (you can click buttons, but they don't work, not even Logout). Some instance servers behave better than others. Switching zones or characters may trigger the use of one of these problematic servers. Pinging the server specifically (using the log data from clientservercomm.log) reports about 10% packet loss, occurring in bursts. This does not occur when using a properly functional route.
3. Using the Cryptic US proxy works around the issue. Similarly, using my corporate VPN based out of Dallas, TX also works around the issue.
4.
$ tracert nettest.crypticstudios.com
Tracing route to nettest.crypticstudios.com [208.95.184.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms sthelena [10.0.1.1]
2 28 ms 30 ms 29 ms 50.131.236.1
3 42 ms 9 ms 9 ms te-5-8-ur04.pinole.ca.sfba.comcast.net [68.85.100.69]
4 20 ms 11 ms 23 ms te-0-2-0-13-ar01.oakland.ca.sfba.comcast.net [68.86.143.38]
5 21 ms 23 ms 23 ms he-2-15-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.91.225]
6 16 ms 19 ms 19 ms pos-0-9-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.85.181]
7 17 ms 17 ms 16 ms pos-0-7-0-0-pe01.529bryant.ca.ibone.comcast.net [68.86.88.202]
8 16 ms 16 ms 17 ms te0-0-0-12.ccr21.sjc04.atlas.cogentco.com [154.54.13.17]
9 17 ms 18 ms 16 ms te0-0-0-6.mpd21.sfo01.atlas.cogentco.com [154.54.2.165]
10 60 ms 59 ms 61 ms te0-3-0-1.ccr22.mci01.atlas.cogentco.com [154.54.6.41]
11 72 ms 73 ms 71 ms te0-4-0-3.ccr21.ord01.atlas.cogentco.com [154.54.6.157]
12 97 ms 95 ms 96 ms te0-5-0-6.ccr22.bos01.atlas.cogentco.com [154.54.45.242]
13 94 ms 95 ms 95 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
14 95 ms 108 ms 107 ms 38.111.40.114
15 104 ms 95 ms 97 ms nettest.crypticstudios.com [208.95.184.10]
Without the US Proxy Setting, I'm experiencing some rubber-banding at ESD, Sol System, and Q's Winter Wonderland. I'm also still having issues with the Doff Assignment menus being populated, and claiming 'complete' on the finished ones. At least I no longer have the issue of being a bodiless entity stuck on the transporter pad waiting to beam in...
Starting having some connection issues on the 6th of this month, but got very bad on the morning of the 7th, through out the weekend. Started using the US Proxy on the 9th (which has some minor rubber-banding)
This mornings Trace route output...
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 25 ms 20 ms 30 ms 76.21.124.1
2 10 ms 9 ms 9 ms te-0-0-0-1-ur13.sanjose.ca.sfba.comcast.net [68.85.190.217]
3 23 ms 12 ms 11 ms te-1-13-0-1-ar01.sfsutro.ca.sfba.comcast.net [69.139.198.66]
4 17 ms 23 ms 23 ms he-1-6-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.90.157]
5 14 ms 14 ms 13 ms pos-0-1-0-0-pe01.529bryant.ca.ibone.comcast.net [68.86.87.2]
6 14 ms 13 ms 15 ms te0-7-0-12.ccr21.sjc04.atlas.cogentco.com [154.54.11.109]
7 13 ms 14 ms 14 ms te0-1-0-7.ccr21.sfo01.atlas.cogentco.com [154.54.5.113]
8 57 ms 57 ms 56 ms te0-1-0-2.ccr22.mci01.atlas.cogentco.com [154.54.30.70]
9 71 ms 69 ms 69 ms te0-3-0-7.ccr21.ord01.atlas.cogentco.com [154.54.84.74]
10 92 ms 93 ms 110 ms te0-1-0-6.ccr22.bos01.atlas.cogentco.com [154.54.43.206]
11 130 ms 100 ms 92 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
12 94 ms 93 ms 102 ms 38.111.40.114
13 91 ms 98 ms 92 ms 208.95.185.41
Trace complete.
NetTest...
contacting nettest server..
Local IP: 76.21.124.242
Ping: 97.1 msec
Port: 80: 423 KB/sec 19 KB/sec 448 KB/sec 500
Port: 80: 353 KB/sec 14 KB/sec 374 KB/sec 500
Port: 443: 561 KB/sec 21 KB/sec 593 KB/sec 500
Port: 443: 612 KB/sec 24 KB/sec 645 KB/sec 500
Port: 7255: 557 KB/sec 20 KB/sec 588 KB/sec 500
Port: 7255: 236 KB/sec 14 KB/sec 253 KB/sec 500
Port: 7003: 345 KB/sec 18 KB/sec 366 KB/sec 500
Port: 7003: 567 KB/sec 20 KB/sec 598 KB/sec 500
Port: 7202: 614 KB/sec 24 KB/sec 650 KB/sec 500
Port: 7202: 583 KB/sec 27 KB/sec 616 KB/sec 500
Port: 7499: 562 KB/sec 21 KB/sec 594 KB/sec 500
Port: 7499: 621 KB/sec 23 KB/sec 654 KB/sec 500
Port: 80: 464 KB/sec 25 KB/sec 490 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 1 KB/sec
hit return to exit
The game was unplayable for long periods, which is unusual, because normally there is not much lag at all.
I will report future problems.
I am experiencing extreme lag loading Sibiran Solar system for ISE (several minutes delay). ISE was extremely lagging for the first 60 seconds.
Will try US proxy setting and cross fingers.
12th Fleet
Fleet Executive Officer
12th Fleet
Fleet Executive Officer
Other Northern California Comcast users should disable the use of the US Proxy setting and go back to a direct connect for a cleaner as faster connection to the STO servers...
Just letting you know I disabled the proxy last night and I did not have any lag or disconnection problems.
So for me at least it seems to be resolved. Thanks.