← Back to GitHub History
minor✓ Resolved

Degradation in repos contents API

GitHub•
Status
resolved
Duration
21m
Updates
2
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
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.<br /><br />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.<br /><br />We are improving per-zone capacity guarantees, cross-zone load-shedding, and pre-production testing of multi-zone changes to prevent recurrence.
investigating
We are investigating reports of impacted performance for some GitHub services.

📊 TECHNICAL DETAILS

Internal ID
ae38e89d-0a98-4678-a7a0-31a264dcf221
External ID
r05vk75c594j
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
21m
Total Duration
2
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed