Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms 2 ms <1 ms CISCO69961 [192.168.1.1]
2 34 ms 15 ms 25 ms cpe-024-211-140-001.nc.res.rr.com [24.211.140.1]
3 19 ms 8 ms 9 ms te0-0-0-6-1132.rlghnca-rtr1.nc.rr.com [66.26.46.
169]
4 9 ms 8 ms 9 ms ae19.rlghncpop-rtr1.southeast.rr.com [24.93.64.0
]
5 15 ms 22 ms 23 ms 107.14.19.44
6 16 ms 18 ms 16 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 17 ms 18 ms 18 ms te0-7-0-11.mpd22.iad02.atlas.cogentco.com [154.5
4.10.209]
8 17 ms 20 ms 16 ms te0-5-0-2.mpd22.dca01.atlas.cogentco.com [154.54
.2.41]
9 25 ms 24 ms 28 ms te0-6-0-8.mpd22.jfk02.atlas.cogentco.com [154.54
.26.174]
10 29 ms 31 ms 31 ms te0-3-0-5.ccr21.bos01.atlas.cogentco.com [154.54
.44.34]
11 31 ms 30 ms 32 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
12 * * 51 ms 38.111.40.114
13 * * * Request timed out.
14 32 ms * * 208.95.185.41
15 * * * Request timed out.
16 * * 35 ms 208.95.185.41
Tracing route to accounts.crypticstudios.com [208.95.185.165]
over a maximum of 30 hops:
1 47 ms <1 ms 3 ms CISCO69961 [192.168.1.1]
2 16 ms 18 ms 18 ms cpe-024-211-140-001.nc.res.rr.com [24.211.140.1]
3 12 ms 9 ms 8 ms te0-0-0-6-1132.rlghnca-rtr1.nc.rr.com [66.26.46.
169]
4 10 ms 12 ms 13 ms ae19.rlghncpop-rtr1.southeast.rr.com [24.93.64.0
]
5 23 ms 23 ms 22 ms ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]
6 17 ms 24 ms 18 ms 107.14.19.133
7 18 ms 18 ms 20 ms te0-7-0-11.mpd22.iad02.atlas.cogentco.com [154.5
4.10.209]
8 16 ms 19 ms 18 ms te0-3-0-1.mpd22.dca01.atlas.cogentco.com [154.54
.30.117]
9 24 ms 27 ms 24 ms te0-3-0-6.mpd22.jfk02.atlas.cogentco.com [154.54
.3.234]
10 30 ms 30 ms 34 ms te0-1-0-5.ccr21.bos01.atlas.cogentco.com [154.54
.44.30]
11 132 ms 204 ms 218 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
12 * * * Request timed out.
13 30 ms 30 ms 31 ms accounts.crypticstudios.com [208.95.185.165]
Cryptic is still talking about "launcher issues" while the problem is the availability of their patchserver.
The on-demand patching ingame doesn't work properly either.
This also allows only one conclusion: Cryptic is lying. They did not find any sort of solution yesterday - they probably didn't do anything.
Actually the funny thing is, while I hate the fact that this stands true, cryptic has given nearly zero information about whats going on anyways. They didn't actually say what happened last night, that was myself and a few others.
The only things I know that are absolutely true right now is last night a border network device failed in an internap cabinet. The cascading effect of this was pretty nasty and it affected a rather large number of user groups. The catastrophe really just shows that redundancy wasn't in place, which in and of itself was bad. Chances are right now they're testing why that failed if there is any reasoning to what they're doing.
That being said, even the small glimmer of info we've been given isn't wrong nor is it lying, its just not giving any truth - its whitewashed "please listen to this hold music" info that doesn't provide any chance for saying the WRONG thing and thereby limits the community manager's liability for wrong or misleading information.
In other words, its third hand and we're getting the timeshare brochure end of it.
Ok, so I don't pay for this game. I don't expect much either. But this is definitely getting annoying. I was able to play around 1:30p (-5 GMT). Got booted during map change at around 3:30p. Can't load back in at 5p? What the heck???
>tracert launcher.startrekonline.com
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 2 ms <1 ms 1 ms **************
2 * * * Request timed out.
3 8 ms 9 ms 15 ms dtr02bgrpmi-tge-0-1-1-3.bgrp.mi.charter.com [96.34.34.162]
4 10 ms 11 ms 10 ms dtr02rcfrmi-tge-0-0-1-0.rcfr.mi.charter.com [96.34.34.192]
5 13 ms 22 ms 23 ms crr01aldlmi-tge-0-6-0-7.aldl.mi.charter.com [96.34.34.92]
6 17 ms 23 ms 23 ms bbr01aldlmi-bue-1.aldl.mi.charter.com [96.34.2.8]
7 17 ms 22 ms 23 ms bbr01chcgil-bue-4.chcg.il.charter.com [96.34.0.99]
8 19 ms 21 ms 23 ms bbr02chcgil-bue-6.chcg.il.charter.com [96.34.0.67]
9 16 ms 18 ms 17 ms te0-2-0-0.ccr21.ord03.atlas.cogentco.com [38.122.180.81]
10 19 ms 17 ms 22 ms te0-4-0-0.mpd21.ord01.atlas.cogentco.com [154.54.41.53]
11 40 ms 128 ms 40 ms te0-2-0-2.ccr21.bos01.atlas.cogentco.com [154.54.43.178]
12 115 ms 42 ms 121 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
>tracert accounts.crypticstudios.com
Tracing route to accounts.crypticstudios.com [208.95.185.165]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms **************
2 * * * Request timed out.
3 9 ms 9 ms 15 ms dtr02bgrpmi-tge-0-1-1-3.bgrp.mi.charter.com [96.34.34.162]
4 19 ms 10 ms 11 ms dtr02rcfrmi-tge-0-0-1-0.rcfr.mi.charter.com [96.34.34.192]
5 18 ms 22 ms 11 ms crr01aldlmi-tge-0-6-0-7.aldl.mi.charter.com [96.34.34.92]
6 14 ms 14 ms 16 ms bbr01aldlmi-bue-1.aldl.mi.charter.com [96.34.2.8]
7 20 ms 23 ms 28 ms bbr01chcgil-bue-4.chcg.il.charter.com [96.34.0.99]
8 38 ms 31 ms 23 ms bbr02chcgil-bue-6.chcg.il.charter.com [96.34.0.67]
9 19 ms 16 ms 17 ms te0-5-0-4.ccr21.ord03.atlas.cogentco.com [38.122.180.25]
10 16 ms 16 ms 17 ms te0-3-0-1.mpd21.ord01.atlas.cogentco.com [154.54.2.93]
11 41 ms 39 ms 41 ms te0-7-0-8.ccr21.bos01.atlas.cogentco.com [154.54.24.53]
12 47 ms 39 ms 40 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
13 * * * Request timed out.
14 43 ms 41 ms 40 ms accounts.crypticstudios.com [208.95.185.165]
To me this looks like:
Cryptic didn't do anything yesterday, the network worked its thing out.
The whole diagnostic thing today is a sham to mask a plain repeat of the problem
They're doing nothing again.
Next time there will be an "emergency downtime" to address this - just another ruse for Cryptic not doing anything and the issue repeating itself.
Star Wars the Old Republic
Lord of the Rings Online
Planetside 2
Alternatively, anyone spending subscriptions on STO or thinking of spending money on it. Go get a subscription to another MMO or buy a better game. If this garbage service continues your going to NEED another game to keep you busy while waiting for Cryptic to become competant.
meh setting up SWTOR now....damn this mess:rolleyes:
As a SWTOR subscriber, the CS isn't any better there. There was a point last month were we could not buy Cartel Coins(their version of Zen) for over a week. They kept on blaming the customer when clearly it was over 90% of the community who could not use the shopping cart system there.
The issue appeared before the patch yesterday, so it's unrelated.
Cheers,
Brandon =/\=
From your perspective, right?
Branflakes, I respect all the hard you folks put into this game, and I have enjoyed virtually every other aspect of "Star Trek: Online". As someone who is sitting on the outside, the only thing I can verify is that this occurred after the patch and maintenance. I know you guys do not have a reason to lie; however, I just have a problem with seeing this as a coincidence.
If you guys can repeat this in-house, I just have this feeling it was cause in-house.
To me this looks like:
Cryptic didn't do anything yesterday, the network worked its thing out.
The whole diagnostic thing today is a sham to mask a plain repeat of the problem
They're doing nothing again.
Next time there will be an "emergency downtime" to address this - just another ruse for Cryptic not doing anything and the issue repeating itself.
:eek:
Conspiracy.
This is why I love the forms, random nonsense that's just funny, and pointless like a sketch comedy show....but sad at the same time...but mostly funny.:D
Branflakes, I respect all the hard you folks put into this game, and I have enjoyed virtually every other aspect of "Star Trek: Online". As someone who is sitting on the outside, the only thing I can verify is that this occurred after the patch and maintenance. I know you guys do not have a reason to lie; however, I just have a problem with seeing this as a coincidence.
I started having this problem 30 minutes before the maintenance downtime yesterday. I just assumed they started early, but the symptoms were exactly the same. And others claim to have been able to play right up to the scheduled downtime.
As hard as it can be to accept, correlation =/= causation.
Im having the same problem, a popup say trying to update the launcher please be patient, tried to conect 1 and 2 times. then an error message is displayed saying unable to establish a conection to patch server. Please check your internet conection. If problem persists, please contact Tech Support. Its been doing this since 1600 yesterday and still doesn't work today.
Seriously, before the patch was applied yesterday, I had absolutely no problem with logging into the system. Everything ran smoothly. Once the system went down, I ran that darn test four times. I waited an entire day, so that I could sign into the game.
If Cryptic is able to repeat the issue in-house, the problem originated with code they implemented in-house.
I don't believe in coincidences.
Unfortunately this is kind of where the difficulty in interpretation comes into play.
Since the real problem is a bit of a tier 4 issue, its not easy to explain whats going on.
The majority of companies in the internet world cannot afford the network hardware required to power the games we play, so in order to facilitate it there is an outside vendor that provides and manages it. There is (nearly) no network issue that is not capable of being replicated, so the capability to repeat is unfortunately irrelevant.
If I had to speculate, the issue they're testing is whether or not the redundancy is now functioning properly or not. Last night shouldn't have happened - there should be at least n+1 redundancy for the hardware that failed, and we should have experienced a quick hiccup/disconnect when it switched over, but that is about it. So, either the redundancy check failed, the switch failed, the secondary/redundant copy wasn't configured fully, or both pieces were bad. Could have been a disconnected cable, could have been a bad heartbeat.
Given what I saw from my own tests last night, it seemed that the network device that was causing problems responded - so there is a good chance that it didn't switch over because the device was still "up" but was not fulfilling traffic needs. You would be surprised how often this happens.
Network admins and engineers are not cheap - its very rare that a gaming company, especially one as small as PWE, have them on staff directly. Moreso, its even rarer that a small company be able to afford (and actually have) the hardware itself - which, per piece, even the smaller ones are over 10k a piece. Couple that with maintenance and the annual salary, its really just a rock and a hard place.
I think we all are just going to have to wait and let them work it out. I'm sure they are trying their best to fix it. I really don't see how having a go at them on here is going to solve anything.
And now its grabbed me as well. Had no problems at all yesterday after playing 10 hours or so, today had played about 3 hours and the game just went down and now I'm having this problem. Is it propagating? ::gasp:: Will it take down the whole intertubes?!?
As a SWTOR subscriber, the CS isn't any better there. There was a point last month were we could not buy Cartel Coins(their version of Zen) for over a week. They kept on blaming the customer when clearly it was over 90% of the community who could not use the shopping cart system there.
Is there any MMO that doesn't have the odd few days of downtime?
Unfortunately this is kind of where the difficulty in interpretation comes into play.
Since the real problem is a bit of a tier 4 issue, its not easy to explain whats going on.
The majority of companies in the internet world cannot afford the network hardware required to power the games we play, so in order to facilitate it there is an outside vendor that provides and manages it. There is (nearly) no network issue that is not capable of being replicated, so the capability to repeat is unfortunately irrelevant.
If I had to speculate, the issue they're testing is whether or not the redundancy is now functioning properly or not. Last night shouldn't have happened - there should be at least n+1 redundancy for the hardware that failed, and we should have experienced a quick hiccup/disconnect when it switched over, but that is about it. So, either the redundancy check failed, the switch failed, the secondary/redundant copy wasn't configured fully, or both pieces were bad. Could have been a disconnected cable, could have been a bad heartbeat.
Given what I saw from my own tests last night, it seemed that the network device that was causing problems responded - so there is a good chance that it didn't switch over because the device was still "up" but was not fulfilling traffic needs. You would be surprised how often this happens.
Network admins and engineers are not cheap - its very rare that a gaming company, especially one as small as PWE, have them on staff directly. Moreso, its even rarer that a small company be able to afford (and actually have) the hardware itself - which, per piece, even the smaller ones are over 10k a piece. Couple that with maintenance and the annual salary, its really just a rock and a hard place.
Thanks for the explanation there, it does start making sense. However, the fact that there has been ZERO communication from PWE's end (BranFlakes, are you listening?) about what is causing the issue, much less when it will be resolved, that's what's ticking most of us off in the first place.
Lane Bjorn Jorgensson, Captain, ISS Voltaire
Here's a map to show how much they've screwed up the game map.
Well, I just started playing this game yesterday. I had a few issues starting the game, but after a quick youtube visit I got it figured out. Yesterday I enjoyed the game so much, I decided to buy the steam starter pack and possibly subscribe. Got up today clicked the game and the same issue everyone is having here, "unable to establish connection to patch server" etc. Included with all the complaints I see here, leaves me wondering if anyone should spend any money here at all!
Who in their right mind runs invasive tests such as this, knowing it will likely cause major issues for people again, whilst the game is live? Surely tests such as these should have been carried out during a maintenance period. An emergency maintenance at least should have been called.
One other symptom I have noticed that I have not seen anyone else mention is I cannot browse the C-Store from within my browser whilst this is happening. Was the same last night.
Is there any MMO that doesn't have the odd few days of downtime?
STO seems more supported than TOR is.
to be fair, i may be moaning but you do have a point here.
STO is rarely down, and im usually able to play with no problems. hopefully this is sorted soon, and that cryptic are trying their hardest to get it sorted quickly.
Unfortunately this is kind of where the difficulty in interpretation comes into play.
Since the real problem is a bit of a tier 4 issue, its not easy to explain whats going on.
The majority of companies in the internet world cannot afford the network hardware required to power the games we play, so in order to facilitate it there is an outside vendor that provides and manages it. There is (nearly) no network issue that is not capable of being replicated, so the capability to repeat is unfortunately irrelevant.
If I had to speculate, the issue they're testing is whether or not the redundancy is now functioning properly or not. Last night shouldn't have happened - there should be at least n+1 redundancy for the hardware that failed, and we should have experienced a quick hiccup/disconnect when it switched over, but that is about it. So, either the redundancy check failed, the switch failed, the secondary/redundant copy wasn't configured fully, or both pieces were bad. Could have been a disconnected cable, could have been a bad heartbeat.
Given what I saw from my own tests last night, it seemed that the network device that was causing problems responded - so there is a good chance that it didn't switch over because the device was still "up" but was not fulfilling traffic needs. You would be surprised how often this happens.
Network admins and engineers are not cheap - its very rare that a gaming company, especially one as small as PWE, have them on staff directly. Moreso, its even rarer that a small company be able to afford (and actually have) the hardware itself - which, per piece, even the smaller ones are over 10k a piece. Couple that with maintenance and the annual salary, its really just a rock and a hard place.
So the duct tape and paper clips didnt work this time......damn:rolleyes:
Its stands as a cruel indication that even Cryptic knows the playerbase has little faith in anything they say or promise. The real kicker is rubbing the customer nose in the fact OTHER players are not affected.
Yeah, thanks for telling me others can play while I cant for the second day in a row. Apparantly, Cryptic only really give a TRIBBLE if a problem is serious enough to affect the ENTIRE community.
Otherwise, as long as some folks are buying lockboxes who cares ?
Yeah them saying that others aren't being affected does make it seem like they don't think its all that important. If everyone was affected then they would be putting more effort into it. Then again they probably don't have the resources to give it all the attention it needs. Who knows. I just know I won't be buying the lifetime membership I was going to buy.
I am a subscriber to swtor, to eve, was to wow for a long time, and to a certain extent every other MMO at one point or another.
Running an MMO is impossible to be perfect at. Blizzard lost character accounts when migrating servers, EVE had years of network problems because single stations were so populated it was affecting the entire cluster. SWTOR has had downtime, bad patches... and the list goes on.
Running a game that is used world wide by a collective customer base that is in the hundreds of thousand into the same, single, cluster... is not easy, and it comes with some major pitfalls. The bigger they are the harder they fall.
Its not like an FPS where a server may have 32 players on it per server. When an MMO goes down, it affects everyone. The perspective is difficult to embrace, and it makes what is a typical problem on the internet seem all the more disastrous.
Comments
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms 2 ms <1 ms CISCO69961 [192.168.1.1]
2 34 ms 15 ms 25 ms cpe-024-211-140-001.nc.res.rr.com [24.211.140.1]
3 19 ms 8 ms 9 ms te0-0-0-6-1132.rlghnca-rtr1.nc.rr.com [66.26.46.
169]
4 9 ms 8 ms 9 ms ae19.rlghncpop-rtr1.southeast.rr.com [24.93.64.0
]
5 15 ms 22 ms 23 ms 107.14.19.44
6 16 ms 18 ms 16 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 17 ms 18 ms 18 ms te0-7-0-11.mpd22.iad02.atlas.cogentco.com [154.5
4.10.209]
8 17 ms 20 ms 16 ms te0-5-0-2.mpd22.dca01.atlas.cogentco.com [154.54
.2.41]
9 25 ms 24 ms 28 ms te0-6-0-8.mpd22.jfk02.atlas.cogentco.com [154.54
.26.174]
10 29 ms 31 ms 31 ms te0-3-0-5.ccr21.bos01.atlas.cogentco.com [154.54
.44.34]
11 31 ms 30 ms 32 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
12 * * 51 ms 38.111.40.114
13 * * * Request timed out.
14 32 ms * * 208.95.185.41
15 * * * Request timed out.
16 * * 35 ms 208.95.185.41
Trace complete.
C:\Windows\system32>tracert launcher.startrekonline.com
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms CISCO69961 [192.168.1.1]
2 72 ms 22 ms 11 ms cpe-024-211-140-001.nc.res.rr.com [24.211.140.1]
3 12 ms 11 ms 60 ms te0-0-0-6-1132.rlghnca-rtr1.nc.rr.com [66.26.46.
169]
4 * 8 ms 8 ms ae19.rlghncpop-rtr1.southeast.rr.com [24.93.64.0
]
5 24 ms 23 ms 23 ms 107.14.19.44
6 16 ms 17 ms 15 ms 107.14.19.133
7 18 ms 18 ms 18 ms te0-7-0-11.mpd21.iad02.atlas.cogentco.com [154.5
4.13.157]
8 18 ms 18 ms 18 ms te0-0-0-4.mpd21.dca01.atlas.cogentco.com [154.54
.24.97]
9 25 ms 24 ms 25 ms te0-7-0-14.mpd21.jfk02.atlas.cogentco.com [154.5
4.41.22]
10 31 ms 30 ms 31 ms te0-6-0-0.ccr21.bos01.atlas.cogentco.com [154.54
.0.29]
11 30 ms 52 ms 32 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
12 35 ms * 33 ms 38.111.40.114
13 31 ms * * sitedown.startrekonline.com [208.95.185.44]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 33 ms * * sitedown.startrekonline.com [208.95.185.44]
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\Windows\system32>tracert accounts.crypticstudios.com
Tracing route to accounts.crypticstudios.com [208.95.185.165]
over a maximum of 30 hops:
1 47 ms <1 ms 3 ms CISCO69961 [192.168.1.1]
2 16 ms 18 ms 18 ms cpe-024-211-140-001.nc.res.rr.com [24.211.140.1]
3 12 ms 9 ms 8 ms te0-0-0-6-1132.rlghnca-rtr1.nc.rr.com [66.26.46.
169]
4 10 ms 12 ms 13 ms ae19.rlghncpop-rtr1.southeast.rr.com [24.93.64.0
]
5 23 ms 23 ms 22 ms ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]
6 17 ms 24 ms 18 ms 107.14.19.133
7 18 ms 18 ms 20 ms te0-7-0-11.mpd22.iad02.atlas.cogentco.com [154.5
4.10.209]
8 16 ms 19 ms 18 ms te0-3-0-1.mpd22.dca01.atlas.cogentco.com [154.54
.30.117]
9 24 ms 27 ms 24 ms te0-3-0-6.mpd22.jfk02.atlas.cogentco.com [154.54
.3.234]
10 30 ms 30 ms 34 ms te0-1-0-5.ccr21.bos01.atlas.cogentco.com [154.54
.44.30]
11 132 ms 204 ms 218 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
12 * * * Request timed out.
13 30 ms 30 ms 31 ms accounts.crypticstudios.com [208.95.185.165]
Trace complete.
C:\Windows\system32>
Actually the funny thing is, while I hate the fact that this stands true, cryptic has given nearly zero information about whats going on anyways. They didn't actually say what happened last night, that was myself and a few others.
The only things I know that are absolutely true right now is last night a border network device failed in an internap cabinet. The cascading effect of this was pretty nasty and it affected a rather large number of user groups. The catastrophe really just shows that redundancy wasn't in place, which in and of itself was bad. Chances are right now they're testing why that failed if there is any reasoning to what they're doing.
That being said, even the small glimmer of info we've been given isn't wrong nor is it lying, its just not giving any truth - its whitewashed "please listen to this hold music" info that doesn't provide any chance for saying the WRONG thing and thereby limits the community manager's liability for wrong or misleading information.
In other words, its third hand and we're getting the timeshare brochure end of it.
>tracert launcher.startrekonline.com
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 2 ms <1 ms 1 ms **************
2 * * * Request timed out.
3 8 ms 9 ms 15 ms dtr02bgrpmi-tge-0-1-1-3.bgrp.mi.charter.com [96.34.34.162]
4 10 ms 11 ms 10 ms dtr02rcfrmi-tge-0-0-1-0.rcfr.mi.charter.com [96.34.34.192]
5 13 ms 22 ms 23 ms crr01aldlmi-tge-0-6-0-7.aldl.mi.charter.com [96.34.34.92]
6 17 ms 23 ms 23 ms bbr01aldlmi-bue-1.aldl.mi.charter.com [96.34.2.8]
7 17 ms 22 ms 23 ms bbr01chcgil-bue-4.chcg.il.charter.com [96.34.0.99]
8 19 ms 21 ms 23 ms bbr02chcgil-bue-6.chcg.il.charter.com [96.34.0.67]
9 16 ms 18 ms 17 ms te0-2-0-0.ccr21.ord03.atlas.cogentco.com [38.122.180.81]
10 19 ms 17 ms 22 ms te0-4-0-0.mpd21.ord01.atlas.cogentco.com [154.54.41.53]
11 40 ms 128 ms 40 ms te0-2-0-2.ccr21.bos01.atlas.cogentco.com [154.54.43.178]
12 115 ms 42 ms 121 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
>tracert accounts.crypticstudios.com
Tracing route to accounts.crypticstudios.com [208.95.185.165]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms **************
2 * * * Request timed out.
3 9 ms 9 ms 15 ms dtr02bgrpmi-tge-0-1-1-3.bgrp.mi.charter.com [96.34.34.162]
4 19 ms 10 ms 11 ms dtr02rcfrmi-tge-0-0-1-0.rcfr.mi.charter.com [96.34.34.192]
5 18 ms 22 ms 11 ms crr01aldlmi-tge-0-6-0-7.aldl.mi.charter.com [96.34.34.92]
6 14 ms 14 ms 16 ms bbr01aldlmi-bue-1.aldl.mi.charter.com [96.34.2.8]
7 20 ms 23 ms 28 ms bbr01chcgil-bue-4.chcg.il.charter.com [96.34.0.99]
8 38 ms 31 ms 23 ms bbr02chcgil-bue-6.chcg.il.charter.com [96.34.0.67]
9 19 ms 16 ms 17 ms te0-5-0-4.ccr21.ord03.atlas.cogentco.com [38.122.180.25]
10 16 ms 16 ms 17 ms te0-3-0-1.mpd21.ord01.atlas.cogentco.com [154.54.2.93]
11 41 ms 39 ms 41 ms te0-7-0-8.ccr21.bos01.atlas.cogentco.com [154.54.24.53]
12 47 ms 39 ms 40 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
13 * * * Request timed out.
14 43 ms 41 ms 40 ms accounts.crypticstudios.com [208.95.185.165]
Trace complete.
Cryptic didn't do anything yesterday, the network worked its thing out.
The whole diagnostic thing today is a sham to mask a plain repeat of the problem
They're doing nothing again.
Next time there will be an "emergency downtime" to address this - just another ruse for Cryptic not doing anything and the issue repeating itself.
:eek:
Conspiracy.
He's dead, Jim.
ottawa ontario canada
Lord of the Rings Online
Planetside 2
Alternatively, anyone spending subscriptions on STO or thinking of spending money on it. Go get a subscription to another MMO or buy a better game. If this garbage service continues your going to NEED another game to keep you busy while waiting for Cryptic to become competant.
As a SWTOR subscriber, the CS isn't any better there. There was a point last month were we could not buy Cartel Coins(their version of Zen) for over a week. They kept on blaming the customer when clearly it was over 90% of the community who could not use the shopping cart system there.
Branflakes, I respect all the hard you folks put into this game, and I have enjoyed virtually every other aspect of "Star Trek: Online". As someone who is sitting on the outside, the only thing I can verify is that this occurred after the patch and maintenance. I know you guys do not have a reason to lie; however, I just have a problem with seeing this as a coincidence.
If you guys can repeat this in-house, I just have this feeling it was cause in-house.
Before the patch was implemented, the game was working just fine.
Just sayin'..
This is why I love the forms, random nonsense that's just funny, and pointless like a sketch comedy show....but sad at the same time...but mostly funny.:D
I started having this problem 30 minutes before the maintenance downtime yesterday. I just assumed they started early, but the symptoms were exactly the same. And others claim to have been able to play right up to the scheduled downtime.
As hard as it can be to accept, correlation =/= causation.
For some people - just like the issue now.
Just sayin'...
Unfortunately this is kind of where the difficulty in interpretation comes into play.
Since the real problem is a bit of a tier 4 issue, its not easy to explain whats going on.
The majority of companies in the internet world cannot afford the network hardware required to power the games we play, so in order to facilitate it there is an outside vendor that provides and manages it. There is (nearly) no network issue that is not capable of being replicated, so the capability to repeat is unfortunately irrelevant.
If I had to speculate, the issue they're testing is whether or not the redundancy is now functioning properly or not. Last night shouldn't have happened - there should be at least n+1 redundancy for the hardware that failed, and we should have experienced a quick hiccup/disconnect when it switched over, but that is about it. So, either the redundancy check failed, the switch failed, the secondary/redundant copy wasn't configured fully, or both pieces were bad. Could have been a disconnected cable, could have been a bad heartbeat.
Given what I saw from my own tests last night, it seemed that the network device that was causing problems responded - so there is a good chance that it didn't switch over because the device was still "up" but was not fulfilling traffic needs. You would be surprised how often this happens.
Network admins and engineers are not cheap - its very rare that a gaming company, especially one as small as PWE, have them on staff directly. Moreso, its even rarer that a small company be able to afford (and actually have) the hardware itself - which, per piece, even the smaller ones are over 10k a piece. Couple that with maintenance and the annual salary, its really just a rock and a hard place.
Is there any MMO that doesn't have the odd few days of downtime?
STO seems more supported than TOR is.
Thanks for the explanation there, it does start making sense. However, the fact that there has been ZERO communication from PWE's end (BranFlakes, are you listening?) about what is causing the issue, much less when it will be resolved, that's what's ticking most of us off in the first place.
Here's a map to show how much they've screwed up the game map.
One other symptom I have noticed that I have not seen anyone else mention is I cannot browse the C-Store from within my browser whilst this is happening. Was the same last night.
U.S.S Banshee
Federation Fleet
to be fair, i may be moaning but you do have a point here.
STO is rarely down, and im usually able to play with no problems. hopefully this is sorted soon, and that cryptic are trying their hardest to get it sorted quickly.
Yeah them saying that others aren't being affected does make it seem like they don't think its all that important. If everyone was affected then they would be putting more effort into it. Then again they probably don't have the resources to give it all the attention it needs. Who knows. I just know I won't be buying the lifetime membership I was going to buy.
#Edit: Whooo, I got an Internet Explorer 404 page in the launcher!
He's dead, Jim.
Running an MMO is impossible to be perfect at. Blizzard lost character accounts when migrating servers, EVE had years of network problems because single stations were so populated it was affecting the entire cluster. SWTOR has had downtime, bad patches... and the list goes on.
Running a game that is used world wide by a collective customer base that is in the hundreds of thousand into the same, single, cluster... is not easy, and it comes with some major pitfalls. The bigger they are the harder they fall.
Its not like an FPS where a server may have 32 players on it per server. When an MMO goes down, it affects everyone. The perspective is difficult to embrace, and it makes what is a typical problem on the internet seem all the more disastrous.
idk I only play this, SWTOR, and DCUO(on my PS3). It's not like STO to have this much TRIBBLE-ups as it had within the last day.
I'm thinking of going back to DCUO for a few hours...or so.
Yeah, it's pretty damn unwise.
Normally our ire is focused at the game...
but in times as these it focuses on Cryptic and the forums.
He's dead, Jim.