CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report

Sensor content-configuration update caused a widespread Windows outage

CrowdStrike resolved M7.5 Severe storm 2024-07-19

CrowdStrike: Sensor content-configuration update caused a widespread Windows outage. Scope: Global.

M7.5

Severe storm

How CHYP Magnitude works

  • 855d 8hDurationand counting
  • 1Systems namedfrom the source
  • 7Places named7 on the map
  • 0Dependentscatalogued, inferred
  • 2/4Evidence kindsindependent families
  • 1Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Oct 1, 2024Mar 2, 2025Jul 31, 2025Dec 29, 2025May 29, 2026Oct 27, 2026 Official statusJul 18, 9:00 PM PT · Impact begins (vendor-stated)Network & routingnothing in this windowEarly signalsnothing in this windowNews & chatternothing in this windowCoincidence (KEV)nothing in this window ▼ startnow ▼

Drag or press Play to replay what was public at each moment. Each dot links to its evidence. Lanes are kept separate on purpose.

What happened

CrowdStrike: Sensor content-configuration update caused a widespread Windows outage. Scope: Global.

What broke

CrowdStrike Falcon sensor (Windows).

Who was hit

Hit: Global. No catalogued services depend on CrowdStrike.

How it recovered

Resolved after 855d 8h.

2Blast radius

CrowdStrike0 dependents

Center: CrowdStrike. Inner ring: what it runs on. Outer ring: catalogued services that run on it, coloured by their official status right now. Dependencies are inferred from public information.

3Blast map

North America · vendor-stated scope: globalSouth America · vendor-stated scope: globalEurope · vendor-stated scope: globalAfrica · vendor-stated scope: globalMiddle East · vendor-stated scope: globalAsia · vendor-stated scope: globalOceania · vendor-stated scope: global
  1. North America
  2. South America
  3. Europe
  4. Africa
  5. Middle East
  6. Asia
  7. Oceania

Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.

4Failure-mode fingerprint

RetriesControl planeConfig pushCascadeCapacity
  • Config propagationvendor post-incident report (Meltdown Index)
  • Retry amplificationno sign
  • Control-plane couplingno sign
  • Dependency cascadeno sign
  • Capacity exhaustionno sign

Failure modes as stated in the vendor's own post-incident report (Meltdown Index).

5Evidence matrix

Official statusOfficial status · Jul 18, 3:00 PM PT: 1 itemOfficial status · Aug 23, 6:36 AM PT: 0 itemsOfficial status · Sep 27, 10:13 PM PT: 0 itemsOfficial status · Nov 2, 1:49 PM PT: 0 itemsOfficial status · Dec 8, 4:26 AM PT: 0 itemsOfficial status · Jan 12, 8:02 PM PT: 0 itemsOfficial status · Feb 17, 11:39 AM PT: 0 itemsOfficial status · Mar 25, 4:16 AM PT: 0 itemsOfficial status · Apr 29, 7:52 PM PT: 0 itemsOfficial status · Jun 4, 11:29 AM PT: 0 itemsOfficial status · Jul 10, 3:05 AM PT: 0 itemsOfficial status · Aug 14, 6:42 PM PT: 0 itemsOfficial status · Sep 19, 10:18 AM PT: 0 itemsOfficial status · Oct 25, 1:55 AM PT: 0 itemsOfficial status · Nov 29, 4:32 PM PT: 0 itemsOfficial status · Jan 4, 8:08 AM PT: 0 itemsOfficial status · Feb 8, 11:45 PM PT: 0 itemsOfficial status · Mar 16, 4:21 PM PT: 0 itemsOfficial status · Apr 21, 7:58 AM PT: 0 itemsOfficial status · May 26, 11:34 PM PT: 0 itemsOfficial status · Jul 1, 3:11 PM PT: 0 itemsOfficial status · Aug 6, 6:48 AM PT: 0 itemsOfficial status · Sep 10, 10:24 PM PT: 0 itemsOfficial status · Oct 16, 2:01 PM PT: 0 itemsNetwork & routingNetwork & routing · Jul 18, 3:00 PM PT: 0 itemsNetwork & routing · Aug 23, 6:36 AM PT: 0 itemsNetwork & routing · Sep 27, 10:13 PM PT: 0 itemsNetwork & routing · Nov 2, 1:49 PM PT: 0 itemsNetwork & routing · Dec 8, 4:26 AM PT: 0 itemsNetwork & routing · Jan 12, 8:02 PM PT: 0 itemsNetwork & routing · Feb 17, 11:39 AM PT: 0 itemsNetwork & routing · Mar 25, 4:16 AM PT: 0 itemsNetwork & routing · Apr 29, 7:52 PM PT: 0 itemsNetwork & routing · Jun 4, 11:29 AM PT: 0 itemsNetwork & routing · Jul 10, 3:05 AM PT: 0 itemsNetwork & routing · Aug 14, 6:42 PM PT: 0 itemsNetwork & routing · Sep 19, 10:18 AM PT: 0 itemsNetwork & routing · Oct 25, 1:55 AM PT: 0 itemsNetwork & routing · Nov 29, 4:32 PM PT: 0 itemsNetwork & routing · Jan 4, 8:08 AM PT: 0 itemsNetwork & routing · Feb 8, 11:45 PM PT: 0 itemsNetwork & routing · Mar 16, 4:21 PM PT: 0 itemsNetwork & routing · Apr 21, 7:58 AM PT: 0 itemsNetwork & routing · May 26, 11:34 PM PT: 0 itemsNetwork & routing · Jul 1, 3:11 PM PT: 0 itemsNetwork & routing · Aug 6, 6:48 AM PT: 0 itemsNetwork & routing · Sep 10, 10:24 PM PT: 0 itemsNetwork & routing · Oct 16, 2:01 PM PT: 0 itemsEarly signalsEarly signals · Jul 18, 3:00 PM PT: 0 itemsEarly signals · Aug 23, 6:36 AM PT: 0 itemsEarly signals · Sep 27, 10:13 PM PT: 0 itemsEarly signals · Nov 2, 1:49 PM PT: 0 itemsEarly signals · Dec 8, 4:26 AM PT: 0 itemsEarly signals · Jan 12, 8:02 PM PT: 0 itemsEarly signals · Feb 17, 11:39 AM PT: 0 itemsEarly signals · Mar 25, 4:16 AM PT: 0 itemsEarly signals · Apr 29, 7:52 PM PT: 0 itemsEarly signals · Jun 4, 11:29 AM PT: 0 itemsEarly signals · Jul 10, 3:05 AM PT: 0 itemsEarly signals · Aug 14, 6:42 PM PT: 0 itemsEarly signals · Sep 19, 10:18 AM PT: 0 itemsEarly signals · Oct 25, 1:55 AM PT: 0 itemsEarly signals · Nov 29, 4:32 PM PT: 0 itemsEarly signals · Jan 4, 8:08 AM PT: 0 itemsEarly signals · Feb 8, 11:45 PM PT: 0 itemsEarly signals · Mar 16, 4:21 PM PT: 0 itemsEarly signals · Apr 21, 7:58 AM PT: 0 itemsEarly signals · May 26, 11:34 PM PT: 0 itemsEarly signals · Jul 1, 3:11 PM PT: 0 itemsEarly signals · Aug 6, 6:48 AM PT: 0 itemsEarly signals · Sep 10, 10:24 PM PT: 0 itemsEarly signals · Oct 16, 2:01 PM PT: 0 itemsNews & chatterNews & chatter · Jul 18, 3:00 PM PT: 0 itemsNews & chatter · Aug 23, 6:36 AM PT: 0 itemsNews & chatter · Sep 27, 10:13 PM PT: 0 itemsNews & chatter · Nov 2, 1:49 PM PT: 0 itemsNews & chatter · Dec 8, 4:26 AM PT: 0 itemsNews & chatter · Jan 12, 8:02 PM PT: 0 itemsNews & chatter · Feb 17, 11:39 AM PT: 0 itemsNews & chatter · Mar 25, 4:16 AM PT: 0 itemsNews & chatter · Apr 29, 7:52 PM PT: 0 itemsNews & chatter · Jun 4, 11:29 AM PT: 0 itemsNews & chatter · Jul 10, 3:05 AM PT: 0 itemsNews & chatter · Aug 14, 6:42 PM PT: 0 itemsNews & chatter · Sep 19, 10:18 AM PT: 0 itemsNews & chatter · Oct 25, 1:55 AM PT: 0 itemsNews & chatter · Nov 29, 4:32 PM PT: 0 itemsNews & chatter · Jan 4, 8:08 AM PT: 0 itemsNews & chatter · Feb 8, 11:45 PM PT: 0 itemsNews & chatter · Mar 16, 4:21 PM PT: 0 itemsNews & chatter · Apr 21, 7:58 AM PT: 0 itemsNews & chatter · May 26, 11:34 PM PT: 0 itemsNews & chatter · Jul 1, 3:11 PM PT: 0 itemsNews & chatter · Aug 6, 6:48 AM PT: 0 itemsNews & chatter · Sep 10, 10:24 PM PT: 0 itemsNews & chatter · Oct 16, 2:01 PM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Jul 18, 3:00 PM PT: 0 itemsCoincidence (KEV) · Aug 23, 6:36 AM PT: 0 itemsCoincidence (KEV) · Sep 27, 10:13 PM PT: 0 itemsCoincidence (KEV) · Nov 2, 1:49 PM PT: 0 itemsCoincidence (KEV) · Dec 8, 4:26 AM PT: 0 itemsCoincidence (KEV) · Jan 12, 8:02 PM PT: 0 itemsCoincidence (KEV) · Feb 17, 11:39 AM PT: 0 itemsCoincidence (KEV) · Mar 25, 4:16 AM PT: 0 itemsCoincidence (KEV) · Apr 29, 7:52 PM PT: 0 itemsCoincidence (KEV) · Jun 4, 11:29 AM PT: 0 itemsCoincidence (KEV) · Jul 10, 3:05 AM PT: 0 itemsCoincidence (KEV) · Aug 14, 6:42 PM PT: 0 itemsCoincidence (KEV) · Sep 19, 10:18 AM PT: 0 itemsCoincidence (KEV) · Oct 25, 1:55 AM PT: 0 itemsCoincidence (KEV) · Nov 29, 4:32 PM PT: 0 itemsCoincidence (KEV) · Jan 4, 8:08 AM PT: 0 itemsCoincidence (KEV) · Feb 8, 11:45 PM PT: 0 itemsCoincidence (KEV) · Mar 16, 4:21 PM PT: 0 itemsCoincidence (KEV) · Apr 21, 7:58 AM PT: 0 itemsCoincidence (KEV) · May 26, 11:34 PM PT: 0 itemsCoincidence (KEV) · Jul 1, 3:11 PM PT: 0 itemsCoincidence (KEV) · Aug 6, 6:48 AM PT: 0 itemsCoincidence (KEV) · Sep 10, 10:24 PM PT: 0 itemsCoincidence (KEV) · Oct 16, 2:01 PM PT: 0 itemsJul 18, 3:00 PM PTnow

Correlation is not causation

Five independent lanes across the window. Brighter = stronger item. Items landing in the same column are coincidence unless the provider says otherwise.

6In the vendor's words

On July 19, 2024, as part of regular operations, CrowdStrike released a content configuration update (via channel files) for the Windows sensor that resulted in a widespread outage.

CrowdStrike reported that as of 29 Jul 2024 at 8:00 p.m. EDT, about 99% of Windows sensors were online compared to before the content update. A single continuous-impact duration is not recorded here because recovery varied by customer and was staggered. Additional official RCA: https://www.crowdstrike.com/wp-content/uploads/2024/08/Executive-Summary_Root-Cause-Analysis_Channel-File-291.pdf (HTTP 200).

Verbatim excerpt from Channel File 291 Incident RCA is Available | CrowdStrike.

7Historical twins

Nearest matches in the Control-Plane Meltdown Index (1.0.0, vendor-sourced, tracked since 2024 with earlier landmark cases). Similarity = provider + failure modes + scope.

Cloudy_Day take

  • A change went wider, faster than its safety net. Staged rollouts and kill switches exist for exactly this.
  • Longer than 19 of 19 indexed control-plane meltdowns with a stated duration.

Automated take: rules written by Cloudy_Day, applied to public data. Not a human verdict on this incident, not a root-cause finding, not affiliated with CrowdStrike.

8Dissection capsule

Share card for this dissection

Everything above as one shareable, citable capsule with a content hash.

JSON capsuleMarkdownShare card (SVG)

Open CrowdStrike in the War Room →Status page →

Embed this card
<a href="https://www.chyp.ai/dissect/m/crowdstrike-channel-file-291-2024-07-19/"><img src="https://www.chyp.ai/dissect/m/crowdstrike-channel-file-291-2024-07-19/card.svg" alt="Sensor content-configuration update caused a widespread Win… · ORBIT Outage Dissector" width="600"></a>

Sources & limits

  • Taken from the vendor's own post-incident report; quotes are verbatim excerpts.
  • Dependents are today's inferred catalogue, not who was affected on the day.
  • Correlation is not causation. Lanes are kept apart so overlap never reads as cause.
  • ORBIT is passive: it never contacts the provider or probes its systems. Independent researcher, not affiliated.