MAIN ARTICLE
Five days of disruption, one atmosphere of anxiety
The sequence began on November 12, when a Microsoft outage disrupted widely used workplace services. On November 13 a telecommunications failure prompted a rare nationwide suspension of flight departures. After the weekend, users reported difficulties with financial transactions as JPMorgan Chase and other institutions dealt with the effects of a banking technology problem; United Airlines reported a separate operational outage. On November 17 Apple services were disrupted, and the National Security Agency acknowledged a temporary internal communications issue.
For a stranded passenger, the distinction between a faulty router and a software bug offers little comfort. For a customer unable to complete a payment, technical labels matter less than the uncertainty over when service will resume. The tight sequence made unrelated incidents look like a single national emergency, especially as rumors traveled faster than comprehensive official briefings.
What investigators know, and what they do not
The FAA said its early examination of abnormal traffic in the aviation communications network identified two possible locations: a radar site in Amarillo, Texas, and a communications facility in El Dorado, Arkansas. Contractor L3Harris had been deploying a new router at the Arkansas location.

















