GitHub outage on October 6, 2026: Several services are degraded

GitHub reported an incident affecting GitHub for 3 hours 43 minutes on 6 October 2026, from 19:57 to 23:40 UTC.

github.com All times UTC

Resolved

Official incident reported by GitHub

Started: 19:57; 6 Oct 2026 UTC
Resolved: 23:40; 6 Oct 2026 UTC
Duration: 3h 43m; 3 hours 43 minutes
Impact: Critical; as rated by GitHub
Updates: 9; posted by GitHub

Timeline

All times UTC.

Official incident from GitHub

Several services are degraded

Resolved Critical impact 6 Oct 2026 19:57 UTC View on GitHub's status page

19:57 Official
Investigating
We are investigating reports of degraded performance for Pull Requests and Webhooks
20:04 Official
Investigating
Webhooks is operating normally.
20:12 Official
Investigating
Pull Requests is operating normally.
20:22 Official
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.
20:26 Official
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
20:57 Official
Investigating
All services are functioning normally except for enterprise migrations, which are still paused. They will resume soon.
21:29 Official
Investigating
We are working towards a mitigation that will allow us to resume processing enterprise migrations.
22:40 Official
Investigating
We are deploying a mitigation and plan to resume migrations shortly thereafter
23:40 Official
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.

"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.

All GitHub incidents Live GitHub status Every service we track

Does your product depend on GitHub?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Start monitoring free Check another address

Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.