Hacker News Reader

Comment by dartos | Hacker News Reader

Bugs happen.

Not staggering the updates is what blew my mind.

Since the issue manifested at 04:09 UTC, which is 11pm where Crowdstrikes HQ is, I would guess someone was working late at night and skipped the proper process so they could get the update done and go to bed.

They probably considered it low risk, had done similar things of times hundreds of times before, etc.

> They probably considered it low risk

Wild that anyone would consider anything in the “critical path” low risk. I would bet that they just don’t do rolling releases normally since it never caused issues before.

Companies these days are global btw.

Not everyone is working on the same timezone.

They don't appear to have engineering jobs in any location where that would be considered regular office hours...

https://crowdstrike.wd5.myworkdayjobs.com/crowdstrikecareers

I see remote, Israel, Canada.

https://crowdstrike.wd5.myworkdayjobs.com/en-US/crowdstrikec...

This one specifically Spain and Romania

I know they bought companies all over the globe from Denmark to other locations.

0409UTC is 07:09 AM in Israel. Doubt an engineer was doing a push then either...

All the other engineering locations seem even less likely.

On Friday, no less. (Israel's weekend is Friday / Saturday instead of the usual Saturday / Sunday.)

Not sure of Crowdstrike's specific arrangements, but a lot of Israelis do work on Friday mornings.

A good reminder of the fact that your Thursday might be someone else's Friday.

Their sales pitch is being the first to apply patches for any virus. I think it makes sense to try to push as quickly as possible when speed of updates is core to your sales pitch.

Marketing is supposed to sell the product, not lead the product. They need to get their priorities straight.

Reply on news.ycombinator.com