Provider
GitHubIncident detail
Several services are degraded
Timeline window
to
Get alerted the next time GitHub breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Investigating
We are investigating reports of degraded performance for Pull Requests and Webhooks
Investigating
Webhooks is operating normally.
Investigating
Pull Requests is operating normally.
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.
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
Investigating
All services are functioning normally except for enterprise migrations, which are still paused. They will resume soon.
Investigating
We are working towards a mitigation that will allow us to resume processing enterprise migrations.
Investigating
We are deploying a mitigation and plan to resume migrations shortly thereafter
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.<br /><br />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.
Keep exploring
More from GitHub
Neighboring incidents on GitHub's timeline and the rest of their record on OutageDeck.
← Older incident
Disruption with some GitHub services
Newer incident →
Incident with Git Operations, Pull Requests and Actions