- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Webhooks, Issues, Pull Requests, Actions
- Down Index
- 36of 100
What to do
Check whether you use GitHub Webhooks, Issues, Pull Requests, Actions. 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 45m it lasted.
Anything that failed between 2026-07-23 07:53 UTC and 2026-07-23 09: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 degraded availability for Actions, Issues and Webhooks
provider
- investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
We're currently investigating latency across multiple services. This can show as Actions jobs taking longer to start, Issues search serving stale results, and other listed services being similarly impacted.
provider
- investigating
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
provider
- investigating
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
provider
- investigating
We identified the source of latency affecting multiple services and applied a fix. Issues and Actions are recovering, and remaining affected services are seeing improvement as processing backlogs clear. We are actively monitoring recovery across all services.
provider
- investigating
The degradation affecting Pull Requests 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 July 23, 2026, between 07:08 and 09:39 UTC, several services experienced delays: 8% of actions workflow runs experienced an average run start delay of 10 minutes, 5% of webhook deliveries exceeded SLO, and code scanning, repos, notifications, issues and pull requests experienced increased latency over the life of the incident. The root cause of the incident was a node of our background job processing system which did not recover after entering scheduled host maintenance. The incident was mitigated by identifying the problematic shard and restoring its correct state, after which queue backlogs drained and services recovered. To speed mitigation, we have added monitors for nodes in this unhealthy state after maintenance operations. To prevent future recurrence, we are adapting our lifecycle automation to verify host rejoin after a scheduled reboot.
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-cc5053893e
Is GitHub still down?
No, this incident was resolved 2026-07-23 09:39 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
1h 45m, from 2026-07-23 07:53 UTC to 2026-07-23 09:39 UTC, by the times GitHub posted.
What was affected?
GitHub named Webhooks, Issues, Pull Requests, Actions.
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.