- Level
- confirmed
- Worst impact
- Major outage
- Components
- Git Operations, Webhooks, Issues, Pull Requests, Actions, Packages, Pages, Codespaces
- Down Index
- 52of 100
What to do
Check whether you use GitHub Git Operations, Webhooks, Issues, Pull Requests and 4 more. 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 55m it lasted.
Anything that failed between 2026-05-04 15:45 UTC and 2026-05-04 16:40 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 19
- investigating
We are investigating reports of degraded performance for Issues and Webhooks
provider
- investigating
We are investigating Increased latency and timeouts across multiple GitHub services.
provider
- investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Packages is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Pull Requests is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
Actions is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Codespaces is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Pages is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Git Operations is operating normally.
provider
- investigating
Actions and Packages are operating normally.
provider
- investigating
Latency across services has normalized. We are continuing to investigate the root cause and prevent reoccurrence.
provider
- investigating
Pages is operating normally.
provider
- investigating
Pull Requests is operating normally.
provider
- investigating
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
provider
- investigating
The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.
provider
- investigating
Webhooks is operating normally.
provider
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
provider
- resolved
On 2026-05-04 at 3:37:17 PM UTC we detected increased latency on issues resulting in timeouts, and elevated 500 errors on webhooks. A scheduled workload drove high utilization on the primary host of a critical datastore, saturating the connection pool. We paused the job to mitigate the problem at 4:40:05 PM UTC and have implemented measures 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-64d7d2f501
Is GitHub still down?
No, this incident was resolved 2026-05-04 16:40 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
55m, from 2026-05-04 15:45 UTC to 2026-05-04 16:40 UTC, by the times GitHub posted.
What was affected?
GitHub named Git Operations, Webhooks, Issues, Pull Requests and 4 more.
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.