Technology

59446 readers

4674 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

1202

Major IT outage affecting banks, airlines, media outlets across the world (www.abc.net.au)

submitted 4 months ago* (last edited 4 months ago) by rxxrc@lemmy.ml to c/technology@lemmy.world

555 comments fedilink hide all child comments

All our servers and company laptops went down at pretty much the same time. Laptops have been bootlooping to blue screen of death. It's all very exciting, personally, as someone not responsible for fixing it.

Apparently caused by a bad CrowdStrike update.

Edit: now being told we (who almost all generally work from home) need to come into the office Monday as they can only apply the fix in-person. We'll see if that changes over the weekend...

you are viewing a single comment's thread
view the rest of the comments

[–] CircuitSpells@lemmy.world 56 points 4 months ago (28 children)

I mean I know it's easy to be critical but this was my exact thought, how the hell didn't they catch this in testing?

[–] Voroxpete@sh.itjust.works 44 points 4 months ago (14 children)

Completely justified reaction. A lot of the time tech companies and IT staff get shit for stuff that, in practice, can be really hard to detect before it happens. There are all kinds of issues that can arise in production that you just can't test for.

But this... This has no justification. A issue this immediate, this widespread, would have instantly been caught with even the most basic of testing. The fact that it wasn't raises massive questions about the safety and security of Crowdstrike's internal processes.

[–] kaffiene@lemmy.world 0 points 4 months ago (5 children)

Yes. And Microsoft's

[–] wizardbeard@lemmy.dbzer0.com 5 points 4 months ago (2 children)

How exactly is Microsoft responsible for this? It's a kernel level driver that intercepts system calls, and the software updated itself.

This software was crashing Linux distros last month too, but that didn't make headlines because it effected less machines.

[–] Mikina@programming.dev 2 points 4 months ago (2 children)

From what I've heard, didn't the issue happen not solely because of CS driver, but because of a MS update that was rolled out at the same time, and the changes the update made caused the CS driver to go haywire? If that's the case, there's not much MS or CS could have done to test it beforehand, especially if both updates rolled out at around the same time.

[–] Voroxpete@sh.itjust.works 3 points 4 months ago

I've seen zero suggestion of this in any reporting about the issue. Not saying you're wrong, but you're definitely going to need to find some sources.

[–] Qwaffle_waffle@sh.itjust.works 2 points 4 months ago

Is there any links to this?

[–] kaffiene@lemmy.world 1 points 4 months ago

My apologies I thought this went out with a MS update

load more comments (2 replies)

load more comments (10 replies)

load more comments (23 replies)