Tech News

Why So Many Outages Lately? What’s Known, and How to Prepare

Back to Blog & News
Person looking at a laptop showing an error screen during a service outage

Six big names went dark within a single week. According to WIRED, Microsoft, the FAA, Chase, United, the NSA and Apple all went down, and officials say none of the outages were cyberattacks. Plenty of people don’t believe that, and the Washington Post has now published a guide on how to protect yourself amid all these outages.

One caveat up front. We could read only the Post’s short summary, not the full article. So we can’t tell you which specific steps it recommends. What follows is what the sources do say, what they don’t, and a clearly labeled section of our own general advice.

Why these outages matter to everyday users and small businesses

An outage isn’t an abstract tech problem. It can mean a bank app that won’t load, a flight that doesn’t leave, or a work tool that’s suddenly unreachable. For a small business, a few hours without email, payments or cloud software can cost real money.

The Post’s summary frames the goal modestly. You can limit how much damage these failures inflict while waiting for professionals to fix the problem. That’s a realistic aim. You can’t prevent someone else’s system from failing, but you can decide how exposed you are when it does.

What we know about the outages

The facts here come mostly from one source, a WIRED podcast episode, and they’re thin on specifics. Here’s what is on the record:

  • WIRED says Microsoft, the FAA, Chase, United, the NSA and Apple all went down within one week.
  • WIRED says officials maintain none of the outages were cyberattacks, but that “the internet isn’t buying it.”
  • On the show, executive editor Brian Barrett said Secretary of State Marco Rubio says “we are not under attack.” Barrett added, “He’s right, but the internet is not convinced.”
  • Barrett described the order as Microsoft first, then the FAA and air traffic control, then Chase Bank, United Airlines, the NSA and Apple.
  • WIRED’s hosts say they’ll discuss what actually went wrong and why people’s first instinct is to blame hackers and AI. Senior business editor Sophie Kleeman said on the show she’s “one of those people.”

The episode page also lists related WIRED stories, including “The Microsoft Outage Is a Warning for the World,” “The Bank Outage May Have Nothing to Do With Your Bank” and “How to Tell If It’s a Cyberattack or Just an Outage.” We only have the headlines, so we won’t characterize what those pieces conclude.

What isn’t confirmed

Our notes don’t include the cause of any individual outage. They also don’t say how long each one lasted, how many people were affected, or whether the outages share a common cause. WIRED’s framing treats the “not a cyberattack” line as the officials’ position, and it notes that many people doubt it. We can’t resolve that from the material we have, so treat both claims as unsettled.

The notes also don’t give calendar dates for each outage. WIRED published its episode page on Nov. 19, 2026, and the Post published its guide on Nov. 20, 2026.

Background: how the week unfolded

The sequence as described by WIRED’s hosts is the only timeline we can responsibly offer. It starts with Microsoft, moves to the FAA and air traffic control, and then adds Chase, United, the NSA and Apple. WIRED’s episode page also lists a headline reading “FAA Grounds All US Flights Until Further Notice.” We haven’t seen that article’s text, so we can’t say what it reports beyond the headline.

What the episode really shows is how quickly a run of unrelated-looking failures turns into a single story in people’s heads. Whether they’re linked is the open question.

Our take: sensible prep, based on common practice, not the Post or WIRED

This section is Nexonic’s own analysis and general advice. It isn’t drawn from the Post or WIRED, whose specific recommendations we couldn’t review.

Your goal isn’t to outguess the cause. It’s to stay functional while someone else fixes it. A few habits make that easier:

  • Keep key information reachable offline. Important documents, contact numbers and account details are worth having somewhere that doesn’t depend on one cloud service or one app.
  • Have a second way in. If one bank, email provider or work tool is your only route to something important, think about what you’d do if it were down for a day.
  • Check official channels first. A company’s own status page or verified account is a better place to learn what’s happening than a rumor thread. If you don’t know where a provider’s status page lives, find it now, not mid-outage.
  • Be wary of messages that appear during an outage. Unexpected emails or texts offering a “fix” or asking you to log in again deserve suspicion. Go to the company’s site directly instead.
  • For businesses, write down a short fallback plan. Who do customers call? How do you take payments or share files if your main tool fails?

None of this is exotic, and it won’t make you immune. It will cut down on scrambling.

Quick answers

Were these outages cyberattacks?

According to WIRED, officials say none of them were. WIRED also says many people don’t believe that. We have no independent information to settle the question.

Which companies and agencies went down?

WIRED names Microsoft, the FAA, Chase, United, the NSA and Apple.

What does the Washington Post recommend?

Its summary says you can limit how much damage these failures inflict while waiting for professionals to fix the problem. We couldn’t read the full piece, so we can’t list its specific steps. It’s worth reading directly at washingtonpost.com.

How can I tell an outage from an attack?

WIRED has a story on exactly that question, titled “How to Tell If It’s a Cyberattack or Just an Outage.” We haven’t seen its contents, so check it on WIRED’s site.

What to watch next

Analysis, based only on what’s in our notes.

The most useful thing to watch is whether the affected organizations publish explanations. Right now, the public record in our notes is an official “not a cyberattack” position, a skeptical public and no named causes. Detailed post-incident write-ups would tell us whether these events were connected or merely clustered. Until then, it’s reasonable to prepare as if any single service could fail on any given day, and to avoid treating any theory about the cause as settled.

Image: Uschi_Du / Pixabay

Sources

This article was researched and drafted with AI assistance and reviewed against the linked sources by the Nexonic editorial team.

← More Tech News

Join the conversation

Ready to grow with a digital partner?

Tell us about your business. We will reply with honest advice and a clear plan.