I suspect this thread will get moved but it saves me having to create my own.
UK here and for the last 2/3 hours I've had immense lag with frequent disconnects. Oddly, I've been playing for quite a bit longer than that and had no problems until the last few hours of them.
This affects the STO forums as well for me.
1 2 ms 1 ms 1 ms 192.168.0.1
2 8 ms 11 ms 8 ms host82-14-174-4.not-set-yet.ntli.net [82.14.174.4]
3 7 ms 6 ms 7 ms host82-14-172-65.not-set-yet.ntli.net [82.14.172.65]
4 8 ms 7 ms 7 ms host82-14-174-97.not-set-yet.ntli.net [82.14.174.97]
5 8 ms 7 ms 7 ms manc-core-1a-ge-410-0.network.virginmedia.net [86.28.65.49]
6 7 ms 8 ms 7 ms manc-bb-1a-as0-0.network.virginmedia.net [213.105.175.1]
7 14 ms 13 ms 12 ms brnt-bb-1b-ae1-0.network.virginmedia.net [212.43.163.86]
8 13 ms 13 ms 13 ms brnt-tmr-1-ae5-0.network.virginmedia.net [213.105.159.50]
9 15 ms 18 ms 14 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
10 16 ms 14 ms 14 ms te1-3.ccr01.lon04.atlas.cogentco.com [130.117.15.69]
11 14 ms 14 ms 14 ms te2-8.mpd01.lon01.atlas.cogentco.com [130.117.3.189]
12 15 ms 14 ms 14 ms te2-1.3493.mpd02.lon01.atlas.cogentco.com [130.117.2.18]
13 96 ms 96 ms * te0-4-0-3.mpd21.jfk02.atlas.cogentco.com [154.54.44.233]
14 102 ms 102 ms 102 ms te0-1-0-2.ccr21.bos01.atlas.cogentco.com [154.54.44.6]
15 * * 103 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
16 * * 127 ms 38.111.40.114
17 * 102 ms 101 ms 208.95.185.41
Map syncs = 15+ seconds.
Any UI interaction = 3+ seconds.
Chat lags up to 40 seconds.
Several disconnects over the past 2 hours.
Also forum has horrible performance.
Same problem in Austria. Also the forum is sometimes extremely slow.
tracert patchserver.crypticstudios.com
[***]
6 35 ms 21 ms 22 ms win-b4-link.telia.net [213.248.96.1]
7 37 ms 29 ms 27 ms prag-bb1-link.telia.net [213.155.133.70]
8 47 ms 47 ms 53 ms ffm-bb1-link.telia.net [80.91.246.138]
9 40 ms 46 ms 46 ms ffm-b12-link.telia.net [80.91.246.103]
10 40 ms 40 ms 40 ms cogent-ic-140550-ffm-b12.c.telia.net [213.248.10.106]
11 46 ms 47 ms 46 ms te0-3-0-2.ccr21.ams03.atlas.cogentco.com [154.54.39.177]
12 56 ms 56 ms 56 ms te7-8.ccr01.lon01.atlas.cogentco.com [130.117.48.141]
13 141 ms 141 ms 140 ms te0-5-0-4.ccr21.jfk02.atlas.cogentco.com [154.54.44.229]
14 147 ms 148 ms 148 ms te0-4-0-7.ccr22.bos01.atlas.cogentco.com [154.54.44.50]
15 144 ms 145 ms 145 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
16 161 ms 165 ms * 38.111.40.114
17 147 ms 146 ms * 208.95.185.41
18 151 ms 158 ms 149 ms 208.95.185.41
Nettest will be added asap... currently working on it but it takes forever...
Yep same here, im in the uk as well and got loads of lag last night after the patch.
Also my fleet admin who is also from europe was having dissconnects all last night.
We pretty much agreed the the next time we dissconnect, that would be it for us until later on tonight. Sure enough 10 mins later we both dissconnect :rolleyes:
Kind of worried to go back on tonight just to get loads of lag!
Funnily enough though, all our american members were not having any problems.....I think cryptic hates europe!
Last Night This morning, Some Germans reports they can't play at all same as in France .
Here in Holland only the north can play south is still down due to an huge thunderstorm .
Can log in in but rather then that can't do a thing, or the server isn't responding and leave me dead and everyone else or I drop out to log in screen all the time if this continues I would like longer time on my subscription this is going on for five days now and I haven't been able to play much then 5 Min's.
I'm noticing it too during PvP, matches are laggy as can be. At the start of Season 4 performance was quite smooth. Now, its just making the game just unplayble.
Can't play men the moment I'm in the server is not responding that is happening the whole stupid day .
I know they are tired from an stressful week but common I want to play after an stress full week.
Can't play men the moment I'm in the server is not responding that is happening the whole stupid day .
I know they are tired from an stressful week but common I want to play after an stress full week.
Yo Cryptic do something for crying out loud !!!
The server isn't down.
The issues today appears to be a local problem. Your issues (which you've already created a thread about) are quite likely a different issue entirely.
The issues that I was having were fixed when I changed to a US proxy server via the options menu.
I'm from the UK and been having lag problems today (16/7/11) as well.
Tried connecting with no proxy and then euro proxy server, made no difference ( not tried US proxy yet)
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 138 ms <1 ms <1 ms
2 10 ms 10 ms 12 ms
3 23 ms 17 ms 17 ms
4 20 ms 20 ms 20 ms
5 77 ms 19 ms 20 ms
6 20 ms 20 ms 20 ms
7 23 ms 23 ms 24 ms
8 24 ms 23 ms 23 ms bundle-ether1.lontr1.London.opentransit.net [193
.251.255.101]
9 61 ms 60 ms 61 ms te7-7.ccr01.lon01.atlas.cogentco.com [130.117.14
.153]
10 102 ms 101 ms 111 ms te0-0-0-4.ccr22.bos01.atlas.cogentco.com [130.11
7.0.46]
11 106 ms 106 ms 102 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
12 104 ms 108 ms 107 ms 38.111.40.114
13 100 ms 101 ms 101 ms 208.95.185.41
This is getting extremely irritating, the first Satruday night i've not been busy and we can't even barely get on the game. Fantastic. I wouldn't mind if it was a one day problem, but it has been a few now.
I've not had much time to play tonight ( 20 mins to test).
EU proxy = no lag in quick 10 min test ( warping in and out of K7)
US proxy = no lag in quick 10 min test ( warping in and out of K7)
no proxy = lag in quick 2 min test ( warping out of memory alpha). It laged out and then disconnected from server.
This is just my experience in the last 20 min, hopefuly the lag from earlier is gone but i haven't been able to play anywhere near as long as i did earlier this afternoon.
Also the earlier tracert was taken this evening NOT when i was experiencing the lag.
Yep same here, im in the uk as well and got loads of lag last night after the patch.
Also my fleet admin who is also from europe was having dissconnects all last night.
We pretty much agreed the the next time we dissconnect, that would be it for us until later on tonight. Sure enough 10 mins later we both dissconnect :rolleyes:
Kind of worried to go back on tonight just to get loads of lag!
Funnily enough though, all our american members were not having any problems.....I think cryptic hates europe!
Definitely not true. I live in North America and let me tell you, since Season 4 launch the game has been unplayable.
Please, if you are experiencing lag issues and similar, please always provide detailed information:
Without detailed information we cannot ever assist you. And detailed information is not "STO does not work but WoW works!". They are different server locations. You so not use the same pathways to get to server A that you use to get to server B.
*Always* run a tracert. Find out which hops you are taking and where the lag starts.
*Always* use the nettest tool to check if you are able to connect properly.
*Always* add from where you are playing (I don't need your address, but we do need to know where in the world you are and what your internet service provider is)
Tracert patchserver.crypticstudios.com to check your routing.
You can run tracerts from a windows prompt or through online tools; select that which works best for you.
Nettest:
Go to files.champions-online.com/nettest.exe
Download this file and run it
A command prompt should appear running the test automatically
Do alt prtscn(be sure the nettest is the active window) to Copy and paste the results in paint and save as jpeg and attach it in a post in this forum else
write down the columns
Good results have column 1 and 3 with values around 300- 500kb/sec, column 2 with 20kb/sec
Please, if you are experiencing lag issues and similar, please always provide detailed information:
Without detailed information we cannot ever assist you. And detailed information is not "STO does not work but WoW works!". They are different server locations. You so not use the same pathways to get to server A that you use to get to server B.
*Always* run a tracert. Find out which hops you are taking and where the lag starts.
*Always* use the nettest tool to check if you are able to connect properly.
*Always* add from where you are playing (I don't need your address, but we do need to know where in the world you are and what your internet service provider is)
You can run tracerts from a windows prompt or through online tools; select that which works best for you.
I did....all is normal as far as I can tell. And the rubberbanding I've experienced is limited to sector space and the social hubs,no lag issues while on a mission map.
Edit: server not responding in the exploration clusters.
Having same problems here. I'm in the U.S. in Alabama with Centurylink ISP.
Tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms dslrouter [192.168.1.1]
2 16 ms 15 ms 16 ms 75-121-65-1.dyn.centurytel.net [75.121.65.1]
3 15 ms 15 ms 14 ms GE-0-0-0-0-J1-rt.pell.centurytel.net [64.91.92.4
]
4 21 ms 21 ms 20 ms bb-atlngamv-jx9-01-ae4-597.core.centurytel.net [
208.110.249.164]
5 18 ms 53 ms 17 ms bb-atlngamv-jx9-02-ae0.core.centurytel.net [206.
51.69.66]
6 34 ms 34 ms 34 ms 207.88.188.33.ptr.us.xo.net [207.88.188.33]
7 36 ms 55 ms * te-12-4-0.rar3.washington-dc.us.xo.net [207.88.1
4.113]
8 33 ms 35 ms * 207.88.14.165.ptr.us.xo.net [207.88.14.165]
9 * 34 ms 34 ms 206.111.0.230.ptr.us.xo.net [206.111.0.230]
10 34 ms 37 ms 34 ms te0-2-0-5.mpd21.dca01.atlas.cogentco.com [154.54
.41.121]
11 41 ms 41 ms 42 ms te0-1-0-7.mpd21.jfk02.atlas.cogentco.com [154.54
.1.106]
12 * 49 ms 49 ms te0-2-0-1.ccr21.bos01.atlas.cogentco.com [154.54
.44.10]
13 47 ms 47 ms 46 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
14 51 ms 53 ms 53 ms 38.111.40.114
15 46 ms 47 ms 47 ms 208.95.185.41
Please, if you are experiencing lag issues and similar, please always provide detailed information:
Without detailed information we cannot ever assist you. And detailed information is not "STO does not work but WoW works!". They are different server locations. You so not use the same pathways to get to server A that you use to get to server B.
*Always* run a tracert. Find out which hops you are taking and where the lag starts.
*Always* use the nettest tool to check if you are able to connect properly.
*Always* add from where you are playing (I don't need your address, but we do need to know where in the world you are and what your internet service provider is)
You can run tracerts from a windows prompt or through online tools; select that which works best for you.
WishStone, the servers have gone bad in the last half hour. A lot of people in TTS chat are upset because they have to claw to get back into the game... I myself got kicked from the game while trying to load a character, and I already rebooted both the mother and the router at my house.
When I go to our network guys, I need to show them something more than "Some folks are being bounced off the servers.". That's why we ask for this data. The more information we can gather from all over, the better we can narrow down what may be happening.
A couple of times, I got a "Disconnected from login serve 208.95.x.x:7001 (I forgot the other parts if the IP address). I'll edit this post with a tracert when I get it.
Data:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms READYSHARE [192.168.1.1]
2 * 12 ms * cpe-69-135-160-1.insight.res.rr.com [69.135.160.1]
3 9 ms 8 ms 40 ms gig1-12.instoh1-rtr01.insight.rr.com [65.24.192.157]
4 * 16 ms 16 ms network-065-024-192-046.insight.rr.com [65.24.192.46]
5 12 ms * 157 ms tge4-0-0.tr00.clmkohpe.mwrtn.rr.com [65.25.137.21]
6 38 ms 32 ms 28 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
7 27 ms 25 ms * ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
8 37 ms 36 ms 22 ms te0-2-0-7.ccr22.ord03.atlas.cogentco.com [154.54.11.145]
9 * * 51 ms te0-3-0-0.ccr22.ord01.atlas.cogentco.com [154.54.5.1]
10 97 ms 40 ms 44 ms te0-1-0-6.ccr22.bos01.atlas.cogentco.com [154.54.43.206]
11 58 ms 49 ms 61 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
12 46 ms 53 ms 72 ms 38.111.40.114
13 57 ms 57 ms * 208.95.185.41
14 * * * Request timed out.
15 67 ms 71 ms 68 ms 208.95.185.41
Trace complete.
Pinging startrekonline.com [208.95.185.44] with 32 bytes of data:
Reply from 208.95.185.44: bytes=32 time=43ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Request timed out.
Request timed out.
Reply from 208.95.185.44: bytes=32 time=47ms TTL=49
Reply from 208.95.185.44: bytes=32 time=48ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=41ms TTL=49
Reply from 208.95.185.44: bytes=32 time=41ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Reply from 208.95.185.44: bytes=32 time=40ms TTL=49
Reply from 208.95.185.44: bytes=32 time=41ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Reply from 208.95.185.44: bytes=32 time=46ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Reply from 208.95.185.44: bytes=32 time=46ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Request timed out.
Reply from 208.95.185.44: bytes=32 time=71ms TTL=49
Request timed out.
Reply from 208.95.185.44: bytes=32 time=41ms TTL=49
Request timed out.
Reply from 208.95.185.44: bytes=32 time=41ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Request timed out.
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Request timed out.
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Request timed out.
Reply from 208.95.185.44: bytes=32 time=43ms TTL=49
Reply from 208.95.185.44: bytes=32 time=43ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=48ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=46ms TTL=49
Reply from 208.95.185.44: bytes=32 time=41ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Reply from 208.95.185.44: bytes=32 time=41ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Reply from 208.95.185.44: bytes=32 time=46ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Reply from 208.95.185.44: bytes=32 time=52ms TTL=49
Reply from 208.95.185.44: bytes=32 time=82ms TTL=49
Reply from 208.95.185.44: bytes=32 time=41ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Request timed out.
Reply from 208.95.185.44: bytes=32 time=49ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Ping statistics for 208.95.185.44:
Packets: Sent = 64, Received = 55, Lost = 9 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 82ms, Average = 45ms
When I go to our network guys, I need to show them something more than "Some folks are being bounced off the servers.". That's why we ask for this data. The more information we can gather from all over, the better we can narrow down what may be happening.
1 1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 9 ms 10 ms 5ED2E801.cm-7-3d.dynamic.ziggo.nl [94.210.232.1]
3 10 ms 6 ms 7 ms mnd-rc0001-cr101-ae15-222.core.as9143.net [213.5
1.162.241]
4 9 ms 11 ms 11 ms asd-lc0006-cr101-ae7-0.core.as9143.net [213.51.1
58.2]
5 103 ms 10 ms 7 ms TenGigabitEthernet9-2.ar7.AMS1.gblx.net [208.49.
195.165]
6 138 ms 135 ms 137 ms te0-3-0-3.ccr21.jfk07.atlas.cogentco.com [154.54
.14.69]
7 134 ms 132 ms 138 ms te0-3-0-1.mpd21.jfk02.atlas.cogentco.com [154.54
.1.133]
8 148 ms 148 ms 146 ms te0-4-0-3.ccr21.bos01.atlas.cogentco.com [154.54
.44.18]
9 143 ms 142 ms 138 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
10 143 ms 143 ms 143 ms 38.111.40.114
11 132 ms 132 ms 134 ms 208.95.185.41
So....your network guys happy now? Oh,and I'm in the Netherlands btw....but you already knew that.;)
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 22 ms 19 ms 24 ms c-68-58-36-1.hsd1.in.comcast.net [68.58.36.1]
2 7 ms 9 ms 9 ms te-7-8-ur04.mishawaka.in.sbend.comcast.net [68.8
7.204.5]
3 9 ms 9 ms 9 ms te-3-3-ur03.mishawaka.in.sbend.comcast.net [68.8
6.184.230]
4 12 ms 13 ms 11 ms te-1-7-0-5-ar01.area4.il.chicago.comcast.net [68
.87.235.17]
5 14 ms 14 ms 13 ms pos-1-10-0-0-cr01.chicago.il.ibone.comcast.net [
68.86.95.237]
6 13 ms 14 ms 13 ms pos-1-8-0-0-pe01.350ecermak.il.ibone.comcast.net
[68.86.87.166]
7 14 ms 14 ms 14 ms te0-3-0-1.ccr22.ord03.atlas.cogentco.com [154.54
.10.253]
8 14 ms 13 ms 14 ms te0-0-0-1.ccr22.ord01.atlas.cogentco.com [154.54
.1.97]
9 47 ms 47 ms 47 ms te0-1-0-6.ccr22.bos01.atlas.cogentco.com [154.54
.43.206]
10 49 ms 49 ms 48 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
11 48 ms 50 ms 53 ms 38.111.40.114
12 48 ms 47 ms 47 ms 208.95.185.41
Comments
it was fairly mild for me and I live in the UK.
Had a couple of disconnects too.
UK here and for the last 2/3 hours I've had immense lag with frequent disconnects. Oddly, I've been playing for quite a bit longer than that and had no problems until the last few hours of them.
This affects the STO forums as well for me.
1 2 ms 1 ms 1 ms 192.168.0.1
2 8 ms 11 ms 8 ms host82-14-174-4.not-set-yet.ntli.net [82.14.174.4]
3 7 ms 6 ms 7 ms host82-14-172-65.not-set-yet.ntli.net [82.14.172.65]
4 8 ms 7 ms 7 ms host82-14-174-97.not-set-yet.ntli.net [82.14.174.97]
5 8 ms 7 ms 7 ms manc-core-1a-ge-410-0.network.virginmedia.net [86.28.65.49]
6 7 ms 8 ms 7 ms manc-bb-1a-as0-0.network.virginmedia.net [213.105.175.1]
7 14 ms 13 ms 12 ms brnt-bb-1b-ae1-0.network.virginmedia.net [212.43.163.86]
8 13 ms 13 ms 13 ms brnt-tmr-1-ae5-0.network.virginmedia.net [213.105.159.50]
9 15 ms 18 ms 14 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
10 16 ms 14 ms 14 ms te1-3.ccr01.lon04.atlas.cogentco.com [130.117.15.69]
11 14 ms 14 ms 14 ms te2-8.mpd01.lon01.atlas.cogentco.com [130.117.3.189]
12 15 ms 14 ms 14 ms te2-1.3493.mpd02.lon01.atlas.cogentco.com [130.117.2.18]
13 96 ms 96 ms * te0-4-0-3.mpd21.jfk02.atlas.cogentco.com [154.54.44.233]
14 102 ms 102 ms 102 ms te0-1-0-2.ccr21.bos01.atlas.cogentco.com [154.54.44.6]
15 * * 103 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
16 * * 127 ms 38.111.40.114
17 * 102 ms 101 ms 208.95.185.41
Trace complete.
unable to allocate performance buffer
contacting nettest server..
Local IP: 81.108.130.229
Ping: 157.9 msec
Port: 80: timed out
Port: 80: 15 KB/sec 0 KB/sec 0 KB/sec 500
Port: 443: timed out
Port: 443: 18 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7255: timed out
Port: 7255: 4 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7003: 14 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7003: timed out
Port: 7202: 22 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7202: 73 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7499: 56 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7499: 58 KB/sec 0 KB/sec 0 KB/sec 500
Port: 80: 174 KB/sec 0 KB/sec 0 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
Map syncs = 15+ seconds.
Any UI interaction = 3+ seconds.
Chat lags up to 40 seconds.
Several disconnects over the past 2 hours.
Also forum has horrible performance.
tracert patchserver.crypticstudios.com
[***]
6 35 ms 21 ms 22 ms win-b4-link.telia.net [213.248.96.1]
7 37 ms 29 ms 27 ms prag-bb1-link.telia.net [213.155.133.70]
8 47 ms 47 ms 53 ms ffm-bb1-link.telia.net [80.91.246.138]
9 40 ms 46 ms 46 ms ffm-b12-link.telia.net [80.91.246.103]
10 40 ms 40 ms 40 ms cogent-ic-140550-ffm-b12.c.telia.net [213.248.10.106]
11 46 ms 47 ms 46 ms te0-3-0-2.ccr21.ams03.atlas.cogentco.com [154.54.39.177]
12 56 ms 56 ms 56 ms te7-8.ccr01.lon01.atlas.cogentco.com [130.117.48.141]
13 141 ms 141 ms 140 ms te0-5-0-4.ccr21.jfk02.atlas.cogentco.com [154.54.44.229]
14 147 ms 148 ms 148 ms te0-4-0-7.ccr22.bos01.atlas.cogentco.com [154.54.44.50]
15 144 ms 145 ms 145 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
16 161 ms 165 ms * 38.111.40.114
17 147 ms 146 ms * 208.95.185.41
18 151 ms 158 ms 149 ms 208.95.185.41
Nettest will be added asap... currently working on it but it takes forever...
[Edit]
Ping: 130.5 msec
Port: 80: timed out
Port: 80: timed out
Port: 443: timed out
Port: 443: timed out
Port: 7255: 211 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7255: 189 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7003: timed out
Port: 7003: 132 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7202: 179 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7202: 224 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7499: 180 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7499: 175 KB/sec 0 KB/sec 0 KB/sec 500
Port: 80: 185 KB/sec 0 KB/sec 0 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
Also my fleet admin who is also from europe was having dissconnects all last night.
We pretty much agreed the the next time we dissconnect, that would be it for us until later on tonight. Sure enough 10 mins later we both dissconnect :rolleyes:
Kind of worried to go back on tonight just to get loads of lag!
Funnily enough though, all our american members were not having any problems.....I think cryptic hates europe!
Just did KA
Had MULTIPLE times where i was "teleported" 5 meters back cause of lag.
Rest of team had same problems.
1 DK, 1 UK, 1 SWE, 1 US
2 other friends from DK having same probs... Different ISP's
Hope you fix soon !
Try going via US Proxy in your Options in your launcher. That seemed to fix it for me.
Here in Holland only the north can play south is still down due to an huge thunderstorm .
Can log in in but rather then that can't do a thing, or the server isn't responding and leave me dead and everyone else or I drop out to log in screen all the time if this continues I would like longer time on my subscription this is going on for five days now and I haven't been able to play much then 5 Min's.
Cryptic please do something !!!
Put in 1 NL
Account server
online (84ms)
Controller checker 1
online (82ms)
Controller checker 2
online (82ms)
Error check server
online (156ms)
Patch server
online (83ms)
Website
online (82ms)
This is one check for others now
http://www.sto-center.de/forum/forumdisplay.php?99-Star-Trek-Online-Serverstatus
Greets
I know they are tired from an stressful week but common I want to play after an stress full week.
Yo Cryptic do something for crying out loud !!!
The server isn't down.
The issues today appears to be a local problem. Your issues (which you've already created a thread about) are quite likely a different issue entirely.
The issues that I was having were fixed when I changed to a US proxy server via the options menu.
We will continue to monitor in case there is anything we can do on our end.
Thank you Dan.
Tried connecting with no proxy and then euro proxy server, made no difference ( not tried US proxy yet)
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 138 ms <1 ms <1 ms
2 10 ms 10 ms 12 ms
3 23 ms 17 ms 17 ms
4 20 ms 20 ms 20 ms
5 77 ms 19 ms 20 ms
6 20 ms 20 ms 20 ms
7 23 ms 23 ms 24 ms
8 24 ms 23 ms 23 ms bundle-ether1.lontr1.London.opentransit.net [193
.251.255.101]
9 61 ms 60 ms 61 ms te7-7.ccr01.lon01.atlas.cogentco.com [130.117.14
.153]
10 102 ms 101 ms 111 ms te0-0-0-4.ccr22.bos01.atlas.cogentco.com [130.11
7.0.46]
11 106 ms 106 ms 102 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
12 104 ms 108 ms 107 ms 38.111.40.114
13 100 ms 101 ms 101 ms 208.95.185.41
Trace complete.
Give the US proxy a try. Let us know if it works
EU proxy = no lag in quick 10 min test ( warping in and out of K7)
US proxy = no lag in quick 10 min test ( warping in and out of K7)
no proxy = lag in quick 2 min test ( warping out of memory alpha). It laged out and then disconnected from server.
This is just my experience in the last 20 min, hopefuly the lag from earlier is gone but i haven't been able to play anywhere near as long as i did earlier this afternoon.
Also the earlier tracert was taken this evening NOT when i was experiencing the lag.
Definitely not true. I live in North America and let me tell you, since Season 4 launch the game has been unplayable.
Without detailed information we cannot ever assist you. And detailed information is not "STO does not work but WoW works!". They are different server locations. You so not use the same pathways to get to server A that you use to get to server B.
- *Always* run a tracert. Find out which hops you are taking and where the lag starts.
- *Always* use the nettest tool to check if you are able to connect properly.
- *Always* add from where you are playing (I don't need your address, but we do need to know where in the world you are and what your internet service provider is)
You can run tracerts from a windows prompt or through online tools; select that which works best for you.I did....all is normal as far as I can tell. And the rubberbanding I've experienced is limited to sector space and the social hubs,no lag issues while on a mission map.
Edit: server not responding in the exploration clusters.
Tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms dslrouter [192.168.1.1]
2 16 ms 15 ms 16 ms 75-121-65-1.dyn.centurytel.net [75.121.65.1]
3 15 ms 15 ms 14 ms GE-0-0-0-0-J1-rt.pell.centurytel.net [64.91.92.4
]
4 21 ms 21 ms 20 ms bb-atlngamv-jx9-01-ae4-597.core.centurytel.net [
208.110.249.164]
5 18 ms 53 ms 17 ms bb-atlngamv-jx9-02-ae0.core.centurytel.net [206.
51.69.66]
6 34 ms 34 ms 34 ms 207.88.188.33.ptr.us.xo.net [207.88.188.33]
7 36 ms 55 ms * te-12-4-0.rar3.washington-dc.us.xo.net [207.88.1
4.113]
8 33 ms 35 ms * 207.88.14.165.ptr.us.xo.net [207.88.14.165]
9 * 34 ms 34 ms 206.111.0.230.ptr.us.xo.net [206.111.0.230]
10 34 ms 37 ms 34 ms te0-2-0-5.mpd21.dca01.atlas.cogentco.com [154.54
.41.121]
11 41 ms 41 ms 42 ms te0-1-0-7.mpd21.jfk02.atlas.cogentco.com [154.54
.1.106]
12 * 49 ms 49 ms te0-2-0-1.ccr21.bos01.atlas.cogentco.com [154.54
.44.10]
13 47 ms 47 ms 46 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
14 51 ms 53 ms 53 ms 38.111.40.114
15 46 ms 47 ms 47 ms 208.95.185.41
Trace complete.
Here's the nettest picture.
http://imageshack.us/photo/my-images/94/unled1copyzm.jpg/
Hopefully that helps because as of right now I'm not able to even play.
WishStone, the servers have gone bad in the last half hour. A lot of people in TTS chat are upset because they have to claw to get back into the game... I myself got kicked from the game while trying to load a character, and I already rebooted both the mother and the router at my house.
A couple of times, I got a "Disconnected from login serve 208.95.x.x:7001 (I forgot the other parts if the IP address). I'll edit this post with a tracert when I get it.
Data:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms READYSHARE [192.168.1.1]
2 * 12 ms * cpe-69-135-160-1.insight.res.rr.com [69.135.160.1]
3 9 ms 8 ms 40 ms gig1-12.instoh1-rtr01.insight.rr.com [65.24.192.157]
4 * 16 ms 16 ms network-065-024-192-046.insight.rr.com [65.24.192.46]
5 12 ms * 157 ms tge4-0-0.tr00.clmkohpe.mwrtn.rr.com [65.25.137.21]
6 38 ms 32 ms 28 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
7 27 ms 25 ms * ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
8 37 ms 36 ms 22 ms te0-2-0-7.ccr22.ord03.atlas.cogentco.com [154.54.11.145]
9 * * 51 ms te0-3-0-0.ccr22.ord01.atlas.cogentco.com [154.54.5.1]
10 97 ms 40 ms 44 ms te0-1-0-6.ccr22.bos01.atlas.cogentco.com [154.54.43.206]
11 58 ms 49 ms 61 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
12 46 ms 53 ms 72 ms 38.111.40.114
13 57 ms 57 ms * 208.95.185.41
14 * * * Request timed out.
15 67 ms 71 ms 68 ms 208.95.185.41
Trace complete.
Pinging startrekonline.com [208.95.185.44] with 32 bytes of data:
Reply from 208.95.185.44: bytes=32 time=43ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Request timed out.
Request timed out.
Reply from 208.95.185.44: bytes=32 time=47ms TTL=49
Reply from 208.95.185.44: bytes=32 time=48ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=41ms TTL=49
Reply from 208.95.185.44: bytes=32 time=41ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Reply from 208.95.185.44: bytes=32 time=40ms TTL=49
Reply from 208.95.185.44: bytes=32 time=41ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Reply from 208.95.185.44: bytes=32 time=46ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Reply from 208.95.185.44: bytes=32 time=46ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Request timed out.
Reply from 208.95.185.44: bytes=32 time=71ms TTL=49
Request timed out.
Reply from 208.95.185.44: bytes=32 time=41ms TTL=49
Request timed out.
Reply from 208.95.185.44: bytes=32 time=41ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Request timed out.
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Request timed out.
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Request timed out.
Reply from 208.95.185.44: bytes=32 time=43ms TTL=49
Reply from 208.95.185.44: bytes=32 time=43ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=48ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=46ms TTL=49
Reply from 208.95.185.44: bytes=32 time=41ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Reply from 208.95.185.44: bytes=32 time=41ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Reply from 208.95.185.44: bytes=32 time=46ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Reply from 208.95.185.44: bytes=32 time=52ms TTL=49
Reply from 208.95.185.44: bytes=32 time=82ms TTL=49
Reply from 208.95.185.44: bytes=32 time=41ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Reply from 208.95.185.44: bytes=32 time=44ms TTL=49
Request timed out.
Reply from 208.95.185.44: bytes=32 time=49ms TTL=49
Reply from 208.95.185.44: bytes=32 time=42ms TTL=49
Reply from 208.95.185.44: bytes=32 time=45ms TTL=49
Ping statistics for 208.95.185.44:
Packets: Sent = 64, Received = 55, Lost = 9 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 82ms, Average = 45ms
Nettest
contacting nettest server..
Local IP: 69.135.171.66
Ping: 49.2 msec
Port: 80: 271 KB/sec 14 KB/sec 289 KB/sec 500
Port: 80: 50 KB/sec 3 KB/sec 57 KB/sec 500
Port: 443: 202 KB/sec 11 KB/sec 215 KB/sec 500
Port: 443: 239 KB/sec 12 KB/sec 256 KB/sec 500
Port: 7255: 264 KB/sec 11 KB/sec 281 KB/sec 500
Port: 7255: 378 KB/sec 19 KB/sec 402 KB/sec 500
Port: 7003: timed out
Port: 7003: 1068 KB/sec 41 KB/sec 1138 KB/sec 500
Port: 7202: 69 KB/sec 8 KB/sec 89 KB/sec 500
Port: 7202: 22 KB/sec 2 KB/sec 24 KB/sec 500
Port: 7499: 169 KB/sec 8 KB/sec 181 KB/sec 500
Port: 7499: timed out
Port: 80: 563 KB/sec 27 KB/sec 609 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
1 1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 9 ms 10 ms 5ED2E801.cm-7-3d.dynamic.ziggo.nl [94.210.232.1]
3 10 ms 6 ms 7 ms mnd-rc0001-cr101-ae15-222.core.as9143.net [213.5
1.162.241]
4 9 ms 11 ms 11 ms asd-lc0006-cr101-ae7-0.core.as9143.net [213.51.1
58.2]
5 103 ms 10 ms 7 ms TenGigabitEthernet9-2.ar7.AMS1.gblx.net [208.49.
195.165]
6 138 ms 135 ms 137 ms te0-3-0-3.ccr21.jfk07.atlas.cogentco.com [154.54
.14.69]
7 134 ms 132 ms 138 ms te0-3-0-1.mpd21.jfk02.atlas.cogentco.com [154.54
.1.133]
8 148 ms 148 ms 146 ms te0-4-0-3.ccr21.bos01.atlas.cogentco.com [154.54
.44.18]
9 143 ms 142 ms 138 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
10 143 ms 143 ms 143 ms 38.111.40.114
11 132 ms 132 ms 134 ms 208.95.185.41
So....your network guys happy now? Oh,and I'm in the Netherlands btw....but you already knew that.;)
I will post a tracert and stuff if it gets messed up again, but for now iam happy just to play a bit.
edit:
...
> Right now < 30 minutes later, it has gone to limbo.. lag locked again, really i dont get it.
While connected to STO, heres the tracert to the adresses the Gameclient.exe is connecting to:
_
Routenverfolgung zu 208.95.184.211
over a maximum of 30 hops:
1 22 ms 19 ms 24 ms c-68-58-36-1.hsd1.in.comcast.net [68.58.36.1]
2 7 ms 9 ms 9 ms te-7-8-ur04.mishawaka.in.sbend.comcast.net [68.8
7.204.5]
3 9 ms 9 ms 9 ms te-3-3-ur03.mishawaka.in.sbend.comcast.net [68.8
6.184.230]
4 12 ms 13 ms 11 ms te-1-7-0-5-ar01.area4.il.chicago.comcast.net [68
.87.235.17]
5 14 ms 14 ms 13 ms pos-1-10-0-0-cr01.chicago.il.ibone.comcast.net [
68.86.95.237]
6 13 ms 14 ms 13 ms pos-1-8-0-0-pe01.350ecermak.il.ibone.comcast.net
[68.86.87.166]
7 14 ms 14 ms 14 ms te0-3-0-1.ccr22.ord03.atlas.cogentco.com [154.54
.10.253]
8 14 ms 13 ms 14 ms te0-0-0-1.ccr22.ord01.atlas.cogentco.com [154.54
.1.97]
9 47 ms 47 ms 47 ms te0-1-0-6.ccr22.bos01.atlas.cogentco.com [154.54
.43.206]
10 49 ms 49 ms 48 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
11 48 ms 50 ms 53 ms 38.111.40.114
12 48 ms 47 ms 47 ms 208.95.185.41
Trace complete.
Nettest results:
http://imageshack.us/photo/my-images/232/nettest.jpg/
Location:
Indiana, USA
Issue:
Frequent server not responding or rubber banding usually resulting in disconnects.
I really hope this helps.