Yes. The problem seems to be especially bad in Texas/Central Texas, and more specifically there seems to be a latency/connection issue at a server hop in Dallas run by Cogentco. A lot of people that are having this problem are using Time Warner Cable as their ISP so it may be a connection issue between Time Warner Cable and Cogentco that is causing this problem. Cogentco nor PWE/Cryptic have acknowledged this problem and I doubt if any communication has been established between Cogentco and PWE to try to solve this issue. At this point in time the game is completely unplayable for me due to connection issues.
"Critics who say that the optimistic utopia Star Trek depicted is now outmoded forget the cultural context that gave birth to it: Star Trek was not a manifestation of optimism when optimism was easy. Star Trek declared a hope for a future that nobody stuck in the present could believe in. For all our struggles today, we haven’t outgrown the need for stories like Star Trek. We need tales of optimism, of heroes, of courage and goodness now as much as we’ve ever needed them." -Thomas Marrone
So I found this elsewhere in this particular forum. And here are my results. Why am I posting this? I am also South Texas / Time Warner. The problem is not us. Follow along...
( the following quote was trimmed for this post )
Here are my results: please note, I have "outstanding" results all the way through Time Warner. It isn't until TWO HOPS from the final server (which would be CRYPTIC'S ISP, not ours) that I get "Report any values above 180ms.
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 16 ms 10 ms 10 ms 10.77.36.1
3 12 ms 14 ms 14 ms tge7-1.snantx1400-er02.texas.rr.com [24.28.133.2
40]
4 30 ms 19 ms 31 ms tge0-8-0-9.snantx1000-tr02.texas.rr.com [24.175.
33.62]
5 21 ms 22 ms 20 ms 24.175.32.152
6 30 ms * 27 ms ae23.dllatxl3-cr01.texas.rr.com [24.175.32.146]
7 22 ms 21 ms 20 ms 107.14.17.136
8 22 ms 24 ms 19 ms ae-3-0.pr0.dfw10.tbone.rr.com [66.109.6.209]
9 17 ms 21 ms 17 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.
49]
10 16 ms 18 ms 25 ms te0-0-0-4.ccr21.dfw01.atlas.cogentco.com [154.54
.6.57]
11 32 ms 27 ms 35 ms te0-2-0-1.mpd21.mci01.atlas.cogentco.com [154.54
.5.218]
12 41 ms 40 ms 39 ms te0-2-0-3.mpd21.ord01.atlas.cogentco.com [154.54
.30.106]
13 63 ms 66 ms 61 ms te0-1-0-1.ccr21.bos01.atlas.cogentco.com [154.54
.24.53]
14 229 ms 211 ms 236 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
15 87 ms 87 ms 90 ms 38.111.40.114
16 92 ms 88 ms 82 ms 208.95.185.41
Trace complete.
Seems to me Cryptic should be talking to THEIR ISP, not us talking to ours - particularly because it's not just one region of the world with this problem. I'll try sending it in -again-, but I haven't ever heard back with this information.
Yes. The problem seems to be especially bad in Texas/Central Texas, and more specifically there seems to be a latency/connection issue at a server hop in Dallas run by Cogentco. A lot of people that are having this problem are using Time Warner Cable as their ISP so it may be a connection issue between Time Warner Cable and Cogentco that is causing this problem. Cogentco nor PWE/Cryptic have acknowledged this problem and I doubt if any communication has been established between Cogentco and PWE to try to solve this issue. At this point in time the game is completely unplayable for me due to connection issues.
Thank you guys! Yes, everything I have read is centered around Texas area and bottlenecks to Cogent. I was not able to play earlier then all of a sudden I had excellent connection with no issues transferring maps or rubberbanding. I will have to test it to see if that continues
BTW. They asked me to tracert there root IP and I got no response which is not what perfect world wanted. Here is that log information
Did as you requested and re-ran tracert on IP address and the URL. Here is
the report.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Main>tracert 208.95.184.0
Tracing route to 208.95.184.0 over a maximum of 30 hops
California Time Warner users are having the issue as well. This is the second time in six months this has happened.
I guess I will put off buying all those C Store ships and Doffs and uniforms etc etc until I am confident they are going to resolve this.
[SIGPIC][/SIGPIC]Captain Gordon Lightfoot, USS Edmund Fitzgerald
We've been informed by a few readers that there is currently an on-going outage for Cryptic Studios' MMORPG titles Star Trek Online and Champions Online for those of them residing in Texas.
The connectivity and latency issues with the game stem from a regional ISP called Cogentco, which the developer uses as a hop to connections from Texas.
We understand that players have been having these problems for several days now, with reports that owners of these games have been uanble to play them throughout most of the day.
The problem is Cogent, specifically te9-4.ccr01.dfw03.atlas.cogentco.com, which is the first Cogent hop out of the D/FW metroplex (much of Central Texas routes through here, as well).
California Time Warner users are having the issue as well. This is the second time in six months this has happened.
I guess I will put off buying all those C Store ships and Doffs and uniforms etc etc until I am confident they are going to resolve this.
DUDE, they don't care if you put it off. All they care about is that once it is fixed that you start playing again and buy it. THAT Is what they are counting on cause they know you have no where else to go to play a game like this!
It is sad that Gene Roddenberry's legacy has come to this TRIBBLE!!!!!!!!!!!!!!!
Posting the latest response from PWI Tech regarding this same problem of constant server not responding, disconnects, lag and total lack of being able to play.
Response Via Email (Support Staff 48)
09/16/2012 02:02 PM
Hello,
If it is indeed the same issue as others, we cannot guarantee a quick fix for this. We have been investigating this issue and trying to solve it and some users have been able to pass the issue, but others are still experiencing it.
Please perform and send us a trace route and your IP
Type tracert 208.95.184.0 into the command prompt. It may take a while to complete.
Traceroute is a program built into Windows that helps determine where network problems are occurring. It works by sending a very small amount of data to the specified server, then displaying the amount of time it takes to make every connection along the way. You can access it by typing tracert at the command prompt.
And so I sent them Tracerts from 9/17 and 9/18 today. I was able to play on the night of the 17th with minimal problems, but then on 9/18 once again I can't hardly play at all and after hours of trying I finally gave up on the game. And stating once again, I also am a TWC, Austin, Tx customer as well and according to the Tracerts I sent to them as well as all of you and probably many others that just aren't posting here or sending in tickets that Cogent Co is the problem server. One of my fleet members lives in Hawaii and is also having this problem although he's not a TWC subscriber but as of yet as not sent in a ticket.
One of the Tracerts done 9/17/12:
Tracing route to 208.95.184.0 over a maximum of 30 hops
1 <1 ms <1 ms 1 ms 192.168.1.1
2 11 ms 9 ms 8 ms 10.239.70.1
3 8 ms 8 ms 23 ms tge7-1.austtxj-er01.texas.rr.com [66.68.3.120]
4 18 ms 23 ms 23 ms tge0-11-0-7.austtxa-cr01.texas.rr.com [24.175.41.72]
5 24 ms 23 ms 22 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 20 ms 23 ms 32 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
7 16 ms 17 ms 14 ms ae-3-0.pr0.dfw10.tbone.rr.com [66.109.6.209]
8 220 ms 235 ms 26 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 16 ms 15 ms 21 ms te0-0-0-3.ccr21.dfw01.atlas.cogentco.com [154.54.7.45]
10 32 ms 28 ms 29 ms te0-3-0-6.mpd21.mci01.atlas.cogentco.com [154.54.46.197]
11 40 ms 48 ms 46 ms te0-5-0-4.mpd21.ord01.atlas.cogentco.com [154.54.45.154]
12 76 ms 79 ms 84 ms te0-4-0-6.ccr21.bos01.atlas.cogentco.com [154.54.45.246]
13 63 ms 71 ms 79 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
14 69 ms 72 ms 70 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.
Two of the Tracerts done 9/18/12:
Tracing route to 208.95.184.0 over a maximum of 30 hops
1 <1 ms <1 ms 1 ms 192.168.1.1
2 9 ms 8 ms 7 ms 10.239.70.1
3 9 ms 7 ms 13 ms tge7-1.austtxj-er01.texas.rr.com [66.68.3.120]
4 21 ms 23 ms 22 ms tge0-11-0-7.austtxa-cr01.texas.rr.com [24.175.41.72]
5 20 ms 16 ms 38 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 24 ms 23 ms 22 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
7 15 ms 34 ms 28 ms ae-3-0.pr0.dfw10.tbone.rr.com [66.109.6.209]
8 17 ms 201 ms 211 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 15 ms 17 ms 18 ms te0-0-0-3.ccr21.dfw01.atlas.cogentco.com [154.54.7.45]
10 28 ms 29 ms 32 ms te0-3-0-6.mpd21.mci01.atlas.cogentco.com [154.54.46.197]
11 37 ms 39 ms 38 ms te0-5-0-4.mpd21.ord01.atlas.cogentco.com [154.54.45.154]
12 63 ms 60 ms 61 ms te0-4-0-6.ccr21.bos01.atlas.cogentco.com [154.54.45.246]
13 64 ms 60 ms 64 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
14 60 ms 67 ms 72 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.
Tracing route to 208.95.184.0 over a maximum of 30 hops
1 <1 ms <1 ms 1 ms 192.168.1.1
2 8 ms 7 ms 7 ms 10.239.70.1
3 10 ms 10 ms 9 ms tge7-1.austtxj-er01.texas.rr.com [66.68.3.120]
4 19 ms 15 ms 15 ms tge0-11-0-7.austtxa-cr01.texas.rr.com [24.175.41.72]
5 15 ms 40 ms 21 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 23 ms 22 ms 23 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
7 15 ms 17 ms 17 ms ae-3-0.pr0.dfw10.tbone.rr.com [66.109.6.209]
8 16 ms 16 ms 15 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 15 ms 16 ms 16 ms te0-0-0-3.ccr21.dfw01.atlas.cogentco.com [154.54.7.45]
10 30 ms 29 ms 28 ms te0-3-0-6.mpd21.mci01.atlas.cogentco.com [154.54.46.197]
11 38 ms 37 ms 37 ms te0-5-0-4.mpd21.ord01.atlas.cogentco.com [154.54.45.154]
12 61 ms 64 ms 60 ms te0-4-0-6.ccr21.bos01.atlas.cogentco.com [154.54.45.246]
13 203 ms 207 ms 205 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
14 59 ms 74 ms 65 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.
Awaiting their next response to my current mail to them as all of you are as well. So SICK of this as well...
I don't think there's anything more I can add about this situation that hasn't been said already. I've gotten the same run-around by PWE, with the same canned responses that they've been giving everyone else.
Just some background on me... I picked up STO about 3 weeks ago, F2P, but in that time I've spent over $100 on ZEN, and yet I haven't been able to play for the majority of that time and PWE support doesn't seem to give a damn about it. I even asked for a refund because I had every intention of giving up on this game forever, but they denied my request so I decided to continue working on resolving the issue. They still haven't responded with any further updates or troubleshooting recommendations.
I'm still experiencing the issues this morning. At this point, I think it's safe to say that the problem isn't on our end, and Cryptic needs to take the reins and resolve their own network problems instead of putting that burden on their customers.
And yes, some compensation for the lengthy disruption of service would go a long way toward keeping your customers.... well, paying customers.
how do i trace where it's going to. i live in sw PA, USA. armstrong cable. i'm lucky if i can play the game for 15 minutes before server gets disconnected.
how do i trace where it's going to. i live in sw PA, USA. armstrong cable. i'm lucky if i can play the game for 15 minutes before server gets disconnected.
Please contact me in-game @draco0167 and I'd be happy to send you some instructions on how to perform one as well as how to read it so that you know what it says.
Got update on the ISP issues for most of the PWE games for the last three days. Those should be resolved. I posted stickies about it on most of the game forums.
There are back and forth communication threads going on with PWE, Cogentco and any other related parties for the STO and CO issues. Sorry I can't share more info yet. You know what I know!
"Critics who say that the optimistic utopia Star Trek depicted is now outmoded forget the cultural context that gave birth to it: Star Trek was not a manifestation of optimism when optimism was easy. Star Trek declared a hope for a future that nobody stuck in the present could believe in. For all our struggles today, we haven’t outgrown the need for stories like Star Trek. We need tales of optimism, of heroes, of courage and goodness now as much as we’ve ever needed them." -Thomas Marrone
Guys, cross linking from multiple sites isn't allowed. If you are getting help on the official ones then by all means suggest people go there, but having two threads on two different sites about the same thing is kinda redundant :P
I'm going to go ahead and close this thread since Darthpanda is trying his hardest on the official forums to help those involved --
Yes, I'm that Askray@Batbayer in game. Yes, I still play. No, I don't care. Former Community Moderator, Former SSR DJ, Now Full time father to two kids, Husband, Retail Worker. Tiktok: @Askray Facebook: Askray113
Comments
@DevolvedOne
Sigh.
"Critics who say that the optimistic utopia Star Trek depicted is now outmoded forget the cultural context that gave birth to it: Star Trek was not a manifestation of optimism when optimism was easy. Star Trek declared a hope for a future that nobody stuck in the present could believe in. For all our struggles today, we haven’t outgrown the need for stories like Star Trek. We need tales of optimism, of heroes, of courage and goodness now as much as we’ve ever needed them."
-Thomas Marrone
Thank you guys! Yes, everything I have read is centered around Texas area and bottlenecks to Cogent. I was not able to play earlier then all of a sudden I had excellent connection with no issues transferring maps or rubberbanding. I will have to test it to see if that continues
BTW. They asked me to tracert there root IP and I got no response which is not what perfect world wanted. Here is that log information
Did as you requested and re-ran tracert on IP address and the URL. Here is
the report.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Main>tracert 208.95.184.0
Tracing route to 208.95.184.0 over a maximum of 30 hops
1 * * * Request timed out.
2 * ^C
C:\Users\Main>tracert http://support.crypticstudios.com
Unable to resolve target system name http://support.crypticstudios.com.
I guess I will put off buying all those C Store ships and Doffs and uniforms etc etc until I am confident they are going to resolve this.
Check out Firefly Fleet: http://serenitystation.forumotion.com/
We've been informed by a few readers that there is currently an on-going outage for Cryptic Studios' MMORPG titles Star Trek Online and Champions Online for those of them residing in Texas.
The connectivity and latency issues with the game stem from a regional ISP called Cogentco, which the developer uses as a hop to connections from Texas.
We understand that players have been having these problems for several days now, with reports that owners of these games have been uanble to play them throughout most of the day.
The problem is Cogent, specifically te9-4.ccr01.dfw03.atlas.cogentco.com, which is the first Cogent hop out of the D/FW metroplex (much of Central Texas routes through here, as well).
DUDE, they don't care if you put it off. All they care about is that once it is fixed that you start playing again and buy it. THAT Is what they are counting on cause they know you have no where else to go to play a game like this!
It is sad that Gene Roddenberry's legacy has come to this TRIBBLE!!!!!!!!!!!!!!!
Response Via Email (Support Staff 48)
09/16/2012 02:02 PM
Hello,
If it is indeed the same issue as others, we cannot guarantee a quick fix for this. We have been investigating this issue and trying to solve it and some users have been able to pass the issue, but others are still experiencing it.
Please perform and send us a trace route and your IP
Type tracert 208.95.184.0 into the command prompt. It may take a while to complete.
Traceroute is a program built into Windows that helps determine where network problems are occurring. It works by sending a very small amount of data to the specified server, then displaying the amount of time it takes to make every connection along the way. You can access it by typing tracert at the command prompt.
Regards,
The Perfect World Tech Support Team
http://techsupport.perfectworld.com/
https://support.perfectworld.com/
And so I sent them Tracerts from 9/17 and 9/18 today. I was able to play on the night of the 17th with minimal problems, but then on 9/18 once again I can't hardly play at all and after hours of trying I finally gave up on the game. And stating once again, I also am a TWC, Austin, Tx customer as well and according to the Tracerts I sent to them as well as all of you and probably many others that just aren't posting here or sending in tickets that Cogent Co is the problem server. One of my fleet members lives in Hawaii and is also having this problem although he's not a TWC subscriber but as of yet as not sent in a ticket.
One of the Tracerts done 9/17/12:
Tracing route to 208.95.184.0 over a maximum of 30 hops
1 <1 ms <1 ms 1 ms 192.168.1.1
2 11 ms 9 ms 8 ms 10.239.70.1
3 8 ms 8 ms 23 ms tge7-1.austtxj-er01.texas.rr.com [66.68.3.120]
4 18 ms 23 ms 23 ms tge0-11-0-7.austtxa-cr01.texas.rr.com [24.175.41.72]
5 24 ms 23 ms 22 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 20 ms 23 ms 32 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
7 16 ms 17 ms 14 ms ae-3-0.pr0.dfw10.tbone.rr.com [66.109.6.209]
8 220 ms 235 ms 26 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 16 ms 15 ms 21 ms te0-0-0-3.ccr21.dfw01.atlas.cogentco.com [154.54.7.45]
10 32 ms 28 ms 29 ms te0-3-0-6.mpd21.mci01.atlas.cogentco.com [154.54.46.197]
11 40 ms 48 ms 46 ms te0-5-0-4.mpd21.ord01.atlas.cogentco.com [154.54.45.154]
12 76 ms 79 ms 84 ms te0-4-0-6.ccr21.bos01.atlas.cogentco.com [154.54.45.246]
13 63 ms 71 ms 79 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
14 69 ms 72 ms 70 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.
Two of the Tracerts done 9/18/12:
Tracing route to 208.95.184.0 over a maximum of 30 hops
1 <1 ms <1 ms 1 ms 192.168.1.1
2 9 ms 8 ms 7 ms 10.239.70.1
3 9 ms 7 ms 13 ms tge7-1.austtxj-er01.texas.rr.com [66.68.3.120]
4 21 ms 23 ms 22 ms tge0-11-0-7.austtxa-cr01.texas.rr.com [24.175.41.72]
5 20 ms 16 ms 38 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 24 ms 23 ms 22 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
7 15 ms 34 ms 28 ms ae-3-0.pr0.dfw10.tbone.rr.com [66.109.6.209]
8 17 ms 201 ms 211 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 15 ms 17 ms 18 ms te0-0-0-3.ccr21.dfw01.atlas.cogentco.com [154.54.7.45]
10 28 ms 29 ms 32 ms te0-3-0-6.mpd21.mci01.atlas.cogentco.com [154.54.46.197]
11 37 ms 39 ms 38 ms te0-5-0-4.mpd21.ord01.atlas.cogentco.com [154.54.45.154]
12 63 ms 60 ms 61 ms te0-4-0-6.ccr21.bos01.atlas.cogentco.com [154.54.45.246]
13 64 ms 60 ms 64 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
14 60 ms 67 ms 72 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.
Tracing route to 208.95.184.0 over a maximum of 30 hops
1 <1 ms <1 ms 1 ms 192.168.1.1
2 8 ms 7 ms 7 ms 10.239.70.1
3 10 ms 10 ms 9 ms tge7-1.austtxj-er01.texas.rr.com [66.68.3.120]
4 19 ms 15 ms 15 ms tge0-11-0-7.austtxa-cr01.texas.rr.com [24.175.41.72]
5 15 ms 40 ms 21 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 23 ms 22 ms 23 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
7 15 ms 17 ms 17 ms ae-3-0.pr0.dfw10.tbone.rr.com [66.109.6.209]
8 16 ms 16 ms 15 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 15 ms 16 ms 16 ms te0-0-0-3.ccr21.dfw01.atlas.cogentco.com [154.54.7.45]
10 30 ms 29 ms 28 ms te0-3-0-6.mpd21.mci01.atlas.cogentco.com [154.54.46.197]
11 38 ms 37 ms 37 ms te0-5-0-4.mpd21.ord01.atlas.cogentco.com [154.54.45.154]
12 61 ms 64 ms 60 ms te0-4-0-6.ccr21.bos01.atlas.cogentco.com [154.54.45.246]
13 203 ms 207 ms 205 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
14 59 ms 74 ms 65 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.
Awaiting their next response to my current mail to them as all of you are as well. So SICK of this as well...
Fed Up in Texas... Shannara
Just some background on me... I picked up STO about 3 weeks ago, F2P, but in that time I've spent over $100 on ZEN, and yet I haven't been able to play for the majority of that time and PWE support doesn't seem to give a damn about it. I even asked for a refund because I had every intention of giving up on this game forever, but they denied my request so I decided to continue working on resolving the issue. They still haven't responded with any further updates or troubleshooting recommendations.
I'm still experiencing the issues this morning. At this point, I think it's safe to say that the problem isn't on our end, and Cryptic needs to take the reins and resolve their own network problems instead of putting that burden on their customers.
And yes, some compensation for the lengthy disruption of service would go a long way toward keeping your customers.... well, paying customers.
- Will - Austin, TX - TWC -
Darth responded in the primary Tech thread to my post, go there and have yourself a quick laugh.
Please contact me in-game @draco0167 and I'd be happy to send you some instructions on how to perform one as well as how to read it so that you know what it says.
"Critics who say that the optimistic utopia Star Trek depicted is now outmoded forget the cultural context that gave birth to it: Star Trek was not a manifestation of optimism when optimism was easy. Star Trek declared a hope for a future that nobody stuck in the present could believe in. For all our struggles today, we haven’t outgrown the need for stories like Star Trek. We need tales of optimism, of heroes, of courage and goodness now as much as we’ve ever needed them."
-Thomas Marrone
I'm going to go ahead and close this thread since Darthpanda is trying his hardest on the official forums to help those involved
http://techsupport.perfectworld.com/showthread.php?p=29771
Former Community Moderator, Former SSR DJ, Now Full time father to two kids, Husband, Retail Worker.
Tiktok: @Askray Facebook: Askray113