Captains, as I've mentioned, the team is continuing to investigate. This started occurring before the patch, so it's not related. The reason I'm letting you know that "there are a ton of players in-game" is to provide more transparency on the issue and to let you know that it does not seem to be affecting everyone. There is no ETA I can provide, and I will continue to update you as I receive more information.
Cheers,
Brandon =/\=
So why was this not fixed with the patch?
If you had this issue prior to today's maintenance and patch, why did Cryptic allow the problem to get more wide spread?
Did anyone try to stop this before it got out of hand?
That's not the only place they're having connection issues. My trace got stopped at Perfect World's connection:
perfectworldent-4.border11.bsn.pnap.net
Just looking at that...
bsn.pnap = the Boston Area again.
STO Member since February 2009. I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born! Forever a STO Veteran-Minion
Seriously, what's with the finger pointing out of house? Cryptic's software worked fine before they "fixed" things, and now, after a "fix" they want to say that it's an ISP fault? Seems kinda donkeyish to me.
Please don't buy into the "it's not our fault" line. I have empathy for the devs, but no respect for shirking responsibility.
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"?
As has been shown, some packets ARE getting through, but then the next being blocked.
My connection also does not go through Cogent. Mine goes through Alter Communications. It does, interestingly, go through Boston as well, but not through Cogent.
I live in California. Cryptic hosts in California. Why is my connection going all the way through Boston? :mad:
Tracing route to patchserver.crypticstudios.com
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms darren91979.mshome.net
2 * * * Request timed out.
3 45 ms 38 ms 41 ms ip-84-38-37-56.easynet.co.uk [84.38.37.56]
4 35 ms 41 ms 38 ms 02780884.bb.sky.com [2.120.8.132]
5 101 ms 35 ms 34 ms ae55.edge3.London2.Level3.net [212.187.201.57]
6 34 ms 35 ms 35 ms ae-0-11.edge4.London2.Level3.net [4.69.200.126]
7 36 ms 35 ms 36 ms ae-3-3.ebr1.London1.Level3.net [4.69.141.189]
8 36 ms 49 ms 57 ms ae-59-114.csw1.London1.Level3.net [4.69.153.126]
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 35 ms 27 ms 19 ms cpe-76-182-208-1.tx.res.rr.com [76.182.208.1]
3 12 ms 12 ms 13 ms tge7-1.dllatx3c-er01.texas.rr.com [70.125.218.97
]
4 23 ms 22 ms 15 ms tge0-8-0-1.dllatx34-tr01.texas.rr.com [24.175.38
.108]
5 15 ms 15 ms 15 ms agg23.dllatx1k-cr01.texas.rr.com [24.175.36.224]
6 23 ms 15 ms 15 ms agg21.dllatxl3-cr01.texas.rr.com [24.175.49.0]
7 22 ms 14 ms 16 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
8 28 ms 93 ms 15 ms 107.14.17.234
9 18 ms 17 ms 15 ms te0-7-0-15.ccr21.dfw03.atlas.cogentco.com [154.5
4.11.49]
10 16 ms 55 ms 17 ms te0-3-0-4.ccr21.dfw01.atlas.cogentco.com [154.54
.82.17]
11 27 ms 28 ms 28 ms te0-4-0-1.mpd21.mci01.atlas.cogentco.com [154.54
.5.126]
12 83 ms 44 ms 44 ms te0-4-0-3.mpd21.ord01.atlas.cogentco.com [154.54
.30.169]
13 68 ms 66 ms 66 ms te0-7-0-2.ccr21.bos01.atlas.cogentco.com [154.54
.28.114]
14 65 ms 67 ms 86 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
15 80 ms * * 38.111.40.114
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.
C:\Windows\system32>:mad:
So, I just push the buttons and things blow up? Fascinating...
I was getting kicked over an hour before the maintenance started due to a patching timing out issue, so the problem was there before the maintenance started, unless they started maintenance early while we were still playing....:(
Sure sounds like a patch problem to me, even if it occurred before the "official" patch time. This doesn't mean they weren't pre-patching both clients and servers prior to the official downtime to increase efficiency. I'm impressed,
Regardless, this isn't for clients to fix. Customer service has been very lax, especially in times like this, and tech support is always saying "It's your fault, not ours". I find it hard to believe that another player would back this point of view.
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)
every damn time i'm having issues it's that cognet server isn't there some way to connect to a game server elsewhere? west coast might cost me ping time but at least it would work
C:\Users\Dan>tracert launcher.startrekonline.com
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms CISCO47751 [192.168.1.1]
2 24 ms 19 ms 26 ms cable-mac1.glvlny09-ar4002.nyroc.rr.com [67.240.
64.1]
3 10 ms 8 ms 8 ms gig4-47.glvlny09-rtr001.alb.northeast.rr.com [24
.29.45.229]
4 10 ms 11 ms 19 ms rdc-74-76-241-10.alb.northeast.rr.com [74.76.241
.10]
5 19 ms 22 ms 22 ms rdc-74-76-241-193.alb.northeast.rr.com [74.76.24
1.193]
6 23 ms 21 ms 23 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
7 18 ms 28 ms 26 ms ae-0-0.pr0.nyc20.tbone.rr.com [66.109.6.157]
8 17 ms 17 ms 18 ms te0-0-0-5.ccr21.jfk05.atlas.cogentco.com [154.54
.13.185]
9 21 ms 18 ms 18 ms te0-6-0-4.mpd21.jfk02.atlas.cogentco.com [154.54
.46.249]
10 25 ms 24 ms 24 ms te0-3-0-2.ccr21.bos01.atlas.cogentco.com [154.54
.44.14]
11 110 ms 362 ms 214 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
12 * 34 ms * 38.111.40.114
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.
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 [208.95.185.44] ?ber maximal
Abschnitte:
1 1 ms 1 ms 1 ms Vigor2130.lan [196.169.0.1]
2 8 ms 7 ms 9 ms 217.0.118.233
3 9 ms 9 ms 10 ms 87.186.237.58
4 16 ms 16 ms 16 ms f-ed6-i.F.DE.NET.DTAG.DE [62.156.131.254]
5 16 ms 15 ms 16 ms te0-7-0-7.ccr21.fra03.atlas.cogentco.com [13
7.14.105]
6 24 ms 23 ms 21 ms te0-4-0-2.ccr21.ams03.atlas.cogentco.com [15
.39.181]
7 42 ms 40 ms 41 ms te0-5-0-7.ccr21.lpl01.atlas.cogentco.com [13
7.48.41]
8 118 ms 103 ms 103 ms te0-2-0-3.ccr21.bos01.atlas.cogentco.com [15
.31.189]
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.
21 ^C
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
STO Member since February 2009. I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born! Forever a STO Veteran-Minion
My connection also does not go through Cogent. Mine goes through Alter Communications. It does, interestingly, go through Boston as well, but not through Cogent.
I live in California. Cryptic hosts in California. Why is my connection going all the way through Boston? :mad:
Cryptic is located in California. The servers are located in the Boston area. Better for people across the pond.
My connection also does not go through Cogent. Mine goes through Alter Communications. It does, interestingly, go through Boston as well, but not through Cogent.
I live in California. Cryptic hosts in California. Why is my connection going all the way through Boston? :mad:
My best guess is the load balancer that that is used to converge their IPS(s) connections, depending on route, is at fault. Hence, a different location = a different trace route.
This is probably NOT a perfect world owned bit of equipment.
All this fuss over a few minor changes, according to the Patch Notes.
Looking forward to Thursday, when the 3 year anniverary event is slated to begin (according to the in-game calender). Why not just patch that today and save us another day of broken launcher issues?
You're just a machine. And machines can be broken.
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".
Above and beyond the call of duty?
Excuse me, but keeping their servers accessable is part of their call of duty. There is nothing above and beyond about them working on this. It is their job, and it is what we pay them for.
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.
As I said, I didn't see them say that which is why I asked where it was said by the devs.
Although honestly, I can see why they would blame the ISP first, especially if it seems to be a regional issue. From what I've read, once they realized it isn't regional they began investigating.
Must really suk to have the problem be 1500+ miles away from where They are.
STO Member since February 2009. I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born! Forever a STO Veteran-Minion
Not bashing, usually their maintenance is routine & finishes before the stated time, but they could just upload the patch, give us the url to download it so we can move it into our sto folder and run the exe.
I remember having this problem back in Season 1; but, I would have thought they would be byond this issue, now. I am having the same issue as the OP. Checked everything. I can sign into other MMO's, but not STO.
Comments
If you had this issue prior to today's maintenance and patch, why did Cryptic allow the problem to get more wide spread?
Did anyone try to stop this before it got out of hand?
Just looking at that...
bsn.pnap = the Boston Area again.
I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born!
Forever a STO Veteran-Minion
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"?
My connection also does not go through Cogent. Mine goes through Alter Communications. It does, interestingly, go through Boston as well, but not through Cogent.
I live in California. Cryptic hosts in California. Why is my connection going all the way through Boston? :mad:
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms darren91979.mshome.net
2 * * * Request timed out.
3 45 ms 38 ms 41 ms ip-84-38-37-56.easynet.co.uk [84.38.37.56]
4 35 ms 41 ms 38 ms 02780884.bb.sky.com [2.120.8.132]
5 101 ms 35 ms 34 ms ae55.edge3.London2.Level3.net [212.187.201.57]
6 34 ms 35 ms 35 ms ae-0-11.edge4.London2.Level3.net [4.69.200.126]
7 36 ms 35 ms 36 ms ae-3-3.ebr1.London1.Level3.net [4.69.141.189]
8 36 ms 49 ms 57 ms ae-59-114.csw1.London1.Level3.net [4.69.153.126]
9 82 ms 36 ms 36 ms ae-116-3502.edge3.London1.Level3.net [4.69.166.1
34]
10 36 ms 37 ms 37 ms te0-7-0-7.ccr22.lon01.atlas.cogentco.com [130.11
7.15.245]
11 36 ms 37 ms 36 ms te0-3-0-5.ccr22.lon13.atlas.cogentco.com [130.11
7.0.93]
12 108 ms 108 ms 109 ms te0-0-0-4.ccr22.bos01.atlas.cogentco.com [130.11
7.0.46]
13 110 ms 108 ms 109 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
14 * 112 ms * 38.111.40.114
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Still cant get to patching window. im in the UK.
Are other still having this issue?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>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 192.168.1.1
2 35 ms 27 ms 19 ms cpe-76-182-208-1.tx.res.rr.com [76.182.208.1]
3 12 ms 12 ms 13 ms tge7-1.dllatx3c-er01.texas.rr.com [70.125.218.97
]
4 23 ms 22 ms 15 ms tge0-8-0-1.dllatx34-tr01.texas.rr.com [24.175.38
.108]
5 15 ms 15 ms 15 ms agg23.dllatx1k-cr01.texas.rr.com [24.175.36.224]
6 23 ms 15 ms 15 ms agg21.dllatxl3-cr01.texas.rr.com [24.175.49.0]
7 22 ms 14 ms 16 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
8 28 ms 93 ms 15 ms 107.14.17.234
9 18 ms 17 ms 15 ms te0-7-0-15.ccr21.dfw03.atlas.cogentco.com [154.5
4.11.49]
10 16 ms 55 ms 17 ms te0-3-0-4.ccr21.dfw01.atlas.cogentco.com [154.54
.82.17]
11 27 ms 28 ms 28 ms te0-4-0-1.mpd21.mci01.atlas.cogentco.com [154.54
.5.126]
12 83 ms 44 ms 44 ms te0-4-0-3.mpd21.ord01.atlas.cogentco.com [154.54
.30.169]
13 68 ms 66 ms 66 ms te0-7-0-2.ccr21.bos01.atlas.cogentco.com [154.54
.28.114]
14 65 ms 67 ms 86 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
15 80 ms * * 38.111.40.114
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.
C:\Windows\system32>:mad:
Sure sounds like a patch problem to me, even if it occurred before the "official" patch time. This doesn't mean they weren't pre-patching both clients and servers prior to the official downtime to increase efficiency. I'm impressed,
Regardless, this isn't for clients to fix. Customer service has been very lax, especially in times like this, and tech support is always saying "It's your fault, not ours". I find it hard to believe that another player would back this point of view.
Cogent rarely says its having a problem even when its in the middle of a major problem.
Not all issues can be fixed with a patch. For example if its an outside issue with the isp no patch in the world on cryptics end will fix it.
Still "patience is a virtue" or for those seeking a trek quote; "Time is patience so we must be patient with it".
C:\Users\Dan>tracert launcher.startrekonline.com
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms CISCO47751 [192.168.1.1]
2 24 ms 19 ms 26 ms cable-mac1.glvlny09-ar4002.nyroc.rr.com [67.240.
64.1]
3 10 ms 8 ms 8 ms gig4-47.glvlny09-rtr001.alb.northeast.rr.com [24
.29.45.229]
4 10 ms 11 ms 19 ms rdc-74-76-241-10.alb.northeast.rr.com [74.76.241
.10]
5 19 ms 22 ms 22 ms rdc-74-76-241-193.alb.northeast.rr.com [74.76.24
1.193]
6 23 ms 21 ms 23 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
7 18 ms 28 ms 26 ms ae-0-0.pr0.nyc20.tbone.rr.com [66.109.6.157]
8 17 ms 17 ms 18 ms te0-0-0-5.ccr21.jfk05.atlas.cogentco.com [154.54
.13.185]
9 21 ms 18 ms 18 ms te0-6-0-4.mpd21.jfk02.atlas.cogentco.com [154.54
.46.249]
10 25 ms 24 ms 24 ms te0-3-0-2.ccr21.bos01.atlas.cogentco.com [154.54
.44.14]
11 110 ms 362 ms 214 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
12 * 34 ms * 38.111.40.114
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.
He's dead, Jim.
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 [208.95.185.44] ?ber maximal
Abschnitte:
1 1 ms 1 ms 1 ms Vigor2130.lan [196.169.0.1]
2 8 ms 7 ms 9 ms 217.0.118.233
3 9 ms 9 ms 10 ms 87.186.237.58
4 16 ms 16 ms 16 ms f-ed6-i.F.DE.NET.DTAG.DE [62.156.131.254]
5 16 ms 15 ms 16 ms te0-7-0-7.ccr21.fra03.atlas.cogentco.com [13
7.14.105]
6 24 ms 23 ms 21 ms te0-4-0-2.ccr21.ams03.atlas.cogentco.com [15
.39.181]
7 42 ms 40 ms 41 ms te0-5-0-7.ccr21.lpl01.atlas.cogentco.com [13
7.48.41]
8 118 ms 103 ms 103 ms te0-2-0-3.ccr21.bos01.atlas.cogentco.com [15
.31.189]
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.
21 ^C
Best uneducated guess, anyway.
Three more timing out at bos-xx.atlas.cogentco
I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born!
Forever a STO Veteran-Minion
Cryptic is located in California. The servers are located in the Boston area. Better for people across the pond.
My best guess is the load balancer that that is used to converge their IPS(s) connections, depending on route, is at fault. Hence, a different location = a different trace route.
This is probably NOT a perfect world owned bit of equipment.
Looking forward to Thursday, when the 3 year anniverary event is slated to begin (according to the in-game calender). Why not just patch that today and save us another day of broken launcher issues?
Above and beyond the call of duty?
Excuse me, but keeping their servers accessable is part of their call of duty. There is nothing above and beyond about them working on this. It is their job, and it is what we pay them for.
Perhaps there is truth to your statement.
As I said, I didn't see them say that which is why I asked where it was said by the devs.
Although honestly, I can see why they would blame the ISP first, especially if it seems to be a regional issue. From what I've read, once they realized it isn't regional they began investigating.
I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born!
Forever a STO Veteran-Minion
But you can confirm Boston is still there? No big explosions anything?
He's dead, Jim.
Not bashing, usually their maintenance is routine & finishes before the stated time, but they could just upload the patch, give us the url to download it so we can move it into our sto folder and run the exe.