- Level
- confirmed
- Worst impact
- Degraded
- Components
- Issues
- Down Index
- 17of 100
What to do
Check whether you use GitHub Issues. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 22m it lasted.
Anything that failed between 2026-04-17 14:56 UTC and 2026-04-17 15:18 UTC may need a replay.Subscribe to GitHub's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from GitHub 6
- investigating
We are investigating reports of impacted performance for some GitHub services.
provider
- investigating
Issues is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
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.
provider
- investigating
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.
provider
- monitoring
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
provider
- resolved
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-a9672cb771
Is GitHub still down?
No, this incident was resolved 2026-04-17 15:18 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
22m, from 2026-04-17 14:56 UTC to 2026-04-17 15:18 UTC, by the times GitHub posted.
What was affected?
GitHub named Issues.
What caused it?
GitHub hasn't published a root cause. If it does, it shows here.
Where does this come from?
GitHub's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.