跳到内容
现在

科技 · Microsoft 365服务中断持续报道 · 第 3 篇,共 5 篇

微软服务中断导致医学影像检查和最终轮求职面试延误,服务恢复仍不全面

澳大利亚民众称,检查被推迟、医疗相关工作受到干扰,最终轮求职面试也被推迟一周。微软报告称稳定性有所改善,但全球范围内能否持续恢复仍未得到确认。

文字 阅读需 8 分钟 · 167 个来源

原语言视频

译自英文原文。

自上次报道以来的变化

1 小时后

现在

澳大利亚民众称,检查被推迟、医疗相关工作受到干扰,最终轮求职面试也被推迟一周。微软报告称稳定性有所改善,但全球范围内能否持续恢复仍未得到确认。

新的进展

  • 《爱尔兰时报》报道称,夜间多次恢复运行的服务器再次崩溃。此前关于稳定性的说法已被新一轮故障所取代。
  • 微软称,在优化流量后,服务稳定性和容量有所改善,同时将相关措施扩大到受影响地区,以争取实现持续恢复——而非宣称已经恢复。

Maria Derosa遭遇车祸后需要做医学影像检查。但她和墨尔本的诊所都无法通过电子邮件或传真取回转诊单。她告诉ABC新闻,检查因此被取消或推迟——患者与所需检查之间的沟通链路中断了。⁠4

这正是微软谨慎描述恢复情况背后的现实代价。微软称,在全球Microsoft 365服务中断期间,服务器稳定性有所改善,但尚未确认服务已全面恢复。其公开事件通知由微软于11月13日07:29 UTC发布,08:39 UTC再次调取时,仍将事件归类为“服务降级”。⁠1⁠167

我们在11月13日08:16 UTC发布的报道中,介绍了反复恢复失败,以及政府通信、公共服务事务和金融行业工作受到的影响。新增的个案使这些后果更加具体:检查延误、医疗相关工作中断、学习支持中断,以及最终轮面试被推迟一周。这些个案补充了停运给人们带来何种代价的证据,并不能证明服务已全面恢复。⁠4⁠6⁠20

在墨尔本,Manny Flores无法登录Teams参加那场面试。他失业近一年,已进入最后一轮面试;面试改期至下一周。对他而言,连接失败意味着还要再等一周,才能得到有关工作的答复。在阿德莱德,Peter Roche称,身份验证问题导致他无法访问会计软件和处理发票。订单没有进来,发票也发不出去。他说自己损失了数千美元——这是他对自身业务情况的陈述,并非对更广泛损失的审计估算。⁠4

同样来自墨尔本的职业治疗师Lauren Van Ingen告诉ABC,无法登录Outlook导致她无法开展工作,帮助运动神经元病、亨廷顿病及其他神经系统疾病患者获取在家安全生活所需的设备。Derosa的说法则单独描述了获取医学检查时受到的中断,并未证明因此造成了伤害或医疗后果。⁠4

此前关于某些急救或临床服务仍可使用的保证,应按照其实际适用范围来理解。昆士兰州政府称,紧急医疗服务和患者护理未受影响。这是对该州服务情况的一项归因性保证,并不能证明其他地方的每位患者都能取得转诊单或按时赴约。墨尔本的个案即使不与这一保证相矛盾,也仍然值得重视。⁠141⁠4

教育也依赖相关服务。墨尔本学生Emilie Yu称,在准备剩余的两门VCE语言考试时,她无法获得教师帮助,也无法访问学习资料。利斯莫尔的Susan Wallace则称,她无法使用TAFE NSW及其他机构采用的Teams虚拟课堂。这两则个案都没有提供课程取消或受影响学生的总数。⁠4

恢复为何未能持续

事件于11月12日美国东海岸时间中午前后开始,并在11月13日持续影响亚太和欧洲地区。美国方面将其描述为11月12日发生的服务中断,日本方面则称其为11月13日凌晨发生的中断;两者指的是同一场跨时区持续事件,并非已确认的第二次故障。⁠1⁠19

微软的解释是,服务器意外不可用导致可用容量下降,剩余基础设施因此在多个地区承受过多工作负载。微软将这种负载集中与客户需求增加区分开来。重启服务器可能暂时恢复容量,却无法增强其韧性:部分服务器在流量回归后再次停止响应。⁠2⁠20⁠6

进展、挫折与谨慎的改善

  1. 11月12日,23:47 UTC

    朝日电视台报道称,服务仅有限恢复;微软表示,部分重启的服务器迄今运行稳定。

    19
  2. 11月13日,06:27 UTC

    《爱尔兰时报》报道称,夜间多次恢复运行的服务器再次崩溃。此前关于稳定性的说法已被新一轮故障所取代。

    6
  3. 11月13日,07:44 UTC

    微软称,在优化流量后,服务稳定性和容量有所改善,同时将相关措施扩大到受影响地区,以争取实现持续恢复——而非宣称已经恢复。

    1156

调查涉及自动健康检查失败,以及一个负责建立安全连接的进程不堪重负。一个处理服务器健康状态的组件可能存在问题,但这仍只是一种假设。这些细节有助于解释服务器为何会停止处理请求,却没有指出最初导致服务器不可用的原因。⁠4⁠10⁠158

工程师暂停部署、重新分配流量、重启服务器,并测试配置更改和替代健康检查。07:29发布的公开通知称,在将上游身份验证/路由配置组件补丁应用于部分基础设施后,稳定性表现积极。扩大一项有希望的修复措施是实质性进展,但涉及身份验证或路由的修复,并不能证明原始故障是由有缺陷的更新造成的。⁠8⁠23⁠167

该通知承诺在08:30 UTC前再次更新。这是提供信息的目标时间,并非服务恢复期限;此后调取的通知副本仍保留着先前的撰写时间。微软没有确定全面恢复的时间。⁠167

微软高管Charles Lamanna表示,“没有迹象”表明存在恶意活动或网络攻击。这一限定很重要:目前没有迹象,并不等于已完成取证并排除所有安全方面的原因。微软承诺,待事件得到缓解后,将发布有关根本原因和防护修复措施的事后说明,但未给出发布日期。⁠8⁠167

一项依赖关系,多种不同故障

公开通知列出了20项产品和服务,而非20个完全无法使用的应用程序。各类别有所重叠,关键区别在于功能:依赖Exchange Online和电子邮件的功能可能失效,而同一产品的其他部分仍可使用。⁠167

Exchange用户可能无法访问邮箱、收不到最新邮件,或遇到邮件延迟送达。Teams的大多数核心通话、会议、群聊和频道消息仍可使用,但日历安排、邀请以及部分活动或频道操作可能失效。SharePoint用户仍可直接访问存储的文件。这些边界解释了为何一个人还能继续工作,另一个人却失去了必不可少的工作流程。⁠3⁠167

影响还波及教育工具、设备注册、任务管理、Copilot对工作信息的访问,以及安全与合规功能。微软报告称,Defender的安全链接、安全附件、隔离邮件释放和邮件修复可能出现故障,Purview的标签功能、受保护内容访问和法律调查功能也可能受影响。这些是防护功能和访问故障,并非攻击者入侵客户系统的证据。⁠167

与微软相连的人工智能工具也出现了各自尚未解决的问题。OpenAI表示,新的Microsoft连接器连接可能中断,工具也可能无法按预期运行,但未指出具体是哪些工具。Anthropic最近一次有记录的更新发布于11月12日22:23 UTC,称其连接器的邮件、日历和搜索工具仍在大多数请求中失效,Claude for Outlook也仍受影响。没有确认这些服务已全面恢复;这两则通知都不意味着ChatGPT或Claude的所有服务均已宕机。⁠6⁠11⁠16

影响范围超出已有统计数字

Downdetector的报告在约一小时内覆盖74个国家和地区。BBC描述的全球Outlook投诉峰值接近140,000;RTÉ报道,美国地区的投诉峰值超过130,000。这些数字的地域范围不同,统计的是投诉报告,并非经过审计的独立用户人数,不能相加作为此次停运的总受影响人数。⁠1⁠2⁠16

其影响显然遍及多个国家。洛杉矶地区的执法机构失去了电子邮件或其他重要通信渠道。新西兰外交部报告称,邮件接收受到干扰,驻世界各地的外交机构也包括在内。日本政府改用纸质文件;香港的摩根士丹利和高盛员工则称,午休时间前都无法使用电子邮件或Teams。这些情况均不能证明政府或银行的全部业务已经停止。⁠7⁠5⁠1

关于旅行的说法也需要同样准确地表述。悉尼居民Livinia Drummond告诉ABC,一名同事前往巴布亚新几内亚的航班延误,因为有人将通过Outlook发送的文件打印后送到飞机上。这一转述并未确认航空公司或延误时长。另外,IndiGo、Akasa Air和CemAir报告了电子邮件或系统问题,但未报告航班受影响;印度航空则称运营未受影响。这并不能证明全球航班普遍停飞。⁠4⁠1

一项商业后果已有确定的新日期。Workhorse Group因服务中断,推迟了第三季度财报发布以及业绩和业务展望电话会议。电话会议改至11月16日东部时间16:30举行;财报将在会前发布。这是有记录的延误,与任何关于全球财务损失总额的推测不同。⁠16⁠146⁠153

已知

  • 微软报告称恢复有所进展,但具名人士称工作、医疗和学习受到干扰。服务全面恢复仍未得到确认。 14167

未知

  • 最初的故障原因、受影响用户和组织的审计总数、总体损失,以及连接器全面恢复的时间,仍未得到确认。

后续

  • 随着流量回归,恢复后的容量能否继续响应;以及微软承诺发布的事件报告能否解释反复恢复尝试失败的原因。

收件箱短暂恢复正常并不意味着万事大吉。真正的考验是系统能否持续可用,直到转诊单送达、发票发出、面试如期进行。

时间线

第 4 天 · 5 篇报道

事件时间线
  1. 微软所称客户受到实际影响的结束时间。

  2. 微软表示,所有仍受影响的客户和地区服务均已恢复,并继续监控延迟邮件。

  3. 初步报告发布;拉曼纳在 X 上致歉。

来源123

在此处引用的来源中,Claude最先发布,比本报道播出早3天。 随后还有89家媒体发布。

33家媒体未注明日期:Workhorse Group, Inc.cloud.microsoftreddit.comInvesting.com भारतnacionale.comRed Hot Singapore

持续报道 · 第 3 篇,共 5 篇

按媒体查看所有来源

来自 123 家媒体的 167 个来源· 引用最多的优先

播出原貌
  1. Microsoft's outage has delayed medical scans and a final job interview. The company reports better server stability, but it still classifies the incident as service degradation.
  2. On November 13, we reported repeated recovery failures and disruption to government correspondence and financial-sector work. The additional accounts show what those failures cost people. Can the repaired systems stay responsive as people return to work?
  3. Manny Flores couldn't get into Teams for his final job interview in Melbourne. He'd been unemployed for almost a year. The interview was moved to the following week, extending his wait for an answer about work.
  4. In Adelaide, Peter Roche said authentication problems blocked his accounting software and stopped him processing invoices. Orders weren't arriving and invoices weren't going out. He described losing thousands of dollars.
  5. Melbourne occupational therapist Lauren Van Ingen said she was locked out of Outlook. That stopped work helping people with motor neurone disease, Huntington's disease and other neurological conditions obtain equipment to live safely at home.
  6. Maria Derosa, also in Melbourne, said scans after a car accident were cancelled or delayed. She and the clinic couldn't retrieve referrals through email or fax. She described being unable to get the tests she needed to check that she was okay.
  7. Emilie Yu was preparing for two remaining VCE language exams in Melbourne when she lost access to teachers' help and work. In Lismore, Susan Wallace described losing Teams virtual classrooms used at TAFE NSW and elsewhere.
  8. Those accounts add specific interruptions to education and care. Earlier assurances about available clinical services applied to particular organizations and functions. They couldn't guarantee that every patient could obtain a referral or keep an appointment.
  9. The disruption crossed working days and continents. Public agencies lost communications in Los Angeles. Bank employees couldn't access email or Teams in Hong Kong. Government systems were affected in Singapore, while Melbourne residents described interrupted work, care and study.
  10. The incident began around noon on the US East Coast on November 12 and continued into November 13. The different dates in American and Japanese accounts describe the same continuing outage across time zones. By Friday morning, it had already lasted more than twelve hours.
  11. Outlook complaints peaked at nearly 140,000 worldwide. The US peak exceeded 130,000, with more than 25,000 still being logged that evening. These are complaint reports with different scopes, rather than a count of unique people.
  12. Complaints reached 74 countries and territories within about an hour. Nearly three in ten reports during an early reporting window came from outside the United States. Users in Denmark were among those affected; the number affected in Finland wasn't known.
  13. In Singapore, Outlook reports rose from about 730 to 1,130 in an hour. Microsoft 365 reports rose from 434 to 566 during a separate morning window. Different products and reporting windows can't be combined into one global outage curve.
  14. Microsoft says more than 430 million people use its Microsoft 365 apps, and more than 90 percent of Fortune 500 companies use Copilot. Those adoption figures explain the dependency. Nobody has supplied an audited total of affected users or a worldwide financial-loss figure.
  15. Subscribe to this channel to follow whether Microsoft's recovery holds and how essential services recover.
  16. Some restarted servers initially looked stable. Later, restored servers stopped responding again. A gradual-recovery announcement in Australia was followed about an hour later by renewed unresponsiveness. An inbox briefly working again couldn't guarantee that the repair would hold.
  17. Microsoft says servers unexpectedly became unavailable, leaving the remaining infrastructure carrying too much work across multiple regions. The company distinguished that loss of capacity from a surge in customer demand.
  18. Losing servers concentrated requests on the machines still operating. Some couldn't process requests reliably or pass their health checks. Restarting them restored capacity temporarily, but returning traffic sometimes made them unresponsive again.
  19. The investigation included automated health-check failures and an overwhelmed process responsible for establishing secure connections. A suspected problem in a component processing server health remains a hypothesis. Microsoft hasn't identified what first made the servers unavailable.
  20. Microsoft's early changes weren't taking as expected. Engineers continued recovering frontend servers and adjusting traffic. Later updates described positive server-stability results after a patch, followed by better stability and capacity from traffic optimization.
  21. Engineers paused deployments, redistributed traffic and restarted servers. They tested alternative health checks and configuration changes, then checked stability before bringing more traffic back. A repair involving authentication or routing doesn't tell us that a defective update caused the original failure.
  22. The patch brought positive stability results on part of Microsoft's infrastructure. Engineers were expanding it. The later traffic changes were also being broadened across affected regions to achieve persistent recovery. Microsoft still hadn't announced full restoration.
  23. The public notice promised another update by 08:30 UTC. That was a target for information, rather than a restoration deadline. The notice retrieved afterward still carried its earlier authored timestamp and service-degradation status.
  24. Microsoft executive Charles Lamanna said there was no indication of malicious or cyber activity. Microsoft's public notice used similarly limited language. The company hasn't presented a completed forensic exclusion of every possible security cause.
  25. Australian Home Affairs Minister Tony Burke compared the failure to an update going wrong while relaying Microsoft's assessment. That comparison didn't identify the initiating cause. Microsoft's own investigation into the server failures continued.
  26. Microsoft's public notice lists twenty product and service entries. An earlier local account counted nineteen. The snapshots and overlapping categories don't show that exactly one more standalone application failed. The notice describes email-dependent features failing while other functions remain available.
  27. Most core Teams calls, meetings, group chats and channel messages remained available. Calendar scheduling and invitations could fail, along with some event and channel actions. Standard channels worked, and SharePoint users could still access stored files directly.
  28. Exchange Online was central to the disruption. People could lose mailbox access through web, desktop and mobile connections, miss their newest messages or face delayed delivery. Some Microsoft 365 administration pages failed to load, and the apps could lose their recent-files view.
  29. Education assignments and reading and speaking tools could be impaired. Copilot could fail to respond or access work email, calendars and files. Device enrollment and compliance checks, Planner tasks and To Do operations could also become unreliable.
  30. Microsoft Graph requests for email, calendars and contacts could time out, interfering with Teams management and notifications. Some Power Apps and Field Service mobile sign-ins failed intermittently. Universal Print could fail to submit jobs, while some Windows 365 customers using Purview Customer Key could lose connectivity.
  31. For Power Apps and Field Service, web access could provide an alternative. Already signed-in users could potentially avoid disruption by staying signed in and avoiding data clearing or reinstallation. That advice applied to those applications, with no universal fix for the outage.
  32. Security and compliance tools also lost functions. Defender for Office 365 could fail on Safe Links, Safe Attachments, quarantine releases and email remediation. Message traces, reporting and protection changes could be delayed. Defender XDR portal pages might not load.
  33. Purview labeling, data-loss prevention, authorization and classification were affected. Protected content, audit searches and legal discovery could fail. Fabric and Power BI could also struggle with sensitivity-labeled files or exports. These were protection-feature failures; they don't demonstrate that attackers breached customers.
  34. Removing a sensitivity label was described as a possible workaround only where an organization's data-protection policies allowed it. The outage didn't make it safe to disregard those policies.
  35. The Los Angeles County Sheriff's Department lost essential communications and directed inquiries to its official website. The LAPD and county district attorney also had disrupted email. Torrance said municipal services would continue. Colorado's Arapahoe Sheriff's Office reported delayed bond payments for prisoners.
  36. Miami Beach, Austin and Jacksonville reported email failures while keeping emergency services available. Baltimore County urged people to telephone departments. Pasadena, Fremont, Burbank and Santa Barbara also warned that email was down.
  37. Japan's government switched to physical documents after email disruption. The Philippines' Supreme Court warned of delayed email responses and transactions. New Zealand's foreign ministry lost email reception, including at diplomatic offices worldwide. Australian intelligence and federal-police organizations were also affected.
  38. Singapore's earlier assessment kept emergency calls to 995 and 999, Singpass and public officers' internal Teams communications available. GovTech warned that some replies could be delayed. Service NSW advised postponing service-centre visits and using online transactions where possible.
  39. The University of Iowa hospital network directed patients to its online portal after email and voicemail disruption. Several UK general practices warned of possible problems and directed urgent queries to the telephone rather than email or web forms.
  40. A travel account showed another email dependency. Sydney resident Livinia Drummond said a colleague's flight to Papua New Guinea was delayed because the captain's documents had arrived through Outlook. Passengers waited on a tarmac bus while someone brought printed copies on foot.
  41. That second-hand account didn't identify the carrier or the delay's length. IndiGo, Akasa Air and CemAir described email or system difficulties without reporting flight disruptions. Air India rerouted email and said operations and communication channels remained unaffected.
  42. IndiGo directed customers to its website or mobile app while incoming email support was impaired. Those different experiences show why an email outage can't be expanded into a claim of worldwide flight groundings.
  43. Hong Kong employees at Morgan Stanley and Goldman Sachs described losing email or Teams from logging on through lunch. Nomura staff also reported problems. In Raleigh, a medical-supply salesperson couldn't send quotes, and legal work was interrupted.
  44. Microsoft-connected AI tools had their own problems. OpenAI said new Microsoft connector connections might break and tools might fail. Anthropic said its connector's mail, calendar and search tools were failing for most requests, with Claude for Outlook also affected.
  45. Those connector notices didn't mean every part of ChatGPT or Claude was down. Anthropic also described incomplete connections and Outlook add-in failures. Neither company had provided a confirmed full restoration of these Microsoft-connected functions.
  46. Banks warned that criminals could exploit the confusion. Standard Chartered Singapore, Bank of Queensland and ING Australia cautioned about fake technical support, requests for personal information or one-time passwords, and attempts to gain remote access to devices.
  47. Workhorse Group postponed both its third-quarter earnings release and its results-and-business-outlook call because of the disruption. The call moved from November 12 to November 16 at 4:30 p.m. Eastern. The release will precede it.
  48. The patch and traffic changes have improved stability, but Microsoft is still extending them across affected regions to achieve persistent recovery. It hasn't given a time for full restoration. Microsoft has promised a post-incident explanation once the incident is mitigated, without setting a publication date.

译文更新于

近期播出