Companies / GitHub / incidents

GitHub: Several services are degraded

Impact: criticalStatus: resolvedStarted Resolved (3.7 h)9 updatesSource: stspg.io (opens in new tab)
Summary

GitHub’s critical incident degraded Pull Requests and Webhooks and paused enterprise migrations, starting 2026-10-06 19:57 UTC and resolving 2026-10-06 23:40 UTC (3 h 43 min). GitHub reported an outage from 19:44 to 19:50 UTC affecting 12 services, with approximately 1.16 million failed requests. It identified GitHub Enterprise Importer as the trigger and reported deploying a mitigation.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: WebhooksPull Requests

Timeline of updates

  1. investigating

    We are investigating reports of degraded performance for Pull Requests and Webhooks

  2. investigating

    Webhooks is operating normally.

  3. investigating

    Pull Requests is operating normally.

  4. 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.

  5. monitoring

    The degradation has been mitigated. We are monitoring to ensure stability.

  6. investigating

    All services are functioning normally except for enterprise migrations, which are still paused. They will resume soon.

  7. investigating

    We are working towards a mitigation that will allow us to resume processing enterprise migrations.

  8. investigating

    We are deploying a mitigation and plan to resume migrations shortly thereafter

  9. 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.

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). GitHub profile · Recent GitHub incidents · Markdown · JSON