- Level
- confirmed
- Worst impact
- Degraded
- Components
- Git Operations, API Requests, Issues, Pull Requests
- Down Index
- 25of 100
What to do
Check whether you use GitHub Git Operations, API Requests, Issues, Pull Requests. 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 7m it lasted.
Anything that failed between 2026-05-27 12:10 UTC and 2026-05-27 13:16 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 3
- investigating
We are investigating reports of degraded performance for API Requests, Git Operations, Issues and Pull Requests
provider
- investigating
We're continuing to investigate degraded performance of Git operations, Issues and Pull requests.
provider
- resolved
On May 27, 2026, between 12:07 UTC and 13:16 UTC, users experienced degraded performance for Git operations, Pull Requests, Issues, GraphQL API, and related services on github.com. During this time, operations that depended on Git file servers experienced elevated error rates (3.5% of pushes via HTTPS and 0.2% of pushes via SSH failed; no fetches/clones failed). An internal analytics component generated unexpectedly high load, which caused CPU saturation on the underlying infrastructure. This led to cascading slowdowns and errors across services that depend on Git operations. The issue was mitigated by stopping the offending component. Services began recovering shortly after mitigation and were fully restored by 13:16 UTC. We are taking steps to add resource limits and kill switches for internal analytics components to prevent similar issues in the future.
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-bfd85e3a15
Is GitHub still down?
No, this incident was resolved 2026-05-27 13:16 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
1h 7m, from 2026-05-27 12:10 UTC to 2026-05-27 13:16 UTC, by the times GitHub posted.
What was affected?
GitHub named Git Operations, API Requests, Issues, Pull Requests.
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.