Bank payments slowed, flights stopped and email went dark in a series of disruptions between November 11 and 16. The public evidence points to separate failures. A New Hampshire hospital confirmed a cyber incident during the same period, and no public evidence links it to the nationwide disruptions.
Nov. 11 onward — New Hampshire hospital. An earlier server outage was already disrupting elective care at Monadnock Community Hospital and its clinics on Wednesday. The hospital confirmed Monday that it had experienced a cyber incident. Specialists were still investigating what data might have been affected and working to restore systems.
Nov. 12–14 — Microsoft 365. Outlook, Exchange Online, Teams and Copilot experienced widespread trouble. Microsoft’s preliminary account traced the outage to a software defect that surfaced when traffic shifted while some capacity was already unavailable. The main incident lasted just under 24 hours by Microsoft’s accounting, with monitoring continuing into Saturday. Microsoft reported no indication of malicious activity.
Nov. 13 — FAA ground stop. The agency says its communications network became unstable at 17 of 22 en route centers. The nationwide stop began around 3:30 p.m. Eastern and lifted at 8:15 p.m. The FAA said older equipment was overwhelmed and the network later stabilized. It reported no indication of a cyberattack and was still investigating the underlying failure. It counted roughly 12,462 cancellations Friday, including some unrelated to the stop. Read PartialMedia’s FAA coverage.
Nov. 15 — Amazon Web Services. AWS reported connectivity, sign-in and sign-up problems in its Northern Virginia region between 3:05 and 6:10 a.m. Pacific. AWS marked the regional incident resolved.
Nov. 16 — Chase and bank payments. JPMorgan told Reuters that a software bug slowed processing and that other banks might see delays when they were on the other end of a Chase transaction. U.S. Bank said its systems were unaffected directly. Zelle’s operator told the Associated Press that its network was operating. Customer reports show where people encountered trouble, but they do not identify which bank’s system failed. Chase said the problem was unrelated to a cyberattack. The available reporting did not establish that every delayed transfer had cleared.
Nov. 16 — United Airlines. United said it resolved a system outage that delayed its departures for more than 90 minutes, according to AP and Axios. The airline said it had no indication of a cybersecurity issue. Monday’s stoppage involved United’s operations. Friday’s nationwide ground stop was ordered by the FAA.
Editorial Opinion
The timing deserves scrutiny. To establish a coordinated attack, investigators would need evidence connecting the incidents, such as corroborated signs of unauthorized activity across operators or a documented common cause. The outages already show how quickly a failure at one provider can reach people who never deal with that provider directly. Operators should tell the public when trouble started, what still worked and when customers could expect normal service.
References
Monadnock Community Hospital. (2026, November 16). Server outage update.
Federal Aviation Administration. (2026, November 15). Nationwide ground stop: Questions and answers.
Reuters. (2026, November 16). JPMorgan says software bug slows its transactions. MarketScreener.
Axios. (2026, November 16). United Airlines resolves widespread system outage that delayed flights.
Have a factual correction or website problem? Contact PartialMedia with the article link, disputed passage and supporting source.
Discussion
Comments load automatically through Disqus. This connects to Disqus and its partners, which may use cookies and process your IP address and browser information. Disqus privacy policy.