Strong disagree. I ran non-ECC memory on my server and services would unexpectedly crash maybe once per week. Over the span of a year I had two databases get corrupted that cost me a lot of time to fix. I tried swapping sticks but it happened with all of them. I switched to ECC memory and the problems disappeared. I needed more memory anyway and the price delta for ECC was about $100. I didn’t have to swap CPUs or anything, AMD desktop CPUs and chipsets support it out of the box. ECC memory is absolutely worth it.

Not that I know of, at least not for our cubesat. The aerospace sector moves extremely slowly because of ‘flight heritage’ - basically, if it hasn’t been in multiple long-term space missions before then it’s an instant rejection. You might ask ‘then how does any new tech get into space?’ and the answer to that is ‘it generally doesn’t’. More amateur satellite developers like university programs tend to ‘move fast and break things’ but with an emphasis on ‘break’.

Besides this suborbital flight I haven’t heard of anyone using carbon fibre frames before. I’m not a chemical engineer but I would imagine CF composites may have issues with outgassing, compared to metals. Outgassing can result in volatile compounds leaving suspension under a vacuum and depositing elsewhere, particularly bad for camera lenses and solar panels and such. Since the frame touches basically every part of the satellite, the risk here is high.

This is not uncommon for high-profile CVEs. For example, brokenwire.fail, heartbleed.com, spectreattack.com, etc…

A solar flare is just one example of many possible causes. There are plenty of other ones. You didn’t touch on any of the others so let me explain - NASA reports on small satellite missions show that about 40% of satellites experience at least partial mission failure within their lifetime. Studies have shown the leading cause of satellite failure is propulsion systems, responsible for about half of all failures. This is not uncommon at all.

Most altitude ranges in LEO still have debris from decades ago, the exception being below 300km, which is basically still in the atmosphere. Unfortunately, debris strikes have regularly produced debris that are flung into higher orbits, so even collisions between satellites in this range are dangerous.

Edit: I also forgot to mention, the five day estimate (now three days actually) wasn’t for a close-call, it was for a debris-generating event.

Collisions aren’t theoretical, near misses are so common that there’s an entire department at NASA dedicated to detecting them and warning satellite owners to adjust course, I know because we were contacted about a possible collision involving our cubesat. Prior to megaconstellations being deployed if humanity stopped adjusting satellite orbits there would be a collision within a month, now there would be a collision within 5 days. It’s only a matter of time until both satellites on a collision course don’t have the ability to adjust course (engine failure or no propulsion/fuel/comms). In the event of a Carrington-style solar flare there’s a good chance a decent percentage of satellites would be knocked out, making this hypothetical into a reality. Further, we can only currently track objects down to about 10cm, but NASA estimates suggest about 500,000 objects exist between 1-10cm in size in LEO.