First and foremost, I am unable to create a new thread. Not sure of the reason for this nor is it important at the moment.
Secondly, for the second straight weekend we seem to be having problems logging in. I understand all the technical issues associated with running this game. However, I'm like many who can only afford the time to play Star Trek Online on the weekends. So when we have issues like this, it's more than just a bit frustrating. With that in mind, I've already cancelled my monthly subscription and I'm about ready to quit playing altogether. This is very sad because I do enjoy this game so very much. It would be nice to know that the technical experts at Cryptic are devoting all their energies on fixing the various problems that exist in this game rather than on creating new content. There are far more problems that the game itself cannot be expanded properly with new content unless the issues are fixed
Here we are again... getting repeated messages of 'Connection to the login server timed out.', 'Login2_timeout', and 'Connection to the account server timed out.'. Game has been quite unplayable since I started the client approximately 3.5 hours ago.
I've confirmed, to the best of my ability, that the problems are not at this end of the connection. Rebooted our gateway, and checked several websites (our fleet forums and YouTube to name a couple) to ensure our internet connection is stable, and it is.
For your reading pleasure, here's my ping/tracert data, taken 5 minutes ago.
C:\Users\****>ping patchserver.crypticstudios.com
Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=71ms TTL=48
Reply from 208.95.185.41: bytes=32 time=70ms TTL=48
Reply from 208.95.185.41: bytes=32 time=70ms TTL=48
Reply from 208.95.185.41: bytes=32 time=70ms TTL=48
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 71ms, Average = 70ms
C:\Users\****>ping accounts.crypticstudios.com
Pinging accounts.crypticstudios.com [208.95.185.165] with 32 bytes of data:
Reply from 208.95.185.165: bytes=32 time=68ms TTL=113
Reply from 208.95.185.165: bytes=32 time=70ms TTL=113
Reply from 208.95.185.165: bytes=32 time=68ms TTL=113
Reply from 208.95.185.165: bytes=32 time=101ms TTL=113
Ping statistics for 208.95.185.165:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 101ms, Average = 76ms
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms dsldevice.att.net [192.168.1.254]
2 368 ms 209 ms 201 ms 107-139-204-2.lightspeed.jcsnms.sbcglobal.net [107.139.204.2]
3 58 ms 129 ms 59 ms 99.183.77.54
4 22 ms 21 ms 22 ms 99.183.77.119
5 22 ms 24 ms 21 ms 12.83.102.17
6 30 ms 31 ms 33 ms 12.122.157.6
7 32 ms 32 ms 30 ms gar3.brhal.ip.att.net [12.122.141.189]
8 30 ms 30 ms 30 ms te0-7-0-1.ccr21.atl02.atlas.cogentco.com [154.54.13.173]
9 40 ms 65 ms 40 ms be2050.ccr41.atl01.atlas.cogentco.com [154.54.0.165]
10 48 ms 49 ms 50 ms be2168.ccr21.dca01.atlas.cogentco.com [154.54.31.94]
11 54 ms 50 ms 52 ms be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31.118]
12 61 ms 59 ms 60 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30.14]
13 57 ms 57 ms 59 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.134]
14 79 ms 71 ms 71 ms 38.111.40.114
15 72 ms 68 ms 71 ms patchserverrebirth.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Users\****>tracert accounts.crypticstudios.com
Tracing route to accounts.crypticstudios.com [208.95.185.165]
over a maximum of 30 hops:
1 1 ms <1 ms 3 ms dsldevice.att.net [192.168.1.254]
2 30 ms 40 ms 30 ms 107-139-204-2.lightspeed.jcsnms.sbcglobal.net [107.139.204.2]
3 31 ms 71 ms 23 ms 99.183.77.54
4 21 ms 22 ms 22 ms 99.183.77.119
5 27 ms 23 ms 28 ms 12.83.102.9
6 34 ms 32 ms 36 ms 12.122.157.6
7 32 ms 34 ms 32 ms gar3.brhal.ip.att.net [12.122.141.189]
8 33 ms 29 ms 30 ms te0-7-0-1.ccr21.atl02.atlas.cogentco.com [154.54.13.173]
9 43 ms 29 ms 29 ms be2051.ccr42.atl01.atlas.cogentco.com [154.54.0.161]
10 52 ms 45 ms 55 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31.98]
11 51 ms 53 ms 50 ms be2149.ccr42.jfk02.atlas.cogentco.com [154.54.31.126]
12 60 ms 60 ms 60 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
13 124 ms 82 ms 112 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
14 70 ms 72 ms 71 ms 38.111.40.114
15 68 ms 71 ms 68 ms accounts.crypticstudios.com [208.95.185.165]
Trace complete.
Edit: 50 minutes later, a new error: 'Timed out connecting to GameServer.' *sigh*
Yeah, we're still working to resolve this issue. It's affecting all Cryptic titles, so it's not something that's purely affecting STO. It's something that's a little more widespread that we're looking into with as many people as we can to get to the bottom of it.
There's a fine delicate line between posting constantly with "Hey guys, still looking into it. No word back yet!" and utter silence. I don't want to spam you every 30 minutes or few hours with fluff responses, but I don't want to go silent and think it's suddenly off the radar. It very much is something we've been looking into and will look into until we get a resolution.
Maybe a question everyone is afraid to ask, but could the latency be related to memory usage/leakage from Arc?
This program, though reasonably normal at times, seems to have a strong affinity to classes belonging to the Cat 2.0 program. Questerius 2.7 will break down on occasion, resulting in garbage and nonsense messages whenever it occurs. Usually a hard reboot or pulling the plug solves the problem when that happens.
We love you, you know this; but guys, you can't leave the office for the weekend with the game like this. The Delta Recruit program really seems to be taking off. There was some great momentum being generated. And its all being wasted on these server issues. There's a brand new episode coming...another great bump. Unfortunately with every episode is going to be more issues (which is understandable) on top of a server you can't depend on (which is unacceptable). I understand that layoffs destroy morale. Perhaps you even feel sick anytime an email from Perfect World hits the inbox. Totally reasonable. But you work in the game industry. If you wanted steady work go into health care or law enforcement. At this point delay episode 10's release until this is ironed out.
Not to post without some ideas:
1) Community management. Get on to the news feeds and start posting updates every few hours. Take care of us to cut down on the flame war.
2) Have your technical director on the phone with whom ever the problem is every hour on the hour requesting updates until this is resolved.
We love you, you know this; but guys, you can't leave the office for the weekend with the game like this. The Delta Recruit program really seems to be taking off. There was some great momentum being generated. And its all being wasted on these server issues. There's a brand new episode coming...another great bump. Unfortunately with every episode is going to be more issues (which is understandable) on top of a server you can't depend on (which is unacceptable). I understand that layoffs destroy morale. Perhaps you even feel sick anytime an email from Perfect World hits the inbox. Totally reasonable. But you work in the game industry. If you wanted steady work go into health care or law enforcement. At this point delay episode 10's release until this is ironed out.
Not to post without some ideas:
1) Community management. Get on to the news feeds and start posting updates every few hours. Take care of us to cut down on the flame war.
2) Have your technical director on the phone with whom ever the problem is every hour on the hour requesting updates until this is resolved.
And to add to that, a little more transparency and acknowledment of problems would go a long way. There's only so much "the problem must be on your end." people are willing to take from cookie cutter customer service responses, before the pitchforks and torches come out.
Automated responses are single-handedly one of the most frustrating parts of sending a request for help.
And to add to that, a little more transparency and acknowledment of problems would go a long way. There's only so much "the problem must be on your end." people are willing to take from cookie cutter customer service responses, before the pitchforks and torches come out.
Automated responses are single-handedly one of the most frustrating parts of sending a request for help.
I agree. I'd honestly prefer Morrigan (or someone else) to spam us with, "We're still aware of this issue and are still working on resolving it, still no ETA." on a daily basis than hearing nothing at all.
I mean we have things in STO itself like the Bulletin system. We have pink admin text. We have the ability to get updates via in-game mail. We have the STO launcher itself. We have ARC. We have the forums. They even have all of our e-mail addresses they can send us mail to.
It's not like PWE/Cryptic doesn't have the tools in place to keep people informed and up to date. They do. They just don't use them.
I think that all the new content will more than likely be pretty nice; But If we can't login than what the use of having new content. It has now been 2 weeks sence people have been able to
login. Lets see the progress being made on this issue.
Week 1
1. Login issue through ARC login, players complain.
2. Ops ask for login tracert, players comply and post them if they can get that to work.
3. Thursday patch released thing like uniforms, storyline issues, and other minor issues fixed.
Week 2
1. Still having login issue through ARC login, players complain.
2. Ops ask for login tracert, players comply and post them if they can get that to work.
3. Thursday patch released thing like uniforms, storyline issues, and other minor issues fixed. Lots
of stuff released about season 10.
Week 1 + Week 2 = Players not being able to login and play there new Delta Recruit or there
old characters.
Lets put the new toys away and get the login server fixed so people can actually play the game.
Lets put the new toys away and get the login server fixed so people can actually play the game.
I would have to agree. Cryptic should delay Season 10 and extend the Delta Recruit event until the server issues have been fixed. While the login issues haven't affected me personally, I have every bit of sympathy for those who have been affected by it. It's not really fair for them to miss out on both these events as a result of server issues. Issues that have progressively gotten worse since the winter event.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
tracert 208.95.186.11
Tracing route to 208.95.186.11 over a maximum of 30 hops
1 2 ms 3 ms 2 ms homeportal [192.168.1.254]
2 35 ms 27 ms 28 ms 107-218-200-1.lightspeed.mssnks.sbcglobal.net [1
07.218.200.1]
3 28 ms 28 ms 29 ms 71.150.19.52
4 32 ms 29 ms 28 ms 71.150.32.138
5 28 ms 30 ms 31 ms 71.150.32.199
6 30 ms 29 ms 27 ms 12.83.42.129
7 41 ms 38 ms 44 ms ggr3.dlstx.ip.att.net [12.122.138.17]
8 40 ms 39 ms 40 ms 192.205.36.222
9 41 ms 38 ms 37 ms be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.
53]
10 49 ms 45 ms 44 ms be2146.ccr22.iah01.atlas.cogentco.com [154.54.25
.241]
11 56 ms 56 ms 56 ms be2173.ccr42.atl01.atlas.cogentco.com [154.54.29
.117]
12 61 ms 62 ms 59 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31
.98]
13 65 ms 64 ms 65 ms be2149.ccr42.jfk02.atlas.cogentco.com [154.54.31
.126]
14 73 ms 74 ms 71 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
15 72 ms 72 ms 71 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.130]
16 77 ms 74 ms 85 ms 38.111.40.114
17 76 ms 74 ms 74 ms 208.95.186.11
Trace complete.
---> So... is Cogent Communications the source of all our distress?
traceroute to 208.95.186.11 (208.95.186.11), 30 hops max, 60 byte packets
1 vl99.mag01.mci01.atlas.cogentco.com (66.250.250.17) 0.289 ms 0.293 ms
2 te0-0-0-4.ccr21.mci01.atlas.cogentco.com (154.54.30.173) 0.925 ms 0.932 ms
3 be2157.ccr42.ord01.atlas.cogentco.com (154.54.6.118) 12.796 ms be2156.ccr41.ord01.atlas.cogentco.com (154.54.6.86) 12.931 ms
4 be2351.ccr21.cle04.atlas.cogentco.com (154.54.44.86) 19.858 ms be2185.ccr22.cle04.atlas.cogentco.com (154.54.43.178) 20.903 ms
5 be2189.ccr22.alb02.atlas.cogentco.com (154.54.43.185) 31.913 ms 32.430 ms
6 be2302.ccr22.bos01.atlas.cogentco.com (154.54.43.13) 35.847 ms be2299.ccr21.bos01.atlas.cogentco.com (154.54.43.9) 35.765 ms
7 te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.com (154.54.46.134) 35.755 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com (154.54.46.130) 36.247 ms
8 * *
9 * *
10 * *
11 * *
12 * *
13 * *
14 * *
15 * *
16 * *
17 * *
18 * *
19 * *
20 * *
21 * *
22 * *
23 * *
24 * *
25 * *
26 * *
27 * *
28 * *
29 * *
30 * *
It is very possible that they have a master DNS server with a corrupt routing table that is gumming up the entire works. Give them a call and see if they can refresh and rebuild their routing tables.
BTW... 48 hours and counting and still Poor to no Access to STO. The game is generally unplayable for me in its current state.
Has anyone correlated this information with, say, IPviking? It's possible that you guys are being routed through datacenters under ddos attack or the like, which would explain the packet loss and the lag.
Monday afternoon, less than 24 hours until season 10. Launcher still does not load.
Was able to change to EU proxy yesterday and was able to play for the longest time in 10 days, no SNRS or dcs. Today seems the proxy has nothing to do with the launcher loading. Cannot sign on at all.
Just got kicked again - and for a full 120+ seconds as I saw "Server Not Responding" and my character frozen - the CHAT SERVER was fine and I could continue my converstations (and see my response posted in chat and replied to) -- so honestly; I don't see how it's an ISP issue on my end (as others and Cryptic seem to imply when this pops up for those of us affected.) When attempting to log in from the in game client log on screen - the account server takes a few seconds to respond (see a 'waiting for respose from Account Server" and when that goes away - about 10 - 30 seconds later (multiple tries) was getting "Connection to Login Server Timed Out."
After dropting back to my desktop - now getting the usual 'empty launcher with black background' and a 'Loading Please Wait...' in the upper left corner. If I wait long enough it will either partially load a portion of the STO graphics (after5 5-10 minutes and not progress further..)
^^^
Had this issue randomly/intermittently since Tues. 4/7/15. No other internet functionality (or speed) is affect - just my connection to any Cryptic MMO (STO, CO, NeverWinter)
My location: Southern California, L.A. area
Tracert to Patch Server:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254]
2 19 ms 20 ms 19 ms 23-114-212-2.lightspeed.irvnca.sbcglobal.net [23.114.***.***]
3 21 ms 21 ms 21 ms 75.20.0.202
4 23 ms 23 ms 24 ms 12.83.38.157
5 22 ms 22 ms 24 ms 12.123.132.137
6 23 ms 22 ms 23 ms be3013.ccr23.lax05.atlas.cogentco.com [154.54.13.149]
7 24 ms 22 ms 23 ms be2179.ccr22.lax01.atlas.cogentco.com [154.54.41.81]
8 59 ms 59 ms 59 ms be2066.ccr22.iah01.atlas.cogentco.com [154.54.7.53]
9 73 ms 72 ms 72 ms be2173.ccr42.atl01.atlas.cogentco.com [154.54.29.117]
10 89 ms 89 ms 89 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31.98]
11 90 ms 90 ms 89 ms be2149.ccr42.jfk02.atlas.cogentco.com [154.54.31.126]
12 96 ms 96 ms 97 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
13 97 ms 97 ms 97 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
14 111 ms 121 ms 110 ms 38.111.40.114
15 111 ms 110 ms 112 ms patchserverrebirth.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Users\***>
Tracert to Account Server:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\***>tracert accounts.crypticstudios.com
Tracing route to accounts.crypticstudios.com [208.95.185.165]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254]
2 20 ms 19 ms 19 ms 23-114-212-2.lightspeed.irvnca.sbcglobal.net [23.114.***.***]
3 23 ms 21 ms 20 ms 75.20.0.202
4 21 ms 22 ms 24 ms 12.83.38.153
5 23 ms 23 ms 23 ms 12.123.132.137
6 22 ms 24 ms 22 ms be3013.ccr23.lax05.atlas.cogentco.com [154.54.13.149]
7 23 ms 23 ms 22 ms be2179.ccr22.lax01.atlas.cogentco.com [154.54.41.81]
8 60 ms 59 ms 59 ms be2066.ccr22.iah01.atlas.cogentco.com [154.54.7.53]
9 72 ms 72 ms 71 ms be2173.ccr42.atl01.atlas.cogentco.com [154.54.29.117]
10 90 ms 88 ms 88 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31.98]
11 89 ms 90 ms 89 ms be2149.ccr42.jfk02.atlas.cogentco.com [154.54.31.126]
12 96 ms 95 ms 95 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
13 97 ms 97 ms 96 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
14 122 ms 111 ms 122 ms 38.111.40.114
15 111 ms 110 ms 111 ms accounts.crypticstudios.com [208.95.185.165]
Trace complete.
C:\Users\***>
Would give a tracert to the Login server, but it appears to be named 'cryptically'.
Formerly known as Armsman from June 2008 to June 20, 2012 PWE ARC Drone says: "Your STO forum community as you have known it is ended...Display names are irrelevant...Any further sense of community is irrelevant...Resistance is futile...You will be assimilated..."
Ok...there have been a number of threads concerning lag, disconnects, general performance issues etc. etc., the past couple of weeks... I've experienced them myself....over the past... I believe? 2 weeks...generally speaking of course, the game's lag goes from annoying... to full on nuclear level frustration because of how the game ends up becoming completely unplayable...
and these are performance issues! not related to the dissconnects... and occasionally not being able to even connect at all! which i am experiencing now...and.. again...something showing itself over the past about 2 weeks...but whatever...there are other places to spend my money...my point!
unless these issues over the past couple of weeks are related to some sort of major hardware or software upgrade thats been happening behind closed doors...and it will go completely live tomorrow... a new system that works towards resolving fundamental gameplay issues...my question is...How on bloody earth is the current system expected to handle season 10?! by every indication...the answer is...well...you know the answer...
this is one of my old posts...dug it up just as a reminder...
I liken the stability issues, e.g. regular amounts of lag, rubberbanding, disconnects, and the Cryptic STO team's aggressive... almost overwhelming amount of new content over the past 6 months ...to a man who wants to put a new floor on his home...the engineer tells him that his foundation on his home could use some work... but he believes he can add the addition... but any other additions would require repairing the foundation...the man...happy with his new floor... ignores the engineer and finds someone who will keep adding to his home...you can figure out what happens next...
When players experience regular stability issues the common reaction is frustration...to different degrees...frustrated players do not spend money!
If I experience regular rubberbanding for example...why would I spend $30 on a ship that I would not be able to enjoy using?
If I am a new player, why would I spend any money at all if my fundamental game playing is regularly interrupted by stability issues?
In short... new content will not continue to save the game if the foundation needs work...in fact...and no pun indented...you'll find things eventually crashing down...
Hey ya'll! Just a reminder that the net-ops team in charge of handling this, any and all tracerts as well as publicIPs will help assist them in the issue.
As another reminder, the issues that are currently being faced are exclusive to one specific branch of engineers. The team who is in charge of handling this issue is still investigating and addressing the issue. Other teams, such as environmental artists and web developers will still be creating their respective content.
This is a red-alert issue as far as the team is concerned, however that does not mean that other teams will halt their respective work. Too often I have seen wide-spread claims that "the devs need to be stop work on everything" Tacofangs will not stop his work on Sector Space to try and resolve login issues. That is neither his job, nor is it fair to the hard work in delivering what is frankly a beautiful update. Those who have worked tirelessly to build up new content should see their work come to fruition.
In regards to the team who IS responsible for the respective login issues, I have and will continue to be pinging them trying to find resolution to an issue that is affecting all Cryptic titles.
As another reminder, the issues that are currently being faced are exclusive to one specific branch of engineers. The team who is in charge of handling this issue is still investigating and addressing the issue. Other teams, such as environmental artists and web developers will still be creating their respective content.
This is a red-alert issue as far as the team is concerned, however that does not mean that other teams will halt their respective work. Too often I have seen wide-spread claims that "the devs need to be stop work on everything" Tacofangs will not stop his work on Sector Space to try and resolve login issues. That is neither his job, nor is it fair to the hard work in delivering what is frankly a beautiful update. Those who have worked tirelessly to build up new content should see their work come to fruition.
heh, I'd love to see Tacofangs face if one where to hand him some Ethernet cables demanding he fix the connectivity problems. Might get a "dammit Cryptic I'm an environmental artist, not a network engineer!"
In regards to the team who IS responsible for the respective login issues, I have and will continue to be pinging them trying to find resolution to an issue that is affecting all Cryptic titles.
Oh Trendy, nice networking pun. Did you get a "Request timed out" when pinging the network team? hehehe
heh, I'd love to see Tacofangs face if one where to hand him some Ethernet cables demanding he fix the connectivity problems. Might get a "dammit Cryptic I'm an environmental artist, not a network engineer!"
Oh Trendy, nice networking pun. Did you get a "Request timed out" when pinging the network team? hehehe
Thanks! I'm always happy when my slight puns get picked up.
I often joke around about "that one time I burned off a bunch of Caitain fur trying to fix the warp core" because in reality, that's not what I do. I post updates when I get them, I do web development, I do blogs, I do art asset generation, I do social media, I do excessive amounts of coffee.
But networking? No. Don't let me near those cables. I'd probably start biting them or something.
7:01 pm pst
Using old sto long-in method, unable to connect to cryptic login server,
Using Arc unable to connect to account server.
Login to forums is accessible and working fine.
Thanks! I'm always happy when my slight puns get picked up.
I often joke around about "that one time I burned off a bunch of Caitain fur trying to fix the warp core" because in reality, that's not what I do. I post updates when I get them, I do web development, I do blogs, I do art asset generation, I do social media, I do excessive amounts of coffee.
But networking? No. Don't let me near those cables. I'd probably start biting them or something.
hehe, biting the networking cables? Wait...that's it! Have your network team check for Cardassian voles in the server room and then get O'Brien on the case!
7:01 pm pst
Using old sto long-in method, unable to connect to cryptic login server,
Using Arc unable to connect to account server.
Login to forums is accessible and working fine.
The network team can't do anything with that information if you don't provide a trace route. To do so:
Press Ctrl + R (opens the "Run" box)
In the run box, type "cmd". (short for Command Prompt)
This opens the Command Prompt window.
In command prompt type "tracert accounts.crypticstudios.com" (without quotes)
Wait for the trace route to complete.
Copy/paste the results into a post here on the forums.
This process greatly assists network engineers as it indicates exactly where the connectivity problem is occurring.
At bout 7:40 PM I finished patching Tribble, tried to log in saw "Server Not Available" (That's normal I assume as you guys just put a final/new patch on it) -- so exited -- re-launched and getting the Blank/Black Baground with "Loading Please Wait..." in upper left corner.
Tracert to account server:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\***>tracert accounts.crypticstudios.com
Tracing route to accounts.crypticstudios.com [208.95.185.165]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254]
2 19 ms 19 ms 18 ms 23-114-212-2.lightspeed.irvnca.sbcglobal.net [23.114.***.***]
3 21 ms 21 ms 20 ms 75.20.0.202
4 21 ms 24 ms 23 ms 12.83.38.153
5 22 ms 25 ms 22 ms 12.123.132.137
6 23 ms 24 ms 23 ms be3013.ccr23.lax05.atlas.cogentco.com [154.54.13.149]
7 23 ms 22 ms 23 ms be2179.ccr22.lax01.atlas.cogentco.com [154.54.41.81]
8 59 ms 58 ms 59 ms be2066.ccr22.iah01.atlas.cogentco.com [154.54.7.53]
9 71 ms 71 ms 71 ms be2173.ccr42.atl01.atlas.cogentco.com [154.54.29.117]
10 88 ms 87 ms 89 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31.98]
11 90 ms 90 ms 90 ms be2149.ccr42.jfk02.atlas.cogentco.com [154.54.31.126]
12 96 ms 95 ms 95 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
13 97 ms 97 ms 96 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
14 100 ms 105 ms 107 ms 38.111.40.114
15 97 ms 96 ms 96 ms accounts.crypticstudios.com [208.95.185.165]
Trace complete.
C:\Users\***>
Tracert to Patchserver:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254]
2 20 ms 19 ms 19 ms 23-114-212-2.lightspeed.irvnca.sbcglobal.net [23.114.***.***]
3 21 ms 21 ms 20 ms 75.20.0.202
4 23 ms 23 ms 23 ms 12.83.38.157
5 23 ms 24 ms 23 ms 12.123.132.137
6 23 ms 22 ms 23 ms be3013.ccr23.lax05.atlas.cogentco.com [154.54.13.149]
7 25 ms 23 ms 22 ms be2179.ccr22.lax01.atlas.cogentco.com [154.54.41.81]
8 60 ms 59 ms 60 ms be2066.ccr22.iah01.atlas.cogentco.com [154.54.7.53]
9 71 ms 72 ms 71 ms be2173.ccr42.atl01.atlas.cogentco.com [154.54.29.117]
10 89 ms 88 ms 89 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31.98]
11 90 ms 90 ms 90 ms be2149.ccr42.jfk02.atlas.cogentco.com [154.54.31.126]
12 96 ms 95 ms 96 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
13 97 ms 97 ms 96 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
14 107 ms 107 ms 108 ms 38.111.40.114
15 96 ms 97 ms 96 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Users\***>
Formerly known as Armsman from June 2008 to June 20, 2012 PWE ARC Drone says: "Your STO forum community as you have known it is ended...Display names are irrelevant...Any further sense of community is irrelevant...Resistance is futile...You will be assimilated..."
Comments
Secondly, for the second straight weekend we seem to be having problems logging in. I understand all the technical issues associated with running this game. However, I'm like many who can only afford the time to play Star Trek Online on the weekends. So when we have issues like this, it's more than just a bit frustrating. With that in mind, I've already cancelled my monthly subscription and I'm about ready to quit playing altogether. This is very sad because I do enjoy this game so very much. It would be nice to know that the technical experts at Cryptic are devoting all their energies on fixing the various problems that exist in this game rather than on creating new content. There are far more problems that the game itself cannot be expanded properly with new content unless the issues are fixed
I've confirmed, to the best of my ability, that the problems are not at this end of the connection. Rebooted our gateway, and checked several websites (our fleet forums and YouTube to name a couple) to ensure our internet connection is stable, and it is.
For your reading pleasure, here's my ping/tracert data, taken 5 minutes ago.
C:\Users\****>ping patchserver.crypticstudios.com
Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=71ms TTL=48
Reply from 208.95.185.41: bytes=32 time=70ms TTL=48
Reply from 208.95.185.41: bytes=32 time=70ms TTL=48
Reply from 208.95.185.41: bytes=32 time=70ms TTL=48
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 71ms, Average = 70ms
C:\Users\****>ping accounts.crypticstudios.com
Pinging accounts.crypticstudios.com [208.95.185.165] with 32 bytes of data:
Reply from 208.95.185.165: bytes=32 time=68ms TTL=113
Reply from 208.95.185.165: bytes=32 time=70ms TTL=113
Reply from 208.95.185.165: bytes=32 time=68ms TTL=113
Reply from 208.95.185.165: bytes=32 time=101ms TTL=113
Ping statistics for 208.95.185.165:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 101ms, Average = 76ms
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 dsldevice.att.net [192.168.1.254]
2 368 ms 209 ms 201 ms 107-139-204-2.lightspeed.jcsnms.sbcglobal.net [107.139.204.2]
3 58 ms 129 ms 59 ms 99.183.77.54
4 22 ms 21 ms 22 ms 99.183.77.119
5 22 ms 24 ms 21 ms 12.83.102.17
6 30 ms 31 ms 33 ms 12.122.157.6
7 32 ms 32 ms 30 ms gar3.brhal.ip.att.net [12.122.141.189]
8 30 ms 30 ms 30 ms te0-7-0-1.ccr21.atl02.atlas.cogentco.com [154.54.13.173]
9 40 ms 65 ms 40 ms be2050.ccr41.atl01.atlas.cogentco.com [154.54.0.165]
10 48 ms 49 ms 50 ms be2168.ccr21.dca01.atlas.cogentco.com [154.54.31.94]
11 54 ms 50 ms 52 ms be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31.118]
12 61 ms 59 ms 60 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30.14]
13 57 ms 57 ms 59 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.134]
14 79 ms 71 ms 71 ms 38.111.40.114
15 72 ms 68 ms 71 ms patchserverrebirth.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Users\****>tracert accounts.crypticstudios.com
Tracing route to accounts.crypticstudios.com [208.95.185.165]
over a maximum of 30 hops:
1 1 ms <1 ms 3 ms dsldevice.att.net [192.168.1.254]
2 30 ms 40 ms 30 ms 107-139-204-2.lightspeed.jcsnms.sbcglobal.net [107.139.204.2]
3 31 ms 71 ms 23 ms 99.183.77.54
4 21 ms 22 ms 22 ms 99.183.77.119
5 27 ms 23 ms 28 ms 12.83.102.9
6 34 ms 32 ms 36 ms 12.122.157.6
7 32 ms 34 ms 32 ms gar3.brhal.ip.att.net [12.122.141.189]
8 33 ms 29 ms 30 ms te0-7-0-1.ccr21.atl02.atlas.cogentco.com [154.54.13.173]
9 43 ms 29 ms 29 ms be2051.ccr42.atl01.atlas.cogentco.com [154.54.0.161]
10 52 ms 45 ms 55 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31.98]
11 51 ms 53 ms 50 ms be2149.ccr42.jfk02.atlas.cogentco.com [154.54.31.126]
12 60 ms 60 ms 60 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
13 124 ms 82 ms 112 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
14 70 ms 72 ms 71 ms 38.111.40.114
15 68 ms 71 ms 68 ms accounts.crypticstudios.com [208.95.185.165]
Trace complete.
Edit: 50 minutes later, a new error: 'Timed out connecting to GameServer.' *sigh*
Federation Engineer, Human: U.S.S. Cobalt, NX-92925 (Fleet Shepard Miracle Worker Battlecruiser)
12th Fleet Engineering Division, Beta Squadron Captain
their server(s) need to be fixed
This might be a coincidence but ATT to L3 is saturated at the same moment I cant use launcher.
Not Cogent though.
http://www.internethealthreport.com/Main.aspx?Logout=y
Maybe a question everyone is afraid to ask, but could the latency be related to memory usage/leakage from Arc?
Not to post without some ideas:
1) Community management. Get on to the news feeds and start posting updates every few hours. Take care of us to cut down on the flame war.
2) Have your technical director on the phone with whom ever the problem is every hour on the hour requesting updates until this is resolved.
And to add to that, a little more transparency and acknowledment of problems would go a long way. There's only so much "the problem must be on your end." people are willing to take from cookie cutter customer service responses, before the pitchforks and torches come out.
Automated responses are single-handedly one of the most frustrating parts of sending a request for help.
I agree. I'd honestly prefer Morrigan (or someone else) to spam us with, "We're still aware of this issue and are still working on resolving it, still no ETA." on a daily basis than hearing nothing at all.
I mean we have things in STO itself like the Bulletin system. We have pink admin text. We have the ability to get updates via in-game mail. We have the STO launcher itself. We have ARC. We have the forums. They even have all of our e-mail addresses they can send us mail to.
It's not like PWE/Cryptic doesn't have the tools in place to keep people informed and up to date. They do. They just don't use them.
Unless it's for marketing purposes, natch.
[SIGPIC][/SIGPIC]
login. Lets see the progress being made on this issue.
Week 1
1. Login issue through ARC login, players complain.
2. Ops ask for login tracert, players comply and post them if they can get that to work.
3. Thursday patch released thing like uniforms, storyline issues, and other minor issues fixed.
Week 2
1. Still having login issue through ARC login, players complain.
2. Ops ask for login tracert, players comply and post them if they can get that to work.
3. Thursday patch released thing like uniforms, storyline issues, and other minor issues fixed. Lots
of stuff released about season 10.
Week 1 + Week 2 = Players not being able to login and play there new Delta Recruit or there
old characters.
Lets put the new toys away and get the login server fixed so people can actually play the game.
I would have to agree. Cryptic should delay Season 10 and extend the Delta Recruit event until the server issues have been fixed. While the login issues haven't affected me personally, I have every bit of sympathy for those who have been affected by it. It's not really fair for them to miss out on both these events as a result of server issues. Issues that have progressively gotten worse since the winter event.
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
tracert 208.95.186.11
Tracing route to 208.95.186.11 over a maximum of 30 hops
1 2 ms 3 ms 2 ms homeportal [192.168.1.254]
2 35 ms 27 ms 28 ms 107-218-200-1.lightspeed.mssnks.sbcglobal.net [1
07.218.200.1]
3 28 ms 28 ms 29 ms 71.150.19.52
4 32 ms 29 ms 28 ms 71.150.32.138
5 28 ms 30 ms 31 ms 71.150.32.199
6 30 ms 29 ms 27 ms 12.83.42.129
7 41 ms 38 ms 44 ms ggr3.dlstx.ip.att.net [12.122.138.17]
8 40 ms 39 ms 40 ms 192.205.36.222
9 41 ms 38 ms 37 ms be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.
53]
10 49 ms 45 ms 44 ms be2146.ccr22.iah01.atlas.cogentco.com [154.54.25
.241]
11 56 ms 56 ms 56 ms be2173.ccr42.atl01.atlas.cogentco.com [154.54.29
.117]
12 61 ms 62 ms 59 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31
.98]
13 65 ms 64 ms 65 ms be2149.ccr42.jfk02.atlas.cogentco.com [154.54.31
.126]
14 73 ms 74 ms 71 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
15 72 ms 72 ms 71 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.130]
16 77 ms 74 ms 85 ms 38.111.40.114
17 76 ms 74 ms 74 ms 208.95.186.11
Trace complete.
---> So... is Cogent Communications the source of all our distress?
If I run the trace through Cogent's Looking Glass tool the results are even worse. (http://www.cogentco.com/en/network/looking-glass)
traceroute to 208.95.186.11 (208.95.186.11), 30 hops max, 60 byte packets
1 vl99.mag01.mci01.atlas.cogentco.com (66.250.250.17) 0.289 ms 0.293 ms
2 te0-0-0-4.ccr21.mci01.atlas.cogentco.com (154.54.30.173) 0.925 ms 0.932 ms
3 be2157.ccr42.ord01.atlas.cogentco.com (154.54.6.118) 12.796 ms be2156.ccr41.ord01.atlas.cogentco.com (154.54.6.86) 12.931 ms
4 be2351.ccr21.cle04.atlas.cogentco.com (154.54.44.86) 19.858 ms be2185.ccr22.cle04.atlas.cogentco.com (154.54.43.178) 20.903 ms
5 be2189.ccr22.alb02.atlas.cogentco.com (154.54.43.185) 31.913 ms 32.430 ms
6 be2302.ccr22.bos01.atlas.cogentco.com (154.54.43.13) 35.847 ms be2299.ccr21.bos01.atlas.cogentco.com (154.54.43.9) 35.765 ms
7 te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.com (154.54.46.134) 35.755 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com (154.54.46.130) 36.247 ms
8 * *
9 * *
10 * *
11 * *
12 * *
13 * *
14 * *
15 * *
16 * *
17 * *
18 * *
19 * *
20 * *
21 * *
22 * *
23 * *
24 * *
25 * *
26 * *
27 * *
28 * *
29 * *
30 * *
It is very possible that they have a master DNS server with a corrupt routing table that is gumming up the entire works. Give them a call and see if they can refresh and rebuild their routing tables.
BTW... 48 hours and counting and still Poor to no Access to STO. The game is generally unplayable for me in its current state.
Question: How do I change proxies if the launcher does not load?
Was able to change to EU proxy yesterday and was able to play for the longest time in 10 days, no SNRS or dcs. Today seems the proxy has nothing to do with the launcher loading. Cannot sign on at all.
After dropting back to my desktop - now getting the usual 'empty launcher with black background' and a 'Loading Please Wait...' in the upper left corner. If I wait long enough it will either partially load a portion of the STO graphics (after5 5-10 minutes and not progress further..)
^^^
Had this issue randomly/intermittently since Tues. 4/7/15. No other internet functionality (or speed) is affect - just my connection to any Cryptic MMO (STO, CO, NeverWinter)
My location: Southern California, L.A. area
Tracert to Patch Server:
Tracert to Account Server:
Would give a tracert to the Login server, but it appears to be named 'cryptically'.
PWE ARC Drone says: "Your STO forum community as you have known it is ended...Display names are irrelevant...Any further sense of community is irrelevant...Resistance is futile...You will be assimilated..."
Under command prompt/ MS dos promt, I entered "ipconfig /flushdns"
But I did not reset my router or my dynamic IP.
The SNRS and DCs also stopped while on the EU gameplay proxy.
I hope this helps someone else.
30 minutes later, still waiting...
and these are performance issues! not related to the dissconnects... and occasionally not being able to even connect at all! which i am experiencing now...and.. again...something showing itself over the past about 2 weeks...but whatever...there are other places to spend my money...my point!
unless these issues over the past couple of weeks are related to some sort of major hardware or software upgrade thats been happening behind closed doors...and it will go completely live tomorrow... a new system that works towards resolving fundamental gameplay issues...my question is...How on bloody earth is the current system expected to handle season 10?! by every indication...the answer is...well...you know the answer...
this is one of my old posts...dug it up just as a reminder...
I liken the stability issues, e.g. regular amounts of lag, rubberbanding, disconnects, and the Cryptic STO team's aggressive... almost overwhelming amount of new content over the past 6 months ...to a man who wants to put a new floor on his home...the engineer tells him that his foundation on his home could use some work... but he believes he can add the addition... but any other additions would require repairing the foundation...the man...happy with his new floor... ignores the engineer and finds someone who will keep adding to his home...you can figure out what happens next...
When players experience regular stability issues the common reaction is frustration...to different degrees...frustrated players do not spend money!
If I experience regular rubberbanding for example...why would I spend $30 on a ship that I would not be able to enjoy using?
If I am a new player, why would I spend any money at all if my fundamental game playing is regularly interrupted by stability issues?
In short... new content will not continue to save the game if the foundation needs work...in fact...and no pun indented...you'll find things eventually crashing down...
As another reminder, the issues that are currently being faced are exclusive to one specific branch of engineers. The team who is in charge of handling this issue is still investigating and addressing the issue. Other teams, such as environmental artists and web developers will still be creating their respective content.
This is a red-alert issue as far as the team is concerned, however that does not mean that other teams will halt their respective work. Too often I have seen wide-spread claims that "the devs need to be stop work on everything" Tacofangs will not stop his work on Sector Space to try and resolve login issues. That is neither his job, nor is it fair to the hard work in delivering what is frankly a beautiful update. Those who have worked tirelessly to build up new content should see their work come to fruition.
In regards to the team who IS responsible for the respective login issues, I have and will continue to be pinging them trying to find resolution to an issue that is affecting all Cryptic titles.
heh, I'd love to see Tacofangs face if one where to hand him some Ethernet cables demanding he fix the connectivity problems. Might get a "dammit Cryptic I'm an environmental artist, not a network engineer!"
Oh Trendy, nice networking pun. Did you get a "Request timed out" when pinging the network team? hehehe
--->Ground Combat General Bugs Directory
Real join date: March 2012 / PvP Veteran since May 2012 (Ground and Space)
and for the guy posted before ya. You keep showing us your puns, they may illicit some response.. Nice puns always do.
I often joke around about "that one time I burned off a bunch of Caitain fur trying to fix the warp core" because in reality, that's not what I do. I post updates when I get them, I do web development, I do blogs, I do art asset generation, I do social media, I do excessive amounts of coffee.
But networking? No. Don't let me near those cables. I'd probably start biting them or something.
Image not for the faint of heart.
Using old sto long-in method, unable to connect to cryptic login server,
Using Arc unable to connect to account server.
Login to forums is accessible and working fine.
hehe, biting the networking cables? Wait...that's it! Have your network team check for Cardassian voles in the server room and then get O'Brien on the case!
http://vignette2.wikia.nocookie.net/memoryalpha/images/1/1b/Cardassian_vole_hunting.jpg/revision/latest?cb=20071218015034&path-prefix=en
That's quite a feast! I count at two Cat 5 cables, one cat 6, and one set of RCA connectors on that plate.
The network team can't do anything with that information if you don't provide a trace route. To do so:
This process greatly assists network engineers as it indicates exactly where the connectivity problem is occurring.
--->Ground Combat General Bugs Directory
Real join date: March 2012 / PvP Veteran since May 2012 (Ground and Space)
Don't worry all you need to do is power everything off and on again and make sure those cables are in secure.
At bout 7:40 PM I finished patching Tribble, tried to log in saw "Server Not Available" (That's normal I assume as you guys just put a final/new patch on it) -- so exited -- re-launched and getting the Blank/Black Baground with "Loading Please Wait..." in upper left corner.
Tracert to account server:
Tracert to Patchserver:
PWE ARC Drone says: "Your STO forum community as you have known it is ended...Display names are irrelevant...Any further sense of community is irrelevant...Resistance is futile...You will be assimilated..."