Coffee Break: Tech Outages Everywhere and Hardly a Hacker to Thank/Blame
The past month has seen a series of well-publicized technical outages in the US and Europe that have attracted increasing levels of media attention and have more and more people speculating as to the causes.A Roundup of…

The past month has seen a series of well-publicized technical outages in the US and Europe that have attracted increasing levels of media attention and have more and more people speculating as to the causes.
A Roundup of Outages
Let’s start with a quick summary of some of the high-profile outages:
- Google Cloud: A power failure in its London zone on Oct. 20th took down services for Lloyds, HSBC, Royal Mail and Revolut after the backup generators never started. (The Register)
- Microsoft 365: Outlook, Exchange and Teams were down for about 24 hours on Nov. 12th–14th when a latent bug from July hit an overloaded network gateway. (The Guardian)
- 911: Users reported problems reaching 911 starting the night of Nov. 12th, and no official cause has been given. (Downdetector on X)
- FAA: A nationwide ground stop on Nov. 13th halted flights for nearly five hours after new L3Harris routers flooded the air traffic control network. (FAA)
- Workday: Payroll and HR systems went offline Nov. 13th–14th after a disaster-recovery test connected backup systems to production databases. (UC Today)
- Amazon Web Services: Sign-in failures hit 11 services in Northern Virginia for about three hours on Nov. 15th, and AWS has given no root cause. (Cyber Press)
- JPMorgan Chase: A software bug took down Chase’s online banking on Nov. 16th, and outage reports followed at Wells Fargo, Capital One and other banks. (CBS News)
- United Airlines: A 30-minute outage on Nov. 16th hit flight-planning and crew apps, affecting fewer than 150 flights. (CNN)
- Optimizely: Hackers used a flaw in its website-testing tool on Nov. 16th to plant card-skimming and crypto-stealing code on the websites of 178 organizations, including the BBC, CNN and Zoom. (Report URI)
- NSA: The agency’s classified internal network went offline on Nov. 17th after routine patching. (CBS News)
- Apple: iCloud, Apple Pay, Apple Music and the App Store went down on Nov. 17th, which Apple blamed on an internal update. (CNBC)
Trump Administration Denials Not Reassuring
Transportation Secretary Sean Duffy, previously notable for his expensive reality show boondoggle, came out on the 14th to reassure the public that the FAA outage “was [not] cyber at all. This was an FAA system that didn’t meet didn’t meet the moment” and to demand as much as $50 billion in additional funding from Congress, despite some trouble accounting for the $12.5 billion approved for the agency last year.
POTUS Trump was dismissive, telling reporters in Manila, “It’s life. When you’re big and powerful and have all the money, things like this happen. It’s fine.”
Director of National Intelligence Jay Clayton was more specific, telling Fox Business, “We do not see the indicia of a coordinated cyber attack. And we do not see the indicia of state-sponsored activity here” and tying the NSA outage to patching after a PHP vulnerability.
The PHP2Shell vulnerability has certainly been an issue for everyone trying to run websites for the past month, so it’s entirely possible that’s what caused the NSA issues.
Secretary of State Marco Rubio piled on, telling a press gaggle, “we have zero evidence whatsoever. We have no indication, no evidence, and no reason to believe at all that any of these incidents are related to each other.” And “zero evidence” of links to “nefarious actors, with cyber hackers, with criminals, with another nation state.”
But for some reason, even plausible explanations and likely truths don’t reassure when coming from the Trump administration. Maybe it’s just me.
Is AI Playing a Role?
Or maybe it’s because Secretary of Homeland Security Markwayne Mullin diverted questions about a possible role of artificial intelligence by reminding reporters, “We call it SI [superintelligence] around here, remember? SI.”
Q: Could this be AI related?
Mullin: We call it SI around here. https://t.co/D0HpFyLocH
— Acyn (@Acyn) November 13, 2026
Mullin also told Fox News, citing an unnamed tech executive (who, Mullin added, is definitely NOT Elon Musk):
“Breathe. The Homeland is secure. Our banking system is secure.”
“He said, I believe that it’s the SI. He said because these programs aren’t designed to work as fast as SI is. And so when they contribute or when they put in a program that’s able to write codes and it goes in and it self fixes itself.”
“As it starts to self fix itself, it’s like doing a change order on a house. When you change one thing in a house, everything else starts changing, that’s a ripple effect. And it causes the systems to be overran — that weren’t designed to run as fast as the SI technology is is today.”
It’s cute that Mullin, a former plumbing contractor and mixed martial arts fighter, attempted to translate the tech talk into home contractor terminology.
According to the Washington Sun, multiple Wall Street executives and the NSA told members of Congress that at least some of the outages came from attempts to fix vulnerabilities identified by AI, per three sources. A congressional official told the Sun, “They’re trying to push through a lot of patches all at once — more than the system was designed for.”
Virginia Democratic Senator Mark Warner, vice chair of the Senate Intelligence Committee, tweeted:
I understand why Americans are concerned about the widespread outages we’ve seen in recent days, affecting everything from banks and major technology companies to critical government systems. At this point, there is no indication that these incidents are the result of a cyberattack, foreign interference, or some coordinated effort.
What appears to be happening instead is a consequence of how quickly artificial intelligence is changing the cybersecurity landscape.
AI is making it possible to identify vulnerabilities across enormous numbers of systems at unprecedented speed, creating enormous pressure on companies and government agencies to patch those vulnerabilities immediately, often all at once, putting tremendous strain on systems that weren’t built to handle that pace of change.
While we still need to get to the bottom of these incidents, the evidence so far points toward legitimate efforts to secure our systems, not malicious activity.
Still, these disruptions should serve as a wake-up call. It feels like every day brings another reminder that AI is moving faster than our ability to manage its consequences.
This is exactly why I’ve been pushing for commonsense guardrails on AI and stronger cybersecurity protections.
That last bit makes the hair on the back of my neck stand up a bit because I trust Mark “RussiaGate” Warner to get the wrong end of the stick nearly every time on this kind of thing and to be reliably in thrall to Silicon Valley interests.
A bipartisan letter from Sens. Maria Cantwell (D-WA) and Mike Rounds (R-SD) to DNI Jay Clayton saying, “AI is rapidly increasing the ability to discover and exploit weaknesses in software and our defenses are not keeping pace” did nothing to reassure.
Gary Marcus was both more forthright and more credible on his Substack, noting that he predicted something like this in Politico for 2025 due to wider adoption of AI and pointing at three likely factors:
I see at least three key vectors in the rise of cybersecurity and infrastructure isses (all of which I have warned about here repeatedly):
First, vibe coding is a recipe for disaster. Some of what we are seeing is probably a function of vulnerable code written by people who lack sufficient experience to understand the messes they are getting themselves into. (As the always-wise security expert Dr. Heidy Khlaaf points out, the widespread adoption of vibe coding itself “is a symptom of poor industry practices we’ve witnessed over the last decade”).
Second, AI agents with unrestricted internet access can easily cause considerable harm. They are poor at following instructions, and, as the OpenAI/Hugging Face incident (and many others) revealed, they have no moral compass. Agents just do stuff, without regard to consequences. And while “most” of these incidents may be harmless, as OpenAI once said, some of them are not.
Third, because current AI really doesn’t have a larger picture about the consequences of what it can do, bad actors can readily exploit it. My guess is that both state actors and criminal syndicates are exploring the limits of what can be done as quickly as possible, and at least for now attackers may have an advantage over defenders. (How much is malice and how much is incompetence, we don’t really know.)
But others deny that vibe coding is to blame, with Liz Fong-Jones of Honeycomb telling Axios, “Nothing to do with writing code, nothing to do with shipping code with AI.” The same article includes Downdetector pointing out that their “data also show that while the seven days through Monday represent the highest number of weekly outages in the last 12 months, the pattern over longer periods such as 30 days is far from unprecedented.”
Being Pattern Identification Machines, We Speculate
As Bruce Schneier said in that same Axios piece, “Humans see patterns in everything, regardless of whether they’re there, and generally interpret coincidences as conspiracies. It’s human psychology.”
But nonetheless, when this old number came up on my music shuffle today it struck a chord:
Have you ever had a feeling
the world’s about to end?
Have your brains kept on reeling?
You seem without a friend.Have you had those mean old blues too,
but didn’t understand?
Everyone around refused to
lend you a helping hand.
And when malignant idiots like Benny Johnson and Alex Jones are racking up hundreds of thousands of views with tweets proclaiming the US is under a massive cyber attack, it’s definitely time to be skeptical.
On the other hand, I was skeptical that the Israeli government was aware that the October 7 attack was coming and time has told a different story on that one.
Plausible If Not Reassuring Explanations
I did find a couple more plausible explanations for what’s going on.
This from Ballistic Ventures venture partner and former Google Cloud CISO Phil Venables:
I will preface this with the humility that I might be totally wrong and all these recent events really are some type of coordinated cyber-attack, although I would say if it is it’s all rather pointless and unfocused. But, I doubt this is really an “attack” in any way. However, just because you’re paranoid doesn’t mean that they are not really out to get you.
No, the most likely explanation of what is going on is:
1. Fragility of increasingly large-scale and under-maintained, complex and brittle infrastructure.
2. Our increased digital dependence such that when these events happen we notice them more.
3. A few independent incidents coincidentally occurring together which causes the media and the rest of us to be more attuned to other outages that would normally go unreported, that we now bucket into some mythologized growing category.
4. Lack of resilience in the presence of failures so that their impact is longer-lasting and more impactful.
Let’s pick on a few of these. First, independent occurrences of events that seem to be connected. One example I remember was a day many years ago when the New York Stock Exchange was down for the day (software error), a US airline was ground stopped (hardware event), and on the same day a bunch of major bank CISOs, including me, were going into the White House Situation Room for a totally unrelated threat briefing (we had to hide from the White House Press Corp in case that was further coincidental evidence of “attack on America”.) After this I looked at what else happened that was unreported that day and there were dozens of other unrelated outages at hospitals, power plants, and so on. Perhaps even more happened that one day than has been happening this past week. It just went unreported.
Second, do we have any base rate data to understand if what of anything that has happened is actually so unusual or surprising? [Note: something being unsurprising doesn’t mean it’s acceptable, in fact we want such events to become ever more surprising of course].
His whole piece is worth a look as he goes into several of the specific incidents in a little detail.
Author Nicole Perlroth had a reasonable take:
I haven’t lived here in awhile, but I see no other way to answer the hundreds of texts/DMs asking me if the world is, indeed, ending.
In the span of six days, we’ve experienced;
11/12 — Microsoft outage
11/13 — Nationwide FAA ground stop
11/16 — Major US banking disruptions
11/17 — NSA’s classified internal network goes downWe need far more analysis of why so much is breaking at once. I don’t want to get out over my skis here, and what I am hearing does not contradict the messaging that most of this is the result of screwy updates.
But stepping back, the dots are starting to form a collective picture. We are seeing:
• An explosion in severe and critical vulnerabilities, with AI accelerating discovery to 3X the number of vulnerabilities discovered in the same period last year. This is collectively being referred to as “vulnageddon” or “the vulnpocalypse.”
• Mean time to exploit those vulnerabilities has collapsed to NEGATIVE SEVEN DAYS. AI allows attackers to find/exploit vulns far faster than software makers have time to fix them.
• Powerful AI-enabled offensive tools like ARTEX have been thrown into the hands of every third tier nation state, cybercriminal and digital arsonist, which logically creates havoc.
• This creates enormous pressure to compress patching windows and accelerate software updates, increasing the likelihood these fixes break things in unexpected, cascading ways.
• Pressure to just “AI everything” means we are rolling out automated AI tooling on top of brittle infrastructure that can’t support it.
My generation grew up in an extraordinary period of technological stability. We worked our way up the software stack, abstracting away layer after layer, until we lost a fundamental understanding of how the underlying systems actually work.
We were told to “move fast and break things.” VCS told us to celebrate the idea that “software would eat the world.” Now we’re telling ourselves we can simply “roll out AI” across everything, as though nothing underneath will buckle.
We never stopped to ask: SHOULD WE?
Should we be digitizing every last nook and cranny of our companies, infrastructure, healthcare, homes, cars, bodies, lives? Especially when the complexity, interdependence, and fragility we were introducing overwhelmed our ability to understand/secure/maintain the systems we built?
Nobody every asked: What if, in the name of progress, we were creating the ripest attack surface in human history?
We are now entirely dependent on software systems that almost nobody understands end to end, that increasingly few people can repair, and that attackers can now probe at machine speed. We are hearing that incident response firms, the 911 for breach victims, are backlogged six months. Even those paid on retainer lack the bandwidth to triage every incident. The cavalry is disappearing.
We are entering a period of unprecedented technological instability.
“Software Beirut” is an incredibly apt analogy. We are in for a period of cascading failures, whether triggered by attackers, bad updates, or our own accumulated complexity.
This, I’m sorry to say, is just the opening chapter.
— Nicole Perlroth (@nicoleperlroth) November 17, 2026
Key quotes:
My generation grew up in an extraordinary period of technological stability. We worked our way up the software stack, abstracting away layer after layer, until we lost a fundamental understanding of how the underlying systems actually work.
We were told to “move fast and break things.” VCS told us to celebrate the idea that “software would eat the world.” Now we’re telling ourselves we can simply “roll out AI” across everything, as though nothing underneath will buckle.
We never stopped to ask: SHOULD WE?
Should we be digitizing every last nook and cranny of our companies, infrastructure, healthcare, homes, cars, bodies, lives? Especially when the complexity, interdependence, and fragility we were introducing overwhelmed our ability to understand/secure/maintain the systems we built?
Nobody every asked: What if, in the name of progress, we were creating the ripest attack surface in human history?
We are now entirely dependent on software systems that almost nobody understands end to end, that increasingly few people can repair, and that attackers can now probe at machine speed. We are hearing that incident response firms, the 911 for breach victims, are backlogged six months. Even those paid on retainer lack the bandwidth to triage every incident. The cavalry is disappearing.
We are entering a period of unprecedented technological instability.
“Software Beirut” is an incredibly apt analogy. We are in for a period of cascading failures, whether triggered by attackers, bad updates, or our own accumulated complexity.
This, I’m sorry to say, is just the opening chapter.
Time will tell what’s really going on here, but I’m afraid Perlroth is right and we’re in a new era of technological instability.
Mo Bittar summed up the situation well:
For 50 years, the rest of the world has been telling America to go eff itself. And this week, we finally did it. In 6 days, we took down our own email, our airports, our biggest bank, and our spy agency.
And it turns out nobody even laid a finger on us. I know, I know you want this to be some great conspiracy theory, but I’m going to show you exactly what happened.
Microsoft broke because of a fix. The FAA broke because of an upgrade. Chase broke because of a software release. The NSA broke because of a patch. And then Apple broke because of an update. It wasn’t an attack. We basically shot ourselves cleaning our own gun five times in 6 days.
Daario, CEO of Anthropic, spent a lot of time earlier this year, if you recall, warning about these kind of things. We kind of just ridiculed him. But somebody else from Anthropic warned us. His name is Jason Clinton. no relation, but he is the first Clinton in history to warn people before something blew. He is the deputy head of security at Anthropic, the company that makes Claude. And on August 20th, he posted that the vulnerability tsunami is coming in just a few months and there won’t be enough time to patch critical infrastructure.
Hang tough, y’all.
Figures reflect the source report and its stated period. This article is for information and is not investment advice.



