请不要在回答技术问题时复制粘贴 AI 生成的内容
This topic created in 1218 days ago, the information mentioned may be changed or developed.
 | 1 outtime OP 更新：现在好了 |
 | 2 BeautifulSoap Jan 25, 2023 via Android 并没有好，已经摸鱼 20 多分钟了，收拾下准备提前下班（狂喜 |
| 3 outtime OP @BeautifulSoap 哈哈哈哈是的，只是间歇性正常一下 |
 | 4 KMpAn8Obw1QhPoEP Jan 25, 2023 via Android office365 已挂 |
 | 5 hiugo Jan 25, 2023 微软也学阿里云是吧，整个机房离线 |
 | 6 haotian22 Jan 25, 2023 MS 的 Azure 机房有问题，自己服务大规模翻车 Team Outlook Onedrive Github 等都有不同程度影响 |
 | 7 kkk9 Jan 25, 2023  1 过年顶班的临时工不小心把主路由的电源拔了 |
 | 8 leonunix Jan 25, 2023 office 365 都挂了。真的可以回家了 |
 | 9 azure2023us Jan 25, 2023 |
 | 11 jimyag Jan 25, 2023 应该只是某些设备不能用，15.56 时候电脑不能使用了，但是手机依然可以用 https://imgloc.com/i/bNXAc |
 | 12 Ranying Jan 25, 2023 昨天 Figma 也断了一会。 |
 | 13 buwenhe Jan 25, 2023 Azure 被 DDOS 了 |
 | 14 hongzhng Jan 26, 2023 -- from Azure Status page Summary of Impact: Between 07:05 UTC and 09:45 UTC on 25 January 2023, customers experienced issues with networking connectivity, manifesting as network latency and/or timeouts when attempting to connect to Azure resources in Public Azure regions, as well as other Microsoft services including Microsoft 365 and PowerBI. Preliminary Root Cause: We determined that a change made to the Microsoft Wide Area Network (WAN) impacted connectivity between clients on the internet to Azure, connectivity between services within regions, as well as ExpressRoute connections. Mitigation: We identified a recent change to WAN as the underlying cause and have rolled back this change. Networking telemetry shows recovery from 09:00 UTC onwards across all regions and services, with the final networking equipment recovering at 09:35 UTC. Most impacted Microsoft services automatically recovered once network connectivity was restored, and we worked to recover the remaining impacted services. |
 | 15 haikouwang Jan 26, 2023 我差点想说开个代理 [ https://go.huyun.cf ] 上 github / o365 吧，结果原来是 az 自己炸了 |
Select Language