---
id: "INC-github-r05vk75c594j"
kind: "incident"
aliases: []
title: "GitHub: Degradation in repos contents API"
severity: "medium"
cvss: null
epss: null
exploited: false
status: "resolved"
category: "vendor"
products: [{"name": "GitHub", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["ci", "git", "github", "incident", "ops", "vendor"]
not_affected_if: []
published_at: "2026-09-04T22:02:15+00:00"
first_seen_at: "2026-10-23T19:12:22+00:00"
updated_at: "2026-10-23T21:50:49+00:00"
sources: [{"source": "statuspage", "url": "https://stspg.io/vhmsw2rhdcgv", "first_seen_at": "2026-10-23T19:12:22+00:00"}]
---

# GitHub: Degradation in repos contents API

## Affected

- vendor:GitHub affected ? fixed ?

## Timeline

- 2026-10-23T19:12:22+00:00 statuspage https://stspg.io/vhmsw2rhdcgv

## From the sources

On September 4, 2026, between approximately 21:45 and 22:07 UTC, some users experienced errors and elevated latency for repository operations. The incident was fully resolved at 22:23 UTC.The cause was a capacity change that spread one of our clusters across additional availability zones; our zone-aware traffic routing kept sending requests to the original zone for performance, overloading a small set of servers while the new capacity sat idle. We resolved the incident by reverting the change and letting traffic rebalance.We are improving per-zone capacity guarantees, cross-zone load-shedding, and pre-production testing of multi-zone changes to prevent recurrence.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_