In less than a week, Americans watched Microsoft 365 email go dark, every flight in the country get grounded, Chase banking transactions stall, United flights pile up, and Apple's iCloud and Apple Pay drop out. Online, many people asked the obvious question: is the United States under a coordinated cyberattack?
According to every affected company and to US officials, the answer is no. On Tuesday, Secretary of State Marco Rubio told reporters there was "zero evidence" linking the incidents: "We are not under systemic attack," he said, as reported by the BBC. Director of National Intelligence Jay Clayton also said the outages were not the product of a cyberattack, pointing to institutions patching and upgrading systems.
What actually broke
- Microsoft 365 (Outlook/Exchange Online): Microsoft's post-incident report describes three factors. A fix deployed to its networking gateway servers in July carried a dormant bug (lock contention inside an internal Windows process) that load tests missed because they ran on weaker hardware with fewer cores. About 15 hours before the outage, Teams traffic failed over to the gateway that also serves Exchange Online, and nearly 14% of that gateway's capacity was already out of service. Requests piled up, healthy servers inherited the load, and at the lowest point more than 80% of the servers were unresponsive.
- FAA nationwide ground stop: the US transport secretary said the issue was technical, tied to a copper wire upgrade and outdated equipment, and the FAA has paused installing new routers at its telecom sites after a faulty router was identified as the cause.
- JPMorgan Chase: the bank said a "software bug in on-premise hardware systems" slowed transactions on Monday, with "no evidence this is cyber-related." Other banks and Zelle payments were affected only when Chase was a party to the transaction.
- United Airlines: a technology failure delayed about 150 flights on Monday; the airline said a software issue was behind it.
- Apple: on Tuesday an "internal update" disrupted iCloud sign-in, Apple Pay, the App Store, AppleCare and retail store systems. Apple said it was not a cyberattack, and its status page showed all services restored by about 6 p.m. ET.
Why this matters for builders
The common thread is not an attacker but change. Updates, upgrades and failovers are some of the riskiest moments for any system, and tightly coupled infrastructure lets one bug cascade. Microsoft's case is a textbook example: a change that ran safely for three months only failed when extra load, reduced capacity and newer hardware lined up, and the failover meant to protect users spread the problem across the fleet.
- Load-test on hardware and traffic that match production, including your newest machines.
- Roll out changes in stages and keep capacity headroom so failovers don't overload the survivors.
- Design isolation so one region or component can fail without taking the rest down.
The security angle
Outage panic is a gift to scammers. Expect phishing that poses as "outage refunds," "verify your account" or service-restoration notices. Go directly to the official app or status page instead of clicking links in texts or emails.
Sources
- BBC: Rubio says US not 'under systemic attack' after series of tech outages
- Ars Technica: Three small failures combined to take down Microsoft 365
- Computerworld: Microsoft outage, a cascading failure
- CNBC: JPMorgan Chase says temporary software bug is affecting consumer banking
- CBS News: Apple restores services after internal update caused outages
- Fox News live updates: tech outages, FAA router pause


