- Level
- confirmed
- Worst impact
- Major outage
- Components
- Issues, Pull Requests, Actions, Packages
- Regions
- us
- Down Index
- 51of 100
What to do
Check whether you use GitHub Issues, Pull Requests, Actions, Packages in us. 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 6h 16m it lasted.
Anything that failed between 2026-04-27 16:31 UTC and 2026-04-27 22:46 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 15
- investigating
We are investigating reports of degraded performance for Actions
provider
- investigating
Customers across GitHub are experiencing failures with searches. Examples include: workflow run failures, projects failing to load, and timed out search requests. This is due to an ongoing infrastructure issue that we have been investigating.
provider
- investigating
Issues 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 performance. We are continuing to investigate.
provider
- investigating
Users are experiencing intermittent failures to view issues, pull requests, projects and Actions workflow runs. We are still investigating and attempting mitigations. We will provide further updates.
provider
- investigating
We're continuing to see connectivity issues reaching elasticsearch. Impact on downstream services will be intermittent as we find the root cause
provider
- investigating
Pull Requests is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
We have identified the source of the additional load causing stress on our ElasticSearch clusters. We have disabled the source of that load and are seeing signs of recovery
provider
- investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
We've applied a mitigation and continuing to monitor
provider
- monitoring
The degradation affecting Actions, Issues, Packages and Pull Requests has been mitigated. We are monitoring to ensure stability.
provider
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
provider
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
provider
- resolved
On April 27, 2026 between 16:15 UTC and 22:46 UTC, GitHub search services experienced degraded connectivity due to saturation of the load balancing tier deployed in front of our search infrastructure. This resulted in intermittent failures for services relying on our search data including Issues, Pull Requests, Projects, Repositories, Actions, Package Registry and Dependabot Alerts. The impact was varied by search target, with services seeing up to 65% of searches timing out or returning an error between 16:15 UTC and 18:00 UTC. We detected the drop in search results through our ongoing monitoring and declared an incident at 16:21 UTC when we determined the issues would not self-heal. We tracked the incident as mitigated as of 21:33 UTC and monitored the systems until 22:46 UTC when we declared the incident resolved. Our existing monitoring did not classify the increased scraping as a risk and this dimension of the incident was only discovered while working to mitigate. The saturation was caused by a large influx of anonymous distributed scraping traffic that was crafted to avoid our public API rate limits. This scraping traffic made up 30% of the day’s total search traffic, but it was concentrated within a four-hour period. The traffic originated from over 600,000 Unique IP addresses, with matching actor information across the board. To mitigate, we immediately focused on relieving pressure from the load balancers while simultaneously working on scaling the load balancing tier, blocking the anomalous traffic and applying tuning to the balancers to fully resolve the incident. Looking ahead, we’ve not only scaled the load balancer tier, but applied optimizations to improve our connection handling and re-use to reduce the possibility that a saturation event like this can re-occur. We’ve also added new monitors and controls within the platform to allow us to restrict anonymous traffic to mitigate the impact to our registered users.
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-9d8f9f20a8
Is GitHub still down?
No, this incident was resolved 2026-04-27 22:46 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
6h 16m, from 2026-04-27 16:31 UTC to 2026-04-27 22:46 UTC, by the times GitHub posted.
What was affected?
GitHub named Issues, Pull Requests, Actions, Packages in us.
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.