thewayne: (Default)
Delta sued Crowdstrike in George court for $500mil in actual damages for having to cancel over 7,000 flights over the five day period that its IT systems were kaput, plus punitive reputational damages.

Crowdstrike says its terms of service limits recovery to 2x the fees you pay for the product. Which I suspect is a bit less than $500mil.

The problem is that pretty much every other IT org IN THE WORLD were able to recover their systems within a day, and both Microsoft and Crowdstrike offered to help Delta recover their systems at their own expense. The PRESIDENT of Microsoft couldn't get his calls returned from Delta for THREE DAYS, and the response was 'Nah, we're good'.

Those facts are going to weigh very heavily against Delta in court.

The basic problem is one that's not uncommon in IT: the corporation apparently has been cheap in keeping their IT infrastructure up to date. Old hardware, old versions of software, and likely IT staff who weren't as good at their jobs as they should have been for a company as big as Delta seems to have been the reason the recovery process dragged on for so long. And all of that is going to come out in court, and when it does, I expect the revelation of that soft white underbelly to really drive down their stock price. It doesn't matter how big an airline is, there's always room for the stock price to crash.

Yes, Crowdstrike made mistakes. And Delta probably has some valid claims to make. But to refuse free offers of assistance from both Microsoft and Crowdstrike? No one in their right mind would do that, and a jury is really going to question the rationality of the IT directors and C-Suite minds who said no.

It's possible that Delta may win the suite. But they might get a token amount, like $10. Or the TOS stipulation of twice the cost of the software. Regardless, all their bad practices will be revealed and that will be a topic of discussion at the next shareholder meeting.

https://arstechnica.com/tech-policy/2024/10/crowdstrike-accuses-delta-of-blaming-its-own-it-failures-on-global-outage/


The amusing bit is that Delta did not name Microsoft in the suit, nor sue Microsoft separately. It seems that MS told Delta that they would defend themselves vigorously, and told Delta to preserve all documentation regarding the state of their system, what software, operating systems and versions they use, all communications regarding this incident, etc. Microsoft has an extremely good legal team and would have no problem saying in court "Look, we offered to help. You said no. Why are you suing us?"
thewayne: (Default)
You don't think of old hardware getting updated, but on occasion it does. In this case, it's the Voyager probes, currently a pretty far distance away from home base. Well, 12 billion miles. A bit far to send out a service tech.

From the Slashdot summary, extracted from the NASA announcement: "From NASA's announcement:
One effort addresses fuel residue that seems to be accumulating inside narrow tubes in some of the thrusters on the spacecraft. The thrusters are used to keep each spacecraft's antenna pointed at Earth. This type of buildup has been observed in a handful of other spacecraft... In some of the propellant inlet tubes, the buildup is becoming significant. To slow that buildup, the mission has begun letting the two spacecraft rotate slightly farther in each direction [almost 1 degree] before firing the thrusters. This will reduce the frequency of thruster firings... While more rotating by the spacecraft could mean bits of science data are occasionally lost — akin to being on a phone call where the person on the other end cuts out occasionally — the team concluded the plan will enable the Voyagers to return more data over time.

Engineers can't know for sure when the thruster propellant inlet tubes will become completely clogged, but they expect that with these precautions, that won't happen for at least five more years, possibly much longer. "This far into the mission, the engineering team is being faced with a lot of challenges for which we just don't have a playbook," said Linda Spilker, project scientist for the mission as NASA's Jet Propulsion Laboratory in Southern California. "But they continue to come up with creative solutions."

But that's not the only issue:
The team is also uploading a software patch to prevent the recurrence of a glitch that arose on Voyager 1 last year. Engineers resolved the glitch, and the patch is intended to prevent the issue from occurring again in Voyager 1 or arising in its twin, Voyager 2...

In 2022, the onboard computer that orients the Voyager 1 spacecraft with Earth began to send back garbled status reports, despite otherwise continuing to operate normally... The attitude articulation and control system (AACS) was misdirecting commands, writing them into the computer memory instead of carrying them out. One of those missed commands wound up garbling the AACS status report before it could reach engineers on the ground.

The team determined the AACS had entered into an incorrect mode; however, they couldn't determine the cause and thus aren't sure if the issue could arise again. The software patch should prevent that.

"This patch is like an insurance policy that will protect us in the future and help us keep these probes going as long as possible," said JPL's Suzanne Dodd, Voyager project manager. "These are the only spacecraft to ever operate in interstellar space, so the data they're sending back is uniquely valuable to our understanding of our local universe."


https://hackaday.com/2023/10/22/nasa-jpls-voyager-team-is-patching-up-both-voyagers-firmware/

https://science.slashdot.org/story/23/10/23/004220/nasa-transmits-patches-to-the-two-voyager-probes-launched-in-1977

July 2025

S M T W T F S
   1 2345
6789101112
13141516171819
20212223242526
2728293031  

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jul. 3rd, 2025 02:43 pm
Powered by Dreamwidth Studios