Degradation in repos contents API

GitHub

1. 4 Sep 22:23 UTCResolvedOn 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.
2. 4 Sep 22:02 UTCInvestigatingWe are investigating reports of impacted performance for some GitHub services.

No field changes in the recorded history.

Cite this recorded revision to keep the same title, summary, facts and links when the page changes.

A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.

• Service status now: every provider ChangeIntel reads, with ongoing incidents first.
• Status RSS feed: new and ended incidents as they happen.
• Everything about GitHub: its changes, known issues and incidents on one timeline.