aiAI Status Monitor

Incident with Git Operations, Pull Requests and Actions

Major outageResolved · started Oct 7, 2026, 3:14 PM UTC (5d ago)
Share:Post to XRedditFacebookWhatsApp

Was GitHub Copilot down? GitHub reported “Incident with Git Operations, Pull Requests and Actions” on Oct 7, 2026, 3:14 PM UTC. Full timeline below. This incident affects GitHub Copilot — see live GitHub Copilot status. Source: official vendor status feed.

Timeline

  1. Oct 7, 2026, 4:25 PM UTC

    On October 7, 2026, GitHub had two outages of write operations with the same cause, totaling about 19 minutes. The first ran from 15:06 to 15:16 UTC (about 10 minutes) and the second from 16:52 to 17:01 UTC (about 9 minutes). In both windows, actions that save or change data failed across Git operations, pull requests, issues, GitHub Actions, the API, webhooks, sign-in and authentication, GitHub Apps and OAuth, code scanning, Codespaces, and Copilot. Reading data was largely unaffected. In the first outage, 5.6% of all web and API requests failed, peaking at 8.9%, and more than 12,000 organizations saw failed requests. Up to 26% of Git authentication requests failed, and 17% of Actions workflow runs failed with infrastructure errors. In the second outage, 6.2% of web and API requests failed, peaking at 9.3%, and more than 11,000 organizations were affected. Up to 25% of Git authentication requests failed, and 19% of Actions workflow runs failed. No databases experienced data loss, and operations retried after recovery succeeded. GitHub relies on an internal service that keeps track of which database servers should receive new and updated data. While replacing machines that run this service as part of regular maintenance, one of the new machines started with an outdated copy of its records, which still listed database servers we had already retired. When this node came online, it incorrectly modified routing configuration with the outdated records, routing write requests to non-existent database servers. Each outage ended when one of our established machines with correct configuration became the leader of the quorum and sent the correct configuration. After the first outage, we identified the new machine as the source and paused automated maintenance to stop it from being leader again. At 16:52 UTC, an automated maintenance task that did not honor the pause put it back in charge, and the outage happened again. We shut that machine down at 17:02 UTC and have since rem

  2. Oct 7, 2026, 4:23 PM UTC

    Git Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.

  3. Oct 7, 2026, 3:58 PM UTC

    We are seeing full recovery across all systems including Git Operations, Pull Requests and Actions. We are continuing to investigate the root cause of the disruption between 15:06 UTC and 15:16 UTC, and will share another update shortly.

  4. Oct 7, 2026, 3:56 PM UTC

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

  5. Oct 7, 2026, 3:49 PM UTC

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

  6. Oct 7, 2026, 3:49 PM UTC

    The degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.

  7. Oct 7, 2026, 3:47 PM UTC

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

  8. Oct 7, 2026, 3:41 PM UTC

    We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.

  9. Oct 7, 2026, 3:35 PM UTC

    Git Operations is experiencing degraded performance. We are continuing to investigate.

  10. Oct 7, 2026, 3:32 PM UTC

    Actions is operating normally.

  11. Oct 7, 2026, 3:31 PM UTC

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

  12. Oct 7, 2026, 3:27 PM UTC

    Webhooks is experiencing degraded performance. We are continuing to investigate.

  13. Oct 7, 2026, 3:27 PM UTC

    Git Operations is operating normally.

  14. Oct 7, 2026, 3:25 PM UTC

    Pull Requests is experiencing degraded performance. We are continuing to investigate.

  15. Oct 7, 2026, 3:24 PM UTC

    We observed widespread impact across GitHub services between 15:06 UTC and 15:16 UTC, and are investigating the root cause. We are seeing all systems recover, and will provide another update shortly.

  16. Oct 7, 2026, 3:21 PM UTC

    Git Operations is experiencing degraded performance. We are continuing to investigate.

  17. Oct 7, 2026, 3:16 PM UTC

    Webhooks is experiencing degraded availability. We are continuing to investigate.

  18. Oct 7, 2026, 3:15 PM UTC

    Issues is experiencing degraded performance. We are continuing to investigate.

  19. Oct 7, 2026, 3:14 PM UTC

    Webhooks is experiencing degraded performance. We are continuing to investigate.

  20. Oct 7, 2026, 3:14 PM UTC

    We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests

More GitHub Copilot outages