I can resolve the name but the connection is timing out. I'm in Michigan and use Charter. This has been going on since last night so it's not the patch.
The team is continuing to investigate. There are tons of players in-game, and tons more loading in, so it's not affecting everyone.
Cheers,
Brandon =/\=
This Maybe, but by the looks of this thread there are "Tons" of us from all over who are SOL. I can tell be my speed tests that my service isnt the problem and i was on BEFORE the 'update' so just what DID you guys do? Should those of us who are down just "re-down load" the game for a quicker solution? I'll add in my "test" results, but I dont see that as the problem helper here...
I just get a time out and fail to connect message for the most part... here's hoping its resolved soon...
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 4 ms L100.BFLONY-VFTTP-04.verizon-gni.net [71.186.236
.1]
3 8 ms 5 ms 6 ms G9-1-1204.BFLONY-LCR-02.verizon-gni.net [130.81.
185.168]
4 18 ms 16 ms 17 ms so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81
.28.136]
5 17 ms 18 ms 18 ms 0.so-4-3-0.XT2.NYC9.ALTER.NET [152.63.10.5]
6 27 ms 36 ms 29 ms 0.so-7-1-0.XL4.BOS4.ALTER.NET [152.63.0.221]
7 30 ms 26 ms 26 ms POS7-0.GW5.BOS4.ALTER.NET [152.63.25.57]
8 25 ms 25 ms 25 ms internap-gw.customer.alter.net [65.207.236.58]
9 27 ms 26 ms 26 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
10 30 ms 35 ms 34 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
11 * * * Request timed out.
12 * 28 ms * 208.95.185.41
13 * * * Request timed out.
14 * 28 ms * 208.95.185.41
15 30 ms * * 208.95.185.41
16 29 ms * * 208.95.185.41
17 * * * Request timed out.
18 27 ms * * 208.95.185.41
19 * * * Request timed out.
20 * * * Request timed out.
21 27 ms 27 ms * 208.95.185.41
22 * * * Request timed out.
23 * 28 ms * 208.95.185.41
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 27 ms 28 ms * 208.95.185.41
30 * *
contacting nettest server..
Local IP: 96.243.31.12
Ping: 29.1 msec
Port: 80: 1158 KB/sec 33 KB/sec 1224 KB/sec 500
Port: 80: timed out
Port: 443: timed out
Port: 443: 1755 KB/sec 42 KB/sec 1859 KB/sec 500
Port: 7255: 1794 KB/sec 42 KB/sec 1899 KB/sec 500
Port: 7255: 1687 KB/sec 40 KB/sec 1786 KB/sec 500
Port: 7003: 1846 KB/sec 39 KB/sec 1955 KB/sec 500
Port: 7003: 2073 KB/sec 54 KB/sec 2199 KB/sec 500
Port: 7202: 2239 KB/sec 55 KB/sec 2374 KB/sec 500
Port: 7202: 2319 KB/sec 53 KB/sec 2461 KB/sec 500
Port: 7499: 2012 KB/sec 44 KB/sec 2133 KB/sec 500
Port: 7499: 2052 KB/sec 40 KB/sec 2175 KB/sec 500
Port: 80: 2339 KB/sec 57 KB/sec 2480 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
Captains, as I've mentioned, the team is continuing to investigate. This started occurring before the patch, so it's not related. The reason I'm letting you know that "there are a ton of players in-game" is to provide more transparency on the issue and to let you know that it does not seem to be affecting everyone. There is no ETA I can provide, and I will continue to update you as I receive more information.
Before this whole mess went down, my service provider had no problem with connecting to "STO". Now the game launcher doesn't even load.
If this many people are having issues, the only logical explanation would be on Cryptic's end.
It's technically not Cryptic's fault...
If you look at all the tracerts listed so far, most of them are timing out at the Boston, Massachusetts (bos)cogent.co connection...
Something there is the culprit.
I've noticed before with other tracerts of my own, that the connection there tends to be a bit of a bottleneck.
STO Member since February 2009. I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born! Forever a STO Veteran-Minion
1 <1 ms <1 ms 1 ms alice.box [TRIBBLE]
2 21 ms 21 ms 22 ms rdsl-essn-de01.nw.mediaways.net [213.20.58.2]
3 22 ms 21 ms 22 ms xmwc-essn-de01-chan-18.nw.mediaways.net [62.53.159.226]
4 21 ms 22 ms 21 ms rmwc-essn-de01-gigaet-11-0-0.nw.mediaways.net [213.20.53.161]
5 25 ms 25 ms 26 ms rmwc-frnk-de01-ge-5-0-0-0.nw.mediaways.net [195.71.254.113]
6 44 ms 44 ms 119 ms 176.52.173.177
7 50 ms 53 ms 50 ms 84.16.13.234
8 50 ms 51 ms 51 ms 195.50.90.129
9 61 ms 58 ms 67 ms ae-51-51.csw1.London1.Level3.net [4.69.139.88]
10 57 ms 58 ms 57 ms ae-118-3504.edge3.London1.Level3.net [4.69.166.142]
11 64 ms 64 ms 66 ms te0-7-0-1.ccr21.lon01.atlas.cogentco.com [130.117.15.241]
12 63 ms 65 ms 62 ms te0-1-0-4.ccr21.lon13.atlas.cogentco.com [154.54.57.106]
13 128 ms 129 ms 128 ms te0-7-0-27.ccr21.bos01.atlas.cogentco.com [154.54.1.93]
14 179 ms 207 ms 211 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
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 * * * Zeit?berschreitung der Anforderung.
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 116 ms * * 208.95.185.41
30 * * * Zeit?berschreitung der Anforderung.
Ping statistics for 208.95.185.44:
Packets: Sent = 36, Received = 2, Lost = 34 (94% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 30ms, Average = 30ms
Seriously, what's with the finger pointing out of house? Cryptic's software worked fine before they "fixed" things, and now, after a "fix" they want to say that it's an ISP fault? Seems kinda donkeyish to me.
Please don't buy into the "it's not our fault" line. I have empathy for the devs, but no respect for shirking responsibility.
To be fair, this thread is chock full of evidence that would heavily suggest it very much is the fault of an ISP, at least for the majority. They aren't shirking anything, it's just that the facts support the hypothesis that it's not directly something Cryptic has done. It has been like this for some of us since before today's patch, after all.
So just chill out, cynicism won't help it get fixed any quicker
Before this whole mess went down, my service provider had no problem with connecting to "STO". Now the game launcher doesn't even load.
If this many people are having issues, the only logical explanation would be on Cryptic's end.
Thank god someone knows the answer!
Now we just have to find the guy with the time traveling gun that caused the problem to begin hours before the patching even began for those of us who have had this problem all morning..:)
Captains, as I've mentioned, the team is continuing to investigate. This started occurring before the patch, so it's not related. The reason I'm letting you know that "there are a ton of players in-game" is to provide more transparency on the issue and to let you know that it does not seem to be affecting everyone. There is no ETA I can provide, and I will continue to update you as I receive more information.
Here is a tracert, and I also did a few pings to illustrate that the problem is intermittent. I think there is a routing issue at work somewhere here. Something like this: http://en.wikipedia.org/wiki/Route_flapping
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.belkin [192.168.2.1]
2 * * * Request timed out.
3 41 ms 34 ms 45 ms 433be0b9.cst.lightpath.net [67.59.224.185]
4 16 ms 12 ms 30 ms rtr3-ge1-10.mhe.hcvlny.cv.net [167.206.39.141]
5 25 ms 16 ms 18 ms 64.15.2.21
6 11 ms 12 ms 11 ms 64.15.1.54
7 * * * Request timed out.
8 49 ms 12 ms 12 ms te0-1-0-2.mpd22.jfk02.atlas.cogentco.com [154.54
.1.161]
9 22 ms 18 ms 18 ms te0-4-0-3.ccr21.bos01.atlas.cogentco.com [154.54
.44.18]
10 21 ms 21 ms 18 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
11 30 ms 21 ms 29 ms 38.111.40.114
12 * * * Request timed out.
13 20 ms * * 208.95.185.41
14 21 ms * * 208.95.185.41
15 * * 19 ms 208.95.185.41
Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 208.95.185.41: bytes=32 time=17ms TTL=46
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 17ms, Average = 17ms
Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=19ms TTL=50
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 19ms, Average = 19ms
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 156 ms 186 ms 170 ms 027fef76.bb.sky.com [2.127.239.118]
3 58 ms 56 ms 58 ms 027fed72.bb.sky.com [2.127.237.114]
4 161 ms 190 ms 193 ms 5adfcf02.bb.sky.com [**.***.***.*]
5 122 ms 236 ms 142 ms 5adfcf02.bb.sky.com [**.***.***.*]
6 82 ms 100 ms 76 ms ae-3.r02.londen03.uk.bb.gin.ntt.net [83.231.221.
45]
7 195 ms 244 ms 244 ms te2-4.ccr01.lon02.atlas.cogentco.com [130.117.14
.249]
8 141 ms 109 ms 151 ms te0-0-0-2.ccr21.lon01.atlas.cogentco.com [130.11
7.1.157]
9 78 ms 74 ms 71 ms te0-0-0-2.ccr21.lon01.atlas.cogentco.com [130.11
7.1.157]
10 80 ms 187 ms 150 ms te0-7-0-27.ccr21.bos01.atlas.cogentco.com [154.5
4.1.93]
11 152 ms 152 ms 150 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
12 * * 215 ms 38.111.40.114
13 194 ms * * 38.111.40.114
14 235 ms * * 208.95.185.41
15 * * * Request timed out.
16 * * * Request timed out.
17 * * 155 ms 208.95.185.41
I was getting kicked over an hour before the maintenance started due to a patching timing out issue, so the problem was there before the maintenance started, unless they started maintenance early while we were still playing....:(
1 <1 ms 1 ms <1 ms speedport.ip [192.168.2.1]
2 17 ms 17 ms 17 ms 217.0.119.85
3 21 ms 19 ms 18 ms 217.0.65.250
4 27 ms 34 ms 26 ms f-ed6-i.F.DE.NET.DTAG.DE [62.156.131.250] 5 26 ms 26 ms 26 ms te0-7-0-7.ccr21.fra03.atlas.cogentco.com [130.11
7.14.105]
6 49 ms 35 ms 34 ms te0-2-0-2.ccr21.ams03.atlas.cogentco.com [130.11
7.1.162]
7 54 ms 54 ms 54 ms te0-3-0-7.ccr21.lpl01.atlas.cogentco.com [154.54
.37.98]
8 110 ms 110 ms 110 ms te0-5-0-4.ccr21.bos01.atlas.cogentco.com [154.54
.85.213]
9 110 ms 110 ms 111 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
10 * * * Zeit?berschreitung der Anforderung.
11 * * * Zeit?berschreitung der Anforderung.
12 * * * Zeit?berschreitung der Anforderung.
13 * * * Zeit?berschreitung der Anforderung.
I can resolve the name but the connection is timing out. I'm in Michigan and use Charter. This has been going on since last night so it's not the patch.
The issue seems to just after cogent side of things and tracing the fault might take some time.
***Released new patch to fix NPC's atacking players at drozana station.***
**Resulting patch has led to the launcher not launching.....SOUND RED ALERT!!!..were out of coffee*
**Coffee supply has been replenished a disaster averted so it is time to fix the problem..if only we could remember what the problem was in the first place, oh well it will come to us...eventually**
**Finally remembered the problem was something to do with the launcher but cant figure out how to fix it...i wonder if anyone got around to feeding the server hamsters last week..hmm*
**Launcher still not working we cant figure out what we did or how to fix it so we should just...blame the players and see if we can talk them into fixing it for us**
***Just found out we forgot to feed server hamsters must go to pet store to get more trained server hamsters to power our servers**
**Players getting angry want progress updates what to do..I KNOW!! we take a nap after we drain our juice boxes**
That was a cracking piece of PR to sooth the mob baying for your blood. Tell them there's tons of players in game .....Wonderful !! ....Its the tons of people that CANT get in the game that need the soothing buddy.
Captains, as I've mentioned, the team is continuing to investigate. This started occurring before the patch, so it's not related. The reason I'm letting you know that "there are a ton of players in-game" is to provide more transparency on the issue and to let you know that it does not seem to be affecting everyone. There is no ETA I can provide, and I will continue to update you as I receive more information.
Cheers,
Brandon =/\=
Thank you, that is a post that should have happened 30 min. ago.....
The idea that "Tons of people" are in game is even more infuriating though. If you want transparency, maybe tell us what you are doing instead of just saying that they are investigating..... well what are they investigating?
Because right now we are getting the feeling that you have NO IDEA what is going on several hours after the problem first appeared (it is several hours since you said it started before the patch.)
And spending hours investigating, and you still have no idea what the cause is is rather concerning. Where did the $500 I've put into this game go if you can't even figureout what the problem is in a reasonable amount of time?
Hope this will help a bit...
Location: Cracow, Poland
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 4 ms 1 ms 192.168.1.1
2 33 ms 14 ms 14 ms 89-78-120-1.dynamic.chello.pl [89.78.120.1]
3 10 ms 48 ms 31 ms 89-75-4-65.infra.chello.pl [89.75.4.65]
4 53 ms 36 ms 40 ms pl-krk01a-rd4-ae0-2183.aorta.net [84.116.253.70]
5 * * * Request timed out.
6 40 ms 36 ms 38 ms 84.116.137.205
7 36 ms 37 ms 52 ms de-fra01a-ri2-xe-4-1-0.aorta.net [84.116.130.146]
8 60 ms 71 ms 37 ms xe-5-1-1.fra23.ip4.tinet.net [77.67.73.105]
9 138 ms 149 ms 155 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
10 254 ms 213 ms 219 ms internap-gw.ip4.tinet.net [77.67.77.54]
11 138 ms 131 ms 129 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
Other requests are timed out.
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 78 ms 18 ms 24 ms 89-78-120-1.dynamic.chello.pl [89.78.120.1]
3 12 ms 9 ms 10 ms 89-75-4-65.infra.chello.pl [89.75.4.65]
4 40 ms 37 ms 37 ms pl-krk01a-rd4-ae0-2183.aorta.net [84.116.253.70]
5 * 40 ms 36 ms pl-waw04a-rd1-ae12-2158.aorta.net [84.116.252.225]
6 56 ms 40 ms 35 ms 84.116.134.193
7 59 ms 40 ms 36 ms de-fra01a-ri2-xe-4-1-0.aorta.net [84.116.130.146]
8 43 ms 61 ms 77 ms xe-5-1-1.fra23.ip4.tinet.net [77.67.73.105]
9 149 ms 170 ms 141 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
10 168 ms 133 ms 144 ms internap-gw.ip4.tinet.net [77.67.77.54]
11 184 ms 154 ms 161 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
12 159 ms 143 ms 144 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
Other requests are timed out.
I've been running periodic a tracert with no change beyond the one I previously posted. I'm in Boston (Arlington actually). There's no other internet-related issues here that I can notice (Verizon FIOS here).
Funny how things go wrong when you patch things. It's becoming a pattern:D haha! Anyway, I've noticed i cannot get on the website for sto on chrome but on others like Firefox and EE no problem:eek:
It's something to do with their end and not us. I've called my isp and they said it's fine.
Routenverfolgung zu launcher.startrekonline.com [208.95.185.44] ?ber maximal 30
Abschnitte:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 6 ms 6 ms 10.149.64.1
3 24 ms 6 ms 6 ms 7111A-MX960-01-ae10-1410.fra.unity-media.net [81
.210.130.17]
4 6 ms 7 ms 5 ms 84-116-131-149.aorta.net [84.116.131.149]
5 8 ms 7 ms 5 ms 84.116.132.161
6 7 ms 6 ms 13 ms 84.116.132.166
7 19 ms 7 ms 7 ms xe-10-2-2.fra23.ip4.tinet.net [141.136.99.97]
8 110 ms 109 ms 110 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
9 103 ms 103 ms 105 ms internap-gw.ip4.tinet.net [77.67.77.54]
10 105 ms 103 ms 104 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
11 107 ms 107 ms 107 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
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 * * * Zeit?berschreitung der Anforderung.
23 * * * Zeit?berschreitung der Anforderung.
24 * * * Zeit?berschreitung der Anforderung.
25 * * * Zeit?berschreitung der Anforderung.
26 * * * Zeit?berschreitung der Anforderung.
27 * ^C
C:\Users>
Comments
No other report of cogent having issues exists. If this were a network issue it wouldn't be limited to STO.
http://status.cogentco.com/
So, Cogent says, no problem, Cryptic says no problem. What are we to say? No Problem?
PrePatch breaking things?
This Maybe, but by the looks of this thread there are "Tons" of us from all over who are SOL. I can tell be my speed tests that my service isnt the problem and i was on BEFORE the 'update' so just what DID you guys do? Should those of us who are down just "re-down load" the game for a quicker solution? I'll add in my "test" results, but I dont see that as the problem helper here...
I just get a time out and fail to connect message for the most part... here's hoping its resolved soon...
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 4 ms L100.BFLONY-VFTTP-04.verizon-gni.net [71.186.236
.1]
3 8 ms 5 ms 6 ms G9-1-1204.BFLONY-LCR-02.verizon-gni.net [130.81.
185.168]
4 18 ms 16 ms 17 ms so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81
.28.136]
5 17 ms 18 ms 18 ms 0.so-4-3-0.XT2.NYC9.ALTER.NET [152.63.10.5]
6 27 ms 36 ms 29 ms 0.so-7-1-0.XL4.BOS4.ALTER.NET [152.63.0.221]
7 30 ms 26 ms 26 ms POS7-0.GW5.BOS4.ALTER.NET [152.63.25.57]
8 25 ms 25 ms 25 ms internap-gw.customer.alter.net [65.207.236.58]
9 27 ms 26 ms 26 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
10 30 ms 35 ms 34 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
11 * * * Request timed out.
12 * 28 ms * 208.95.185.41
13 * * * Request timed out.
14 * 28 ms * 208.95.185.41
15 30 ms * * 208.95.185.41
16 29 ms * * 208.95.185.41
17 * * * Request timed out.
18 27 ms * * 208.95.185.41
19 * * * Request timed out.
20 * * * Request timed out.
21 27 ms 27 ms * 208.95.185.41
22 * * * Request timed out.
23 * 28 ms * 208.95.185.41
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 27 ms 28 ms * 208.95.185.41
30 * *
contacting nettest server..
Local IP: 96.243.31.12
Ping: 29.1 msec
Port: 80: 1158 KB/sec 33 KB/sec 1224 KB/sec 500
Port: 80: timed out
Port: 443: timed out
Port: 443: 1755 KB/sec 42 KB/sec 1859 KB/sec 500
Port: 7255: 1794 KB/sec 42 KB/sec 1899 KB/sec 500
Port: 7255: 1687 KB/sec 40 KB/sec 1786 KB/sec 500
Port: 7003: 1846 KB/sec 39 KB/sec 1955 KB/sec 500
Port: 7003: 2073 KB/sec 54 KB/sec 2199 KB/sec 500
Port: 7202: 2239 KB/sec 55 KB/sec 2374 KB/sec 500
Port: 7202: 2319 KB/sec 53 KB/sec 2461 KB/sec 500
Port: 7499: 2012 KB/sec 44 KB/sec 2133 KB/sec 500
Port: 7499: 2052 KB/sec 40 KB/sec 2175 KB/sec 500
Port: 80: 2339 KB/sec 57 KB/sec 2480 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
Cheers,
Brandon =/\=
Still a network issue just beyond cogent..
The problems started BEFORE the patch was issued.
It's technically not Cryptic's fault...
If you look at all the tracerts listed so far, most of them are timing out at the Boston, Massachusetts (bos)cogent.co connection...
Something there is the culprit.
I've noticed before with other tracerts of my own, that the connection there tends to be a bit of a bottleneck.
I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born!
Forever a STO Veteran-Minion
1 <1 ms <1 ms 1 ms alice.box [TRIBBLE]
2 21 ms 21 ms 22 ms rdsl-essn-de01.nw.mediaways.net [213.20.58.2]
3 22 ms 21 ms 22 ms xmwc-essn-de01-chan-18.nw.mediaways.net [62.53.159.226]
4 21 ms 22 ms 21 ms rmwc-essn-de01-gigaet-11-0-0.nw.mediaways.net [213.20.53.161]
5 25 ms 25 ms 26 ms rmwc-frnk-de01-ge-5-0-0-0.nw.mediaways.net [195.71.254.113]
6 44 ms 44 ms 119 ms 176.52.173.177
7 50 ms 53 ms 50 ms 84.16.13.234
8 50 ms 51 ms 51 ms 195.50.90.129
9 61 ms 58 ms 67 ms ae-51-51.csw1.London1.Level3.net [4.69.139.88]
10 57 ms 58 ms 57 ms ae-118-3504.edge3.London1.Level3.net [4.69.166.142]
11 64 ms 64 ms 66 ms te0-7-0-1.ccr21.lon01.atlas.cogentco.com [130.117.15.241]
12 63 ms 65 ms 62 ms te0-1-0-4.ccr21.lon13.atlas.cogentco.com [154.54.57.106]
13 128 ms 129 ms 128 ms te0-7-0-27.ccr21.bos01.atlas.cogentco.com [154.54.1.93]
14 179 ms 207 ms 211 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
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 * * * Zeit?berschreitung der Anforderung.
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 116 ms * * 208.95.185.41
30 * * * Zeit?berschreitung der Anforderung.
Ablaufverfolgung beendet.
good luck in finding the problem, detectives!
Best,
D
Ping statistics for 208.95.185.44:
Packets: Sent = 36, Received = 2, Lost = 34 (94% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 30ms, Average = 30ms
Delirium Tremens
Tier 4 Starbase, Tier 3 Embassy
http://dtfleet.com/
To be fair, this thread is chock full of evidence that would heavily suggest it very much is the fault of an ISP, at least for the majority. They aren't shirking anything, it's just that the facts support the hypothesis that it's not directly something Cryptic has done. It has been like this for some of us since before today's patch, after all.
So just chill out, cynicism won't help it get fixed any quicker
Thank god someone knows the answer!
Now we just have to find the guy with the time traveling gun that caused the problem to begin hours before the patching even began for those of us who have had this problem all morning..:)
(Yes, that was sarcasm.)
Thanks, sir.
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 <1 ms <1 ms <1 ms 192.168.0.1
2 156 ms 186 ms 170 ms 027fef76.bb.sky.com [2.127.239.118]
3 58 ms 56 ms 58 ms 027fed72.bb.sky.com [2.127.237.114]
4 161 ms 190 ms 193 ms 5adfcf02.bb.sky.com [**.***.***.*]
5 122 ms 236 ms 142 ms 5adfcf02.bb.sky.com [**.***.***.*]
6 82 ms 100 ms 76 ms ae-3.r02.londen03.uk.bb.gin.ntt.net [83.231.221.
45]
7 195 ms 244 ms 244 ms te2-4.ccr01.lon02.atlas.cogentco.com [130.117.14
.249]
8 141 ms 109 ms 151 ms te0-0-0-2.ccr21.lon01.atlas.cogentco.com [130.11
7.1.157]
9 78 ms 74 ms 71 ms te0-0-0-2.ccr21.lon01.atlas.cogentco.com [130.11
7.1.157]
10 80 ms 187 ms 150 ms te0-7-0-27.ccr21.bos01.atlas.cogentco.com [154.5
4.1.93]
11 152 ms 152 ms 150 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
12 * * 215 ms 38.111.40.114
13 194 ms * * 38.111.40.114
14 235 ms * * 208.95.185.41
15 * * * Request timed out.
16 * * * Request timed out.
17 * * 155 ms 208.95.185.41
Trace complete.
C:\Windows\system32>
Your cogento server knot !!
1 <1 ms 1 ms <1 ms speedport.ip [192.168.2.1]
2 17 ms 17 ms 17 ms 217.0.119.85
3 21 ms 19 ms 18 ms 217.0.65.250
4 27 ms 34 ms 26 ms f-ed6-i.F.DE.NET.DTAG.DE [62.156.131.250]
5 26 ms 26 ms 26 ms te0-7-0-7.ccr21.fra03.atlas.cogentco.com [130.11
7.14.105]
6 49 ms 35 ms 34 ms te0-2-0-2.ccr21.ams03.atlas.cogentco.com [130.11
7.1.162]
7 54 ms 54 ms 54 ms te0-3-0-7.ccr21.lpl01.atlas.cogentco.com [154.54
.37.98]
8 110 ms 110 ms 110 ms te0-5-0-4.ccr21.bos01.atlas.cogentco.com [154.54
.85.213]
9 110 ms 110 ms 111 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
10 * * * Zeit?berschreitung der Anforderung.
11 * * * Zeit?berschreitung der Anforderung.
12 * * * Zeit?berschreitung der Anforderung.
13 * * * Zeit?berschreitung der Anforderung.
The issue seems to just after cogent side of things and tracing the fault might take some time.
***Released new patch to fix NPC's atacking players at drozana station.***
**Resulting patch has led to the launcher not launching.....SOUND RED ALERT!!!..were out of coffee*
**Coffee supply has been replenished a disaster averted so it is time to fix the problem..if only we could remember what the problem was in the first place, oh well it will come to us...eventually**
**Finally remembered the problem was something to do with the launcher but cant figure out how to fix it...i wonder if anyone got around to feeding the server hamsters last week..hmm*
**Launcher still not working we cant figure out what we did or how to fix it so we should just...blame the players and see if we can talk them into fixing it for us**
***Just found out we forgot to feed server hamsters must go to pet store to get more trained server hamsters to power our servers**
**Players getting angry want progress updates what to do..I KNOW!! we take a nap after we drain our juice boxes**
That's not the only place they're having connection issues. My trace got stopped at Perfect World's connection:
perfectworldent-4.border11.bsn.pnap.net
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\********>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 Wireless_Broadband_Router.home [***.***.*.*]
2 7 ms 7 ms 8 ms L100.BLTMMD-VFTTP-46.verizon-gni.net [96.244.246
.1]
3 9 ms 7 ms 7 ms G0-10-3-5.BLTMMD-LCR-22.verizon-gni.net [130.81.
215.138]
4 13 ms 12 ms 11 ms so-6-1-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
199.4]
5 33 ms 23 ms 13 ms so-0-2-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.
7.186]
6 17 ms 17 ms 16 ms 0.xe-8-0-0.XL4.NYC1.ALTER.NET [152.63.5.217]
7 23 ms 21 ms 22 ms 0.ge-3-1-0.XL4.BOS4.ALTER.NET [152.63.20.218]
8 26 ms 22 ms 21 ms POS6-0.GW5.BOS4.ALTER.NET [152.63.25.69]
9 37 ms 39 ms 42 ms internap-gw.customer.alter.net [65.207.236.58]
10 33 ms 39 ms 32 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
11 31 ms 34 ms 37 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
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 * *
...looks like its dropping at the gateway to me.
Thank you, that is a post that should have happened 30 min. ago.....
The idea that "Tons of people" are in game is even more infuriating though. If you want transparency, maybe tell us what you are doing instead of just saying that they are investigating..... well what are they investigating?
Because right now we are getting the feeling that you have NO IDEA what is going on several hours after the problem first appeared (it is several hours since you said it started before the patch.)
And spending hours investigating, and you still have no idea what the cause is is rather concerning. Where did the $500 I've put into this game go if you can't even figureout what the problem is in a reasonable amount of time?
Location: Cracow, Poland
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 4 ms 1 ms 192.168.1.1
2 33 ms 14 ms 14 ms 89-78-120-1.dynamic.chello.pl [89.78.120.1]
3 10 ms 48 ms 31 ms 89-75-4-65.infra.chello.pl [89.75.4.65]
4 53 ms 36 ms 40 ms pl-krk01a-rd4-ae0-2183.aorta.net [84.116.253.70]
5 * * * Request timed out.
6 40 ms 36 ms 38 ms 84.116.137.205
7 36 ms 37 ms 52 ms de-fra01a-ri2-xe-4-1-0.aorta.net [84.116.130.146]
8 60 ms 71 ms 37 ms xe-5-1-1.fra23.ip4.tinet.net [77.67.73.105]
9 138 ms 149 ms 155 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
10 254 ms 213 ms 219 ms internap-gw.ip4.tinet.net [77.67.77.54]
11 138 ms 131 ms 129 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
Other requests are timed out.
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 78 ms 18 ms 24 ms 89-78-120-1.dynamic.chello.pl [89.78.120.1]
3 12 ms 9 ms 10 ms 89-75-4-65.infra.chello.pl [89.75.4.65]
4 40 ms 37 ms 37 ms pl-krk01a-rd4-ae0-2183.aorta.net [84.116.253.70]
5 * 40 ms 36 ms pl-waw04a-rd1-ae12-2158.aorta.net [84.116.252.225]
6 56 ms 40 ms 35 ms 84.116.134.193
7 59 ms 40 ms 36 ms de-fra01a-ri2-xe-4-1-0.aorta.net [84.116.130.146]
8 43 ms 61 ms 77 ms xe-5-1-1.fra23.ip4.tinet.net [77.67.73.105]
9 149 ms 170 ms 141 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
10 168 ms 133 ms 144 ms internap-gw.ip4.tinet.net [77.67.77.54]
11 184 ms 154 ms 161 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
12 159 ms 143 ms 144 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
Other requests are timed out.
As has been shown, some packets ARE getting through, but then the next being blocked.
It's something to do with their end and not us. I've called my isp and they said it's fine.
Routenverfolgung zu launcher.startrekonline.com [208.95.185.44] ?ber maximal 30
Abschnitte:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 6 ms 6 ms 10.149.64.1
3 24 ms 6 ms 6 ms 7111A-MX960-01-ae10-1410.fra.unity-media.net [81
.210.130.17]
4 6 ms 7 ms 5 ms 84-116-131-149.aorta.net [84.116.131.149]
5 8 ms 7 ms 5 ms 84.116.132.161
6 7 ms 6 ms 13 ms 84.116.132.166
7 19 ms 7 ms 7 ms xe-10-2-2.fra23.ip4.tinet.net [141.136.99.97]
8 110 ms 109 ms 110 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
9 103 ms 103 ms 105 ms internap-gw.ip4.tinet.net [77.67.77.54]
10 105 ms 103 ms 104 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
11 107 ms 107 ms 107 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
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 * * * Zeit?berschreitung der Anforderung.
23 * * * Zeit?berschreitung der Anforderung.
24 * * * Zeit?berschreitung der Anforderung.
25 * * * Zeit?berschreitung der Anforderung.
26 * * * Zeit?berschreitung der Anforderung.
27 * ^C
C:\Users>
I had never issues, but now!