Microsoft 365 Outage - Post Incident Report
9 comments · distributed, pdf
- Comments7
9 comments · distributed, pdf
Story details from Lobsters ↗ · linked article on tianyin.github.io.
Microsoft 365 Outage - Post Incident Report was first seen on Lobsters · Hottest on Nov 21, 2026. Since then it has appeared in 59 checks on 2 different days. Its best position was #6 of 25, reached on Nov 21, 19:22 UTC. It is #13 right now, slipping from #11 to #13 over the last 6 checks.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
▲ as reported by Lobsters.
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
Source with comment: https://www.teapaw.org/tianyin_xu/status/2122303460783935651 Tianyin Xu is PhD advisor of Jackson Clark, has also added the [incident to a project called SREGym](https://github.com/SREGym/SREGym/pull/1202), pretty cool.
Really interesting read, it shows how complicated a modern cloud system can get in terms of automated recovery systems and how those systems don't always do the right thing. I would be thinking about lead shedding as a mitigation. When you have more load coming in than a system can handle you're going to shed load…
Archived daily, weekly and monthly lists that include this entry.
Yes. As of Nov 22, 17:52 UTC it is #13, slipping from #11 to #13 over the last 6 checks.
#6 on Lobsters · Hottest, on Nov 21, 19:22 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Nov 21, 2026 and has been on the list on 2 days (59 checks) since.