Thank you for the information Brandon. I'd like to defend Cryptic's support and say they are going above and beyond the call of duty to solve this sort of thing (not specifically this) BUT given Cryptic's track record I can understand why quite a few people are sharpening their pitchforks and lighting torches. It's not the first time Cryptic's taken something working and broken it.
Still "patience is a virtue" or for those seeking a trek quote; "Time is patience so we must be patient with it".
so i went a did a a run of malwarebytes and used CCcleaner then restarted the computer a few times. this seemed to help if only for a second. i went from the cryptic autoupdater to teh regular launcher (loading...) for about 4 min. i clicked the X on that and tried again. cuz you know sometimes it hangs up and works if you do it again. so i restarted to the launcher and cryptic autoupdater again..... gir! im glad that atleast the team here is helping with such issues. instead of the playerbase doing all the work like on other MMO fourms (hint hint nudge nudge *cough*wow*cough)
This problem was happening before the patch so that has nothing to do with it. Also apparently CO is having the same issue and they weren't patched. It seems to be a problem with the server, frankly they should probably just reboot it.
Quick question, I really haven't been reading every post in this thread, where did the devs say "it's not our fault"?
You missed the point.
Regardless about how bad it is now, Cryptic said it was our service provider's fault.
Cryptic technically blamed our connections for something in which is happening in-house.
What I know is that my connection was working fine prior to today's patch and maintenance.
looks like from some locations the "atlas.cogentco.com" is the Problem.
Routenverfolgung zu launcher.startrekonline.com [220.127.116.11] ?ber maximal
1 1 ms 1 ms 1 ms Vigor2130.lan [18.104.22.168]
2 8 ms 7 ms 9 ms 22.214.171.124
3 9 ms 9 ms 10 ms 126.96.36.199
4 16 ms 16 ms 16 ms f-ed6-i.F.DE.NET.DTAG.DE [188.8.131.52]
5 16 ms 15 ms 16 ms te0-7-0-7.ccr21.fra03.atlas.cogentco.com [13
6 24 ms 23 ms 21 ms te0-4-0-2.ccr21.ams03.atlas.cogentco.com [15
7 42 ms 40 ms 41 ms te0-5-0-7.ccr21.lpl01.atlas.cogentco.com [13
8 118 ms 103 ms 103 ms te0-2-0-3.ccr21.bos01.atlas.cogentco.com [15
9 103 ms 103 ms 104 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.
10 * * * Zeit?berschreitung der Anforderung.
11 * * * Zeit?berschreitung der Anforderung.
12 * * * Zeit?berschreitung der Anforderung.
13 * * * Zeit?berschreitung der Anforderung.
14 * * * Zeit?berschreitung der Anforderung.
15 * * * Zeit?berschreitung der Anforderung.
16 * * * Zeit?berschreitung der Anforderung.
17 * * * Zeit?berschreitung der Anforderung.
18 * * * Zeit?berschreitung der Anforderung.
19 * * * Zeit?berschreitung der Anforderung.
20 * * * Zeit?berschreitung der Anforderung.
The weird revisiting of the fr. system leads me to believe that there might be multiple points of failure. I am making a wild guess that if the US patcher fails, it rolls over to the EU patcher, and either that is overloaded, or another routing problem is occurring.
More suggestive proof that it's the Boston area...
Three more timing out at bos-xx.atlas.cogentco
DaveyNY - STO Forum Minion since February - 2009
................Star Trek Fan since Thursday Sept. 8th, 1966
There are No Longer any STO Veterans... We're Just Minions who have Played the Game for the last 5.0 years.