Just going to repost this here in the main thread. I know people are concerned about the latency issues. I just want to say that we are too.
There are a ton of variables that need to be taken into consideration, when you have a problem such as this that's affecting certain players than others. You look over demographics. Are all the players experiencing latency issues exclusively from one region? No, it's more generalized? Ok, next route of questioning. Is it failed routing through a switch that's mismanaging certain networking? Yay or nay?
If it's as simple of an ah-ha moment, the team usually catches it within an hour or so from the point of entry. This is where we see a whole lot of failed maps specific to an event and go "that's a pattern!" This is where we see that for some reason one of the Boston routers is glowing red and hissing at us.
If it's not one of those, it's usually a more nebulous problem that requires more time before we can find the solution. Are we still looking though?
You're damn right we are.
Thank you for acknowledging that there are latency issues. Part of my main gripe with that is that I've not seen a lot of communication from Cryptic's end -- which gives me the impression they either do not think there is a problem, or the problem lies with the players.
In either scenario, it gives me some peace of mind that players don't need to keep obsessing over something that is ultimately out of their hands. I'm not saying they should stop providing tracerts and other diagnostics to Cryptic, just that they can stop getting irritated because Cryptic seems to think it's on their side of things, or just does not exist at all and things are business as usual.
My speedtest. net from FL to San Jose is 17.54 mbps
FYI
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\*>Tracert 208.95.185.165
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 56 ms 25 ms 24 ms 162-206-20-2.lightspeed.dybhfl.sbcglobal.net [16
2.206.20.2]
3 25 ms 27 ms 29 ms 99.134.205.82
4 26 ms 26 ms 27 ms 12.83.114.9
5 38 ms 38 ms 38 ms 12.122.140.245
6 44 ms 39 ms 37 ms te0-0-0-1.ccr21.atl02.atlas.cogentco.com [154.54
.10.69]
7 38 ms 40 ms 38 ms be2050.ccr41.atl01.atlas.cogentco.com [154.54.0.
165]
8 54 ms 55 ms 55 ms be2168.ccr21.dca01.atlas.cogentco.com [154.54.31
.94]
9 59 ms 58 ms 58 ms be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31
.118]
10 65 ms 71 ms 64 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
11 65 ms 64 ms 64 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.134]
12 83 ms 87 ms 89 ms 38.111.40.114
13 76 ms 75 ms 78 ms accounts.crypticstudios.com [208.95.185.165]
My server/login issues today started around 1630 PST. Well, the ones severe enough for me to post about.
[EDIT] Seems to have cleared for now. Still getting lag and occasional rubberbanding, but no longer unplayable after taking a day off. Keep up the hard work folks.
With each passing day I wonder if I stepped into an alternate reality. The Cubs win the world series. Donald Trump is President. Britain leaves the EU. STO gets a dedicated PvP season. Engineers are "out of control" in STO.
Thank you for acknowledging that there are latency issues. Part of my main gripe with that is that I've not seen a lot of communication from Cryptic's end -- which gives me the impression they either do not think there is a problem, or the problem lies with the players.
In either scenario, it gives me some peace of mind that players don't need to keep obsessing over something that is ultimately out of their hands. I'm not saying they should stop providing tracerts and other diagnostics to Cryptic, just that they can stop getting irritated because Cryptic seems to think it's on their side of things, or just does not exist at all and things are business as usual.
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.
Just got disconnected from the Login server and can't get back in. I tried from the actual client log in screen and could get a response from the account server - but either would get "Login Server Timed out' - or get to the character list; but no character would complete it's 'Loading' phase to progress further - and I would get disconnected from the Login server and dropped to the login screen again.
Tracerts follow:
Cryptic 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 21 ms 22 ms 23-114-212-2.lightspeed.irvnca.sbcglobal.net [23.114.***.***]
3 21 ms 21 ms 20 ms 75.20.0.202
4 22 ms 23 ms 24 ms 12.83.38.153
5 24 ms 24 ms 22 ms 12.123.132.137
6 23 ms 22 ms 22 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 73 ms 71 ms 72 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 89 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 97 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
14 99 ms 106 ms 111 ms 38.111.40.114
15 99 ms 99 ms 99 ms accounts.crypticstudios.com [208.95.185.165]
Trace complete.
C:\Users\***>
Cryptic 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 19 ms 19 ms 19 ms 23-114-212-2.lightspeed.irvnca.sbcglobal.net [23.114.***.***]
3 22 ms 21 ms 20 ms 75.20.0.202
4 23 ms 23 ms 24 ms 12.83.38.157
5 23 ms 25 ms 25 ms 12.123.132.137
6 22 ms 23 ms 22 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 74 ms 71 ms 73 ms be2173.ccr42.atl01.atlas.cogentco.com [154.54.29.117]
10 88 ms 89 ms 88 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31.98]
11 90 ms 89 ms 90 ms be2149.ccr42.jfk02.atlas.cogentco.com [154.54.31.126]
12 96 ms 96 ms 95 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
13 97 ms 98 ms 96 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
14 109 ms 109 ms 106 ms 38.111.40.114
15 102 ms 100 ms 98 ms xboxpatchserver.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Users\***>
/sigh
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..."
For the first time in a while, I'm rubberbanding everywhere, not just certain STFs or in ESD as per normal. I just finished with rubberbanding my way through Of Bajor, that was fun (not)
It's good to know the team's on it, though. Not much more that can be done from the players' end other than wait.
Just going to repost this here in the main thread. I know people are concerned about the latency issues. I just want to say that we are too.
There are a ton of variables that need to be taken into consideration, when you have a problem such as this that's affecting certain players than others. You look over demographics. Are all the players experiencing latency issues exclusively from one region? No, it's more generalized? Ok, next route of questioning. Is it failed routing through a switch that's mismanaging certain networking? Yay or nay?
If it's as simple of an ah-ha moment, the team usually catches it within an hour or so from the point of entry. This is where we see a whole lot of failed maps specific to an event and go "that's a pattern!" This is where we see that for some reason one of the Boston routers is glowing red and hissing at us.
If it's not one of those, it's usually a more nebulous problem that requires more time before we can find the solution. Are we still looking though?
You're damn right we are.
Of course Trendy, those of us in the player base who have networking knowledge and/or experience understand it's a process that takes time. It is, however, extremely frustrating, and PWE and Cryptic should be willing to listen to and understand our complaints.
the fact that cardassian keldon classships are near to impossible unless you have a close respawn spot, op ship your self which if your broke you cant get, and unless you have strong special ship equip stuff. The game needs to make it where there are either closer respawn point or fix those classes opedness.
I'm a U-verse ATT user here, and it's 830 am est in the morning and it's still an issue going on. So, I don't know. I think I might take a few days off till things get ironed out (hopefully).
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.
Comments
Thank you for acknowledging that there are latency issues. Part of my main gripe with that is that I've not seen a lot of communication from Cryptic's end -- which gives me the impression they either do not think there is a problem, or the problem lies with the players.
In either scenario, it gives me some peace of mind that players don't need to keep obsessing over something that is ultimately out of their hands. I'm not saying they should stop providing tracerts and other diagnostics to Cryptic, just that they can stop getting irritated because Cryptic seems to think it's on their side of things, or just does not exist at all and things are business as usual.
My speedtest. net from FL to San Jose is 17.54 mbps
FYI
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\*>Tracert 208.95.185.165
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 56 ms 25 ms 24 ms 162-206-20-2.lightspeed.dybhfl.sbcglobal.net [16
2.206.20.2]
3 25 ms 27 ms 29 ms 99.134.205.82
4 26 ms 26 ms 27 ms 12.83.114.9
5 38 ms 38 ms 38 ms 12.122.140.245
6 44 ms 39 ms 37 ms te0-0-0-1.ccr21.atl02.atlas.cogentco.com [154.54
.10.69]
7 38 ms 40 ms 38 ms be2050.ccr41.atl01.atlas.cogentco.com [154.54.0.
165]
8 54 ms 55 ms 55 ms be2168.ccr21.dca01.atlas.cogentco.com [154.54.31
.94]
9 59 ms 58 ms 58 ms be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31
.118]
10 65 ms 71 ms 64 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
11 65 ms 64 ms 64 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.134]
12 83 ms 87 ms 89 ms 38.111.40.114
13 76 ms 75 ms 78 ms accounts.crypticstudios.com [208.95.185.165]
Trace complete.
My server/login issues today started around 1630 PST. Well, the ones severe enough for me to post about.
[EDIT] Seems to have cleared for now. Still getting lag and occasional rubberbanding, but no longer unplayable after taking a day off. Keep up the hard work folks.
Mine Trap Supporter
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.
http://www.warren-news.com/peeringpoints.htm
I'm on Comcast Business, so to the first no. As for Cogent, I can't say. I get fast times through to it and yet I still lag in everything I do.
Top DPS 102k
Tracerts follow:
Cryptic Account Server:
Cryptic Patchserver:
/sigh
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..."
It's good to know the team's on it, though. Not much more that can be done from the players' end other than wait.
Of course Trendy, those of us in the player base who have networking knowledge and/or experience understand it's a process that takes time. It is, however, extremely frustrating, and PWE and Cryptic should be willing to listen to and understand our complaints.
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?