IT & SOFTWARE / A SPECIAL COLLECTION
Behind an outage is a system of code, networks, people, permissions, and organizational choices. Follow the dependencies.
Select a stage to explore the questions it raises. This is a conceptual investigation aid, not a universal sequence.
Identify the change and its intended purpose. A change can expose an existing weakness.
Museum interpretation. Actual cases may follow a different sequence or include feedback loops.
CONTEXT / PHOTOGRAPHA backbone configuration change disrupted services and the internal tools needed to restore them.
CONTEXT / PHOTOGRAPHAttackers accessed sensitive records through an online dispute portal; a GAO review examined the response.
PHOTOGRAPHBoth inertial reference systems failed, and testing did not expose the guidance software’s limitations.
CONTEXT / PHOTOGRAPHA maintenance command removed more servers than intended, disrupting S3 subsystems.
CONTEXT / INTERFACE SCREENSHOTA production database incident led to data loss and a prolonged restoration effort.
CONTEXT / INTERFACE SCREENSHOTA WAF rule with an expensive regular expression caused CPU exhaustion across the network.
CONTEXT / INTERFACE SCREENSHOTA backbone configuration problem directed traffic toward an overloaded location.
SOURCE FIGUREA network configuration change caused an outage at key data centers.
CONTEXT / PHOTOGRAPHA data-center power event disrupted control-plane and analytics services.
CONTEXT / INTERFACE SCREENSHOTA maintenance script deleted customer sites, and restoration took much longer than expected.
PHOTOGRAPHA Channel File 291 update triggered Windows crashes on affected systems.
CONTEXT / PRODUCT IDENTITYA valid customer configuration triggered a previously undiscovered software bug.
CONTEXT / PHOTOGRAPHThe June 12 incident produced widespread errors across multiple products.
CONTEXT / PHOTOGRAPHA network disruption triggered database failover and inconsistent database state.
CONTEXT / PHOTOGRAPHSlack’s January 4 outage involved infrastructure capacity and connectivity constraints.
CONTEXT / PHOTOGRAPHThe migration caused serious operational disruption; regulators later found operational-resilience failings.
CONTEXT / PHOTOGRAPHA network maintenance change caused a major outage on July 8.
CONTEXT / PRODUCT IDENTITYA deployment left one server running old code that produced unintended trades.
CONTEXT / PHOTOGRAPHRansomware disrupted NHS organizations, including organizations that shut systems down as a precaution.
A redundant component is not independent if it shares power, configuration, software assumptions, or access controls. For each case, ask what the system could still do after its normal operating infrastructure became unavailable.