Edition of Thursday 19 November 2026

Microsoft's Giant Outlook Outage

Comments on “Microsoft's Giant Outlook Outage”

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

A nearly 24-hour Exchange Online outage knocked out Outlook email for employees, businesses, and governments worldwide after Microsoft's failover systems spread a failure that began in Switzerland.

Read the original at theverge.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. 22 of 144 with a score of 0.67. The panel rated it highest on reader interest (0.80) and audience breadth (0.71), lowest on new information (0.50). The judges disagreed most on new information (spread 0.53), so the story is marked contested. Placed No. 22, No. 23 by score alone: close to “Microsoft blames monster email outage on software defect introduced in July fix”, No. 17 on Tuesday 17 November 2026 (−0.043). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Detailed, sourced account of a major cascading cloud outage with a concrete latent-bug root cause and recovery lessons; strong relevance to infrastructure builders, though primarily a news report from one reporter's sources.
AI judgeJudge 3gpt-5.6-luna
A technically detailed report on a major cascading Microsoft 365 outage, including latent lock contention, failover amplification, capacity loss, and recovery failure. It is highly relevant, but largely duplicates already-covered outage reporting.

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.67total under rubric v2.3Contestedjudges differ by 0.53 on new information

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

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.700.620.720.680.10+0.24+0.163
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.700.850.860.800.16+0.26+0.209
Audience breadthHow many people who build technology does it concern?0.520.800.820.710.30+0.13+0.093
Practical relevanceHow useful is it to someone who builds software or tech products?0.590.700.680.660.10+0.22+0.145
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.420.720.720.620.30+0.05+0.031
Technical depthHow technically substantive is it?0.720.650.680.680.07+0.05+0.034
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.710.600.180.500.53 , above the contested threshold+0.05+0.025
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.060.030.020.040.04−0.19−0.007
OverclaimDo the headline or conclusions claim more than the body supports?0.280.150.200.210.13−0.11−0.023
Sum of contributions+0.669
Claim-check penalty0.000
Total, as published0.669

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 #22 on Rubric, 19 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-19/22/"><img src="https://rubric.hrih.si/badge/2026-11-19/22.svg" alt="Ranked #22 on Rubric, 19 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 5 no source given · 3 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. No source givenNumber

    Microsoft's Outlook outage left users without access to Outlook email for nearly 24 hours.

    The article gives no link or citation for it.

    The article says

    “leaving employees, businesses, and many governments without access to Outlook emails for nearly 24 hours”

    The source says

    No source to compare with.

  2. No source givenNumber

    Within a couple of hours of the outage starting, more than 80 percent of Exchange servers were unresponsive.

    The article gives no link or citation for it.

    The article says

    “Within a couple of hours, more than 80 percent of Exchange servers were unresponsive”

    The source says

    No source to compare with.

  3. No source givenQuote

    Microsoft marked the outage as "sev0", its highest incident severity level, in its internal incident tracking system.

    The article gives no link or citation for it.

    The article says

    “Microsoft marked the outage as “sev0” in its internal incident tracking system, the highest level”

    The source says

    No source to compare with.

  4. Couldn’t checkQuote

    Charles Lamanna wrote that a latent defect caused servers to become overwhelmed and unresponsive under certain load conditions.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “A latent defect caused servers to become overwhelmed and unresponsive under certain load conditions”

    The source says

    No passage could be compared.

    Source cited by the article: x.com/clamanna/status/2122209697226948729

  5. No source givenDate

    The bug had been present on Microsoft 365 networking gateway servers since July without any impact.

    The article gives no link or citation for it.

    The article says

    “the bug had been sitting on Microsoft 365 networking gateway servers since July without any impact to servers”

    The source says

    No source to compare with.

  6. Couldn’t checkCausal conclusion

    Microsoft did not find the bug earlier because its load testing focused on weaker hardware with fewer cores, while the contention issue is worse on machines with more cores and newer hardware.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on weaker hardware with fewer cores”

    The source says

    No passage could be compared.

    Source cited by the article: x.com/clamanna/status/2122209697226948729

  7. Couldn’t checkNumber

    Fifteen hours before the outage, Microsoft Teams failed over to the main gateway supporting Exchange Online, while around 14 percent of that gateway's server capacity was out of service due to an unrelated issue.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “Fifteen hours before this Outlook outage began, Microsoft Teams failed over from an alternative networking gateway to the main gateway that supports Exchange Online”

    The source says

    No passage could be compared.

    Source cited by the article: x.com/clamanna/status/2122209697226948729

  8. No source givenNumber

    Microsoft's engineers' bridge call reached the maximum of 1,000 participants during the outage.

    The article gives no link or citation for it.

    The article says

    “at one point it hit the maximum of 1,000 participants”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 3 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 19 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's Giant Outlook Outage”

More on Rubric

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

  1. Score 0.78

    NoisyTCP