- Level
- confirmed
- Worst impact
- Major outage
- Components
- API Requests, Issues
- Down Index
- 43of 100
What to do
Check whether you use GitHub API Requests, 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 1h 18m it lasted.
Anything that failed between 2026-06-10 15:20 UTC and 2026-06-10 16:39 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 10
- investigating
We are investigating reports of impacted performance for some GitHub services.
provider
- investigating
API Requests is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
Issues is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
We are investigating issues related to sporadic authentication failures impacting approximately 15% of API traffic. We will continue to investigate and provide updates.
provider
- investigating
We continue to investigate issues related to sporadic authentication failures, impacting approximately 15% of API traffic. Further updates will be provided as we work to mitigate.
provider
- investigating
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
provider
- investigating
We continue to investigate issues related to sporadic authentication failures, impacting approximately 15% of API traffic. Erroneous 401 responses are causing app integrations to trigger authentication flows. We have identified a problematic component in our infrastructure and are working to mitigate.
provider
- investigating
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
provider
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
provider
- resolved
Between 15:05 UTC and 16:25 UTC, GitHub API services experienced degraded availability due to sporadic authentication failures affecting approximately 9% of requests. Customers experienced intermittent "logged out" behavior as erroneous 401 responses triggered repeated authentication flows in app integrations. Affected requests also experienced approximately 800ms of additional latency. A memcached proxy service rollout to our internal API infrastructure caused our authentication service to pick up an incorrect memcached host configuration, leading to intermittent authentication lookup failures. We mitigated the incident by deploying a configuration change to memcached to use the correct host. To prevent similar issues in the future, we plan to migrate our authentication system to the new memcached infrastructure to improve resilience and strengthen overall reliability posture.
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-e4ae2cecb0
Is GitHub still down?
No, this incident was resolved 2026-06-10 16:39 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
1h 18m, from 2026-06-10 15:20 UTC to 2026-06-10 16:39 UTC, by the times GitHub posted.
What was affected?
GitHub named API Requests, 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.