GitHub experienced a minor incident on April 17, 2026 affecting Issues, lasting 21m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 17, 2026, 02:56 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Apr 17, 2026, 02:56 PM UTC
Issues is experiencing degraded performance. We are continuing to investigate.
- investigating Apr 17, 2026, 02:57 PM UTC
We are experiencing an issue that impacts approximately 10% of traffic to the web, resulting in slow and failed calls. We are investigating and will continue to post updates as we work toward mitigation.
- investigating Apr 17, 2026, 03:08 PM UTC
We have isolated a problematic component in our infrastructure and are working to mitigate. We will continue to post updates as we work toward resolution.
- monitoring Apr 17, 2026, 03:18 PM UTC
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
- resolved Apr 17, 2026, 03:18 PM UTC
On April 17, 2026, between 14:46 UTC and 15:12 UTC, users experienced a degraded web experience on GitHub.com. During this time, approximately 1.5% of web requests resulted in errors, with some users encountering slow page loads or failed requests. The issue was caused by capacity saturation of a caching component in one of our data center regions. We mitigated the issue by redirecting traffic to an unaffected region and rolling back a recent deployment. The incident was fully resolved at 15:18 UTC. We are taking steps to provide appropriate capacity for this caching path to prevent recurrence.