HELM | Briefings

HEARTLAND TO HOLYLAND™

HELM | STRATEGIC BRIEFING

International Infrastructure Disruptions & Cyberattacks

October 11–November 17, 2026 · Documented impacts, recovery status, and attribution across borders.

In this briefing

Executive Summary

This briefing presents 12 summaries of international cyberattacks and service disruptions from October 11 through November 17, 2026. They cover aviation, banking, medical cold storage, enterprise communications and other services.

The record includes confirmed cyberattacks and separately reported technical outages. The available evidence does not establish a common cause for the U.S. outages.

If Indiana is going to make data centers and AI central to its economic development strategy, we must get cybersecurity right first. Through the Indiana ⇄ Israel Corridor, Heartland to Holyland connects leaders with cybersecurity and resilience specialists to discuss how essential services can keep operating through disruptions.

01 / International incident chronology

The chronology is ordered by incident date where known. Disclosure dates are identified separately. Temporal proximity does not establish a shared attacker or cause.

Times are shown in Eastern Standard Time (EST) and Israel Standard Time (IST).

DateSystemDocumented disruptionReported explanation / limit
Oct. 11–12Refrigeration · FranceControls at more than 700 retail sites targetedCyberattack; France attributed the sabotage to an Iranian unit on Nov. 10[13]
Nov. 1–2Refrigeration · EuropeSecond wave reported across at least 10 additional countriesCyberattack; reported retail impact is distinct from internet-exposure counts[14]
Nov. 2EFS · FranceCold-storage supervision and controls at three plasma-storage sites affectedCybersecurity incident involving a supplier; no blood products lost[15]
Nov. 12–13Microsoft 365 · GlobalExchange Online and dependent servicesPreliminary cascading gateway failure involving software, load and capacity [1]
Nov. 13FAA · United StatesNationwide ground stop after telecommunications instabilityExcessive network traffic; final cause under investigation [2]
Nov. 16Optimizely · Cross-borderMalicious code in scripts belonging to 178 organizationsConfirmed platform compromise; research count is not an internal-network breach count[16]
Nov. 16Chase · United StatesTransaction delays including payments involving other banksChase software-related issue; other banks not necessarily independently down [3]
Nov. 16United · United StatesDelayed departuresTechnology disruption resolved; precise cause not confirmed publicly [4]
Nov. 17NSA · United StatesInternal classified communications degradationReported during scheduled maintenance; full scope not public [5]
Nov. 17Apple · Global servicesSelected consumer services interruptedInternal update cited by Apple [6]
Nov. 17Marriott · Global servicesWebsite and Bonvoy app sign-in disruptedResolved technical issue; company reported no cybersecurity indication[6]
Nov. 17 disclosureEquinor · NorwayAttack against certain IT systemsConfirmed cyberattack; operations and production unaffected at disclosure[17]

France | October 11–12 · Retail refrigeration sabotage

France’s November 10 attribution statement says attackers targeted refrigeration-system controls at more than 700 retail sites overnight on October 11–12. The government reported fires, material damage and spoiled food worth tens of millions of euros. Following its investigation, France attributed the operation to SHAHID KAVEH, a cyber unit affiliated with Iran’s Islamic Revolutionary Guard Corps.[13]

Reported status: Damage reported; a full restoration total was not disclosed. Attribution was issued after investigation.Source: French government statement, November 10.

Europe | November 1–2 · Further refrigeration attacks

Unit 42 reported a second wave overnight on November 1–2 affecting more than 100 retail locations across at least 10 additional European countries. Attackers gained unauthorized access to controllers and altered refrigeration settings. The initial access vector remained unconfirmed in that research. Its separate scan found more than 5,000 internet-exposed devices on November 5–6; exposure does not mean those devices were attacked or were running vulnerable software.[14]

Reported status: Retail disruption reported; a complete restoration count and initial access method were not established in the published research.Source: Unit 42 research; information current as of November 17.

France | November 2 · Plasma cold-storage systems

The French Blood Establishment reported a cybersecurity incident involving a refrigeration-equipment supplier and the supervision and control systems at three plasma-storage sites. Monitoring and alarms detected abnormal settings, allowing staff to secure or transfer products. EFS said no blood products were lost and blood collection and distribution continued.[15]

Reported status: Products secured or transferred; no blood products lost; collection and distribution continued.Source: EFS incident notice (November 2 event); AP reporting, November 4.

Microsoft 365 | November 12–13

  • Impact began · November 12 11:20 a.m. EST · 6:20 p.m. IST.[1]
  • Impact ended · November 13 11:10 a.m. EST · 6:10 p.m. IST.[1]

Exchange Online users experienced mailbox-access failures and delayed email delivery. Exchange-dependent features in other Microsoft 365 products were also affected; availability varied by region and time.[1]

Reported mechanism. A latent gateway software defect, increased load after a Teams traffic failover, and nearly 14% unavailable capacity combined. Within less than two hours, more than 80% of gateway servers became unresponsive. The preliminary report described CPU and memory exhaustion associated with lock contention; regional containment and automated recovery did not stop the cascade.[1]

Engineers reverted the affected code and patched and restarted groups of servers. On November 13, European capacity was healthy by 6:35 a.m. EST · 1:35 p.m. IST, and webmail was normal by 9:17 a.m. EST · 4:17 p.m. IST. These are preliminary technical findings, not a completed forensic investigation.[1]

Reported status: Active impact ended November 13; the November 15 report was preliminary, with final root-cause findings pending.Source: Microsoft preliminary report, November 15.

FAA | November 13

  • Ground stop began · November 13 Approximately 3:30 p.m. EST · 10:30 p.m. IST.[2]
  • Traffic resumed · November 13 8:15 p.m. EST · 3:15 a.m. IST (November 14).[2]

Instability affected 17 of 22 Air Route Traffic Control Centers and several terminal radar facilities. Approximately 3,500 aircraft already airborne landed safely. Critical lifesaving, law-enforcement and military flights continued.[2]

Reported mechanism. Legacy telecommunications equipment became unstable amid approximately 1,000 connection attempts every four to five seconds. Investigators examined a radar site near Amarillo, Texas, and a radio communications site near El Dorado, Arkansas, where the network provider was working with a new router.[2]

Recovery and limits. Isolating two sites stabilized the network. The FAA reported 12,462 cancellations, including 9,082 by major airlines, while cautioning that not all resulted directly from the ground stop. It disabled the same functionality on more than 60 other Juniper routers and paused new installations. The agency reported no indication of a cyberattack; the root-cause investigation continued.[2]

Reported status: Air traffic resumed November 13. Router-installation work paused; the root-cause investigation continued.Source: FAA Q&A, November 15.

Cross-border websites | November 16 · Optimizely compromise

Report URI examined 1,611 Optimizely snippets and identified 188 infected files belonging to 178 organizations. The altered third-party scripts delivered code for payment-card skimming, cryptocurrency-address substitution, cookie and screenshot theft, and iOS exploit delivery. Affected brands included the BBC, CNN, Zoom, HSBC and Air France-KLM. The figures describe observed malicious snippets and organizations, not a complete count of infected devices, successful thefts or direct breaches of each brand’s internal network.[16]

Optimizely confirmed exploitation of a vulnerability in its Experimentation product. Its notice, posted at 8:02 p.m. EST on November 16 · 3:02 a.m. IST on November 17, said the vulnerability had been fixed, injected code removed, and affected accounts secured; the incident was in monitoring. Individual customer exposure windows were not disclosed in the notice.[18]

In its November 17 follow-up, Report URI said all infected Optimizely files in its sample had been cleaned by November 16 at 6:11 p.m. EST / November 17 at 1:11 a.m. IST and had remained clean. The number of stolen cards, cookies or screenshots and infected iOS devices remained unknown.[16]

Reported status: Vulnerability fixed and injected code removed; operator status was monitoring. Individual visitor impact was not fully quantified.Source: Optimizely notice, November 16 EST / November 17 IST.

JPMorgan Chase | November 16

Reported cause and impact. Chase attributed transaction delays to a software bug affecting internal hardware systems. Customers of other banks could experience delays when a transaction involved Chase; this did not establish independent outages at those banks. Zelle’s operator said its network remained fully operational, although payments involving Chase could be delayed.[3]

Recovery and attribution. A Chase spokesperson said the issue was resolved later on November 16 and transactions were processing normally. Chase said it was an isolated software issue, not a cyberattack. A precise incident start time, total affected-customer count and transaction-loss total were not disclosed in the AP report.[3]

Reported status: Chase reported resolution later November 16 and normal transaction processing.Source: AP report, November 17.

United Airlines | November 16

United reported a departure disruption lasting more than 90 minutes on November 16. Flights already airborne and United Express regional flights were unaffected. AP reported that pilots described a weight-calculation system problem, but United did not confirm the precise system or technical cause. The airline said it had no indication of a cybersecurity-related issue.[4]

Reported status: Resolved about one hour and 40 minutes after pilots first reported problems; United reported no indication of a cybersecurity-related issue.Source: AP report, November 17.

NSA | November 17

The NSA reported temporary degradation during scheduled routine maintenance on November 17. AP identified the affected classified internal network as NSANet. The agency said mission-critical capabilities remained fully operational; it did not disclose the full scope or a detailed technical cause.[5]

Reported status: The NSA described temporary degradation during maintenance and said mission-critical capabilities remained fully operational. The statement does not supply a complete restoration time.Source: NSA statement, November 17.[19]

Apple | November 17

Apple reported interruptions to selected consumer services on November 17 and cited an internal update. No attacker or malicious mechanism was identified in the reporting.[6]

Status update. Apple’s status feed marks the App Store outage resolved at 3:00 p.m. EST · 10:00 p.m. IST, AppleCare on Device resolved at 3:39 p.m. EST · 10:39 p.m. IST, and iCloud Account & Sign In resolved at 4:15 p.m. EST · 11:15 p.m. IST, all on November 17. These are service-specific end times, not a single recovery time for every Apple service.[20]

Reported status: The three listed App Store, AppleCare on Device and iCloud sign-in incidents were marked resolved on Apple System Status as of November 17, 7:37 p.m. EST / November 18, 2:37 a.m. IST.Source: Apple System Status, November 17 EST / November 18 IST.[20]

Global hospitality services | November 17 · Marriott

Marriott said a technical issue affected sign-in on Marriott.com and the Bonvoy app. The company reported resolution and said its review found no indication that the problem was cybersecurity-related.[6]

Reported status: Sign-in issue reported resolved; Marriott reported no cybersecurity indication.Source: AP report, November 17.

Norway | November 17 disclosure · Equinor

Equinor disclosed an ongoing cyberattack against certain IT systems and said it had mobilized response resources and was informing authorities. At disclosure, it reported no effect on operations or production and no indication that data had been stolen. The statement did not identify an attacker, initial access method or full incident timeline. November 17 is the disclosure date; it does not establish when access first occurred.[17]

Reported status: Attack ongoing at disclosure; operations and production unaffected; no indication of data theft.Source: Equinor disclosure, November 17.

02 / What is established—and what remains unknown

Confirmed malicious activity. France attributed the October refrigeration sabotage to an Iranian cyber unit. The European refrigeration attacks, EFS supplier incident, Optimizely compromise and Equinor attack have different effects and attribution status. No common campaign linking these incidents has been established.

Operator explanations for outages. Microsoft described a gateway failure sequence; the FAA reported no indication of outside malicious activity; Chase said its issue was not a cyberattack. Marriott also reported no cybersecurity indication. Those accounts remain distinct from the confirmed attacks in this report.

U.S. officials said they saw no evidence of a coordinated cyberattack behind the U.S. outages while technical investigations continued.[5]

03 / Indiana’s AI future starts with cybersecurity

Disruptions to digital systems can affect essential services and everyday operations. For Indiana, they underscore the importance of secure, reliable infrastructure as AI adoption expands.

If Indiana is going to make data centers and AI central to its economic development strategy, we must get cybersecurity right first.

That means building cybersecurity, operational continuity and recovery into growth from the outset. The Indiana ⇄ Israel Corridor provides an existing forum for leaders, universities and resilience specialists to examine these questions together.

Heartland to Holyland connects leaders with corridor specialists in technology, cybersecurity and resilience. Explore their experience to inform your organization’s next conversation.

Meet the Specialists

04 / From the Indiana ⇄ Israel Corridor

Heartland to Holyland’s Indiana ⇄ Israel resilience dialogue began before this autumn’s disruptions.

On February 20, HH convened a leadership roundtable in Indianapolis with Ambassador Ronen Hoffman and leaders from Indiana’s public, private and technology sectors. The discussion explored infrastructure interdependence, continuity and opportunities for cross-sector collaboration.[12]

That dialogue continued at the Indiana Statehouse on June 5, where government, technology, cybersecurity, infrastructure and university participants examined critical infrastructure, energy and water resilience, and public-private coordination. A live infrastructure resilience simulation placed participants in scenarios requiring coordinated decisions across organizations.[9]

In August, HH hosted a three-day EIS Council executive visit to Indiana, connecting the delegation with state leadership, TechIndiana and Purdue University. The Purdue program included cybersecurity, defense and critical infrastructure, extending the dialogue into university research and institutional collaboration.[12]

Continue the Conversation

Recent disruptions make infrastructure continuity a timely subject for Indiana’s government, business and university leaders.

Join Dr. Dennis Trinkle, Chetrice Romero and David Dungan, hosted by Ambassador Dr. Ronen Hoffman, on November 18 for Indiana: A Hub for Resilience in Action.[10]

Bring one question from your organization:

What must keep working when the systems you depend on do not?

Join the Conversation

Sources & methodology

Updated: November 17, 2026, 7:59 p.m. EST / November 18, 2026, 2:59 a.m. IST. Covers selected incidents from October 11–November 17. Findings may change as investigations continue.

Current operator information: Apple System Status · Optimizely Service Status · FAA airport status

  1. Microsoft 365, Preliminary Post Incident Report, report dated November 15, 2026. Document attributed to Microsoft; third-party-hosted copy on 365Fanatic. Read Microsoft’s preliminary incident report
  2. Federal Aviation Administration, Nationwide Ground Stop: Questions and Answers, Nov. 15, 2026. Read the FAA’s incident Q&A
  3. Associated Press, What to know about the online banking delays that affected major US banks, Nov. 17, 2026. Read AP’s banking report
  4. Associated Press, A system outage forces United Airlines to delay departing flights, Nov. 17, 2026. Read AP’s United Airlines report
  5. Associated Press, NSA communications network goes down during maintenance, Nov. 17, 2026. Read AP’s NSA report
  6. Associated Press, Apple joins a parade of technology hiccups in recent days, Nov. 17, 2026. Read AP’s Apple and Marriott report
  7. ABC7 Chicago / WLS, NSA outage, other tech issues raise concerns as officials say disruptions not tied to cyberattacks, November 17, 2026. Read the officials’ statements reported by ABC7
  8. Reuters, Tech outage wave reaches US government, Trump says all is 'fine', Nov. 17, 2026. Read Reuters’ outage coverage
  9. Laura Hatton, Before the MOU: Building the Partnership, The Times of Israel Blogs, July 22, 2026. Read the Statehouse working-session account
  10. EIS Council, Indiana: A Hub for Resilience in Action, Nov. 18, 2026. View the EIS Council program
  11. Laura Hatton, Infrastructure Security and the Future of State to Nation U.S.–Israel Alignment, The Times of Israel Blogs, March 2, 2026. Read the roundtable account
  12. Heartland to Holyland™, Indiana ⇄ Israel Resilience Engagements, 2026. Primary event record for the February roundtable and August executive visit. Read HH’s event record
  13. France Ministry for Europe and Foreign Affairs, Declaration of attribution to Iran of cyber attacks against France, November 10, 2026. Read France’s attribution statement
  14. Palo Alto Networks Unit 42, Turning Up the Heat: Inside the Attacks on Europe’s Refrigeration Systems. Read the refrigeration research
  15. Établissement français du sang, notice concerning the November 2, 2026 refrigeration-supplier incident, reproduced by La Veille Acteurs de Santé. Read the EFS statement Additional reporting: Read AP’s report on EFS continuity and product safety
  16. Scott Helme, Report URI, World’s Largest Brands Infected With Malware Via Optimizely, November 16, 2026. Read Report URI’s investigation
  17. Equinor, Equinor detected cyber-attack, November 17, 2026. Read Equinor’s disclosure
  18. Optimizely, Web Experimentation Security Incident, November 16 EST / November 17 IST, 2026. Read Optimizely’s incident notice
  19. National Security Agency, NSA statement on network issues, November 17, 2026. Read the NSA’s statement
  20. Apple, System Status, service status as of the date and time shown above. Check Apple’s system status
Back to HELM | Briefings