Tech · Microsoft 365 outageContinuing story · report 2 of 5
Microsoft 365 outage disrupts government services as recovery struggles
Singapore warns of delayed government replies and Australian transactions are disrupted as Microsoft struggles to keep recovered servers responsive.
Written 6 min read · 124 sources
What changed since our last report
3 hours later
Now
Singapore warns of delayed government replies and Australian transactions are disrupted as Microsoft struggles to keep recovered servers responsive.
People waiting for replies from Singapore government agencies face delays. In New South Wales, customers have been asked to postpone service-centre visits because some transactions cannot be completed. Microsoft’s worldwide outage has turned an email failure into a public-service problem—even where offices remain open and emergency systems keep working.411
The disruption that began on November 12 continued into November 13 across Asia-Pacific. Microsoft had recovered some server capacity, but bringing machines back online had repeatedly proved different from keeping them responsive once users reconnected. Its documented 06:12 UTC update still described server recovery and traffic adjustments, not full restoration.1681
In our November 13 report at 05:05 UTC, we described unexpectedly unavailable servers, unsuccessful recovery changes and no confirmed restoration time. The subsequent Microsoft statement continued that recovery effort. The additional regional accounts make the consequences clearer: interrupted government correspondence, unavailable administrative transactions and financial workers unable to use email.
We're continuing to work on recovering our frontend servers while implementing further traffic optimization actions to improve service stability and increase capacity.
Public services, with important exceptions
Singapore’s Government Technology Agency, GovTech, said some government systems, including email, were affected. Responses to enquiries could therefore be delayed. People with urgent matters should contact agencies through other channels, including their call centres, the agency advised.4
Its assurances were specific: emergency services remained fully operational and reachable on 995 and 999; Singpass, the national digital-identity service, was unaffected; and public officers could continue using Microsoft Teams internally. Those exceptions matter. Disrupted government email did not mean emergency response, digital identification or every communications channel had stopped.4
In Australia, Service NSW advised customers to delay service-centre visits and complete transactions online where possible. Centres remained open, but some transactions at service centres and call centres were unavailable. Urgent transactions that could not be completed could receive a priority callback. Northern Territory authorities also reported disruption, although the available account does not establish a complete inventory of affected services.117
Healthcare accounts described administrative difficulties, including paper-prescription workarounds. Queensland Health said there were no known current clinical impacts and that business-continuity arrangements were being used where needed to maintain services. That is a qualified assurance about its services, not proof that no clinical consequences occurred anywhere in Australia. In Victoria, Triple Zero said people could still call and that its services faced no direct impact.711
The same distinction between lost communications and stopped operations ran through universities and aviation. Charles Sturt University confirmed Outlook and other Microsoft service problems while Teams and Zoom were functioning. Staff could not send or receive email, and systems requiring email authentication became difficult to use, obstructing requests from staff and students. Melbourne Airport flights were described as unaffected, while Virgin warned that confirmation emails could be delayed.11
Hong Kong bankers encountered another email bottleneck. The South China Morning Post reported accounts from bank sources of staff working offline, with bankers at Goldman Sachs and Nomura describing disrupted work. A Nomura source said email sending and receiving had been unavailable since early Friday and remained affected when they spoke. These were employee accounts—not formal declarations that every system at either bank had failed, trading had stopped or a quantified financial loss had occurred.10
Servers returned, then failed again
The incident centred on Exchange Online, the cloud platform behind Microsoft 365 mailboxes and many connected functions. Users could not open inboxes, reliably retrieve messages, or send and receive email. Some calendar functions failed too. Teams, Copilot and SharePoint also had reported problems, but effects varied by function, organization and location. Singapore’s continuing internal Teams service is a useful correction to any claim that every Microsoft application failed everywhere.1411
Microsoft’s explanation became more specific without becoming a definitive root-cause finding. Servers unexpectedly became unavailable and failed automatic health checks, leaving the remaining infrastructure to carry more work across several regions. The company said this elevated load resulted from losing usable servers, not from a surge in customer demand. It also identified an overwhelmed core process on affected servers that was reducing capacity.61511
Engineers paused deployments, redirected and redistributed traffic, and restarted affected servers. An alternative health-check method brought a subset back into service, and Microsoft began applying it more widely. The company also prepared automated systems to detect and restart servers that stopped responding.51315
But some restarted servers stopped responding again once traffic returned. Other experiments included blocking selected traffic types in particular locations, rebuilding some servers with a previous configuration, and restarting isolated portions of infrastructure before reintroducing requests to test stability. These were recovery attempts, not evidence that the underlying problem had been eliminated.8111
Microsoft acknowledged partial recovery in some regions but said its measures were not producing sustained recovery. That is the central limitation of the progress reported so far: access could improve for some people while the infrastructure remained vulnerable to another failure under ordinary requests.4
A component responsible for processing server health was under investigation as a possible origin of the failed checks. Microsoft had not established the definitive trigger. Australia’s Home Affairs Minister Tony Burke relayed Microsoft’s belief that the disruption was not a cyber event and compared the possible explanation with an update going wrong. Neither that comparison nor rebuilding servers with an older configuration proves a faulty update caused the outage.1211
Reach is clearer than the toll
Downdetector received reports from 74 countries and territories within about an hour, according to Deutsche Welle. That establishes broad geographic reach, not universal failure within each location. The number of individuals and organizations actually affected remains uncounted reliably.8
The tracker figures are observations of complaints, not an audited census of people without service. One service-specific snapshot at 14:07 US Eastern on November 12 recorded more than 97,000 Outlook reports, more than 38,000 Microsoft 365 reports, about 4,500 Teams reports and nearly 6,000 Copilot reports. Those submissions can overlap across services and must not be added into a person total.14
Other snapshots used different times and geographic scopes. Deutsche Welle reported nearly 130,000 US Outlook reports shortly after 18:00 GMT; BBC Mundo described a worldwide snapshot approaching 140,000. Al Jazeera recorded about 77,000 Outlook reports before 20:00 GMT. They do not form a uniformly measured global series, and falling complaints do not establish stable restoration. Likewise, descriptions of nine or ten hours of disruption were publication-time snapshots, not the incident’s final duration.8171912
The outage also reached AI tools connected to Microsoft 365, without establishing that all of ChatGPT or Claude went down. OpenAI reported Microsoft connector problems that could break new connections or prevent tools from working as expected. Its available account did not identify individual tools.5
Anthropic’s documented 22:23 UTC update on November 12 was more specific: mail, calendar and search tools were still failing for most requests, and Claude for Outlook remained affected. No confirmed full-restoration time for either provider’s affected connector was established.100
The operational consequences are now more concrete than in our earlier report, but the largest questions remain unresolved: the initiating cause, the true affected-user total, the full cost and the point at which recovery holds across regions. Microsoft’s meaningful finish line is not another successful restart. It is infrastructure that keeps responding when people return to work.
Timeline
Day 4 · 5 reports
We aired · Update 2You are here
Microsoft 365 outage disrupts government services as recovery strugglesWe aired · Update 3Newer
Microsoft outage delays medical scans and a final job interview as recovery remains partialWe aired · Update 4Newer
Microsoft protects delayed mail for 48 hours as outage recovery remains incompleteMicrosoft's stated end of active customer impact.
Microsoft says service is restored to the remaining affected customers and regions and keeps monitoring delayed mail.
Preliminary report published; Lamanna apologises on X.
Sources98
Every source, by outlet
124 sources from 98 outlets· Most cited first
Google News Pakistan (PK:en)theguardian.com4
- First reported
- A global Microsoft 365 outage has hit thousands – what happened and when will it be fixed? - The Guardian
- Microsoft begins restoring services as global outage affects Outlook and Teams
- Microsoft outage live: Microsoft scrambling for new ways to fix global outage after initial attempts fail to restore Outlook services | Microsoft | The Guardian
- ‘Looks like we’ll have to talk to people’: Australia sent back to time before email with major Microsoft outage | Microsoft | The Guardian
Google News Singapore (SG:en)channelnewsasia.com4
- First reported
- Some Singapore government systems affected by Microsoft outage: GovTech - CNA
- Microsoft 365, Outlook down for thousands of users - CNA
- Microsoft outage drags on for hours, disrupting Outlook, Teams for thousands, including Singapore users - CNA
- Microsoft Outlook outage: Disruptions hit workers worldwide amid setback in recovery efforts - CNA
reddit.com3
- Microsoft 365 outage (EX1550543 / MO1550821): Microsoft's status updates so far, in order : r/sysadmin
- Microsoft 365 outage (EX1550543 / MO1550821): Microsoft's status updates so far, in order : r/Office365
- Yesterday's M365 outage (EX1550543 / MO1550821): Microsoft's updates in order, and the lessons for admins : r/Office365
365Fanatic365fanatic.com2
ABC Newsabcnews.com1 video2
Al Jazeeraaljazeera.com2
cloud.microsoft2
Google News Canada (CA:en)ctvnews.ca2
As aired
- Microsoft is still recovering servers as its outage disrupts government services. Singapore warns that email replies may be delayed, and some Australian government transactions are unavailable. Earlier on November 13, we reported unsuccessful recovery changes and no confirmed restoration time. Can Microsoft bring its servers back and keep them responding when users reconnect?
- Microsoft's latest update still describes work to recover servers and improve capacity. That continues the recovery effort we described earlier. The additional consequences now stretch across government correspondence, public transactions and financial-sector work in Asia-Pacific.
- Problem reports arrived from 74 countries and territories within about an hour. The effects varied sharply between organizations. Singapore's government email, Australian administrative services and Hong Kong bankers' communications all encountered problems, while some other services kept working.
- The disruption centers on Exchange Online, the cloud system behind Microsoft 365 mailboxes and many connected functions. Users couldn't open inboxes, reliably retrieve messages, or send and receive email. Some calendar functions failed too. Teams, Copilot and SharePoint also had reported problems, with different functions affected in different places.
- Microsoft says it's recovering the servers that handle incoming requests and adjusting traffic to improve stability and capacity. Earlier measures produced partial recovery in some regions, but Microsoft said that improvement wasn't sustained. Some restarted servers stopped responding again when traffic returned.
- Microsoft says servers unexpectedly became unavailable and failed automatic health checks. That left the remaining infrastructure carrying more work across several regions. The company says the extra load came from losing usable servers. Customer demand hadn't surged. It also found an overwhelmed core process that was reducing capacity.
- An alternative health-check method brought some servers back, and Microsoft began applying it more widely. But returning traffic exposed continuing failures. Engineers also restarted isolated portions of infrastructure, then reintroduced requests to test whether those portions could stay responsive.
- Microsoft paused deployments, redirected and redistributed traffic, and restarted affected servers. It prepared automatic systems to detect and restart servers that stopped responding. Other experiments included blocking selected traffic types in particular locations and rebuilding some servers with a previous configuration.
- Microsoft is investigating a component that processes server health as a possible origin of the failed checks. It hasn't identified the definitive trigger. Rebuilding servers with an older configuration is one attempted remedy, and doesn't tell us which change caused the failure.
- Australia's Home Affairs Minister Tony Burke relayed Microsoft's belief that the disruption wasn't a cyber event. He compared the possible explanation with an update going wrong. Microsoft is still investigating the cause, so that comparison remains tentative.
- Subscribe to this channel as we follow Microsoft's recovery and the services still affected.
- Singapore's emergency services remain operational on 995 and 999, GovTech says. Singpass, the national digital-identity service, is unaffected. Government officers can still use Teams internally, even as disrupted email threatens to delay replies to the public.
- GovTech advises people with urgent enquiries to contact agencies through other channels, including call centres. The continuing internal Teams service shows how uneven this outage is. Microsoft had also announced recovery of a separate North American Teams issue while broader Microsoft 365 problems continued.
- Service NSW asked customers to postpone service-centre visits and complete transactions online where possible. Some transactions at service centres and call centres were unavailable, although the centres stayed open. Urgent transactions that couldn't be completed could receive a priority callback.
- Northern Territory authorities also reported service disruption. Healthcare organizations described administrative difficulties, including paper-prescription workarounds. Queensland Health said there were no known current clinical impacts and that it was using business-continuity arrangements where needed to maintain services.
- Victoria's Triple Zero said people could still call and that its services faced no direct impact. Charles Sturt University confirmed Outlook and other Microsoft service problems, while Teams and Zoom were functioning. Email-dependent work still encountered obstacles.
- At Charles Sturt, staff couldn't send and receive email, and systems requiring email authentication became difficult to use. That obstructed requests from staff and students even where workarounds existed. An Adelaide University employee also described widespread effects on staff and students.
- Flights at Melbourne Airport were described as unaffected. Virgin warned that confirmation emails could be delayed. Across these institutions, losing a message or an authentication step could interrupt administrative work even when the service behind it kept operating.
- Bank employees in Hong Kong described working offline on Friday morning. Bankers at Goldman Sachs and Nomura reported disruption. A Nomura source said staff had been unable to send or receive email since early morning, with the problem continuing when they spoke.
- Microsoft employees also struggled with email, alongside customers in business and government. The worldwide number of individuals affected hasn't been counted reliably. More than nine hours, and about ten hours, were descriptions of the continuing disruption at different points, rather than its final duration.
- One snapshot recorded more than 97,000 Outlook problem reports and more than 38,000 for Microsoft 365. Teams had about 4,500, and Copilot nearly 6,000. These submissions can overlap across services, so adding them wouldn't produce a count of affected people.
- The US reporting peak exceeded 130,000 in one snapshot. A separate worldwide Outlook snapshot approached 140,000. Those figures cover different geographic areas. Complaints later declined, including an Outlook snapshot of about 77,000, but people reporting fewer problems doesn't demonstrate stable recovery.
- Australia recorded more than 5,500 access complaints in its morning snapshot. A Brazilian snapshot counted 30,073 Outlook notifications. Another observation put the later decline at more than half. The differing reporting windows prevent a reliable, single worldwide rise-and-fall curve.
- Indonesian complaints describe what people encountered as well as where they encountered it. Website and app access each made up 31 percent of submitted Outlook complaints, while login problems represented 20 percent. Those listed categories don't cover every Outlook complaint.
- For Microsoft 365, app issues accounted for 42 percent, login 39 percent and website access 15 percent. For Teams, those shares were 82 percent, 12 percent and 6 percent. Each measures submitted complaints for that service, rather than all its users.
- The outage also reached AI tools that connect to Microsoft 365. OpenAI said new Microsoft connections might break and tools might fail. Anthropic described possible failures involving SharePoint and Teams chat, connections that might not complete, and Outlook add-in actions that could fail.
- Anthropic's later update said mail, calendar and search tools were still failing for most requests. Claude for Outlook remained affected. These connections depend on Microsoft's infrastructure. A confirmed restoration time for either company's affected connector still hasn't been announced.
- Microsoft has brought some capacity back, but returning traffic has repeatedly exposed instability. Its latest statement still describes server recovery and traffic adjustments. The company hasn't given a full-restoration time or explained definitively what triggered the server failures.





