---
title: "CrowdStrike Channel File 291 outage"
description: "What the retained public evidence establishes about the CrowdStrike / Microsoft global outage incident, its attack path, impact, and response."
incident_type: "Cybersecurity incident"
status: "active"
last_modified: "2026-09-19"
canonical_url: "https://www.ally.security/incidents/crowdstrike-channel-file-291-outage-2024"
markdown_url: "https://www.ally.security/incidents/crowdstrike-channel-file-291-outage-2024.md"
stix_url: "https://www.ally.security/incidents/crowdstrike-channel-file-291-outage-2024/stix.json"
---

# CrowdStrike Channel File 291 outage

The retained public source describes the CrowdStrike / Microsoft global outage incident as NOT an attack — a faulty CrowdStrike Falcon sensor content update caused mass Windows BSOD crashes. Other material details remain unresolved.

Last modified Sep 19, 2026 · 1 source

## Summary

- **Environment:** Global IT (all sectors)
- **Operational impact:** The reviewed source does not establish a precise operational or data impact
- **Financial impact:** No financial figure is established by the reviewed source evidence

## What happened

In Jul 19, 2024, CrowdStrike experienced an incident in its global it (all sectors) environment. The retained source describes the attack path as follows: NOT an attack — a faulty CrowdStrike Falcon sensor content update caused mass Windows BSOD crashes. [1](#source-1)

## Impact

- The reviewed source does not establish a precise affected-person count, data scope, or operational consequence.
- No financial loss, ransom amount, recovery cost, or regulatory penalty is established by the reviewed source evidence.

## Threat Group & Attack Vector

The retained source describes the attack path as follows: NOT an attack — a faulty CrowdStrike Falcon sensor content update caused mass Windows BSOD crashes. The canonical record does not add intrusion steps beyond those supported by the source. [1](#source-1)

### Actors

- No threat actor group has been identified in the reviewed public evidence.

### TTPs

- No specific MITRE ATT\&CK technique is currently mapped for this case.

## Response

The reviewed source does not describe containment, notification, or restoration steps in enough detail to summarize them responsibly.

This account is bounded to [Channel File 291 incident RCA is available](https://www.crowdstrike.com/en-us/blog/channel-file-291-rca-available/). Details absent from that evidence are left unresolved rather than inferred. [1](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/crowdstrike-channel-file-291-outage-2024/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### Channel File 291 incident RCA is available

research · CrowdStrike

<https://www.crowdstrike.com/en-us/blog/channel-file-291-rca-available/>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Resulted In · 100% confidence · current**  
   CrowdStrike Channel File 291 outage: The reviewed source documents the crowdstrike channel file 291 outage involving CrowdStrike, Microsoft.
2. **Affected Organization · 100% confidence · current**  
   CrowdStrike Channel File 291 outage: Microsoft
3. **Resulted In · 87% confidence · current**  
   CrowdStrike Channel File 291 outage: NOT an attack — a faulty CrowdStrike Falcon sensor content update caused mass Windows BSOD crashes.
4. **Affected Organization · 100% confidence · current**  
   CrowdStrike Channel File 291 outage: CrowdStrike

</details>