Outlook, FAA, and Chase Outages: Cyberattack or Software Bugs?

By Beau Johnson··9 min read

Quick answer

Based on what officials have said, not this week. Microsoft and Chase blamed software bugs, the FAA traced its ground stop to a router job in Arkansas and a radar site in Texas, and United called it a technology issue. I also cover the real attacks, the scams, and a 9-step outage kit.

This week Outlook broke in 74 countries, the FAA stopped every departure in America for 4 hours and 21 minutes, and Chase and United both broke on Monday. In this video I go through what officials say caused each one, the October attacks that are real, the scams that follow a big outage, and a 9-step kit for the day it's your bank. It's for anyone who saw the cyber war posts and wants the plain version. I read every official statement so you don't have to.

What I cover in this video

  • 0:00 Four outages, one question, and the day by day timeline
  • 0:46 The FAA ground stop, the Chase and United outages, and the Downdetector numbers
  • 1:32 Black October: PHP2Shell, Storm-0940, and AI hacking agents
  • 3:03 What Microsoft's preliminary report says
  • 3:48 The FAA's router job in Arkansas and the radar site in Texas
  • 5:18 Why a few choke points are the real problem
  • 6:04 How a fake text lands in your bank's real thread
  • 6:49 The outage kit, step by step

What broke and what they found

I give each outage a tag based on what the company or agency has said so far.

Microsoft, Thursday. Around midday Eastern, Outlook, Teams, and the rest of Microsoft 365 started failing. Within about an hour, 74 countries were reporting problems and Downdetector logged nearly 130,000 Outlook reports. Microsoft said there was no indication this was malicious or cyber activity. Its preliminary report says a software bug had been sitting in its gateway servers since July. About 14% of those servers were already offline for an unrelated issue, and Teams traffic got moved onto the same gateway that runs Outlook's email. That woke the bug up, and at the worst point more than 80% of the servers stopped responding. Tag: not an attack.

FAA, Friday. At 3:54 p.m. Eastern the FAA stopped every departure in the country until 8:15 p.m. Thousands of flights were cancelled, the White House Situation Room got pulled in, and the FBI went into FAA facilities. The FAA says its network got flooded with 1,000 connection attempts every 4 to 5 seconds. Its first look points to two places: a site in El Dorado, Arkansas, where the contractor L3Harris was putting in a new router as part of a switch from old copper wires to fiber, and a radar site in Amarillo, Texas. FAA chief Bedford said, "I think we've all concluded that it's not a cyber issue," and Transportation Secretary Duffy said it wasn't a foreign actor. Whether it was an install mistake or a bad router is still being investigated. Tag: not an attack, cause still open.

Chase and United, Monday. Chase payments got stuck, and by 1:50 p.m. Eastern Downdetector had over 4,600 Chase reports, with Bank of America, U.S. Bank, and Wells Fargo on there too. Chase blamed a software bug in on-premise hardware, said it was not cyber related, and had transactions posting normally by about 6:30 p.m. Eastern. The other three banks haven't given a cause. United called its outage a technology issue, said there's no indication it was cyber, and fixed it by early evening. Tag: Chase, not an attack. The rest, no cause given.

To be fair, no evidence of an attack isn't proof, and companies don't always tell us everything. But the ones that explained themselves all landed on boring stuff. A bug, a router, a bug.

Black October: the attacks that are real

The fear isn't crazy, because October was rough. People called it Black October. It was never one coordinated attack, but the stuff in it is real.

  • PHP2Shell. Two critical bugs in PHP let an attacker run code on a server without logging in. On October 26th, CISA put them on its list of bugs being actively exploited. PHP runs about 68% of websites where the server language is known. Some posts turn that into most of the internet being vulnerable, but sites that patch those two bugs are fine.
  • AI working for attackers. Microsoft says a China-aligned group it calls Storm-0940 used ARTEX, an open-source AI hacking tool, against hundreds of organizations. In multiple cases it got admin-level access in under 3 hours. Most attempts failed. CrowdStrike says a China-linked group it tracks ran its AI hacking agents mainly on DeepSeek models.
  • French supermarkets. Hackers cranked up the freezers at hundreds of them overnight.

None of that has been tied to this week's outages.

The real problem is a few choke points

Here's how I read this week. Everything runs through way fewer pieces than you'd think. A flood of data, likely from a router job in Arkansas, stopped every departure in the country. One Microsoft gateway had a bad day and people in 74 countries couldn't get into their email. And Chase says other banks only slowed down when a payment touched Chase. One bank trips, and anybody sending money to it waits too.

Now add AI. Tools like ARTEX make attackers faster, and my guess is they'll go looking for choke points like these. A bug and an attack hit you the same way. The card gets declined or the flight sits at the gate. So get ready for both.

Scams and the outage kit

The scams that follow an outage

Scammers love an outage more than anybody. In 2018, when the UK bank TSB had its big meltdown, fraud police got over 300 reports of fake TSB emails, texts, and calls in a month. A fake text can also land right inside your bank's real text thread, because your phone groups messages by sender name and scammers can fake that name. In 2023, Australia's consumer watchdog described a man who lost 38,000 Australian dollars to a text that showed up in the same thread as his bank's real messages.

So never use a link or a phone number from a message. Open the app yourself. Never give anyone a verification code. Forward scam texts to 7726 and file at ReportFraud.ftc.gov.

The 9-step kit

  1. Some cash at home. Ready.gov says small bills, because cards and ATMs may not work.
  2. A second way to pay, like a card from a different bank. That one is my own rule.
  3. Screenshots of your boarding pass and confirmation numbers. Your photos work when the app doesn't. If the airline cancels and you don't take the rebooking or a voucher, DOT rules say you get your money back automatically.
  4. Check the company's own app or status page, not viral posts.
  5. If a transfer fails, check your history before you send it again so you don't pay somebody twice.
  6. Lock down your main email first, because it resets everything else. Use a passkey or a security key, and text codes only if nothing stronger is offered.
  7. Turn on bank and card alerts.
  8. Freeze your credit at all three bureaus. It's free and it doesn't hurt your score.
  9. Turn on auto-updates everywhere.

If you build with AI, also rotate your API keys and set billing caps. In October, OpenCode said some users' saved AI keys may have been exposed.

Key takeaways

  • Based on everything officials have said, we are not in a cyber war this week. Microsoft and Chase blamed software bugs, and the FAA says its ground stop was not a cyber issue.
  • The FAA's cause is still under investigation, and Wells Fargo, Bank of America, and U.S. Bank haven't given one.
  • Black October is real, including PHP2Shell and AI hacking tools like ARTEX, but it was never one coordinated attack.
  • A bug and an attack hit you the same way, so prepare for both with cash, a backup card, screenshots, and a locked down email.
  • Expect scam texts after any big outage. Open the app yourself and never share a verification code.

FAQ

Was the FAA ground stop a cyberattack?

The FAA says no. Its first look points to a new router being installed by L3Harris in El Dorado, Arkansas, and a radar site in Amarillo, Texas, after its network was flooded with 1,000 connection attempts every 4 to 5 seconds. The exact cause is still under investigation.

What caused the Microsoft Outlook outage?

Microsoft's preliminary report says a software bug had been in its gateway servers since July. About 14% of those servers were already offline, and moving Teams traffic onto Outlook's gateway woke the bug up, so more than 80% of the servers stopped responding at the worst point.

What should I do if I get a text from my bank during an outage?

Don't use any link or phone number in the message, even if it shows up in your bank's real text thread, because scammers can fake the sender name. Open the app yourself, never give anyone a verification code, forward scam texts to 7726, and file at ReportFraud.ftc.gov.

Do I get a refund if my flight is cancelled during an outage?

If the airline cancels and you don't take the rebooking or a voucher, DOT rules say you get your money back automatically.

Chapters

  1. 0:00Four outages, one question
  2. 0:33Four outages in five days
  3. 1:29Why it feels like war
  4. 2:38Shipping Skool + Night Crew Studio
  5. 3:09What they actually found
  6. 4:58The real problem: a few choke points
  7. 5:43The scams that follow an outage
  8. 6:33Your outage kit
  9. 7:53So, are we in a cyber war?

Transcript

Read the full transcript

0:00Microsoft's Outlook broke for people in 74 countries on Thursday. On Friday, the FAA stopped every departure in America for over 4 hours. And on Monday, Chase and United both broke. Half the internet is calling it a cyber war. But the people investigating say not one of them was an attack. And honestly, that should bug you more. In this video, I'm covering what actually broke, the attacks that are real, the scams that come next, and a checklist for when it's your bank. I read every official statement. Let's jump right into it. So, let's go dayby day because the order matters. Thursday around midday Eastern, Outlook, Teams, and the rest of Microsoft 365 started failing. Within about an hour, 74 countries were

0:46reporting problems, and Down Detector logged nearly 130,000 Outlook reports. Then Friday at 3:54 p.m. Eastern, the FAA stopped every departure in the country for 4 hours and 21 minutes. Thousands of flights were cancelled. The White House situation room got pulled in and the FBI went into FAA facilities. Then Monday, Chase payments got stuck and by 1:50 p.m. Eastern, Down Detector had over 4,600 chase reports with Bank of America, US Bank, and Wells Fargo on there, too. And that afternoon, United had what it called a widespread system outage that held departing flights. I get why it looks like somebody's behind it. And the fear isn't crazy because

1:32October was rough. People called it black October. It was never one coordinated attack, but the stuff in it is real. First, PHP2 shell. Two critical bugs in PHP let an attacker run code on a server without logging in. On October 26th, CISA put them on its list of bugs being actively exploited, and PHP runs about 68% of websites where the server language is known. Some posts turn that into most of the internet being vulnerable. Sites that patch those two are fine. Second, AI is working for attackers, too. Microsoft says a China aligned group it calls Storm0940 used Artex, an open- source AI hacking tool against hundreds of organizations.

2:17And in multiple cases, it got admin level access in under 3 hours. Most attempts failed. And CrowdStrike says a China linked group it tracks ran its AI hacking agents mainly on deepseek models. Oh, and hackers cranked up the freezers at hundreds of French supermarkets overnight. So, did any of that cause this week's outages? $99 a month. That's every course in Shipping School with a new one every day. Two or three live calls a week, a Q&A with me every Saturday, and now the app that makes your videos. Nightcrew Studio is built from the machine that runs my channels. And in the last 7 days, that machine got me 711,000 views. [music] Every look, unlimited videos on your Mac, on your own Claude

3:03plan. Join free, upgrade inside, and your key lands in your inbox. [music] So, I'm giving each outage a tag. Microsoft first. It said there was no indication this was malicious or cyber activity. And on Monday, it put out a preliminary report. A software bug had been sitting in its gateway servers since July. About 14% of those servers were already offline for an unrelated issue, and Teams traffic got moved onto the same gateway that runs Outlook's email. That woke the bug up. And at the worst point, more than 80% of the servers stopped responding. Tag, not an attack. The FAA1 is the wildest. Its network got flooded with a thousand connection attempts every four to 5 seconds. The FAA's first look points to

3:48two places. A site in El Dorado, Arkansas, where the contractor L3 Harris was putting in a new router as part of a switch from old copper wires to fiber, and a radar site in Amarillo, Texas. FAA Chief Brian Bedford said, "I think we've all concluded that it's not a cyber issue." And Transportation Secretary Shawn Duffy said it wasn't a foreign actor. So, a router job helped stop every departure in America. Come on now. Whether it was an install mistake or a bad router is still being investigated. Tag, not an attack. Cause still open. Chase blamed a software bug in onremise hardware. said it was not cyber related and by about 6:30 p.m. Eastern transactions were posting normally. Wells Fargo, Bank of America, and US

4:33Bank haven't given a cause. And United called it a technology issue, said there's no indication it was cyber and fixed it by early evening. Chase, not an attack. The rest, no cause given. Now, to be fair, no evidence of an attack isn't proof. And companies don't always tell us everything, but the ones that explain themselves all landed on boring stuff. A bug, a router, a bug. So, here's how I read this week. Everything runs through way fewer pieces than you'd think. A flood of data, likely from a router job in Arkansas, stopped every departure in the country. One Microsoft gateway had a bad day, and people in 74 countries couldn't get into their email. And Chase says other banks only slowed

5:18down when the payment touched Chase. One bank trips and anybody sending money to it waits too. Now add AI. Tools like Rex make attackers faster. And my guess is they'll go looking for choke points like these. And a bug and an attack hit you the same way. Either way, the card gets declined or the flight sits at the gate. So get ready for both. And there's one group that loves an outage more than anybody. Scammers. In 2018, when the UK bank TSB had its big meltdown, fraud police got over 300 reports of fake TSB emails, texts, and calls in a month. And I almost missed this one. A fake text can land right inside your bank's real text thread because your phone groups messages by sender name, and scammers

6:04can fake that name. Back in 2023, Australia's consumer watchdog described a man who lost $ 38,000 Australian dollars to a text that showed up in the same thread as his bank's real messages. So, never use a link or a phone number from a message. Open the app yourself. Never give anyone a verification code and report it. Forward scam texts to 7726 and file at reportfraud.fttc.gov. So, say it's next Monday. You're at the store. Your card gets declined and a text says your account is locked. Here's the kit that makes that a non-event. One, some cash at home. Ready.gov says small bills because cards and ATMs may

6:49not work. Two, a second way to pay, like a card from a different bank. That one's my own rule. Three, screenshots. Your boarding pass, your confirmation numbers, your photos work when the app doesn't. And if the airline cancels and you don't take the rebooking or a voucher, DOT rules say you get your money back automatically. Four, check the company's own app or status page, not viral posts. Five, if a transfer fails, check your history before you send it again. You don't want to pay somebody twice. Six, lock down your main email first because it resets everything else. Use a pass key or a security key and text codes only if nothing stronger is offered. Seven, bank and card alerts on. Eight, freeze your credit at all

7:36three bureaus. It's free and it doesn't hurt your score. Nine, auto updates on everywhere. And if you build with AI, rotate your API keys and set billing caps. In October, Open Code said some users saved AI keys may have been exposed. So, are we in a cyber war? Based on everything officials have said, not this week. But this week showed how one router job can feel like one. So be the person in your house who's ready. Which one are you doing tonight? The cash, the credit freeze, or the email lock? Drop yours in the comments. And if somebody in your family panicked this week, send this to them. And if it calmed you down, a like gets it to the next person who's panicking. Have a blessed day.

Ready to start building with AI?

Join the Shipping Skool community free. Paid members get live bootcamp calls every week and weekly-updated courses.

Join Shipping Skool

Keep reading