GitHub Availability October 2026
Comments on “GitHub Availability October 2026”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
GitHub's October availability report says 140 of 151 production services and 32 of 50 MySQL primaries ran in Azure Central US as of November 9, and compute across its nine clusters there more than doubled. Incidents continued. On October 7, a new database-routing machine published stale settings and sent writes to retired servers, with request failures peaking at 8.9% and 9.3% in two outages. Other incidents involved retry storms and connection-pool exhaustion.
Why it ranked
No. 8 of 123 with a score of 0.67. The panel rated it highest on new information (0.91) and substantiated (0.90), lowest on significance (0.58). Placed No. 8, No. 13 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- A detailed monthly incident and availability report from a major code host with specific failure mechanisms and mitigations; useful engineering postmortem content, though mainly about one company's operations.
- AI judgeJudge 3gpt-5.6-luna
- A detailed, first-party reliability report with quantified incidents, failure mechanisms, mitigations, capacity expansion, and operational lessons. It is highly actionable for infrastructure teams, broadly relevant to platform builders, and makes few unsupported claims.
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.3
- Significance0.58
- Reader interest0.73
- Audience breadth0.68
- Practical relevance0.71
- Substantiated0.90
- Technical depth0.78
- New information0.91
- Counts against: Promotional0.08
- Counts against: Overclaim0.13
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.67 | 0.35 | 0.72 | 0.58 | 0.37 | +0.24 | +0.139 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.74 | 0.55 | 0.90 | 0.73 | 0.35 | +0.26 | +0.190 |
| Audience breadthHow many people who build technology does it concern? | 0.61 | 0.60 | 0.82 | 0.68 | 0.22 | +0.13 | +0.088 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.74 | 0.50 | 0.88 | 0.71 | 0.38 | +0.22 | +0.155 |
| 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.92 | 0.80 | 0.98 | 0.90 | 0.18 | +0.05 | +0.045 |
| Technical depthHow technically substantive is it? | 0.82 | 0.70 | 0.82 | 0.78 | 0.12 | +0.05 | +0.039 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.88 | 0.90 | 0.96 | 0.91 | 0.08 | +0.05 | +0.046 |
| 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.05 | 0.15 | 0.03 | 0.08 | 0.12 | −0.19 | −0.015 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.18 | 0.15 | 0.05 | 0.13 | 0.13 | −0.11 | −0.014 |
| Sum of contributions | +0.673 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.673 | ||||||
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-14/8/"><img src="https://rubric.hrih.si/badge/2026-11-14/8.svg" alt="Ranked #8 on Rubric, 14 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 8 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenNumber
As of November 9, 140 of 151 production services and 32 of 50 MySQL primaries were running in Azure Central US.
The article gives no link or citation for it.
The article says “As of November 9, 140 of 151 production services and 32 of 50 MySQL primaries were running in Azure Central US”
The source says No source to compare with.
No source givenNumber
GitHub completed a compute expansion across all nine Central US Kubernetes clusters, more than doubling capacity.
The article gives no link or citation for it.
The article says “We also completed a compute expansion across all nine Central US Kubernetes clusters, more than doubling capacity”
The source says No source to compare with.
No source givenNumber
Migrated-service traffic has increased 82% since March.
The article gives no link or citation for it.
The article says “Migrated-service traffic has increased 82% since March”
The source says No source to compare with.
No source givenNumber
A NAT-gateway mitigation reduced usage by 85%; four production jobs failed during the change versus approximately 800 expected without it.
The article gives no link or citation for it.
The article says “A separate NAT-gateway mitigation reduced usage by 85%; four production jobs failed during the change, compared with approximately 800 expected without the mitigation”
The source says No source to compare with.
No source givenCausal conclusion
Moving a high-traffic Actions endpoint handling over 250 million requests per day to a more efficient service path reduced peak database reads by 85%.
The article gives no link or citation for it.
The article says “moved to a more efficient service path, reducing peak database reads by 85%”
The source says No source to compare with.
No source givenCausal conclusion
Requiring at least three characters before searching repository topics reduced slow or terminated queries for that pattern by approximately 98%.
The article gives no link or citation for it.
The article says “Requiring at least three characters before searching repository topics reduced slow or terminated queries for that pattern by approximately 98%”
The source says No source to compare with.
No source givenNumber
The October 29 Azure network disruption affected all three Central US availability zones and at least 34,128 signed-in users.
The article gives no link or citation for it.
The article says “An October 29 Azure network disruption affected all three Central US availability zones and at least 34,128 signed-in users”
The source says No source to compare with.
No source givenNumber
Web and API request failures peaked at 8.9% in the first October 7 outage and 9.3% in the second.
The article gives no link or citation for it.
The article says “Web and API request failures peaked at 8.9% in the first outage and 9.3% in the second”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 1 pts, not on front page
Recorded for context only, checked 15 Nov 2026, 20:44 UTC. It played no part in the ranking.