← All fact checksMorning run · November 17, 2026 · #1 by reach

Were the Microsoft outage, the flight ground stop and the bank outages connected?

Were the 16 November online outages at Chase, Bank of America, Wells Fargo and other US banks connected to last week's Microsoft outage and FAA ground stop, as part of a coordinated attack?

Misleading

All three outages happened, but officials and the companies say they were separate technical failures.

The three outages were real and happened on consecutive days in November 2026, but they were not linked. Microsoft blamed a software and network-capacity defect, the FAA blamed a communications failure at air traffic control, and the bank outages were traced to a JPMorgan Chase software bug. Officials and the companies denied any connection or cyberattack.

Claims

✓ 3 true · ✕ 1 false

These three outages are connected, or share a single hidden or coordinated cause.12346

✕ FalseCentral claimModerate confidence

This is the claim the post is built around, and it is the one the evidence contradicts. Each outage has a stated technical cause, and the causes are different in kind: Microsoft described a software and network-capacity defect, the FAA ground stop followed a communications problem at air route traffic control centres that The Seattle Times linked to attempted upgrades and new cabling, and the bank outages were traced to a JPMorgan Chase software bug. Two independent lines of denial point the same way. Homeland Security Secretary Markwayne Mullin said there was no connection between the aviation ground stop and the Microsoft outage, and Microsoft said it had no indication of a link. Chase said its problems were not a cyberattack. Analysts quoted by USA TODAY described the incidents as separate failures of highly concentrated systems rather than one event. The confidence is moderate rather than high because the denials are statements about what officials and companies know so far, not a technical audit of every system involved.

Still open: No public technical audit has been released that examines all three systems together; the finding rests on the companies' and officials' statements plus reporting on each cause.

Microsoft went down on Thursday.145

✓ TrueHigh confidence

This part of the post checks out, which is why the whole thing reads as credible. Microsoft's global Microsoft 365, Outlook and Teams outage began around midday Eastern time on Thursday 12 November 2026 and ran into the weekend. Microsoft confirmed it was a technical issue, and said it was not cyber activity and not an AI problem. Two sources describe the same timeline: USA TODAY covers the run of outages across the week, and Hindustan Times reports the outage and the official response to speculation about it. The sources agree on the day, the affected services and the stated cause, which is why we rate this HIGH. What a reader should take from it is narrow: the outage is real and happened on the day named. That tells you nothing about whether it was connected to anything else.

All our flights went down on Friday.356

✓ Likely trueHigh confidence

The substance is right and the wording is a slight overstatement. On Friday 13 November 2026 the FAA ordered a rare nationwide ground stop of departing flights after a communications problem hit air route traffic control centres. Aircraft already in the air continued to land, so 'all our flights went down' overstates a halt on departures. The reporting is consistent across sources: CNN's live coverage describes the ground stop and the rising cancellations with no timeline for resolution, and The Seattle Times attributes it to attempted upgrades and new cabling. The reason this is LIKELY_TRUE rather than TRUE is that framing detail, not doubt about whether the ground stop happened. A nationwide halt of departures is exactly the kind of event that would be reported everywhere, and it was.

Still open: The post says 'all our flights', which reads as every flight everywhere; the order covered departures in the United States, and airborne aircraft kept landing.

The banks are down today.27

✓ TrueHigh confidence

This also holds. On Monday 16 November 2026, Chase, Bank of America, Wells Fargo and other institutions reported online banking and transaction outages. Reporting traced the disruption to a software bug at JPMorgan Chase that rippled through payment networks. Chase said the cause was not a cyberattack. ABC7's live coverage and the Daily Post both describe the same day and the same set of affected institutions, and both note the absence of evidence for a cyberattack at the time of reporting. The two accounts come from different publishers but rest on the same underlying company statements, so they are closer to one confirmation than two independent ones. Even so, the facts are not in dispute: the outages happened, and they happened on the day the post calls 'today'.

A text-only post: there was no media to test.

What was posted

X

A short text-only post on X by Michael Knowles noting that Microsoft went down on Thursday, US flights were grounded on Friday and banks went down on the day of posting. It does not state a cause or offer evidence; the closing phrase invites the reader to infer that the timing is too neat to be coincidence.

“So Microsoft went down on Thursday. All our flights went down on Friday. And now the banks are down today. But these events are in no way connected. Hmm.”

Posted on X by the account @michaeljknowles on the day the US bank outages were reported. The post is text only, with no attached image, video or link.

Who posted it

X

Account check

Looks like a genuine account80%
Likelihood of automation5%

Estimates from public signals — account age, posting pattern, audience — not a judgement of the person behind the account, and separate from whether this post is true.

What stood out

  • @michaeljknowles is the long-established handle of Michael J. Knowles, conservative commentator and host of The Michael Knowles Show (Daily Wire) — a real, publicly identifiable person, not a persona.
  • Handle is corroborated as official: it is listed as his X account in his own show notes/podcast pages, and press outlets (e.g., NY Post, April 2026) quote and embed tweets from @michaeljknowles.
  • Account is old: documented rejections/suspensions of this handle by Twitter in Nov 2018 and March 2023 show continuity for 8+ years.
  • Sparse record here (null bio/followers/creation date, isplatformverified=false) looks like incomplete data capture rather than a sign of a fake or throwaway account; no evidence of impersonation or of a competing 'real' handle.
  • No indication of automated or coordinated inauthentic behaviour; the account's activity is consistent with a professional media figure with staff-produced daily content.
  • Reliability caveat: he is a partisan opinion host with a mixed accuracy record — PolitiFact has rated statements of his False (e.g., 2023 Nassau County voting-machine claim), and his CPAC 'transgenderism must be eradicated' remarks generated widespread dispute and legal threats.
  • Verification/follower metadata should be re-collected before using this profile as a high-confidence source.
Signals (7)+
Identity confirmed
Yes
Known affiliation
The Daily Wire; PragerU 'The Book Club'; syndicated radio
Posting cadence
Not supplied (no recent posts captured)
Follower ratio
Not supplied
Notable news coverage
Wikipedia entry; NY Post (Artemis II 'touch grass', Apr 2026); CPAC 2023 coverage; CensorTrack suspension records
Fact check history
PolitiFact personality page; rated False on 2023 Nassau County voter-machine claim; disputed 'eradication' quote coverage
Impersonation evidence
None found

Account checked November 17, 2026, 02:45 UTC

Sources

8 sources reviewed

Further reading

  • 1USA TODAY Best single overview of the five-day run of outages and the analysts' explanation of why they were unrelated.
  • 3CNN Documents the FAA ground stop and the official statement that it was not connected to the Microsoft outage.
  • 6The Seattle Times Explains what actually went wrong at the FAA and Microsoft, which is the detail the post leaves out.

The full story

Nothing in the post is invented. That is what makes it work.

The week of 12 November 2026 really did produce three disruptions in a row. Microsoft's Microsoft 365, Outlook and Teams went down around midday Eastern time on Thursday 12 November and stayed degraded into the weekend. The company said the cause was a software and network-capacity defect, and that it had no indication of cyber activity. On Friday 13 November the FAA ordered a nationwide ground stop of departing flights after a communications problem at air route traffic control centres. Aircraft already airborne kept landing. According to The Seattle Times, both meltdowns traced back to attempted upgrades that went wrong: new cabling in the FAA's case, a planned increase in computing capacity in Microsoft's.

On Monday 16 November, Chase, Bank of America, Wells Fargo and others reported online and transaction outages, traced to a software bug at JPMorgan Chase. Chase said it was not a cyberattack.

What the post does is line the three up and let the sequence do the arguing. Officials had already addressed that inference directly. Homeland Security Secretary Markwayne Mullin said there was no connection between the aviation ground stop and the Microsoft outage, noting that many people were making that jump. Analysts quoted by USA TODAY described the incidents as unrelated failures of highly concentrated systems rather than a coordinated event.

That concentration is the real story behind the plausibility. When a handful of companies run email, air traffic control and payments, three failures in five days can feel like one system failing.

Kernel of truth

All three outages happened on the days named, which is why the post's insinuation feels plausible to readers who lived through them.

Timeline

  1. November 12, 2026

    Microsoft's global Microsoft 365, Outlook and Teams outage begins around midday Eastern time, later attributed to a software and network-capacity defect. 1USA TODAY

  2. November 13, 2026

    The FAA orders a nationwide ground stop of departing flights after a communications problem at air route traffic control centres. 3CNN

  3. November 16, 2026

    Chase, Bank of America, Wells Fargo and others report online and transaction outages, traced to a JPMorgan Chase software bug. 2ABC7 Chicago

  4. November 16, 2026

    Michael Knowles posts on X that the three events are 'in no way connected', inviting readers to infer otherwise. 8X

How it was framed

Misleading contentFalse connection

Each individual fact in the post is accurate, but the arrangement of three true events into a sequence is used to frame an unrelated set of technical failures as suspicious. The post presents no mechanism and no evidence, relying on the reader to draw the connection from the timing alone.

  • Missing context. The post lists three outages by day and omits the stated cause of each: a Microsoft software defect, an FAA communications failure and a JPMorgan Chase software bug.
  • “Visual proof”. The three-part list ('Thursday... Friday... today') is structured as a pattern the reader can see for themselves, standing in for evidence of a link.
  • Emotional language. 'All our flights went down' and 'the banks are down' present the events in the most sweeping terms available.

Posted on X by the account @michaeljknowles on 16 November 2026, the day the US bank outages were reported. The post is text only.

Bias

NoneSlightModerateStrong

Leans conspiratorial / anti-establishment. The post lists three genuine outages and uses sarcastic phrasing ('But these events are in no way connected. Hmm.') to invite the conclusion that a hidden or coordinated cause is being covered up, without offering any evidence beyond the coincidental timing.

Bias describes how the post frames its message — the slant of the language, selection and emphasis — and is judged separately from whether the claim is true. A true claim can still be framed with a strong slant.

How we checked

36 s
  1. 1

    Searched for coverage of the Microsoft outage, the FAA ground stop and the bank outages, and for the connection between them.

  2. 2

    Searched for the post's own wording to see whether anyone had already fact-checked it; no existing fact-check was found.

  3. 3

    Compared what officials and the companies said about each cause against the implication in the post.

✓ Claim checked– Media not applicable✓ Sources checked

Why 72% confidence

Moderate

We rated the headline MODERATE. The three individual events are documented by multiple outlets and rate HIGH on their own. The central connection claim rests on statements from officials and the companies rather than a published technical audit of all three systems, so it rates MODERATE rather than HIGH.

Limits. We could not open the underlying pages directly in this check and relied on the search results and source excerpts recorded above. No public technical audit covering all three incidents together was available, and no fact-check of this specific post existed.

What we don’t know

  • Whether Microsoft, the FAA and JPMorgan Chase have published full technical post-mortems of each failure.
  • Who first circulated the idea that the three outages were linked, and whether the post picked it up from elsewhere.
  • Whether any later investigation changes the stated cause of any of the three incidents.

Spot it yourself

Spot the fake

Looks suspicious, isn’t proof

  • The sarcastic closing 'But these events are in no way connected. Hmm.' A mocking tone is a reason to look closely, but it is not evidence that the facts are wrong.
  • The sweeping phrasing 'all our flights went down'. Overstatement is a warning sign, but in this case a nationwide ground stop really did happen.
  • The source being a partisan commentator. Who posts something tells you nothing on its own about whether the facts in it hold.
  • The absence of any link or citation. That is a gap, but plenty of accurate posts are short and uncited.

The actual evidence

  • Official statements: Homeland Security Secretary Markwayne Mullin said the aviation ground stop and the Microsoft outage were not connected, and Microsoft said it had no indication of a link.
  • The stated causes differ in kind and were reported separately: a Microsoft capacity defect, FAA cabling and router upgrades, and a JPMorgan Chase software bug.
  • Chase said its outage was not a cyberattack, which cuts against the implication of a hostile event.
  • Analysts quoted by USA TODAY described the incidents as unrelated failures of concentrated systems, not one coordinated event.
  1. 1

    Check whether the pattern survives the causes

    For each event in a list like this, ask what the operator said caused it. If the causes are three unrelated technical faults, the sequence is coincidence plus concentration, not conspiracy.

  2. 2

    Look for official statements made about the link, not just the events

    Officials often address the suspected connection directly, as the Homeland Security Secretary did here. Search for the connection question, not just each outage.

  3. 3

    Test the scale words

    'All our flights' and 'the banks are down' invite you to imagine total failure. Check what was actually halted (departures, not airborne flights) and which banks and services were affected.

  4. 4

    Notice when a post argues by sequence alone

    If a claim rests entirely on 'this, then this, then this', the author has given you a pattern to feel, not a mechanism to examine. Ask what evidence would be needed to show a link, and whether any is offered.

  5. 5

    Separate the true parts from the conclusion

    List the checkable statements. If they all hold, the misinformation is in the conclusion drawn from them, and that is where your scrutiny belongs.

Takeaway

A post can be factually correct line by line and still mislead, if the arrangement of true facts points at a conclusion the evidence does not support. Check the conclusion separately from the facts.

Questions people ask

Were the Microsoft outage, the flight ground stop and the bank outages connected?+

No. Officials and the companies involved said the incidents had separate technical causes: a Microsoft software and network-capacity defect, an FAA communications failure at air traffic control, and a JPMorgan Chase software bug. Homeland Security Secretary Markwayne Mullin said there was no connection, and no evidence of coordinated action has emerged.

Did all US flights really stop on Friday?+

Not quite. On Friday 13 November 2026 the FAA ordered a nationwide ground stop of departing flights after a communications problem at air route traffic control centres. Aircraft already in the air continued to land, so departures were halted but the skies were not emptied. Cancellations climbed as the day went on.

Was the bank outage a cyberattack?+

Chase said its problems were not a cyberattack. Reporting traced the 16 November outages at Chase, Bank of America, Wells Fargo and others to a software bug at JPMorgan Chase that affected payment networks. At the time of reporting there was no evidence of a cyberattack.

Why does the post feel convincing if it is misleading?+

Every event it lists really happened, on the days it names. When a few companies run email, air traffic control and payments, three failures in five days can look like one system breaking. The post supplies the pattern and leaves out the causes, so the conclusion feels obvious without being supported.

What kind of misinformation is this?+

It is misleading content built on a false connection. Nothing in the post is fabricated; the problem is the framing. Three true events are lined up to imply a hidden link, with no mechanism or evidence offered, and with the official explanations left out.

Go deeper

Ground stop
An order halting departures from airports, usually issued by the FAA when a problem means the air traffic system cannot safely handle more aircraft.
False connection
When a headline, caption or post implies a link that the underlying content or evidence does not support.
Misleading content
The use of genuine information in a way that frames a person or event unfairly or points to a conclusion the facts do not support.
Post hoc reasoning
Assuming that because one event followed another, the first caused the second.
For educators+
Misleading content vs fabricated content: true facts arranged to support a false conclusionFalse connection and the post hoc pattern: assuming that things happening in sequence share a causeSystems concentration: why unrelated failures at a few large providers can feel like one eventAppealing to suspicion: how a rhetorical question can carry a claim without asserting it
  • The post contains three true statements and no explicit claim of a link. Where exactly does the misleading part live, and how would you point to it in a classroom?
  • If you were shown three outages in five days with no other information, what would you need to know before deciding whether they were connected?
  • Why might a sarcastic question ('in no way connected. Hmm.') be more persuasive, and harder to correct, than a direct false statement?

About this check

Platform
X
Posted by
@michaeljknowles
Posted
November 16, 2026
Age when checked
Under 24 hours old when checked
Where it spread
United States
Audience
US audience
Language
EN
Status
● Post is live
Verified
November 17, 2026, 02:46 UTC
Published
November 17, 2026, 02:46 UTC

Reach. Knowles post 13.4K likes; Krassenstein 5.7K likes (syndication, checked 17 Nov). Mediaite says influencers on both sides are speculating; Fox, Daily Beast, Fast Company and IBTimes covered the outages; Bluesky trending 'Outages reported at US banks'

This verdict was generated with AI from the sources shown. AI can make mistakes — check the sources before relying on it.

Check anything yourself, in seconds.

Share any social post or video to What the Fact and get the verdict, the confidence, and the receipts.