Outlook, the FAA, Banks, Apple: Was the U.S. Under Attack Last Week?
In six days, Microsoft 365, U.S. air traffic control, major banks, United Airlines and Apple all went down. It looked coordinated, but it wasn't. Here's what happened, why it matters to your business, and what to do about it.

Between November 12 and 17, it felt like everything was breaking. Email stopped working, flights were grounded, bank payments stalled and iPhones logged users out. Many people reasonably asked whether someone was attacking the system.
The evidence says no. The outages weren't connected, and none has been tied to a cyberattack. That doesn't mean there's nothing to learn.
What went down
Date: Nov. 12–14
Service: Microsoft 365 (Outlook, Teams, Copilot)
What happened: Global outage lasting more than a day
Stated cause: A months-old software bug, a traffic failover and reduced server capacity overloaded network gateways.
Date: Nov. 13
Service: FAA
What happened: Nationwide ground stop of more than four hours
Stated cause: A router flooded older air traffic control equipment with data
Date: Nov. 16
Service: JPMorgan Chase
What happened: Payment delays that spread to other banks and Zelle
Stated cause: A software bug in an on-premises hardware system, with no evidence of a cyberattack.
Date: Nov. 16
Service: United Airlines
What happened: About 90 minutes of system problems that delayed departures
Stated cause: Internal system problem; United said it wasn't a cyberattack
Date: Nov. 17
Service: Apple (iCloud, App Store, Apple Pay, Apple Music)
What happened: Sign-in failures and service outages
Stated cause: An internal update
Apple (iCloud, App Store, Apple Pay, Apple Music)
AWS, Workday and the NSA's internal network also had problems that week. Each was again blamed on internal causes such as maintenance or patching.
Are they connected?
Not directly. Each failure had its own cause. The Director of National Intelligence and the Secretary of State both said publicly that this was neither a cyberattack nor a coordinated effort by a nation state. Senator Mark Warner, the top Democrat on the Senate Intelligence Committee, also said he saw no sign of an attack or foreign interference.
There is a common thread, though, and it isn't a hacker:
- Faster patching. AI is helping researchers find software flaws faster than ever, and organizations are under pressure to fix them right away. Two PHP flaws disclosed in October were found with help from AI, and officials linked the NSA outage to patching for them. Rushed changes break things.
- Technical debt. New systems sit on top of decades-old infrastructure. The people who built that infrastructure are often no longer around.
- Concentration. Much of the internet runs on a small number of providers. When one of them fails, the impact spreads widely.
Should we be scared?
No, but you should be prepared. Outages like these will keep happening. Systems are getting more complex and connected, and experts expect more disruptions, not fewer.
Ask yourself this: when Outlook was down for a day, could your business still operate?
For most small and mid-sized businesses in Québec, the honest answer is "not really." Your email, files, phones, payments and line-of-business apps probably depend on a few cloud platforms. That's normal and usually the right choice. But it has to be planned for.
What JC Logic recommends
- Know your dependencies. List the services your business can't run without and what each one depends on.
- Have an alternate way to communicate. If email or Teams goes down, staff should know where to go: a phone tree, SMS or a secondary channel.
- Back up your cloud data. Microsoft keeps its service running, but protecting your data is your responsibility. Independent backups of Microsoft 365 and your critical systems are essential.
- Test your restores. A backup you've never restored is only an assumption.
- Control changes. Updates should be tested, scheduled and reversible. That's how we manage patching for our clients.
- Watch for scams. Major outages bring phishing that pretends to be "service restoration" or "account verification" messages. Treat any urgent login request with suspicion.
Want to know how your business would handle an outage like last week's? Contact JC Logic for a business continuity review.


