You say on Twitter ............ Star Trek Online will have PC Maintenance tomorrow, 9/17, at 6am PT. Estimated downtime is 3.5 hours.
But here you say ........ We will be having a maintenance tomorrow, 4/28 at 7AM Pacific for 2.5 hours.
So Daniels is messing around again is he?
ALL TOGETHER NOW ..... LET'S DO THE TIME WARP AGAINNNNNNNNNNNN
You say on Twitter ............ Star Trek Online will have PC Maintenance tomorrow, 9/17, at 6am PT. Estimated downtime is 3.5 hours.
But here you say ........ We will be having a maintenance tomorrow, 4/28 at 7AM Pacific for 2.5 hours.
So Daniels is messing around again is he?
ALL TOGETHER NOW ..... LET'S DO THE TIME WARP AGAINNNNNNNNNNNN
It will never be right, at this point we just consider ourselves lucky to get the news at all.
Nothing about the crashing when loading and failing to transfer to certain social maps... It doesn't happen a lot but it does happen often enough on specific social maps to be an annoyance.
Nothing about the crashing when loading and failing to transfer to certain social maps... It doesn't happen a lot but it does happen often enough on specific social maps to be an annoyance.
Map transfer fails usually happen when the map you are trying to transfer to is already full
Neverwinter had that same 6AM/7AM issue. There though, the Shard went down at that 6AM (9AM Eastern).
'But to be logical is not to be right', and 'nothing' on God's earth could ever 'make it' right!'
Judge Dan Haywood
'As l speak now, the words are forming in my head.
l don't know.
l really don't know what l'm about to say, except l have a feeling about it.
That l must repeat the words that come without my knowledge.'
Nothing about the crashing when loading and failing to transfer to certain social maps... It doesn't happen a lot but it does happen often enough on specific social maps to be an annoyance.
Map transfer fails usually happen when the map you are trying to transfer to is already full
If only. How do you explain it happening with Fleet Maps then?
Something is not right. I seem to lose connection to the server whenever I try to log in or pick a character. Is the server acting up or is this on my end?
You say on Twitter ............ Star Trek Online will have PC Maintenance tomorrow, 9/17, at 6am PT. Estimated downtime is 3.5 hours.
But here you say ........ We will be having a maintenance tomorrow, 4/28 at 7AM Pacific for 2.5 hours.
So Daniels is messing around again is he?
ALL TOGETHER NOW ..... LET'S DO THE TIME WARP AGAINNNNNNNNNNNN
Listen the way this year have been and how weird a construct time feels here in 2020 I fully believe that it is 4/28 today.
Gentle ribbing aside this:
Resolved an issue that would sometimes prevent progression during the “To Hell with Honor” TFO when the reactors were destroyed too quickly.
Is much appreciated. It was a bit tiresome to get stuck again and again for being effective.
Logic is the beginning of wisdom, not the end of it.
Something is not right. I seem to lose connection to the server whenever I try to log in or pick a character. Is the server acting up or is this on my end?
@zhugui No issues for me and I just logged on. Try doing a tracert and see if akamai is messing with things for you again.
Logic is the beginning of wisdom, not the end of it.
@ilithyn There's a couple of time outs here. Not sure it's Akamai.
1 6 ms 7 ms 3 ms 192.168.0.1
2 29 ms 14 ms 13 ms 072-031-138-113.res.spectrum.com [72.31.138.113]
3 18 ms 18 ms 19 ms 071-046-008-037.res.spectrum.com [71.46.8.37]
4 25 ms 24 ms 24 ms bundle-ether31.orld31-car2.bhn.net [97.69.194.202]
5 83 ms 35 ms 29 ms 072-031-067-254.res.spectrum.com [72.31.67.254]
6 35 ms 29 ms 29 ms 072-031-220-136.res.spectrum.com [72.31.220.136]
7 * 32 ms 38 ms 216.156.105.65.ptr.us.xo.net [216.156.105.65]
8 26 ms 37 ms 29 ms 207.88.13.103.ptr.us.xo.net [207.88.13.103]
9 45 ms 59 ms 59 ms 216.156.104.22.ptr.us.xo.net [216.156.104.22]
10 45 ms 49 ms 59 ms po110.bs-b.sech-mia4.netarch.akamai.com [23.57.103.245]
11 * * * Request timed out.
12 51 ms 59 ms 59 ms ae121.access-a.sech-mia4.netarch.akamai.com [23.57.103.251]
13 * * * Request timed out.
14 * 61 ms 70 ms a72-52-27-212.deploy.static.akamaitechnologies.com [72.52.27.212]
15 136 ms 68 ms 69 ms 198.49.243.237
16 66 ms 79 ms 57 ms patchserver.crypticstudios.com [208.95.184.200]
@ilithyn There's a couple of time outs here. Not sure it's Akamai.
1 6 ms 7 ms 3 ms 192.168.0.1
2 29 ms 14 ms 13 ms 072-031-138-113.res.spectrum.com [72.31.138.113]
3 18 ms 18 ms 19 ms 071-046-008-037.res.spectrum.com [71.46.8.37]
4 25 ms 24 ms 24 ms bundle-ether31.orld31-car2.bhn.net [97.69.194.202]
5 83 ms 35 ms 29 ms 072-031-067-254.res.spectrum.com [72.31.67.254]
6 35 ms 29 ms 29 ms 072-031-220-136.res.spectrum.com [72.31.220.136]
7 * 32 ms 38 ms 216.156.105.65.ptr.us.xo.net [216.156.105.65]
8 26 ms 37 ms 29 ms 207.88.13.103.ptr.us.xo.net [207.88.13.103]
9 45 ms 59 ms 59 ms 216.156.104.22.ptr.us.xo.net [216.156.104.22] 10 45 ms 49 ms 59 ms po110.bs-b.sech-mia4.netarch.akamai.com [23.57.103.245]
11 * * * Request timed out.
12 51 ms 59 ms 59 ms ae121.access-a.sech-mia4.netarch.akamai.com [23.57.103.251]
13 * * * Request timed out.
14 * 61 ms 70 ms a72-52-27-212.deploy.static.akamaitechnologies.com [72.52.27.212]
15 136 ms 68 ms 69 ms 198.49.243.237
16 66 ms 79 ms 57 ms patchserver.crypticstudios.com [208.95.184.200]
Maybe, maybe not. Those two time outs aren't usually there when things are working. At least not for me.
Logic is the beginning of wisdom, not the end of it.
Pinging patchserver.crypticstudios.com [208.95.184.200] with 32 bytes of data:
Reply from 208.95.184.200: bytes=32 time=43ms TTL=48
Reply from 208.95.184.200: bytes=32 time=43ms TTL=48
Reply from 208.95.184.200: bytes=32 time=45ms TTL=48
Reply from 208.95.184.200: bytes=32 time=78ms TTL=48
Ping statistics for 208.95.184.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 78ms, Average = 52ms
C:\Users\bud>ping patchserver.crypticstudios.com
Pinging patchserver.crypticstudios.com [208.95.184.200] with 32 bytes of data:
Reply from 97.71.137.169: Destination net unreachable.
Reply from 97.71.137.169: Destination net unreachable.
Reply from 97.71.137.169: Destination net unreachable.
Reply from 97.71.137.169: Destination net unreachable.
Ping statistics for 208.95.184.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\Users\bud>ping patchserver.crypticstudios.com
Pinging patchserver.crypticstudios.com [208.95.184.200] with 32 bytes of data:
Reply from 208.95.184.200: bytes=32 time=45ms TTL=48
Reply from 208.95.184.200: bytes=32 time=43ms TTL=48
Reply from 208.95.184.200: bytes=32 time=49ms TTL=48
Reply from 208.95.184.200: bytes=32 time=48ms TTL=48
Ping statistics for 208.95.184.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 49ms, Average = 46ms
C:\Users\bud>ping patchserver.crypticstudios.com
Pinging patchserver.crypticstudios.com [208.95.184.200] with 32 bytes of data:
Reply from 208.95.184.200: bytes=32 time=42ms TTL=48
Reply from 208.95.184.200: bytes=32 time=43ms TTL=48
Reply from 97.71.137.169: Destination net unreachable.
Reply from 97.71.137.169: Destination net unreachable.
Ping statistics for 208.95.184.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 43ms, Average = 42ms
This is what I get when trying to ping the server
Too many characters to list but still adding more.......The addiction to this game is real
You say on Twitter ............ Star Trek Online will have PC Maintenance tomorrow, 9/17, at 6am PT. Estimated downtime is 3.5 hours.
But here you say ........ We will be having a maintenance tomorrow, 4/28 at 7AM Pacific for 2.5 hours.
So Daniels is messing around again is he?
ALL TOGETHER NOW ..... LET'S DO THE TIME WARP AGAINNNNNNNNNNNN
It will never be right, at this point we just consider ourselves lucky to get the news at all.
Yeah, i think we posted yesterday about this.. or tomorrow.. or in a year... or last year, it depends on your place in time, i would love to be a Temporal Investigator!
Comments
Experiencing a Gameplay Bug with our latest patch? Please click this link to be taken to our Gameplay Bug Report Section to file your reports.
Thank you for the assistance!
The Star Trek Online Team
But here you say ........ We will be having a maintenance tomorrow, 4/28 at 7AM Pacific for 2.5 hours.
So Daniels is messing around again is he?
ALL TOGETHER NOW ..... LET'S DO THE TIME WARP AGAINNNNNNNNNNNN
It will never be right, at this point we just consider ourselves lucky to get the news at all.
Thanks for the fixes.
Map transfer fails usually happen when the map you are trying to transfer to is already full
I would be so embarrased, every time and time again its wrong.
And damn it Daniels!! Stop dicking with the maintenance times...
Adu-Uss Firefox NCC-93425-F (LVL 65 FED AoY ENG) UR/VR MKXV Fleet Intel Assault Cruiser (July 2016)
Jean-Uss Seratoga Ravenna (LVL 60 FED Delta ENG) UC/R MKVI Bajoran Escort (April 2018)
Dubsa-RRW Mnaudh (LVL 50 FED allied ROM Delta ENG) Warbird (May 2018)
Marop-IKS Orunthi (LVL 50 KNG Delta ENG) BoP (May 2018)
Kanak'lan-TRIBBLE (LVL 65 DOM Gamma ENG) TRIBBLE (June 2018)
There's some good fixes in there, though - thank you!
l don't know.
l really don't know what l'm about to say, except l have a feeling about it.
That l must repeat the words that come without my knowledge.'
If only. How do you explain it happening with Fleet Maps then?
Listen the way this year have been and how weird a construct time feels here in 2020 I fully believe that it is 4/28 today.
Gentle ribbing aside this:
Is much appreciated. It was a bit tiresome to get stuck again and again for being effective.
@zhugui No issues for me and I just logged on. Try doing a tracert and see if akamai is messing with things for you again.
1 6 ms 7 ms 3 ms 192.168.0.1
2 29 ms 14 ms 13 ms 072-031-138-113.res.spectrum.com [72.31.138.113]
3 18 ms 18 ms 19 ms 071-046-008-037.res.spectrum.com [71.46.8.37]
4 25 ms 24 ms 24 ms bundle-ether31.orld31-car2.bhn.net [97.69.194.202]
5 83 ms 35 ms 29 ms 072-031-067-254.res.spectrum.com [72.31.67.254]
6 35 ms 29 ms 29 ms 072-031-220-136.res.spectrum.com [72.31.220.136]
7 * 32 ms 38 ms 216.156.105.65.ptr.us.xo.net [216.156.105.65]
8 26 ms 37 ms 29 ms 207.88.13.103.ptr.us.xo.net [207.88.13.103]
9 45 ms 59 ms 59 ms 216.156.104.22.ptr.us.xo.net [216.156.104.22]
10 45 ms 49 ms 59 ms po110.bs-b.sech-mia4.netarch.akamai.com [23.57.103.245]
11 * * * Request timed out.
12 51 ms 59 ms 59 ms ae121.access-a.sech-mia4.netarch.akamai.com [23.57.103.251]
13 * * * Request timed out.
14 * 61 ms 70 ms a72-52-27-212.deploy.static.akamaitechnologies.com [72.52.27.212]
15 136 ms 68 ms 69 ms 198.49.243.237
16 66 ms 79 ms 57 ms patchserver.crypticstudios.com [208.95.184.200]
Maybe, maybe not. Those two time outs aren't usually there when things are working. At least not for me.
Pinging patchserver.crypticstudios.com [208.95.184.200] with 32 bytes of data:
Reply from 208.95.184.200: bytes=32 time=43ms TTL=48
Reply from 208.95.184.200: bytes=32 time=43ms TTL=48
Reply from 208.95.184.200: bytes=32 time=45ms TTL=48
Reply from 208.95.184.200: bytes=32 time=78ms TTL=48
Ping statistics for 208.95.184.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 78ms, Average = 52ms
C:\Users\bud>ping patchserver.crypticstudios.com
Pinging patchserver.crypticstudios.com [208.95.184.200] with 32 bytes of data:
Reply from 97.71.137.169: Destination net unreachable.
Reply from 97.71.137.169: Destination net unreachable.
Reply from 97.71.137.169: Destination net unreachable.
Reply from 97.71.137.169: Destination net unreachable.
Ping statistics for 208.95.184.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\Users\bud>ping patchserver.crypticstudios.com
Pinging patchserver.crypticstudios.com [208.95.184.200] with 32 bytes of data:
Reply from 208.95.184.200: bytes=32 time=45ms TTL=48
Reply from 208.95.184.200: bytes=32 time=43ms TTL=48
Reply from 208.95.184.200: bytes=32 time=49ms TTL=48
Reply from 208.95.184.200: bytes=32 time=48ms TTL=48
Ping statistics for 208.95.184.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 49ms, Average = 46ms
C:\Users\bud>ping patchserver.crypticstudios.com
Pinging patchserver.crypticstudios.com [208.95.184.200] with 32 bytes of data:
Reply from 208.95.184.200: bytes=32 time=42ms TTL=48
Reply from 208.95.184.200: bytes=32 time=43ms TTL=48
Reply from 97.71.137.169: Destination net unreachable.
Reply from 97.71.137.169: Destination net unreachable.
Ping statistics for 208.95.184.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 43ms, Average = 42ms
This is what I get when trying to ping the server
Yeah, i think we posted yesterday about this.. or tomorrow.. or in a year... or last year, it depends on your place in time, i would love to be a Temporal Investigator!