How a week of failures actually sequenced: Microsoft 365 on Nov. 12, the FAA halt on Nov. 13, JPMorgan’s bug on Nov. 16, NSANet on Nov. 17 — and the rushed-patch theory
What this story is about
Brussels Signal’s timeline of the outage week: it began November 12 when a Microsoft 365 failure knocked out Outlook and disrupted Teams and Copilot across more than 70 countries; on November 13 the FAA halted U.S. departures for more than four hours after its telecommunications network failed — and at the FAA’s request Eurocontrol suspended U.S.-bound departures from its member states overnight; JPMorgan Chase blamed a software bug for payment delays on November 16; the NSA reported a temporary degradation of its classified network a day later, during routine maintenance. The expert theory offered to Reuters is the engineering story: as AI tools surface vulnerabilities faster, vendors rush patches, and rushed patches break production. The administration’s line — separate technical issues, maintenance and upgrades, no malicious actor — has held for a week; the pattern underneath it is a change-management pattern.
Why it matters
Four failures, four owners, one pattern: change. The rushed-patch theory -- AI finds flaws faster than change windows can absorb -- is the week's most consequential engineering hypothesis, and it's testable in every org's own incident log.
About the source
via timeline relayA careful dated timeline from a Brussels outlet relaying wire reporting; the sequence checks against the week's individual reports.
Brussels Signal — Brussels-based news outlet
English-language European outlet with Polish police sourcing on the Krakow file (governor and prosecutor quotes, times). Solid on the facts it carries; single-outlet for this story's details.