Jump to content

Talk:2024 CrowdStrike-related IT outages

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Silikonz (talk | contribs) at 22:24, 19 July 2024 (→Requested move 19 July 2024: Reply). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

What about Bitlocker?

The article should be updated to reference the complexities Bitlocker adds. — Preceding unsigned comment added by 152.110.101.206 (talk) 19:32, 19 July 2024 (UTC)[reply]

Do you have any reliable sources discussing this? GhostOfNoMeme 20:03, 19 July 2024 (UTC)[reply]
it this counts: https://www.crowdstrike.com/blog/statement-on-falcon-content-update-for-windows-hosts/ ZalnaRs (talk) 22:22, 19 July 2024 (UTC)[reply]

What infobox should we use?

I was thinking Template:Infobox bug, but I'm not sure what one would be the best. Lordseriouspig 07:50, 19 July 2024 (UTC)[reply]

Template:Infobox event might be the most appropriate option, in the lack of any obvious alternative. The article at least right now is about the outages, not the specific bug (which is yet to be identified) that might be causing this. Gust Justice (talk) 08:16, 19 July 2024 (UTC)[reply]
We could use event for the article <top> and then use infobox bug for the "technical details" section ZalnaRs (talk) 18:28, 19 July 2024 (UTC)[reply]

Impact section already too unwieldy

I know that it's very early days, but the Impact section is already getting out of hand. Is it too early to consider a spinoff? I'm not convinced that the readers are coming to this particular action for an exhaustive list of everyone impacted (a gargantuan list, evidently), and I think we should already start using the summary style, at least for the Impact section. Melmann 08:56, 19 July 2024 (UTC)[reply]

Agree it is getting out of hand with just an inventory of geographic regions. It would seem to make more sense to go sector by sector, as an "IT outage" is more relevant to certain economnic/social impacts, rather than geographic regions. I'd favor of going with headings like "Transportation," "Banking and economics," "Broadcast and communications." Those three alone might account for 50-70% of all entries. - Fuzheado | Talk 09:09, 19 July 2024 (UTC)[reply]
It should be done by sector instead of country. For example, a paragraph on aviation, one on banking, one on TV/media, etc. 2A00:23C8:308D:9E00:7588:FB7E:2907:414F (talk) 09:06, 19 July 2024 (UTC)[reply]
Jinx. Great minds think alike. - Fuzheado | Talk 09:09, 19 July 2024 (UTC)[reply]
Agreed. Should be split off by Sector Wolfstorm94 (talk) 09:39, 19 July 2024 (UTC)[reply]
Good idea. This means we can summarise it all better. For example we can say how airlines were affected (and list major ones) which means we aren't duplicating content when listing every country. ―Panamitsu (talk) 10:07, 19 July 2024 (UTC)[reply]
I've started with a new "Air transport" section and will be moving things there. - Fuzheado | Talk 10:47, 19 July 2024 (UTC)[reply]
I will just add that I'm not sure sectors is necessarily cleaner, it is a bit more confusing to assess impact by country for example with some responses and impacts could being different. Now that some information has moved the impact on Germany or the USA is harder to understand than the yet to be touched Australia section to me.MyacEight (talk) 11:31, 19 July 2024 (UTC)[reply]
Agreed, seems like a more logical way to split it in this context. Benpiano800 (talk) 13:58, 19 July 2024 (UTC)[reply]
Just to provide a counterpoint: I came here specifically for a regional itemization of issues, so the current format was great for my needs. ―Rob Frawley 2nd (talk) 14:58, 19 July 2024 (UTC)[reply]
To be honest, I preferred regional itemisation as well. I can understand both arguments. GhostOfNoMeme 15:46, 19 July 2024 (UTC)[reply]
Fair enough. :-) ―Rob Frawley 2nd (talk) 16:52, 19 July 2024 (UTC)[reply]
Crowdstrike has nearly 24,000 clients as per its last earnings report. That's customers, not devices. kencf0618 (talk) — Preceding unsigned comment added by Kencf0618 (talk • contribs) 09:58, 19 July 2024 (UTC)[reply]
I am in the middle of implementing this sectioning. Are you sure it is an improvement?
If we don't trim stuff down, it will become a wall of text for each sector. 174.92.25.207 (talk) 15:43, 19 July 2024 (UTC)[reply]
It would be a shame to have to trim significantly. Divided by sector, I feel that there isn't much room to comfortably go into sufficient detail. I would have kept the "Impact by country" with detailed descriptions, and reserved "Impact by sector" for something more akin to "Hospitals were affected in Australia, Brazil, Canada ..." and "Flights were delayed or cancelled in Australia, France, Germany ..." and so on. Maybe that would lead to a cumbersome article with an overwhelming amount of information and repetition, though...
Either way, there seems to be support for itemising by sector so I think it's worth sticking with it now. GhostOfNoMeme 15:54, 19 July 2024 (UTC)[reply]
Neutral. Please do not delete information about the impact. Users will skim to the section that interests them. -- Dandv 22:04, 19 July 2024 (UTC)[reply]

Wikipedia

For a few minutes yesterday, I could not access this website. I think Wikipedia was affected. Bearian (talk) 09:21, 19 July 2024 (UTC)[reply]

Wikipedia's hosting infrastructure is built on Debian Linux, so it is unlikely to have been affected, at least not directly. See meta:Wikimedia servers. Melmann 09:27, 19 July 2024 (UTC)[reply]
Hard to imagine this would be the case as Wikipedia has few if any ties to Microsoft software, especially Microsoft Windows. - Fuzheado | Talk 09:28, 19 July 2024 (UTC)[reply]
It may simply have been affected by the number of people searching it for info about the outage. --Ef80 (talk) 09:41, 19 July 2024 (UTC)[reply]
Wikipedia's problems appear to be resolved and were unrelated to the CrowdStrike issue. See Wikipedia:Village pump (technical)#Mediawiki errors and phab:T370304. Johnuniq (talk) 10:16, 19 July 2024 (UTC)[reply]

Response

Should Response be listed by country? Currently only has Australian governmental response. TirFarThoinnExpora (talk) 09:26, 19 July 2024 (UTC)[reply]

Either by country or by sector, I reckon, going by a previous conversation above. Procyon117 (talk) 09:54, 19 July 2024 (UTC)[reply]
One initial appraisal is that the travel sector seems to be the hardest hit. https://techcrunch.com/2024/07/19/banks-airlines-brokerage-houses-report-widespread-outages-across-the-globe/ kencf0618 (talk) 10:37, 19 July 2024 (UTC)[reply]
Um, I removed it in [1] without seeing this. Most other editors seemed to disregard the section distinction anyway. 174.92.25.207 (talk) 14:58, 19 July 2024 (UTC)[reply]

Too, this is occurring by time zone. We'll need a sortable list... kencf0618 (talk) 10:00, 19 July 2024 (UTC)[reply]

I'm not convinced it's very sensible to have this section. Every W10 corporate and public sector computer which received the CrowdStrike update will now be unbootable until the botched driver update is rolled back. IT departments are going to be very, very busy this weekend, and somebody at CrowdStrike will be looking for a new job. --Ef80 (talk) 10:10, 19 July 2024 (UTC)[reply]
Agree - if it's typical "we're fixing it" type of responses, there's no need to include it. Only unusual or novel examples of responses would seem relevant to a special section. - Fuzheado | Talk 10:45, 19 July 2024 (UTC)[reply]
I would advocate for public official responses, but maybe in one specific response section. Yes, an industry saying "we're working on it" isn't much of anything, but if a world leader or some major political figure starts talking shit about CrowdStrike, calls for better oversight, or erroneously jumps to blame foreign powers, it should get a mention. Schiffy (Speak to me|What I've done) 15:19, 19 July 2024 (UTC)[reply]

Cyber

Is any reliable source calling it a "cyber outage"? The only footnote using such a term is a CBC article which uses the term "IT outage" in the title. Nemo 10:15, 19 July 2024 (UTC)[reply]

I know Reuters and DW are calling it a cyber outage. But with that being said quite a number of outlets are calling it an IT outage too. Is there any huge differences between these 2 terms? S5A-0043Talk 10:18, 19 July 2024 (UTC)[reply]
The page was originally called "July 2024 global IT outages" but was moved without any explanation. ―Panamitsu (talk) 10:25, 19 July 2024 (UTC)[reply]
The term "IT" in titles is not a great practice – it relies on jargon and as an acronym, it is too English-centric and does not lend itself to ready translation. Cyber or computer outage has its advantages. I do agree moves like these should be discussed. - Fuzheado | Talk 10:32, 19 July 2024 (UTC)[reply]
I forgot to read the talk page before moving the page, but I would say that the current '2024 CrowdStrike incident' is a fine title. PhotographyEdits (talk) 11:13, 19 July 2024 (UTC)[reply]
It's really bad form to unilaterally move the page without getting some form of consensus. Please don't do that. - Fuzheado | Talk 11:19, 19 July 2024 (UTC)[reply]
AP is calling it a Global IT outage, but I think global cyber outage would be better. JoseMoranUrena (talk) 14:50, 19 July 2024 (UTC)[reply]

Driver or Content Update?

The president of Crowd Strike has just posted to Twitter/X that the issue was a faulty content update. Would this not be different to a driver update as written in the article? Should we change to content update? BeigeTeleprinter (talk) 10:48, 19 July 2024 (UTC)[reply]

Are those two statements contradictory though? A driver is just a more specific description of the "content." - Fuzheado | Talk 10:51, 19 July 2024 (UTC)[reply]
"Content" is just management PR bullshit. They rolled out a kernel driver update without testing it properly on W10. --Ef80 (talk) 11:15, 19 July 2024 (UTC)[reply]
And none of the end users checked it before rolling it out either? 2A0A:EF40:10B2:D801:4960:9247:5147:8900 (talk) 11:23, 19 July 2024 (UTC)[reply]
The updates install automatically without user intervention. Most Windows updates happen like that now, particularly in the corporate world. --Ef80 (talk) 12:38, 19 July 2024 (UTC)[reply]
The files in question are not drivers. They are rather more configuration files that are loaded by the CrowdStrike sensor driver and controls it's behavior.
The format of those files is proprietary but it's easily possible to verify that they are not valid drivers. 2003:DE:9727:7A1E:E9AB:32B4:B808:A188 (talk) 11:39, 19 July 2024 (UTC)[reply]
Per Ef80, I don't understand "content update". Perhaps "Configuration update"? 174.92.25.207 (talk) 13:44, 19 July 2024 (UTC)[reply]

remedy from users on reddit

https://www.reddit.com/r/crowdstrike/s/InhLrq6vTj Robinlight (talk) 11:38, 19 July 2024 (UTC)[reply]

Thanks, that fix is already described in the Wikipedia article. - Fuzheado | Talk 11:42, 19 July 2024 (UTC)[reply]
Someone appears to have just removed it under WP:NOTHOW. Highresheadphones (talk) 15:20, 19 July 2024 (UTC)[reply]
Yeah, that's odd. I have restored it. Describing the problematic file and what the fix is is not a violation of WP:NOTHOWTO, as it is not an instruction manual or guide. - Fuzheado | Talk 18:16, 19 July 2024 (UTC)[reply]
It was removed again by the same editor for the same reason (WP:NOTHOW). I've restored it, but pointed them to the talk page in case this is worthy of a discussion. I don't see how WP:NOTHOW is violated at all. GhostOfNoMeme 18:48, 19 July 2024 (UTC)[reply]
Thanks for restoring that. Celjski Grad, please don't remove it without discussing here first. - Fuzheado | Talk 18:51, 19 July 2024 (UTC)[reply]
It absolutely is a how-to guide, providing detailed instructions on “how to” remedy the situation. This is undeniable. The previous version of this section contained even more troubleshooting tips. Celjski Grad (talk) 18:57, 19 July 2024 (UTC)[reply]
It is true – one iteration that had a long sequence of steps is inappropriate. But mentioning the faulty file and that removing it alleviates the problem? That's not a "guide" or "manual" and does not "read like a 'how-to' style owner's manual." - Fuzheado | Talk 19:06, 19 July 2024 (UTC)[reply]
Describing a fix in a technical section is not anything like the type of content, or style of writing, that WP:HOWTO is intended to dissuade. It's useful information; it's not guiding the user through the steps. GhostOfNoMeme 19:10, 19 July 2024 (UTC)[reply]

Vagueness of "experiencing issues"

Is there a better alternative? TirFarThoinnExpora (talk) 12:06, 19 July 2024 (UTC)[reply]

§ Technical details makes it clear the computers won't start. We don't need to repeat that info. 174.92.25.207 (talk) 13:42, 19 July 2024 (UTC)[reply]
Very well. TirFarThoinnExpora (talk) 13:58, 19 July 2024 (UTC)[reply]

Which Windows OS?

The article doesn't specify which Windows versions. Are the versions 10 and 11? Unsure whether CrowdStrike still offers updates for its software on Windows 7. George Ho (talk) 12:11, 19 July 2024 (UTC)[reply]

It appears to be W10 systems that are affected. Presumably CS developed the update on W11 and didn't test it on properly on W10. --Ef80 (talk) 12:46, 19 July 2024 (UTC)[reply]
According to Cyber Security News it is at least Windows 10 and 11, although I don’t know where they have this information from. BeigeTeleprinter (talk) 12:47, 19 July 2024 (UTC)[reply]

Protection

Why was this page featured on ITN before it was protected? GeorgeMemulous (talk) 12:20, 19 July 2024 (UTC)[reply]

There is no requirement that a page in the ITN box needs to be protected. - Fuzheado | Talk 12:36, 19 July 2024 (UTC)[reply]
I regularly edit ITN articles. 174.92.25.207 (talk) 13:09, 19 July 2024 (UTC)[reply]

Lack of images

This is a huge outage that affects a lot of places in the world but there is little to no images showcassing it ? i added one image of a self checkout being affected by the outage on wikimedia but on twitter i'm seeing a tonne of images of entire airport being shutdown its kind of bizare that none have made their way here no ? should i go to the airport to take more pictures ? Kou~ (talk) 13:29, 19 July 2024 (UTC)[reply]

ive also seen images by social media users showing handwritten boarding passes, i think this could be a good addition to the above suggestion 197.240.106.98 (talk) 13:36, 19 July 2024 (UTC)[reply]
@Koupip: You may have forgotten to save your "one image". In Special:Contributions/Koupip, you didn't edit the article. 174.92.25.207 (talk) 13:41, 19 July 2024 (UTC)[reply]
i edited the french one not the english one as i try to not interfere too much with wikipedia since i suck at it as much as id like to help out lol, french wikipedia is kind of abandoned so i edit it on occassions. should i add the image to the english wiki page too ? the page seems really bloated and still under construction so i feel like it would caus more trouble then its worth no ? Kou~ (talk) 13:49, 19 July 2024 (UTC)[reply]
Please just WP:BOLDly add the image to English Wikipedia. I think you adding the image is beautiful. Don't worry about causing trouble while the page just because the page is under construction, until you are reverted.
I doubt "french wikipedia ... so i edit it on occassions" after seeing fr:Spécial:Contributions/Koupip. There was a grammatical error (affecter) corrected later. 174.92.25.207 (talk) 14:29, 19 July 2024 (UTC)[reply]
yeah i'm not too good with grammar which is why i don't edit wikipedia at all i just add pictures very rarely when it can help Kou~ (talk) 15:35, 19 July 2024 (UTC)[reply]
Nvm, I will boldly add it instead. My edit got blocked by WP:EF 174.92.25.207 (talk) 14:50, 19 July 2024 (UTC)[reply]
I've successfully asked someone on Xiaohongshu to give permission to upload an image of the crowd at an airport during the outage. They haven't put the permissions yet, so once they do it I'll upload the pic. S5A-0043Talk 13:45, 19 July 2024 (UTC)[reply]

Windows activation servers down

People from the massgrave project reported that activation was not possible from 0:44 to 0:53 (azure vms started to fail). possibly only US servers? ZalnaRs (talk) 13:57, 19 July 2024 (UTC)[reply]

Consistency with Time Zones

Most times in the article reference UTC, there is a single use of IST, and 2 rather unhelpful uses of "10:00" and "7:00 a.m".

Is there reason to warrant changing all times to UTC? TirFarThoinnExpora (talk) 14:03, 19 July 2024 (UTC)[reply]

about the IST one, MOS:TIMEZONE allows it. Warm Regards, Miminity (talk) (contribs) 14:20, 19 July 2024 (UTC)[reply]
Aha! Thank you! I'm a rather new editor, so thanks for the link. Kind regards, TirFarThoinnExpora (talk) 18:18, 19 July 2024 (UTC)[reply]
I've taken a look at the sources for the uses of 10:00 and 7:00. They appear to be from sources within UTC+2 timezones, so I've added '(UTC+2)' to them. 🔥HOTm̵̟͆e̷̜̓s̵̼̊s̸̜̃🔥 (talk・edits) 14:33, 19 July 2024 (UTC)[reply]

Google Cloud and Azure detections

Google Cloud and Azure started reporting bootlooping windows VMs. I think it should be included in the article.[1][2] ZalnaRs (talk) 14:03, 19 July 2024 (UTC)[reply]

Both are now included. I note the Azure status page gets the date wrong; it says 04:09 UTC on the 18th, but it should say the 19th. GhostOfNoMeme 17:47, 19 July 2024 (UTC)[reply]

References

  1. ^ https://status.cloud.google.com/incidents/DK3LfKowzJPpZq4Q9YqP#RP1d9aZLNFZEJmTBk8e1
  2. ^ https://azure.status.microsoft/en-us/status/

DMY dates and American English?

This combination seems inconsistent with MOS:TIES. Using MDY dates seems more appropriate. —⁠ ⁠BarrelProof (talk) 15:07, 19 July 2024 (UTC)[reply]

It was originally written with tag {{Use New Zealand English}} and dmy dates [2]. We should not be defaulting to American English and date formats for a worldwide event. MOS:TIES does not demand use of American English, since it is a worldwide event, and the fact that it's a US company is trivial in comparison to the worldwide nature of the event. If anything, it should be switched back to New Zealand English (or similar Commonwealth English) as per MOS:RETAIN. Joseph2302 (talk) 15:16, 19 July 2024 (UTC)[reply]
It currently says to use American English. It's about a faulty patch released by an American company for computers running an operating system from another American company. It was first observed in virtual computers running on a cloud computing system of an American company, and the source of the problem was identified about three hours later by another American company. —⁠ ⁠BarrelProof (talk) 15:22, 19 July 2024 (UTC)[reply]
The impact is worldwide, but I don't believe it's fair to say the US connection is "trivial". CrowdStrike and Microsoft are American companies. GhostOfNoMeme 15:27, 19 July 2024 (UTC)[reply]
And so is Google, which was who identified the source of the problem. —⁠ ⁠BarrelProof (talk) 15:36, 19 July 2024 (UTC)[reply]
(edit conflict) It's about a worldwide outage that affected many companies and countries, not just the US. That's enough reason not to default to one countries' spellings/date formats, and apply MOS:RETAIN instead. Joseph2302 (talk) 15:28, 19 July 2024 (UTC)[reply]
But if it's going to use DMY dates, it shouldn't be using American English. If it's going to use American English, it shouldn't be using DMY dates. The current combination doesn't make sense. —⁠ ⁠BarrelProof (talk) 15:32, 19 July 2024 (UTC)[reply]
I would be happy with a switch to {{Use New Zealand English}} or {{Use British English}}, then, especially in light of the article's use of {{Use dmy dates}}. I have no strong opinion. But the current mismatch between dates and variety of English is worth addressing. GhostOfNoMeme 15:39, 19 July 2024 (UTC)[reply]
It is a worldwide event, and the very first revision is clear in using {{Use New Zealand English}}. Per MOS:RETAIN, it should be used in this article. MOS:TIES does not apply since CrowdStrike is not the subject of the article, and the event itself is worldwide. You could just as easily say that MOS:TIES should be with Australia/New Zealand since the majority of early impact/reporting was in those timezones. Melmann 16:30, 19 July 2024 (UTC)[reply]
The logic is that it happens worldwide, and especially in Australia/New Zealand. Why not use {{engvarb}} instead, and dmy dates. It should not use American English. ToadetteEdit! 16:39, 19 July 2024 (UTC)[reply]
I agree with BarrelProof that we should be using American English, given that the companies involved are all American and the impact seems to be spread pretty evenly worldwide. I don't see that it's especially bad in Australia/NZ, that impression may just be because of the time that it started (2PM AEST vs midnight EST) leading to it being noticed earlier there, or also customized search/news results based on user location. Kdroo (talk) 17:50, 19 July 2024 (UTC)[reply]
At this stage (and considering MOS:RETAIN per the above) I think it's best left with New Zealand English (and dmy dates). GhostOfNoMeme 18:29, 19 July 2024 (UTC)[reply]
There is insufficient justification for enforcing NZ English here. We have American companies on both counts - Microsoft as the main platform, and CrowdStrike as the one that caused the error. - Fuzheado | Talk 18:48, 19 July 2024 (UTC)[reply]
The standard ISO 8601 for dates is YYYY-MM, YYYY-MM-DD or YYYYMMDD and should be used in all articles whose expected viewership is more than regional. — Preceding unsigned comment added by 2603:6000:aa00:151f::193b (talk • contribs) 19:55, 19 July 2024 (UTC)[reply]
The Wikipedia guideline MOS:BADDATE does not consider that date format acceptable for Wikipedia. It says to use it "Only in limited situations where brevity is helpful". —⁠ ⁠BarrelProof (talk) 21:33, 19 July 2024 (UTC)[reply]

Title should be more specific

There was a similar incident where crowdstrike pinned CPUs to 100% until devices were updated and restarted just 3 weeks ago at end of June, which was less impactful.

The title should probably be more specific with this in mind. "July 2024 CrowdStrike incident" perhaps? Or perhaps we can include a section to also mention this. Aveaoz (talk) 15:11, 19 July 2024 (UTC)[reply]

I agree, we should make the title more specific.
I don't think it's appropriate to include a section on this article that mentions a separate (unrelated) incident. Jtbwikiman (talk) 15:26, 19 July 2024 (UTC)[reply]
There is a contested request at Wikipedia:Requested moves/Technical requests by Luminism to move the article to July 2024 global IT outages. --Ahecht (TALK
PAGE) 15:39, 19 July 2024 (UTC)[reply]
But since that incident doesn't have an article or even a mention at CrowdStrike, that is no reason to change the article title. Gråbergs Gråa Sång (talk) 15:59, 19 July 2024 (UTC)[reply]
Sounds to me like the June incident probably fails WP:N. Unlike today's incident. 🔥HOTm̵̟͆e̷̜̓s̵̼̊s̸̜̃🔥 (talk・edits) 16:15, 19 July 2024 (UTC)[reply]
The title needs to be more specific. Many sources say it is an outrage, while the title implies that it is an incident. Maybe start a requested move? ToadetteEdit! 16:42, 19 July 2024 (UTC)[reply]
Or wait a few days. This article is like 10h old. Gråbergs Gråa Sång (talk) 16:50, 19 July 2024 (UTC)[reply]
Agreed, "outrage" is rather tabloid in the circumstances. It's certainly a massive corporate screwup by CS though, and we'll have to see what's left of the company after the many, many lawsuits have beed settled. --Ef80 (talk) 17:06, 19 July 2024 (UTC)[reply]
I believe Toadette means "outage", instead of "outrage". GhostOfNoMeme 17:29, 19 July 2024 (UTC)[reply]
We could do a topbar. and say not to be confused with this ZalnaRs (talk) 18:50, 19 July 2024 (UTC)[reply]
When we have a "not to be confused with", that usually refers to another WP-article. Gråbergs Gråa Sång (talk) 20:45, 19 July 2024 (UTC)[reply]
Given the disparity between the notoriety of these two events, this feels unnecessary to me. It's like saying Barack Obama is not to be confused with my friend Barack, who works at McDonald's. Jtbwikiman (talk) 21:28, 19 July 2024 (UTC)[reply]

Requested move 19 July 2024

2024 CrowdStrike incident → ? – Two reasons: the first is that the lede of this article is straightforward; it instead say that there is an outrage, before saying how, where the title is derived from. Second, most reliable sources often refer this event as an outrage. The title should at least be moved to a title containing "outrage". ToadetteEdit! 16:54, 19 July 2024 (UTC)[reply]

  • You mean "outage", not "outrage", right? :)
Oppose. My only concern is that the title may be misleading: this was not an outage at CrowdStrike, rather it was a global outage of systems caused by CrowdStrike. The incident led to the outages. I do see many articles using "CrowdStrike outage" nevertheless. GhostOfNoMeme 17:01, 19 July 2024 (UTC)[reply]
It's not a good name, because it's not just the CrowdStrike "company" who was effected. Everyone was effected who was at airports etc... ZalnaRs (talk) 18:27, 19 July 2024 (UTC)[reply]
• Move to 2024 CrowdStrike outage as per above. FloridaMan21 (talk) 18:28, 19 July 2024 (UTC)[reply]
–Gluonz talk contribs 18:40, 19 July 2024 (UTC)[reply]
Oppose - CrowdStrike did not experience an outage themselves. Here for the one billionth edit (talk) 19:28, 19 July 2024 (UTC)[reply]
I mean outage nor Incident are the right words. AidenT06 (talk) 19:32, 19 July 2024 (UTC)[reply]
Support Alt to 2024 worldwide IT outage or similar to be WP:TITLECON with other outages, but oppose 2024 Crowdstrike outage - Like other people have been saying, this isn't an outage at Crowdstrike, it's an incident caused by Crowdstrike. The current title is also too vague, I would oppose keeping it at the current title. MetropolitanIC (💬|📝) 20:42, 19 July 2024 (UTC)[reply]
Neutral. I do agree the page needs moving, but 2024 CrowdStrike outage is slightly misleading, but I feel the name should involve CrowdStrike in some way. Lordseriouspig 20:55, 19 July 2024 (UTC)[reply]
Oppose. "CrowdStrike outage" is not correct - the software wasnt "out" at all it just broke any PC it was installed on. "incident" works best, so keep status quo.  Nixinova   T   C   21:28, 19 July 2024 (UTC)[reply]
Neutral. I do think the article needs a stronger word than "incident," but I don't think "2024 CrowdStrike outage" would be a good term. Maybe something like "2024 worldwide IT outage" like @MetropolitanIC suggested. Benpiano800 (talk) 21:37, 19 July 2024 (UTC)[reply]
Oppose the term 'CrowdStrike Outage'. It wasn't a CrowdStrike outage, as there was no outage on behalf of CrowdStrike (unlike the 2021 Facebook outage or the 2023 Optus outage or the various Google services outages). Yes, there were many outages as a result of this incident caused by the CrowdStrike oopsie - but like CrowdStrike itself didn't have an outage, so saying they had an outage in the article name would be a bit misleading.
On that note, weak propose the title 2024 CrowdStrike Oopsie /s 🔥HOTm̵̟͆e̷̜̓s̵̼̊s̸̜̃🔥 (talk・edits) 21:47, 19 July 2024 (UTC)[reply]
Oppose - CrowdStrike did not suffer an outage; rather, their customers did; change is ambiguous, also per above. Silikonz💬 22:24, 19 July 2024 (UTC)[reply]

Impact on the Government of the United States

I'm a civilian employee of the US government and noticed that the impact on us has yet to be mentioned. I know my agency was hit due to the BSOD on my government-issued laptop referencing csagent.sys; OPM was presumably hit as well, the operating status hasn't been updated since yesterday morning.   –Skywatcher68 (talk) 17:30, 19 July 2024 (UTC)[reply]

I started a section on this. Atubofsilverware (talk) 17:47, 19 July 2024 (UTC)[reply]
I see a COI tag got added. Nonetheless, the effects on the US gov are important, so they should stay on the page. Atubofsilverware (talk) 17:53, 19 July 2024 (UTC)[reply]
 Not done for now: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format. Melmann 18:50, 19 July 2024 (UTC)[reply]
It was done; see the bottom of the Social services section. It's a rough start but it's generally what they requested. Atubofsilverware (talk) 18:51, 19 July 2024 (UTC)[reply]

Displaying text as images

I'm concerned that the images of text such as KFC app notice and Vanden Borre website, except the BSOD screenshot itself, may not meet MOS:TEXTASIMAGES. At least for BSOD, it shows us what nearly every person affected saw, and BSODs themselves may have a sort of visceral impact that purely text could not, thus it, in my view, brings a value beyond just the textual content of the image. The other two, however, could be transcribed into one of the divbox templates if the text itself is seen to be of value, so at least the accessibility concerns raised by MOS:TEXTASIMAGES are resolved. Melmann 19:02, 19 July 2024 (UTC)[reply]

English Grammar

Can we follow American English by saying "July 19, 2024" instead of "19 July 2024"? Please. 2601:40A:8400:1820:41C7:7591:2AE9:2851 (talk) 19:24, 19 July 2024 (UTC)[reply]

See the above discussion. GhostOfNoMeme 19:28, 19 July 2024 (UTC)[reply]

Withdrawal of race car?

In the Response section, how is the withdrawal of a car from a race part of a response to the company's faulty software update? The cited source does not explain this. —Finell 19:45, 19 July 2024 (UTC)[reply]

The driver, Sponsor was Crowdstrike and their CEO.
the car was withdrew in the aftermath of the outage. AidenT06 (talk) 20:24, 19 July 2024 (UTC)[reply]

Move the page back

Messed up and moved before the discussion was done. Sorry. Zenphia1 (talk) 20:32, 19 July 2024 (UTC)[reply]

 Done — moved the page back 0xC0000005 (talk) 20:37, 19 July 2024 (UTC)[reply]

Is the Southwest Airlines, bit necessary?

Firstly, Is it needed? Do we need to list the companies that weren't effected? Also the article linked is very speculatory. "Some are attributing that to Windows 3.1. Major portions of Southwest’s systems are reportedly built on Windows 95 and Windows 3.1" AidenT06 (talk) 21:42, 19 July 2024 (UTC)[reply]

@AidenT06 Doesn't add to anything of value to the article, agreed. PipitSweet16 (talk) 22:01, 19 July 2024 (UTC)[reply]
Windows 3.1 is thirty years old. This is nonsense. 24.40.254.80 (talk) 22:17, 19 July 2024 (UTC)[reply]
That's certainly a weirdly specific (and perhaps embarrassing) reason for not being a CrowdStrike customer. 3df (talk) 22:17, 19 July 2024 (UTC)[reply]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:2024_CrowdStrike-related_IT_outages&oldid=1235555329"