Heres mine. UK/Manchester. I'm getting withdrawals and need my daily dose!
2 8 ms 7 ms 8 ms 217.32.142.0
3 7 ms 7 ms 7 ms 217.32.142.30
4 8 ms 7 ms 7 ms 213.120.163.70
5 8 ms 7 ms 8 ms 31.55.165.243
6 7 ms 7 ms 8 ms 31.55.165.109
7 7 ms 8 ms 7 ms acc2-10GigE-11-2-0.mr.21cn-ipp.bt.net [109.159.2
50.206]
8 15 ms 15 ms 19 ms core1-te0-3-5-0.ilford.ukcore.bt.net [109.159.25
0.141]
9 14 ms 14 ms 14 ms transit1-pos9-0.telehouse.ukcore.bt.net [62.6.20
1.118]
10 14 ms 14 ms 14 ms t2as1-tge4-4.uk-lon1.eu.bt.net [166.49.211.145]
11 14 ms 14 ms 14 ms t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.49]
12 17 ms 16 ms 17 ms te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.11
7.14.49]
13 16 ms 15 ms 14 ms te0-4-0-5.mpd21.lon13.atlas.cogentco.com [130.11
7.0.5]
14 90 ms 89 ms 88 ms te0-3-0-4.ccr21.bos01.atlas.cogentco.com [154.54
.30.129]
15 87 ms 87 ms 89 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
16 * * 97 ms 38.111.40.114
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * 87 ms 208.95.185.41
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms api.home [192.168.1.254]
2 7 ms 7 ms 8 ms 217.32.144.162
3 8 ms 9 ms 8 ms 217.32.144.190
4 10 ms 10 ms 10 ms 213.120.181.246
5 11 ms 9 ms 11 ms 217.41.169.209
6 12 ms 13 ms 11 ms 217.41.169.109
7 10 ms 10 ms 10 ms 109.159.251.195
8 22 ms 16 ms 20 ms core1-te0-13-0-2.ilford.ukcore.bt.net [109.159.2
51.137]
9 16 ms 16 ms 15 ms transit1-pos9-0.telehouse.ukcore.bt.net [62.6.20
1.118]
10 18 ms 17 ms 17 ms t2as1-tge4-4.uk-lon1.eu.bt.net [166.49.211.145]
11 17 ms 17 ms 17 ms t2a1-ge4-0-0.uk-lon1.eu.bt.net [166.49.135.17]
12 21 ms 18 ms 20 ms te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.11
7.14.49]
13 19 ms 19 ms 15 ms te0-4-0-5.ccr21.lon13.atlas.cogentco.com [154.54
.72.186]
14 91 ms 88 ms 91 ms te0-7-0-27.ccr21.bos01.atlas.cogentco.com [154.5
4.1.93]
15 91 ms 93 ms 93 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * 94 ms 208.95.185.41
so someone is responsible and they arent fired? can i get a job with you guys? man..
no point in posting a transcript, looks like they have enuf to get a clue. seems..
I'm on Verizon DSL in Maryland. Network dumps show multiple requests to establish a TCP connection, and then the update listener ignores the application level session requests. The intermittent server responses rule out large-scale problems with global routing--some of the packets are clearly making it to the server and some of them are coming back, so routing is working. The packets are dying at the cryptic network. Looks like the firewall is falling down, or the network bandwidth
First connection shows 3 connection requests before the patch server acknowledges, then 2 more retransmissions before the client gives up.
Second attempt shows 4 connection requests before an acknowledgement. But the ACK is for something else, and the client rejects it with a reset. Then tries again a couple more times before giving up.
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 19 ms 99 ms 99 ms BThomehub.home []
2 15 ms 15 ms 15 ms 217.32.147.6
3 17 ms 17 ms 17 ms 217.32.147.46
4 19 ms 18 ms 19 ms 213.120.156.26
5 18 ms 18 ms 19 ms 217.41.168.239
6 18 ms 18 ms 19 ms 217.41.168.109
7 19 ms 19 ms 19 ms 109.159.249.250
8 21 ms 23 ms 23 ms core1-te0-0-0-16.faraday.ukcore.bt.net [109.159.
249.129]
9 20 ms 22 ms 23 ms host213-121-193-38.ukcore.bt.net [213.121.193.38
]
10 19 ms 19 ms 20 ms core1-pos5-0-0.telehouse.ukcore.bt.net [194.74.6
5.122]
11 165 ms 207 ms 210 ms 166-49-211-157.eu.bt.net [166.49.211.157]
12 20 ms 19 ms 19 ms t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.49]
13 20 ms 20 ms 20 ms te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.11
7.14.49]
14 20 ms 21 ms 20 ms te0-2-0-4.ccr21.lon13.atlas.cogentco.com [154.54
.57.114]
15 93 ms 93 ms 92 ms te0-7-0-27.ccr21.bos01.atlas.cogentco.com [154.5
4.1.93]
16 165 ms 201 ms 219 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
17 102 ms * * 38.111.40.114
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
When was the last official update on this problem, seems to be a while ago? I still can't get past the launcher issue. Once I got the white screen but that is all...
99.99% of players do not have to, but for some reason, some do -- we're trying to track down why this is, but in the meantime, players affected may need to update manually when we push a new launcher (as we did this afternoon). Thanks for your patience as we work to resolve the issue.
I'm on Verizon DSL in Maryland. Network dumps show multiple requests to establish a TCP connection, and then the update listener ignores the application level session requests. The intermittent server responses rule out large-scale problems with global routing--some of the packets are clearly making it to the server and some of them are coming back, so routing is working. The packets are dying at the cryptic network. Looks like the firewall is falling down, or the network bandwidth
First connection shows 3 connection requests before the patch server acknowledges, then 2 more retransmissions before the client gives up.
Second attempt shows 4 connection requests before an acknowledgement. But the ACK is for something else, and the client rejects it with a reset. Then tries again a couple more times before giving up.
Could be a firewall problem, maybe the update server is falling over, dunno
It's not the update server, or everyone - even those that use mobile networks would have the same issue. My conjecture is: it's an upstream load balancer.
I am curious as to what compensation will be offered by PWE/Cryptic for this downtime. As has been noted by many people, this is not a rare, one-off issue for STO. So, I would like the Developers to tell me what I can expect for this error.
Its been a few hours and you want compensation? Get off your ****in high horse the game is pretty much Free to Play unless you pay for the subscriptions, i'm pretty sure if you read the eula it will most likely say somewhere in there something about not being able to ensure 100% up-time due to technical difficulties, they do not owe you, or anyone who plays this game, ANYTHING. And if they do offer compensation, which i would assume they will as this hasn't happened in a long time It will most likely be some form of Q activity offering some kinda in-game costume item or xp boost, etc.
UK, Virgin Media - unable to connect to patch server, request timed out. Was fine before the patch today, never had this before.
Same. Can't even load the launcher.
I'm a bit cheesed off. I'm a subscriber. I expect that my subscription entitles me to access for the entire period I pay for. I can handle one or two problems, but this is probably something like the 50th time over the course of my nearly 3 year subscription that I have lost out on not an insignificant amount of game time...which is especially anmoying when you don't have loads of hours to play.
Bull ****.
Every time there is a thread like this someone spouts off on how they used to pay for it, and they were considering playing the game now that it is free, but because they happen to stumble onto a tech support thread for some reason, even though they are not even playing the game, they are just going to pass it up.
Bull **** sir, bull ****.
Seriously, believe what you want. (I just knew someone was going to say that.) I did have an account, in fact I was in the open beta. But I stopped the account not because of the game but because I wanted to play another game and didn't want to pay for two subs. So I dropped STO figuring if Star Wars TOR wasn't any good I could always resub). I recently entered my retirement phase from the military and since I'm on "terminal leave" I have a lot of free time at the moment. Decided to try STO again. Doesn't seem worth the sub, at the moment.
Now if my telling you that is unpleasant to you for some reason, well, so be it. But you have no cause for calling me a liar, just because you don't like what I have to say.
http://sto-forum.perfectworld.com/
guys I need help with this stuff I cant access the launcher and when I do it says my nets not working although it is working perfectly for more info of my problem see the link
1 17 ms 15 ms 14 ms **********
2 25 ms 22 ms 49 ms g5-2-13.bcptme07-rtr001.ne.northeast.rr.com [24.
31.156.58]
3 20 ms 20 ms 18 ms g10-4-3-0.ptldmehx-rtr001.ne.northeast.rr.com [2
04.210.69.238]
4 44 ms 37 ms 38 ms rdc-204-210-69-49.ne.northeast.rr.com [204.210.6
9.49]
5 41 ms 37 ms 47 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
6 36 ms 37 ms 39 ms ae-0-0.pr0.nyc20.tbone.rr.com [66.109.6.157]
7 38 ms 35 ms 38 ms te0-1-0-5.ccr21.jfk05.atlas.cogentco.com [154.54
.13.81]
8 33 ms 37 ms 38 ms te0-3-0-3.mpd21.jfk02.atlas.cogentco.com [154.54
.31.1]
9 42 ms 47 ms 43 ms te0-2-0-1.ccr21.bos01.atlas.cogentco.com [154.54
.44.10]
10 49 ms 50 ms 47 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 41 ms * * 208.95.185.41
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\Windows\system32>
For all those blaming this on the patch:
READ THE THREAD!!!
For those of us who did and realize this is a problem that was happening before the patch was up, we've had to wade through a whole lot of whining and useless nonsense to see if there was any actual helpful information.
Sheesh... :rolleyes:
The 1st posts today started 1.5 hours before the Update. Start reading HERE.
"Logic is a little tweeting bird chirping in a meadow. Logic is a wreath of pretty flowers which smell BAD." - Spock
As requested:For all those blaming this on the patch:
READ THE THREAD!!!
For those of us who did and realize this is a problem that was happening before the patch was up, we've had to wade through a whole lot of whining and useless nonsense to see if there was any actual helpful information.
Sheesh... :rolleyes:
i was still playing the game until the server went down for patching
Routenverfolgung zu patchserver.crypticstudios.com [208.95.185.41] ?ber maximal
30 Abschnitte:
1 1 ms 1 ms 1 ms 192.168.1.1
2 43 ms 44 ms 44 ms 217.0.116.42
3 46 ms 44 ms 46 ms 217.0.66.246
4 46 ms 45 ms 45 ms 217.239.41.94
5 45 ms 46 ms 46 ms te0-7-0-1.ccr21.fra03.atlas.cogentco.com [130.11
7.14.149]
6 84 ms 78 ms 85 ms te0-2-0-2.ccr21.ams03.atlas.cogentco.com [130.11
7.1.162]
7 74 ms 75 ms 74 ms te0-4-0-7.ccr21.lpl01.atlas.cogentco.com [154.54
.58.66]
8 130 ms 129 ms 129 ms te0-5-0-4.ccr21.bos01.atlas.cogentco.com [154.54
.85.213]
9 130 ms 169 ms 164 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
10 * * 132 ms 38.111.40.114
11 * * * Zeit?berschreitung der Anforderung.
12 * * * Zeit?berschreitung der Anforderung.
13 * * * Zeit?berschreitung der Anforderung.
14 * * * Zeit?berschreitung der Anforderung.
15 * * * Zeit?berschreitung der Anforderung.
16 * * * Zeit?berschreitung der Anforderung.
17 * * * Zeit?berschreitung der Anforderung.
18 * * * Zeit?berschreitung der Anforderung.
19 * * * Zeit?berschreitung der Anforderung.
20 * * * Zeit?berschreitung der Anforderung.
21 * * * Zeit?berschreitung der Anforderung.
22 132 ms * * 208.95.185.41
23 * * * Zeit?berschreitung der Anforderung.
24 * * * Zeit?berschreitung der Anforderung.
25 * * * Zeit?berschreitung der Anforderung.
26 * * * Zeit?berschreitung der Anforderung.
27 * * * Zeit?berschreitung der Anforderung.
28 * * * Zeit?berschreitung der Anforderung.
29 * * * Zeit?berschreitung der Anforderung.
30 * * * Zeit?berschreitung der Anforderung.
Its been a few hours and you want compensation? Get off your ****in high horse the game is pretty much Free to Play unless you pay for the subscriptions, i'm pretty sure if you read the eula it will most likely say somewhere in there something about not being able to ensure 100% up-time due to technical difficulties, they do not owe you, or anyone who plays this game, ANYTHING. And if they do offer compensation, which i would assume they will as this hasn't happened in a long time It will most likely be some form of Q activity offering some kinda in-game costume item or xp boost, etc.
I am not on a high horse. I have a Lifetime membership, which means I paid a substantial amont of real money. As I stated, I have had to contact this company before, which means that I have had other issues.
You do not know me. I do not wish for you to know me. I would like you to keep unwarranted opinions to yourself.
Kind Regards.
Comments
2 8 ms 7 ms 8 ms 217.32.142.0
3 7 ms 7 ms 7 ms 217.32.142.30
4 8 ms 7 ms 7 ms 213.120.163.70
5 8 ms 7 ms 8 ms 31.55.165.243
6 7 ms 7 ms 8 ms 31.55.165.109
7 7 ms 8 ms 7 ms acc2-10GigE-11-2-0.mr.21cn-ipp.bt.net [109.159.2
50.206]
8 15 ms 15 ms 19 ms core1-te0-3-5-0.ilford.ukcore.bt.net [109.159.25
0.141]
9 14 ms 14 ms 14 ms transit1-pos9-0.telehouse.ukcore.bt.net [62.6.20
1.118]
10 14 ms 14 ms 14 ms t2as1-tge4-4.uk-lon1.eu.bt.net [166.49.211.145]
11 14 ms 14 ms 14 ms t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.49]
12 17 ms 16 ms 17 ms te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.11
7.14.49]
13 16 ms 15 ms 14 ms te0-4-0-5.mpd21.lon13.atlas.cogentco.com [130.11
7.0.5]
14 90 ms 89 ms 88 ms te0-3-0-4.ccr21.bos01.atlas.cogentco.com [154.54
.30.129]
15 87 ms 87 ms 89 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
16 * * 97 ms 38.111.40.114
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * 87 ms 208.95.185.41
Trace complete.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Smiths>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms api.home [192.168.1.254]
2 7 ms 7 ms 8 ms 217.32.144.162
3 8 ms 9 ms 8 ms 217.32.144.190
4 10 ms 10 ms 10 ms 213.120.181.246
5 11 ms 9 ms 11 ms 217.41.169.209
6 12 ms 13 ms 11 ms 217.41.169.109
7 10 ms 10 ms 10 ms 109.159.251.195
8 22 ms 16 ms 20 ms core1-te0-13-0-2.ilford.ukcore.bt.net [109.159.2
51.137]
9 16 ms 16 ms 15 ms transit1-pos9-0.telehouse.ukcore.bt.net [62.6.20
1.118]
10 18 ms 17 ms 17 ms t2as1-tge4-4.uk-lon1.eu.bt.net [166.49.211.145]
11 17 ms 17 ms 17 ms t2a1-ge4-0-0.uk-lon1.eu.bt.net [166.49.135.17]
12 21 ms 18 ms 20 ms te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.11
7.14.49]
13 19 ms 19 ms 15 ms te0-4-0-5.ccr21.lon13.atlas.cogentco.com [154.54
.72.186]
14 91 ms 88 ms 91 ms te0-7-0-27.ccr21.bos01.atlas.cogentco.com [154.5
4.1.93]
15 91 ms 93 ms 93 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * 94 ms 208.95.185.41
Trace complete.
no point in posting a transcript, looks like they have enuf to get a clue. seems..
First connection shows 3 connection requests before the patch server acknowledges, then 2 more retransmissions before the client gives up.
Second attempt shows 4 connection requests before an acknowledgement. But the ACK is for something else, and the client rejects it with a reset. Then tries again a couple more times before giving up.
Could be a firewall problem, maybe the update server is falling over, dunno
C:\Windows\System32>tracert launcher.startrekonline.com
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 19 ms 99 ms 99 ms BThomehub.home []
2 15 ms 15 ms 15 ms 217.32.147.6
3 17 ms 17 ms 17 ms 217.32.147.46
4 19 ms 18 ms 19 ms 213.120.156.26
5 18 ms 18 ms 19 ms 217.41.168.239
6 18 ms 18 ms 19 ms 217.41.168.109
7 19 ms 19 ms 19 ms 109.159.249.250
8 21 ms 23 ms 23 ms core1-te0-0-0-16.faraday.ukcore.bt.net [109.159.
249.129]
9 20 ms 22 ms 23 ms host213-121-193-38.ukcore.bt.net [213.121.193.38
]
10 19 ms 19 ms 20 ms core1-pos5-0-0.telehouse.ukcore.bt.net [194.74.6
5.122]
11 165 ms 207 ms 210 ms 166-49-211-157.eu.bt.net [166.49.211.157]
12 20 ms 19 ms 19 ms t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.49]
13 20 ms 20 ms 20 ms te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.11
7.14.49]
14 20 ms 21 ms 20 ms te0-2-0-4.ccr21.lon13.atlas.cogentco.com [154.54
.57.114]
15 93 ms 93 ms 92 ms te0-7-0-27.ccr21.bos01.atlas.cogentco.com [154.5
4.1.93]
16 165 ms 201 ms 219 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
17 102 ms * * 38.111.40.114
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Fleet Captain
Starfleet Command Q2
http://www.starfleet-command.org.uk/
Star Trek Online Intro HD [3rd Fleet Anniversary]
Join Date: Jul 2009
Use a Proxy/VPN from another country like Spain for example (somewhere that doesn't have known issues), but make sure it's secure.
Or
Tether via your 3G network to patch, though if any in-game patching occurs during transition it will plonk you out.
Have a nice day.
I expect to see most of you back in game after Thursdays patch
#2311#2700#2316#2500
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 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 1 ms 1 ms 1 ms 192.168.1.1
2 258 ms 170 ms 179 ms cable-mac1.albynyyf-ar4004.nyroc.rr.com
3 180 ms 175 ms 229 ms gig1-2-12.albynyyf-rtr009.alb.northeast.rr.com [
24.29.47.197]
4 198 ms 164 ms 100 ms rdc-74-76-241-222.alb.northeast.rr.com [74.76.24
1.222]
5 206 ms 215 ms 215 ms rdc-74-76-241-193.alb.northeast.rr.com [74.76.24
1.193]
6 252 ms 143 ms 142 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
7 137 ms 201 ms 149 ms 107.14.19.147
8 139 ms 155 ms 190 ms te0-0-0-5.ccr21.jfk05.atlas.cogentco.com [154.54
.13.185]
9 140 ms 197 ms 132 ms te0-0-0-6.mpd22.jfk02.atlas.cogentco.com [154.54
.31.5]
10 158 ms 144 ms 153 ms te0-1-0-5.ccr21.bos01.atlas.cogentco.com [154.54
.44.30]
11 215 ms 185 ms 191 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * 221 ms * 208.95.185.41
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
99.99%? Oh god that's clearly untrue.
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 2 ms 1 ms 2 ms BThomehub.home [***.***.*.***]
2 16 ms 15 ms 15 ms 217.32.147.99
3 16 ms 15 ms 15 ms 217.32.147.126
4 20 ms 22 ms 19 ms 212.140.206.90
5 20 ms 19 ms 19 ms 217.41.169.251
6 19 ms 20 ms 20 ms 217.41.169.109
7 19 ms 19 ms 19 ms 109.159.251.235
8 29 ms 26 ms 27 ms core1-te0-12-0-6.ilford.ukcore.bt.net [109.159.2
51.133]
9 25 ms 25 ms 24 ms core1-pos9-1.telehouse.ukcore.bt.net [194.74.65.
114]
10 26 ms 25 ms 25 ms 166-49-211-153.eu.bt.net [166.49.211.153]
11 29 ms 27 ms 28 ms t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.49]
12 25 ms 27 ms 25 ms te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.11
7.14.49]
13 29 ms 30 ms 24 ms te0-2-0-4.ccr21.lon13.atlas.cogentco.com [154.54
.57.114]
14 101 ms 100 ms 100 ms te0-7-0-33.ccr21.bos01.atlas.cogentco.com [154.5
4.5.161]
15 100 ms 100 ms 101 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 * 124 ms 117 ms 38.111.40.114
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
I am in the UK, which I seem to see a lot of people in the UK hit by this issue.
clicky
the route has pretty much fallen off the face of the earth
It's not the update server, or everyone - even those that use mobile networks would have the same issue. My conjecture is: it's an upstream load balancer.
over a maximum of 30 hops:
1 * * * Request timed out.
2 8 ms 9 ms 8 ms 67.59.234.237
3 12 ms 12 ms 11 ms 67.83.233.13
4 15 ms 12 ms 12 ms 65.19.121.37
5 12 ms 12 ms 15 ms 64.15.1.46
6 * * * Request timed out.
7 15 ms 15 ms 15 ms te0-6-0-5.ccr21.jfk02.atlas.cogentco.com [154.54
.47.21]
8 20 ms 19 ms 21 ms te0-0-0-6.ccr22.bos01.atlas.cogentco.com [154.54
.6.9]
9 19 ms 18 ms 18 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
over a maximum of 30 hops:
2 71 ms 7 ms 8 ms dtr01dntntx-tge-0-0-1-2.dntn.tx.charter.com [96.34.113.92]
3 75 ms 9 ms 14 ms dtr01kllrtx-tge-0-0-1-0.kllr.tx.charter.com [96.34.112.78]
4 64 ms 9 ms 7 ms crr01nrictx-tge-0-1-1-3.nric.tx.charter.com [96.34.113.206]
5 63 ms 11 ms 12 ms crr01ftwotx-tge-0-3-0-5.ftwo.tx.charter.com [96.34.113.140]
6 62 ms 16 ms 15 ms bbr01dllstx-bue-2.dlls.tx.charter.com [96.34.2.32]
7 13 ms 11 ms 12 ms dls-bb1-link.telia.net [213.248.78.237]
8 13 ms 19 ms 14 ms bundle-ether100.ccr21.dfw03.atlas.cogentco.com [154.54.10.153]
9 13 ms 11 ms 13 ms te0-0-0-4.ccr21.dfw01.atlas.cogentco.com [154.54.6.57]
10 22 ms 24 ms 23 ms te0-2-0-6.ccr21.mci01.atlas.cogentco.com [154.54.46.185]
11 48 ms 47 ms 47 ms te0-4-0-3.ccr21.ord01.atlas.cogentco.com [154.54.6.157]
12 61 ms 63 ms 60 ms te0-3-0-6.ccr22.bos01.atlas.cogentco.com [154.54
.43.198] 13 60 ms 61 ms 59 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
14 73 ms * 81 ms 38.111.40.114
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Its been a few hours and you want compensation? Get off your ****in high horse the game is pretty much Free to Play unless you pay for the subscriptions, i'm pretty sure if you read the eula it will most likely say somewhere in there something about not being able to ensure 100% up-time due to technical difficulties, they do not owe you, or anyone who plays this game, ANYTHING. And if they do offer compensation, which i would assume they will as this hasn't happened in a long time It will most likely be some form of Q activity offering some kinda in-game costume item or xp boost, etc.
Same. Can't even load the launcher.
I'm a bit cheesed off. I'm a subscriber. I expect that my subscription entitles me to access for the entire period I pay for. I can handle one or two problems, but this is probably something like the 50th time over the course of my nearly 3 year subscription that I have lost out on not an insignificant amount of game time...which is especially anmoying when you don't have loads of hours to play.
Tracert :
C:\>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 192.168.0.1
2 8 ms 7 ms 7 ms 10.15.181.1
3 8 ms 7 ms 7 ms p55141.net.upc.nl [212.142.55.141]
4 12 ms 10 ms 10 ms 84.116.244.17
5 11 ms 10 ms 9 ms nl-ams04a-ri2-xe-0-0-0.aorta.net [84.116.132.218]
6 23 ms 10 ms 10 ms 213.46.182.18
7 154 ms 103 ms 102 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
8 97 ms 107 ms 97 ms internap-gw.ip4.tinet.net [77.67.77.54]
9 98 ms 97 ms 109 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
10 105 ms 107 ms 107 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\>
Nettest :
contacting nettest server..
Local IP: 77.250.236.249
Ping: 96.8 msec
Port: 80: 470 KB/sec 18 KB/sec 501 KB/sec 500
Port: 80: 614 KB/sec 18 KB/sec 649 KB/sec 500
Port: 443: 667 KB/sec 14 KB/sec 702 KB/sec 500
Port: 443: 611 KB/sec 14 KB/sec 644 KB/sec 500
Port: 7255: 613 KB/sec 15 KB/sec 648 KB/sec 500
Port: 7255: 651 KB/sec 15 KB/sec 685 KB/sec 500
Port: 7003: 661 KB/sec 14 KB/sec 696 KB/sec 500
Port: 7003: 713 KB/sec 16 KB/sec 751 KB/sec 500
Port: 7202: 607 KB/sec 14 KB/sec 640 KB/sec 500
Port: 7202: 577 KB/sec 13 KB/sec 608 KB/sec 500
Port: 7499: 396 KB/sec 11 KB/sec 416 KB/sec 500
Port: 7499: 477 KB/sec 12 KB/sec 502 KB/sec 500
Port: 80: 664 KB/sec 12 KB/sec 699 KB/sec 500
Idle NIC bandwidth Send: 2 KB/sec Recv: 1 KB/sec
hit return to exit
It could be a bigger problem as i have the same problem with the Champion online launcher.
But it's broken?
Seriously, believe what you want. (I just knew someone was going to say that.) I did have an account, in fact I was in the open beta. But I stopped the account not because of the game but because I wanted to play another game and didn't want to pay for two subs. So I dropped STO figuring if Star Wars TOR wasn't any good I could always resub). I recently entered my retirement phase from the military and since I'm on "terminal leave" I have a lot of free time at the moment. Decided to try STO again. Doesn't seem worth the sub, at the moment.
Now if my telling you that is unpleasant to you for some reason, well, so be it. But you have no cause for calling me a liar, just because you don't like what I have to say.
1 * * * Request timed out.
2 7 ms 9 ms 13 ms tge7-2.snantx2100-er02.texas.rr.com [*.*.*.*}
36]
3 21 ms 22 ms 15 ms tge0-8-0-3.snantx2000-tr02.texas.rr.com [24.175.
33.78]
4 22 ms 23 ms 23 ms agg22.snantx6000-cr01.texas.rr.com [24.175.32.16
8]
5 19 ms 23 ms 23 ms 24.175.32.146
6 25 ms 15 ms 15 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
7 15 ms 15 ms 61 ms 107.14.17.232
8 16 ms 18 ms 16 ms te0-7-0-15.ccr21.dfw03.atlas.cogentco.com [154.5
4.11.49]
9 16 ms 15 ms 17 ms multi-use.cogentco.com [154.54.88.70]
10 26 ms 27 ms 27 ms te0-3-0-0.mpd21.mci01.atlas.cogentco.com [154.54
.3.18]
11 43 ms 42 ms 41 ms te0-5-0-4.mpd21.ord01.atlas.cogentco.com [154.54
.45.154]
12 67 ms 79 ms 66 ms te0-3-0-6.ccr21.bos01.atlas.cogentco.com [154.54
.43.182]
13 67 ms 67 ms 67 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * 65 ms de.playstartrekonline.eu [208.95.185.44]
Trace complete
guys I need help with this stuff I cant access the launcher and when I do it says my nets not working although it is working perfectly for more info of my problem see the link
READ THE THREAD!!!
For those of us who did and realize this is a problem that was happening before the patch was up, we've had to wade through a whole lot of whining and useless nonsense to see if there was any actual helpful information.
Sheesh... :rolleyes:
The 1st posts today started 1.5 hours before the Update. Start reading HERE.
same provider here and mainly fine before this patch :eek:
i was still playing the game until the server went down for patching
DELTA PRICE RISING
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\User>tracert patchserver.crypticstudios.com
Routenverfolgung zu patchserver.crypticstudios.com [208.95.185.41] ?ber maximal
30 Abschnitte:
1 1 ms 1 ms 1 ms 192.168.1.1
2 43 ms 44 ms 44 ms 217.0.116.42
3 46 ms 44 ms 46 ms 217.0.66.246
4 46 ms 45 ms 45 ms 217.239.41.94
5 45 ms 46 ms 46 ms te0-7-0-1.ccr21.fra03.atlas.cogentco.com [130.11
7.14.149]
6 84 ms 78 ms 85 ms te0-2-0-2.ccr21.ams03.atlas.cogentco.com [130.11
7.1.162]
7 74 ms 75 ms 74 ms te0-4-0-7.ccr21.lpl01.atlas.cogentco.com [154.54
.58.66]
8 130 ms 129 ms 129 ms te0-5-0-4.ccr21.bos01.atlas.cogentco.com [154.54
.85.213]
9 130 ms 169 ms 164 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
10 * * 132 ms 38.111.40.114
11 * * * Zeit?berschreitung der Anforderung.
12 * * * Zeit?berschreitung der Anforderung.
13 * * * Zeit?berschreitung der Anforderung.
14 * * * Zeit?berschreitung der Anforderung.
15 * * * Zeit?berschreitung der Anforderung.
16 * * * Zeit?berschreitung der Anforderung.
17 * * * Zeit?berschreitung der Anforderung.
18 * * * Zeit?berschreitung der Anforderung.
19 * * * Zeit?berschreitung der Anforderung.
20 * * * Zeit?berschreitung der Anforderung.
21 * * * Zeit?berschreitung der Anforderung.
22 132 ms * * 208.95.185.41
23 * * * Zeit?berschreitung der Anforderung.
24 * * * Zeit?berschreitung der Anforderung.
25 * * * Zeit?berschreitung der Anforderung.
26 * * * Zeit?berschreitung der Anforderung.
27 * * * Zeit?berschreitung der Anforderung.
28 * * * Zeit?berschreitung der Anforderung.
29 * * * Zeit?berschreitung der Anforderung.
30 * * * Zeit?berschreitung der Anforderung.
Ablaufverfolgung beendet.
C:\Users\User>
Another PWE game update server just went down.
I was playing on PWI to wait for this game to be fixed, and I got DC and error message "unable to contact update server"
I wonder if someone pulled the wrong lead out of the wall ?
I am not on a high horse. I have a Lifetime membership, which means I paid a substantial amont of real money. As I stated, I have had to contact this company before, which means that I have had other issues.
You do not know me. I do not wish for you to know me. I would like you to keep unwarranted opinions to yourself.
Kind Regards.
Startrekonline.com keeps having these launcher failures.
Meanwhile http://sto.perfectworld.com/ continues to always work.
SOLUTION: change launcher update to http://sto.perfectworld.com/
I would think this was par for the course since we had to update our accounts to PWE.
10 46 ms * * 38.111.40.114