The Short Answer
Between November 12 and 17, 2026, Microsoft 365, the FAA, Chase and NSANet each failed, and every stated cause was internal (an upgrade, overloaded routers, a software bug, maintenance), not an attack. Two real intrusions and an FBI alert on AI attack agents landed the same week. On ibl.ai you own all the code and the data, so an agency schedules its own AI changes and scopes its own agents.
The posts circulating about "five days" of November 2026 tell one story: a coordinated cascade. The sourced record tells a different one, and it is the more useful one for a government team deciding how to run AI.
No source we found links any of these events to each other. This post takes each one in turn, with its stated cause, and then asks what an agency should change.
What actually failed between November 12 and 17, 2026?
Six incidents and one advisory are confirmed by the organizations involved or by major outlets. The table lists each one with the cause its operator gave, as of November 21, 2026.
| Date (2026) | What failed | Stated cause | Attack? |
|---|---|---|---|
| Nov 12β13 | Microsoft 365: Exchange Online, Teams, SharePoint Online, Copilot, Defender XDR | "An issue during an earlier network capacity upgrade" | No: "not related to cyber or AI / agents" |
| Nov 13 | FAA nationwide ground stop, about 4 hours 21 minutes | Telecommunications outage; switches and routers overloaded | No suspected cyberattack (DHS) |
| Nov 16 | Chase online and branch transactions | "A software bug in on-premise hardware system" | No: not "cyber-related" |
| Nov 17 | NSANet, the NSA's classified internal network | "Temporary degradation during scheduled routine maintenance" | No evidence of one, per CNN's sources |
| Nov 10β14 | RIKEN Fugaku supercomputer, taken offline Nov 14 | Unauthorized access to internal servers | Yes; not attributed |
| Nov 17β20 | Equinor "certain IT systems" | Ongoing cyber-attack, stopped by Nov 20 | Yes; production unaffected |
| Nov 13 | FBI FLASH-20261113-001 on ARTEX | Advisory on an AI agent attack framework | Warning; no link to the rows above |
Two more items from the circulating version need a note. Apple did have an outage on November 17, hitting iCloud and other services.
Apple told Bloomberg it followed "an internal update" and was not a cyberattack, Macworld reported, the same pattern as the four outages above. We found no source for "US courts offline" on November 18, so it is not in the table.
Were the November 2026 outages a cyberattack?
The four outages in the November 2026 record were not attributed to attacks by anyone who ran the systems. Each operator gave an internal cause, and two said in so many words that it was not cyber.
Microsoft 365. Microsoft dated the incident from 1:26 PM ET on Thursday, November 12, and reported "broad recovery" by midday November 13. It said the cause "was introduced by an issue during an earlier network capacity upgrade" and was "not related to cyber or AI / agents," BleepingComputer reported.
The FAA. The ground stop ran from 3:54 PM to 8:15 PM ET on Friday, November 13. More than 4,700 flights were cancelled that day, per FlightRadar24, Al Jazeera reported.
Transportation Secretary Sean Duffy said switches and routers "became overloaded with data and went down," and Homeland Security Secretary Markwayne Mullin said there were "no suspected cyberattacks."
Chase. On Monday, November 16, JPMorganChase said it had "a temporary issue related to a software bug in on-premise hardware system," not "cyber-related," and that transactions were posting normally by about 6:30 PM, NBC News reported.
NSANet. On November 17, CNN reported, citing six people, that NSANet was down, with no evidence of a cyberattack. The NSA called it "temporary degradation during scheduled routine maintenance," per Al Jazeera.
Which November 2026 incidents were real intrusions?
Two incidents in the November 2026 record were real intrusions, and neither has been attributed to a named actor or to ARTEX.
RIKEN Fugaku. An unauthorized party reached internal servers between November 10 and 13, and RIKEN shut Fugaku down on November 14, BleepingComputer reported. Names, emails and user IDs of 4,222 Fugaku users were exposed, along with names and emails of 375 Rikyu users.
The report says the intruder exploited Fugaku's public status dashboard, while RIKEN had yet to confirm the access method. SSH private keys and access keys were among the files reached, and some keys were used to try other systems.
Equinor. On November 17, Equinor said it had "detected an ongoing cyber-attack against certain IT systems" and that operations and production were unaffected. By November 20 Equinor said the attack was stopped, with "no indication that data has been stolen or altered."
What does the FBI ARTEX advisory say about government targets?
The FBI ARTEX advisory names government among the sectors attacked. FLASH-20261113-001, dated November 13, 2026, describes ARTEX as "an open-source, large language model (LLM)-driven agentic platform" that threat actors have used since at least August 2026.
Its sector list is financial services, government, technology, defense, semiconductor, energy, healthcare, manufacturing, telecommunications and legal. Some intrusions went "from initial targeting to privileged access in under three hours."
Researchers counted over 1,600 publicly exposed ARTEX consoles as of early November. The developer removed the GitHub repository on October 8, 2026, but forks, archived copies and a commercial ARTEX PRO keep it available, the FBI says.
The advisory says ARTEX "excels at identifying and exploiting peripheral systems receiving less security attention than flagship applications": partner portals, employee applications, legacy services and third-party integrations.
An agency's AI agents and their connectors belong on that list.
We cover the advisory's checklist in detail for school districts and for enterprise credential management.
What should a government agency change about how it runs AI after November 2026?
The November 2026 record gives an agency running AI two separate lessons, and neither is "the cloud is unsafe." Four of the six incidents were internal failures, and one of those, Chase, was in on-premise hardware.
Lesson one: most failures are changes. An upgrade, a router overload and scheduled maintenance account for three of the four outages. Self-hosting does not remove that risk; it moves the change calendar to the agency, which can freeze, stage and roll back AI changes around its own mission dates.
Lesson two: attacks go to the edges. The FBI's mitigations start with an inventory of every internet-facing application, least privilege on application permissions and consent grants, and scanning configurations and pipelines for embedded secrets. Each applies to an AI agent with tool access.
A practical checklist, drawn from the FBI's recommendations:
- Inventory every AI agent and connector that touches agency data, including pilots a single office started.
- Scope each agent to the records and hosts its task needs, and review its permissions and consent grants.
- Keep agent and administrator interfaces off the public internet, behind trusted networks or private connectivity, as the FLASH advises for administration surfaces.
- Rotate and remove embedded secrets from agent configuration, environment variables and deployment scripts.
- Preserve logs of agent actions and sign-ins, so an investigation has evidence to work with.
How does ibl.ai help an agency apply these lessons?
ibl.ai gives an agency the parts of this checklist that depend on holding the deployment. On ibl.ai you own all the code and the data, under a perpetual license, so the agency's team controls when the AI stack changes and how each agent is scoped.
Access to agents and their settings is governed by roles and RBAC, configuration changes land in an audit log, conversations are kept as transcripts, and tool-using agents can run in a sandbox under a host allowlist.
The platform is model-agnostic, with no per-seat pricing, and agencies can deploy anywhere: their own cloud, on-premise, GovCloud or a fully air-gapped network. None of this replaces an agency security team; it gives that team the logs and the controls.
ibl.ai is family-owned and operated from New York, NY, and its engineers work alongside an agency's own team through updates and new agents. See ibl.ai for government.
Sources: Microsoft 365 from BleepingComputer; FAA from Al Jazeera; Chase from NBC News; NSANet from Al Jazeera, citing CNN; Fugaku from BleepingComputer; Equinor from its own statement; Apple from Macworld; ARTEX from FBI FLASH-20261113-001. No source connects these events.