Edition of Saturday 21 November 2026

Microsoft 365 outage of 12 and 13 November 2026

Comments on “Microsoft 365 outage of 12 and 13 November 2026”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Microsoft's preliminary post-incident report, summarised by 365Fanatic, attributes the 12–13 November Microsoft 365 outage, about 24 hours with Exchange Online hit hardest, to a latent defect in a Windows fix rolled out to its networking gateway servers in July. A Teams failover raised load while nearly 14% of capacity was offline, and the defect cascaded until over 80% of servers failed. Months-old changes blocked quick rollback, and test labs lacked high-core hardware. The report is preliminary; repair items are due 20 November.

Read the original at 365fanatic.com. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 12 of 118 with a score of 0.72. The panel rated it highest on substantiated (0.80) and reader interest (0.80), lowest on practical relevance (0.66). Placed No. 12, No. 10 by score alone: close to “Microsoft's Giant Outlook Outage”, No. 22 on Thursday 19 November 2026 (−0.033). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Major cloud outage with a detailed, primary-source post-incident summary of a gateway defect, cascade, and recovery; highly relevant to infrastructure and IT builders, though it is a summary with preliminary status.
AI judgeJudge 3gpt-5.6-luna
A well-supported outage postmortem with concrete failure mechanisms, recovery steps, timelines, and resilience lessons. It matters broadly to cloud, infrastructure, and enterprise IT builders, though it partly overlaps prior outage coverage.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.72total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.70
  • Reader interest0.80
  • Audience breadth0.77
  • Practical relevance0.66
  • Substantiated0.80
  • Technical depth0.74
  • New information0.75
  • Counts against: Promotional0.04
  • Counts against: Overclaim0.10

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.680.700.720.700.04+0.24+0.168
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.660.850.880.800.22+0.26+0.207
Audience breadthHow many people who build technology does it concern?0.680.800.820.770.14+0.13+0.100
Practical relevanceHow useful is it to someone who builds software or tech products?0.610.600.780.660.18+0.22+0.146
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.770.750.880.800.13+0.05+0.040
Technical depthHow technically substantive is it?0.790.700.740.740.09+0.05+0.037
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.780.900.580.750.32+0.05+0.038
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.050.050.030.040.02−0.19−0.008
OverclaimDo the headline or conclusions claim more than the body supports?0.120.150.040.100.11−0.11−0.011
Sum of contributions+0.715
Claim-check penalty0.000
Total, as published0.715

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #12 on Rubric, 21 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-21/12/"><img src="https://rubric.hrih.si/badge/2026-11-21/12.svg" alt="Ranked #12 on Rubric, 21 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 8 matches source. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. Matches sourceDate

    The Microsoft 365 outage began on 12 November 2026 at 16:20 UTC and impact ended on 13 November at 16:10 UTC.

    The cited source says the same thing.

    The article says

    “Start: Thursday 12 November 2026, 16:20 UTC. End of the impact: Friday 13 November, 16:10 UTC”

    The source says

    “Start: Thursday 12 November 2026, 16:20 UTC. End of the impact: Friday 13 November, 16:10 UTC”

    Source cited by the article: 365fanatic.com/wp-content/uploads/2026/11/postincidentreport.pdf

  2. Matches sourceCausal conclusion

    Microsoft's report names a software defect in its own networking gateway as the cause of the outage.

    The cited source says the same thing.

    The article says

    “The report names a software defect in Microsoft's own networking gateway as the cause”

    The source says

    “The report names a software defect in Microsoft's own networking gateway as the cause”

    Source cited by the article: 365fanatic.com/wp-content/uploads/2026/11/postincidentreport.pdf

  3. Matches sourceDate

    The defect came from a fix prepared specifically for Microsoft 365 networking gateway servers, which began rolling out in July and ran for more than three months without issues.

    The cited source says the same thing.

    The article says

    “The rollout began in July, went out safely and gradually worldwide, and ran for more than three months without issues”

    The source says

    “The defect came from a fix prepared specifically for Microsoft 365 networking gateway servers”

    Source cited by the article: 365fanatic.com/wp-content/uploads/2026/11/postincidentreport.pdf

  4. Matches sourceCausal conclusion

    About fifteen hours before the outage, Teams automatically failed over from the alternative gateway to the primary gateway that also serves Exchange Online, raising load.

    The cited source says the same thing.

    The article says

    “About fifteen hours before the outage, Teams automatically failed over from the alternative gateway to the primary one, which also serves Exchange Online”

    The source says

    “About fifteen hours before the outage, Teams automatically failed over from the alternative gateway to the primary one, which also serves Exchange Online”

    Source cited by the article: 365fanatic.com/wp-content/uploads/2026/11/postincidentreport.pdf

  5. Matches sourceNumber

    Nearly 14% of the gateway's server capacity was out of service because of an unrelated issue the day before.

    The cited source says the same thing.

    The article says

    “nearly 14% of the gateway's server capacity was out of service because of an unrelated issue the day before”

    The source says

    “At the same time nearly 14% of the gateway's server capacity was out of service because of an unrelated issue the day before”

    Source cited by the article: 365fanatic.com/wp-content/uploads/2026/11/postincidentreport.pdf

  6. Matches sourceNumber

    Within two hours the defect had hit across the server fleet, and at the lowest point more than 80% of servers did not respond.

    The cited source says the same thing.

    The article says

    “Within two hours the defect had hit across the fleet, and at the lowest point more than 80% of servers did not respond”

    The source says

    “Within two hours the defect had hit across the fleet, and at the lowest point more than 80% of servers did not respond”

    Source cited by the article: 365fanatic.com/wp-content/uploads/2026/11/postincidentreport.pdf

  7. Matches sourceDate

    Microsoft applied an update reverting the code path to the previously known good state to part of the capacity at 07:20 UTC on 13 November.

    The cited source says the same thing.

    The article says

    “It was applied to part of the capacity at 07:20 UTC on 13 November”

    The source says

    “Fri 13 Nov, 07:20: Mitigation found and applied to part of the capacity: an update that reverts the defective change”

    Source cited by the article: 365fanatic.com/wp-content/uploads/2026/11/postincidentreport.pdf

  8. Matches sourceDate

    Global webmail availability was back at expected levels at 14:17 UTC on 13 November.

    The cited source says the same thing.

    The article says

    “Fri 13 Nov, 14:17: Global webmail availability is back at expected levels”

    The source says

    “Fri 13 Nov, 14:17: Global webmail availability is back at expected levels”

    Source cited by the article: 365fanatic.com/wp-content/uploads/2026/11/postincidentreport.pdf

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 2 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 21 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Microsoft 365 outage of 12 and 13 November 2026”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.

  1. Score 0.78

    NoisyTCP