- Level
- confirmed
- Worst impact
- Major outage
- Components
- Webhooks, Pull Requests
- Regions
- us
- Down Index
- 46of 100
What to do
Check whether you use GitHub Webhooks, Pull Requests 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 3h 43m it lasted.
Anything that failed between 2026-10-06 19:57 UTC and 2026-10-06 23: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.
Root cause
The incident was triggered by GitHub Enterprise Importer (GEI) making multiple, long duration queries which saturated a database connection pool.
Category: Capacity
Read the postmortemUpdates from GitHub 9
- investigating
We are investigating reports of degraded performance for Pull Requests and Webhooks
provider
- investigating
Webhooks is operating normally.
provider
- investigating
Pull Requests is operating normally.
provider
- investigating
A number of services including issues, pull requests, and webhooks, were briefly degraded, but have now recovered. Enterprise migrations are paused while we validate causes and mitigations.
provider
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
provider
- investigating
All services are functioning normally except for enterprise migrations, which are still paused. They will resume soon.
provider
- investigating
We are working towards a mitigation that will allow us to resume processing enterprise migrations.
provider
- investigating
We are deploying a mitigation and plan to resume migrations shortly thereafter
provider
- resolved
On October 6, 2026, from 19:44 to 19:50 UTC, GitHub experienced a service outage with elevated error rates peaking at 1.30% of all requests, totaling approximately 1.16 million failed requests. This impacted 12 services across GitHub, including Pull Requests, Webhooks, Repos, OAuth, Git over SSH, Codespaces, and Gists. The incident was triggered by GitHub Enterprise Importer (GEI) making multiple, long duration queries which saturated a database connection pool. Recovery was seen at approximately 19:50 UTC once the migration's calls stopped; GEI migrations were reenabled at 23:32 UTC after a code fix was merged. We have completed a detailed root-cause review and are implementing improved database-health safeguards. We will continue to review and add additional safeguards to prevent future 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-5edfa898c0
Is GitHub still down?
No, this incident was resolved 2026-10-06 23:40 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
3h 43m, from 2026-10-06 19:57 UTC to 2026-10-06 23:40 UTC, by the times GitHub posted.
What was affected?
GitHub named Webhooks, Pull Requests in us.
What caused it?
Capacity. GitHub wrote: "The incident was triggered by GitHub Enterprise Importer (GEI) making multiple, long duration queries which saturated a database connection pool." The postmortem: https://stspg.io/w3rcssslq22w
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.