Article Read Time

Thanks to FAA and Outlook outages, IT people had a very busy week last week. On Thursday, November 12, Microsoft Outlook stopped working for users in 74 countries and territories, and Downdetector logged more than 130,000 problem reports by early afternoon Eastern time. The next afternoon, the FAA ordered a nationwide ground stop at 3:54 p.m. It lasted more than four hours. ABC News reported it was the second such order since September 11, 2001.
Neither event was a hack. Microsoft blamed an “elevated load” on its servers and said it was not aware of any malicious activity, while federal officials traced the FAA failure to overloaded routers in Arkansas and Texas and said they found no evidence of a cyber attack.
This is good news, and we should report FAA and Outlook outages plainly. Even so, an outage that nobody caused still creates risk. Criminals have learned to move quickly when millions are confused, frustrated, and seeking a fix. For a city hall, a family business, or a non-profit with a small staff, the hours during and right after an outage deserve the same care as a known threat.
What criminals have done during past outages
The clearest example is the CrowdStrike outage on July 19, 2024. A faulty update to a security product crashed 8.5 million Windows computers worldwide. The phishing site offered a fake hotfix. It was dressed as a bank employee portal. The download installed Remcos, a remote access tool that lets attackers control the computer.
Researchers at Akamai found more than 180 new malicious web addresses. These sites claimed to help victims recover from that outage. CrowdStrike warned customers about phishing emails and calls from people pretending to be its support staff. University security teams reported scammers asking for fees to fix the problem.
Power outages draw the same behavior. After the blackout across Spain and Portugal in April 2025, Cofense documented phishing emails. The emails posed as TAP Air Portugal and offered compensation for disrupted travel. They also collected personal and payment details on fake claim forms.
The pattern is consistent. Criminals pretend to be the outage’s company, offering a quick fix or refund. They rely on haste before users verify. Security firms warn that scam campaigns can appear within hours of a major Microsoft outage.
Why small offices carry more risk
Large organizations usually have a security team that sends a staff notice within minutes of an outage. In a county clerk’s office or Main Street hardware store, the tech handler often has another full-time job. Staff must sort out what is real on their own.
An outage also pushes people toward shortcuts. Work email outages cause employees to take shortcuts. They may send invoices from personal Gmail accounts or forward files via text messages. People might search the web for a phone number to call Microsoft. Each of those shortcuts moves sensitive work outside the protections the office has paid for.
How a small organization should respond
The steps below cost little or nothing. Most work best when you agree on them before the next outage arrives. A one-page version taped near the front desk will do more good than a long binder that nobody opens.
- Confirm the outage from a source you already trust, such as the vendor’s official status page or a bookmarked admin console, rather than a link in an email or a search result.
- Tell staff right away that the outage is real, that no one from Microsoft or any vendor will call, text, or email asking for a password, and that any “fix” or download should be ignored.
- Keep a printed list of key phone numbers for your bank, IT provider, and major vendors so no one has to search the internet for a support line during a crisis.
- Agree in advance on a backup way to communicate, such as a group text or phone tree, and make clear that personal email accounts are not to be used for invoices, payroll, or client records.
- Hold any payment requests, banking changes, or wire transfers that arrive during or just after the outage until you confirm them by phone with someone you know.
- Once service returns, sign in by typing the address yourself rather than clicking a link, watch for login prompts that look slightly off, and treat any refund or compensation offer with suspicion.
- Review what happened within a week, including which tasks stopped, which shortcuts staff took, and what to include in the plan before the next outage.
FAA and Outlook Outages: Where Commonwealth Sentinel fits
Commonwealth Sentinel helps small businesses, local governments, and non-profits across the Commonwealth write simple outage and incident plans. Offices that want to talk through their own setup can reach us at 502-234-5554, and the conversation can start wherever the office stands today.
Outages will keep happening as long as people depend on a handful of large systems, and the offices that come through them safely are the ones that decided how to respond while the lights were still on.
