Microsoft outage hits where routines break

The Times of Malta, citing AFP, reported that Microsoft described the incident as a technical failure rather than any malicious “cyber or AI” activity. In an updated statement, the company said the problem was introduced during an earlier network capacity upgrade and surfaced after a later network change. It also said there was “broad recovery” across services, though restoration was still continuing in some regions.

That distinction matters. A cyberattack points to one kind of vulnerability; a failure during a company’s own upgrade points to another. The second is less dramatic, but for the people trying to keep services moving, it is not much gentler.

The disruption reached healthcare in the UK, where the GMB union said National Health Service staff taking emergency calls were unable to refer patient details in the normal way, creating a backlog. Immigration New Zealand halted all visa processing. Airlines in India, including IndiGo and Akasa Air, warned customers that email support had been affected. Japan’s economy, trade and industry minister, Ryosei Akazawa, warned of a “significant impact” because Microsoft products are used by a “vast number of people.”

Downdetector, which tracks user reports of outages, showed the problems spanning users across the Americas and parts of Europe, Asia and Africa. Reports there had begun to decline by 0900 GMT, which is useful evidence that disruption was easing, though not the same thing as a complete technical recovery.

Some of the clearest comments came from workers forced to notice what had quietly become part of the day’s structure. In London’s financial district, people interviewed by AFP pointed not only to Outlook but to the loss of Copilot, Microsoft’s AI assistant. “I think one of the biggest things is Copilot not working,” auditor Yashmit Sharma said. It is a small revealing detail: newer tools do not need years to become routine if a workplace starts leaning on them quickly.

The Australian Computer Society responded by calling for a review of sovereign IT risk. That can sound like committee language until the practical consequences arrive all at once — a support inbox gone dark, a visa application paused, an emergency referral no longer moving in the usual way.