Exchange Online outage: Latent bug in July fix took down gateways
Comments on “Exchange Online outage: Latent bug in July fix took down gateways”
3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked
A faulty July software fix for Microsoft's network gateways caused the worldwide Exchange Online and Microsoft 365 outage on November 12 and 13, according to Microsoft's preliminary post-incident report as reported by heise online.
Why it ranked
No. 54 of 142 with a score of 0.62. The panel rated it highest on reader interest (0.74) and substantiated (0.67), lowest on practical relevance (0.60). Placed No. 54, No. 64 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.050). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Detailed postmortem of a major cloud outage with a concrete concurrency bug and testing gap; well-sourced via Microsoft's report, though it's a secondhand news write-up with a sovereignty-conference promo tail.
- AI judgeJudge 3gpt-5.6-luna
- A well-supported preliminary incident report explains lock contention, inadequate hardware testing, cascading failover, partition failure, and recovery limits. It is highly relevant to infrastructure operators, though much of the outage was already represented in recent coverage and the ending is mildly promotional.
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.62total under rubric v2.3
- Significance0.64
- Reader interest0.74
- Audience breadth0.66
- Practical relevance0.60
- Substantiated0.67
- Technical depth0.66
- New information0.65
- Counts against: Promotional0.13
- Counts against: Overclaim0.16
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.69 | 0.55 | 0.68 | 0.64 | 0.14 | +0.24 | +0.154 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.75 | 0.70 | 0.78 | 0.74 | 0.08 | +0.26 | +0.193 |
| Audience breadthHow many people who build technology does it concern? | 0.70 | 0.60 | 0.68 | 0.66 | 0.10 | +0.13 | +0.086 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.59 | 0.50 | 0.70 | 0.60 | 0.20 | +0.22 | +0.131 |
| 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.61 | 0.65 | 0.76 | 0.67 | 0.15 | +0.05 | +0.034 |
| Technical depthHow technically substantive is it? | 0.74 | 0.60 | 0.62 | 0.66 | 0.14 | +0.05 | +0.033 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.73 | 0.60 | 0.62 | 0.65 | 0.13 | +0.05 | +0.033 |
| 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.09 | 0.15 | 0.14 | 0.13 | 0.06 | −0.19 | −0.024 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.21 | 0.20 | 0.08 | 0.16 | 0.13 | −0.11 | −0.018 |
| Sum of contributions | +0.621 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.621 | ||||||
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.
<a href="https://rubric.hrih.si/editions/2026-11-18/54/"><img src="https://rubric.hrih.si/badge/2026-11-18/54.svg" alt="Ranked #54 on Rubric, 18 Nov 2026" width="245" height="28"></a>Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN —
Recorded for context only, checked 18 Nov 2026, 05:47 UTC. It played no part in the ranking.