在澳大利亚，人们称之为“微软长周末”——这次故障影响范围如此之广，以至于依赖雷德蒙德在线服务（尤其是Exchange Online）的机构周五几乎成了报废之日。据《注册者报》昨日报道，故障始于周四大约18:00 UTC，导致Microsoft 365用户无法访问电子邮件、参加Teams会议、使用云电脑、咨询Copilot，或充分访问另外15项托管服务。
In Australia, they’re calling it the “Microsoft long weekend” – an outage so pervasive it’s just about made Friday a write-off at organizations which rely on Redmond’s online services, especially Exchange Online. As The reported yesterday, the outage started on Thursday at around 18:00 UTC and saw Microsoft 365 users unable to access email, attend Teams meetings, use cloud PCs, consult Copilot, or enjoy full access to another 15 hosted services.
这家软件巨头表示，故障影响的是“与Exchange Online和电子邮件服务交互的Microsoft 365服务”。不需要Exchange Online的服务仍能正常运行。这家软件巨头最初将故障归咎于一个神秘的“导致服务器无法通过自动健康检查并变得不可用的问题”。微软曾以为找到了修复方法，但很快承认“迄今采取的措施未能提供预期的缓解”。
The software giant says the outage impacts Microsoft 365 services “that interact with Exchange Online and email services.”Services that don’t need Exchange Online remain functional. The software giant initially blamed the outage on a mysterious “problem that's causing servers to fail automated health checks and become unavailable.”Microsoft thought it found a fix but quickly admitted “Actions taken thus far have not provided the anticipated relief.”
在随后的几个小时里，情况并未明显好转，微软仍在努力恢复服务。该公司还改变了讨论网络攻击是否是故障原因时所用的措辞。截至04:11 UTC，该公司表示未能发现“这是恶意活动所致的任何迹象”。一份时间戳为05:46 UTC的更新称“截至目前，我们不知有任何恶意活动导致此次事件”。微软的状态页面仅包含公司最近的一条更新，但其RSS订阅源保留了每一条消息。
In the hours since, the situation has not improved markedly, and Microsoft is still struggling to restore service. It has also changed the language it uses when discussing the possibility that a cyberattack is the reason for the outage. As of 04:11 UTC, the company said it could find “no indication this is the result of malicious activity.”An update time-stamped 05:46 UTC stated “As of now, we are not aware of any malicious activity that is causing this incident.”Microsoft’s status page includes only the company’s most recent update, but its RSS feed preserves each missive.
该订阅源讲述了一个悲惨的故事，我们将其提炼为低光点并按时间顺序呈现如下：我们正在尽可能应用基础设施容量改进，以帮助支持正在上线的地区的流量；我们已监控了为改善服务性而应用的更改的状态，并确认该更改未按预期生效；我们正在审查流量流向和受影响的基础设施，以找出优化路由的机会。
That feed tells a tale of woe that we have distilled into lowlights and present in chronological order: We’re applying infrastructure capacity improvements where possible in an effort to help support traffic in regions coming online; We’ve monitored the status of the changes applied to improve serviceability and confirmed that change is not taking as expected; We’re reviewing traffic flows and affected infrastructure to identify opportunities to optimize routing.
这包括核查服务故障的原因，以便制定具体措施提升稳定性；我们正在识别可应用的替代工作流，以在持续的流量管理失衡情况下增加容量；我们观察到，在已应用这些调整的地区出现部分恢复；然而，这些措施并未带来持续恢复；我们目前正在采取的措施包括扩大虚拟机规模，以增加容量并降低负载。然而，我们遇到了虚拟机陷入故障状态的问题，导致更改无法按预期同步。
This includes verifying the reasons for service failures so we can develop specific actions to improve stability; We’re identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances; We're observing partial recovery across regions in which we've applied these adjustments; however, these actions aren't resulting in sustained recovery; Current actions we are taking include scaling up virtual machines to increase capacity and reduce load. However, we are encountering issues with the machines being stuck in a bad state, preventing our changes from syncing as expected.
微软最新的状态更新显示，这场故障短期内不会结束。“我们正在继续推进多个工作流，以确定流量激增的根本原因，并提升后端服务器的可恢复性，”微软写道。“我们正在采取审慎的方法，识别并修复受影响的基础设施，以提高确认已开发的更改已应用的能力。我们正在跟踪该方法的结果，以验证服务器是否呈现出预期的恢复和性能。”
Microsoft’s latest status update doesn’t suggest this will be over any time soon. “We’re continuing to pursue multiple workstreams to pinpoint the underlying cause of the traffic influx and advance the recoverability of the backend servers,” Microsoft wrote. “We’re taking a measured approach to identify and repair affected infrastructure to improve the ability to confirm the developed changes were applied. We’re tracking the results of this approach to verify the servers are showing the anticipated recovery and performance intended.”
希望澳大利亚及附近时区的其他国家不会是唯一获得非计划长周末的地方。® 更新于协调世界时12:00 协调世界时12:00的最新状态更新承认，用户仍“无法连接到多个微软365服务”。更新于协调世界时13:00 微软表示，在受影响地区看到持续的恢复进展，北美地区“现在观察到更广泛的改善”，欧洲大部分地区“持续改善”。
Hopefully, Australia and other countries in nearby time zones won’t be the only ones to get an unscheduled long weekend. ® Updated to add at 1200 UTC The latest status update at 12:00 PM UTC admits users are still "unable to connect to multiple Microsoft 365 services." Updated to add at 1300 UTC Microsoft says it's seeing continued recovery progress across affected regions, with "broader improvements now observed in North America and sustained improvements across much of Europe. We're also seeing encouraging recovery signals in Asia Pacific, although some users may continue to experience intermittent access issues or delayed email delivery as mitigation progresses across the remaining affected infrastructure."
我们还在亚太地区看到令人鼓舞的恢复信号，尽管在剩余受影响基础设施的缓解工作推进过程中，一些用户可能仍会持续遇到间歇性访问问题或电子邮件投递延迟。更新于协调世界时21时44分：雷德蒙德仍声称情况正在稳定中，尚未给出一切恢复正常的预计时间。“随着基础设施稳定下来，我们仍在清理排队的消息并重新平衡流量，因此客户可能会看到登录/访问情况有所改善，而投递和处理仍在继续赶上，”该公司在其状态页面上写道。
Updated to add at 2144 UTC Redmond still claims that the situation is in the process of stabilizing with no estimate for when everything might get back to normal. "As infrastructure stabilizes, we're still draining queued messages and rebalancing traffic, so customers may see improved sign-in/access while delivery and processing continue to catch up," it writes on its status page. "We do not have an ETA for full recovery yet.
“我们目前尚未有完全恢复的预计时间。服务访问可能在邮件流量完全恢复正常之前就恢复。”该公司于协调世界时20时02分发布了最新状态更新，并承诺将于周六协调世界时0时00分前再次更新。
Service access can recover before mail flow fully normalizes." The company issued its latest status update at 2002 UTC and promises another update by Saturday at 0000 UTC.