Our Interconnected, Resilient, Modern World ... Is Still Painfully and Remarkably Brittle: A Case Study of the Risks of Technology Failures
The DOI matches its Crossref record; 8 of the 8 references it cites were found in a registry or an index; 3 of the 42 sources its claims cite were checked for support.
Abstract
8.5 million Windows PCs failed to restart in July of 2024. CrowdStrike, an IT security company, delivered updates with a faulty configuration file to millions of Windows PCs around the world. The failure disrupted or halted the global operations of airlines, banks, medical facilities, and much more. Many PCs were unable to reboot without direct human intervention. This resulted in delays that impacted the recovery time for all types of businesses, as well as their employees, supply chains, and consumers. The paper also provides several other failure scenarios for student analysis, including cyber-attacks on health care and government, and a broader system failure in air traffic control, as well as a detailed background in the underlying principles of technological resilience. This teaching case for undergraduate and graduate information systems courses encourages students to examine key questions for each event: What went wrong, what was the root cause, and why didn't we see this failure coming? What can we learn from each case that might help technology leaders and their business counterparts to further mitigate the risk of any similar events?
Overview
CoChat Summary
TL;DR
This teaching case uses the July 2024 CrowdStrike outage and three other technology-failure scenarios (Newark air traffic control, Baltimore ransomware, Change Healthcare cyberattack) to illustrate system resilience, brittleness, and risk-management concepts for information systems students. It pairs conceptual background with discussion questions and follow-on research prompts rather than presenting original empirical findings.
Key findings
- The CrowdStrike faulty configuration update caused 8.5 million Windows PCs to crash and required manual intervention to recover; Delta alone reported costs over USD 500 million, and the airline industry suffered "many billions of dollars" in damages.
- The Newark TRACON outage lasted 90 seconds (no radio, no radar); over 65 flights were diverted, 160 canceled, and 424 delayed, with the next day seeing more than 370 delayed and more than 500 canceled; the FAA later cut Newark departures/arrivals per hour by 50%.
- Baltimore's 2019 ransomware attack involved a $76,000 ransom demand (refused) but over $18 million in recovery costs, with systems held hostage over five weeks and only 70% of employees back on email by day 36.
- The Change Healthcare attack (detected February 21, 2024, begun February 12) involved a $22 million ransom, an estimated $2.87 billion cost to UnitedHealth Group in 2024, a $100 million per-day industry impact, ~$9 billion in provider loans, and a breach ultimately estimated to affect ~190 million people.
Methods
- Design: a teaching case for undergraduate and graduate introductory information systems courses, structured as a hook, learning objectives, technical background (Section 2), four scenarios with discussion questions (Section 3), additional research prompts (Section 4), and conclusions.
- Data/sample: no primary data collection; the case draws on secondary news and industry sources (e.g., CBS News, NPR, Reuters, Ars Technica, FAA statements) and prior literature to describe the CrowdStrike, Newark, Baltimore, and Change Healthcare events, plus Heathrow and Waymo examples.
- Analysis: conceptual exposition of resilience, brittleness, complexity (Baccarini's organizational/technological distinction), resilience testing, cloud services, pervasive client software, automated updates, root cause analysis, and risk management (avoidance, transfer, reduction, acceptance).
Limitations
- Not stated in the paper: the authors do not include a formal limitations section.
- Evident from the text: the case relies on secondary sources (news reports, vendor blogs, FAA statements) rather than independent verification, and it presents no empirical evaluation of student learning outcomes or of the case's pedagogical effectiveness.
- Evident from the text: several scenarios are described as ongoing or evolving (e.g., Change Healthcare data-leak status "as of June 2025," FAA upgrades "slow-going"), so figures and conditions may be superseded.
Model-written summary. Check it against the paper before relying on it.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
2 Valid · 9 Not valid · 40 Not checked · 27 Own results and interpretations
Every source the paper cites for this claim was checked and supports it.
In the paper
“cloud providers can still experience failures in both primary and backup operations (Alozie et al., 2024).”
What the sources say
- Supportedcites Alozie et al., 2024 matched to “Disaster Recovery in Cloud Computing: Site Reliability Engineering Strategies for Resilience and Business Continuity” (2024) source
Section 4, “Strategies for Effective Disaster Recovery” (page unavailable), describes backup systems taking over when primary systems fail. Section 7, “Challenges and Solutions” (page unavailable), says misconfigured failover can cause extended downtime or partial outages and that backup and recovery processes need testing. Together, these support the claim that primary operations and backup-based recovery can both fail. (LLM, conf=0.86)
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Supported
None of the sources cited for this claim have been checked yet.
In the paper
“The computers affected were unable to recover without direct manual intervention, meaning IT teams had to physically access each machine to fix the problem.”
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
In the paper
“This happened to the air traffic controllers at the Philadelphia Pennsylvania Terminal Radar Approach Control (TRACON) center, which is responsible for separating and sequencing planes in and out of Newark Liberty International Airport in New Jersey. The outage -no radio, no radar -lasted for ninety seconds.”
What the sources say
- Not matchedcites Martínez & Dumas, 2025
An author–year citation the paper’s reference list doesn’t settle. We don’t search these by name.
plainSingle case- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: unclear — It is unclear whether the paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Not matched
A conclusion the paper draws from its own results — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“This resulted in delays that impacted the recovery time for all types of businesses, as well as their employees, supply chains, and consumers.”
plainstates a cause- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
In the paper
“8.5 million Windows PCs failed to restart in July of 2024.”
- Also stated in: § 3. SCENARIOS: SYSTEM RESILIENCE FAILURES · plain
“a faulty software update released by CrowdStrike for its cybersecurity software that caused 8.5 million Windows computers to crash.”
What the sources say
- Not matchedcites Kerner, 2024
An author–year citation the paper’s reference list doesn’t settle. We don’t search these by name.
plainstates a cause- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Also stated in: § 3. SCENARIOS: SYSTEM RESILIENCE FAILURES · plain
30 more claims
Create a free account to see all 78 claims and every source verdict.
- Probably not a substantial claim. 21
- It may state two separate claims as one. 31
- The quote only partly states this claim. 1
Citations
Cites
The concept of project complexity—a review
Baccarini, D. (1996) · International Journal of Project Management · doi:10.1016/0263-7863(95)00093-3 · Cited by 1,192
Design science research contributions: Finding a balance between artifact and theory
Georgia State University, Baskerville, R., Baiyere, A., University of Turku, F., Gergor, S., Australian National University, Hevner, A., University of South Florida, Rossi, M., & Aalto University (2018) · Journal of the Association for Information Systems · doi:10.17705/1jais.00495 · Cited by 437
Supply chain resilience: new challenges and opportunities
Shi, X., Liu, W., & Lim, M. K. (2024) · International Journal of Logistics Research and Applications · doi:10.1080/13675567.2023.2262396 · Cited by 39
Risk Mitigation Strategies in Innovative Projects
Ahmed, R. (2017) · InTech eBooks · doi:10.5772/intechopen.69004 · Cited by 22
Alozie, C. E., Akerele, J. I., Kamau, E., & Myllynen, T. (2024) · International Journal of Management and Organizational Research · doi:10.54660/ijmor.2024.3.1.36-48 · Cited by 5
Update at Your Own Risk: Analysis and Recommendations for Update-Related Vulnerabilities
Usman, A. B., & Asplund, M. (2025) · IFIP Advances in Information and Communication Technology · doi:10.1007/978-3-031-92886-4_7 · Cited by 3
Witman, P. D., Prior, J., Mackelprang, S., et al. (2024) · Information Systems Education Journal · doi:10.62273/efwa2093 · Cited by 2
Self-citationAdvancing information system testing: challenges, methods, and practical recommendations
Otkhozoria, N., Petriashvili, L., Zhvania, T., & Imerlishvili, A. (2025) · International Science Journal of Engineering & Agriculture · doi:10.46299/j.isjea.20250402.13 · Cited by 1
Research works printed but not linked: 2
- Hatton, R. (2024). How has the Change Healthcare cyberattack affected physicians? Becker's ASC Review . Retrieved June 28, 2025, from https://www.beckersasc.com/ascnews/how-has-the-change-healthcarecyberattack-affected-physicians/
- Mathews, R. (2025). The Kelly Review: Lessons from Heathrow's power outage . https://www.thebci.org/news/the-kellyreview-lessons-from-heathrow-s-poweroutage.html
Metadata
- Authors
- Witman, P., & Prior, J.
- Venue
- Information Systems Education Journal
- Published
- 2026
- Volume
- 24
- Issue
- 2
- Pages
- 16-26
- ISSN
- 1545-679X (ISSN-L)
- OpenAlex
- W7139977385
- Cited by
- 0
- References
- 8
- FWCI
- 0.00
- Type
- journal article
- Language
- en
- Open access
- closed
- Locations
- Information Systems Education Journal (publishedVersion)
- Topics
- Physical Sciences › Engineering › Civil and Structural Engineering › Infrastructure Resilience and Vulnerability Analysis
- Social Sciences › Business, Management and Accounting › Strategy and Management › Supply Chain Resilience and Risk Management
- Physical Sciences › Computer Science › Information Systems › Information and Cyber Security
- Keywords
- technology failure, system resilience, interconnected systems, risk, system fragility, information systems
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
The claim verdicts this report counts are experimental: their accuracy is not yet measured.
A language model drew the claims from the paper on 2026-10-07, under version 3 of the claim definition (model deepseek-v4.1-flash, prompt extract-v3).
A second model labelled each claim on 2026-10-07 (model jev-1.13-20260917, definition revision gold-guideline-v0.2).
Cited sources are checked with a language model’s help (gpt-6-sol).
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Our Interconnected, Resilient, Modern World ... Is Still Painfully and Remarkably Brittle: A Case Study of the Risks of Technology Failures. https://app.cochat.ai/papers/10.62273/psas2989
- The paper
- Witman, P., & Prior, J. (2026). Our Interconnected, Resilient, Modern World ... Is Still Painfully and Remarkably Brittle: A Case Study of the Risks of Technology Failures. Information Systems Education Journal. https://doi.org/10.62273/psas2989
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.