First the email stops working. Then flights stop departing. Next, bank transactions stall. Finally, Apple joins the queue.
At what point does “another technical problem” deserve a closer look?
Recent disruptions have affected communications, aviation, banking, hospitals and even supermarket refrigeration. Some organisations have acknowledged cyberattacks. Others have attributed their outages to software bugs, equipment problems or internal updates.
| Date, 2026 | Place or service | What happened | Public position on a cyber incident |
|---|---|---|---|
| 11–12 October | France — refrigeration systems | Attackers altered controls at about 700 food-distribution sites, causing stock losses and equipment damage. France attributed the sabotage to an Iranian Revolutionary Guard cyber unit. | Acknowledged cyber incident |
| 20–21 October | Japan — Onamae.com Desktop Cloud | Malicious software was discovered in customer server environments. The service was shut down to contain the intrusion, and an extortion demand followed. | Acknowledged cyber incident |
| 10 November | Lithuania — Customs | Unauthorised activity prompted the suspension of a user portal, with possible exposure of personal data. | Acknowledged cyber incident |
| 12–14 November | Worldwide — Microsoft 365 | Outlook, Teams and other services suffered an extended disruption. Microsoft reported technical causes and no indication of malicious activity. | Denied cyber incident* |
| 13 November | United States — FAA | A communications failure triggered a nationwide ground stop. Authorities cited equipment and maintenance problems. | Denied cyber incident* |
| 15 November | Germany — Greiz-Ronneburg hospital | A hacker attack disrupted operations and temporarily closed the emergency department to new patients. | Acknowledged cyber incident |
| 16 November | United States — United Airlines | A technology failure delayed departures. United reported no indication of a cybersecurity issue. | Denied cyber incident* |
| 16 November | United States — Chase | A software problem delayed transactions, with customers at other banks also reporting difficulties. Chase said there was no evidence of a cyber cause. | Denied cyber incident* |
| 16–17 November, disclosed | International — Optimizely | An intruder exploited a vulnerability to insert malicious JavaScript into customers’ website projects. | Acknowledged cyber incident |
| 17 November | International — Apple | Several services were disrupted. Apple attributed the outage to an internal update and said it was not a cyberattack. | Denied cyber incident |
“Denied” summarises the organisation’s or authority’s public position, including statements that no evidence of malicious activity had been found. It records their assessment at the time of reporting.
A company explaining an outage has reputational interests to protect. Acknowledging that an attacker penetrated its systems invites questions about security, customer data and management competence. Describing an internal error may offer a more manageable explanation, although it also raises questions about testing and resilience.
That gives us reason to scrutinise official explanations and ask whether subsequent findings support them. The incentive alone cannot establish that an explanation is false.
France shows why scrutiny matters. Someone reached into refrigeration controls and turned digital access into physical damage. Japan’s cloud incident demonstrates how compromised infrastructure can put customers at risk. Both deserve attention alongside the conspicuous failures affecting major American services.
The unanswered question is whether any of these incidents share an organiser, a vulnerability or a wider strategy. Publicly available evidence has yet to establish that connection.
We should expect credible explanations, investigation updates and evidence of what has been fixed. “Technical issue” may be a useful first announcement. It is a poor final account.
Is the West under attack? France’s documented experience gives us one clear answer. Whether this wider succession of disruptions forms part of a coordinated campaign remains a question worth investigating.

No comments:
Post a Comment