GlobalOutageMap
← Live dashboard
GitHub logoGitHub

Incident with Git Operations, Pull Requests and Actions

ResolvedcriticalOfficial source confirmedSpecific component onlyFirst recorded update Oct 7, 2026, 03:14 PM · Resolved Oct 7, 2026, 04:25 PM

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

GitHub live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with GitHub now? Check the current status

Affected services

ActionsWebhooksGit OperationsPull RequestsIssues

Updates (20)

  1. Oct 7, 2026, 04:25 PM
    Incident with Git Operations, Pull Requests and Actions

    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 organiz

    GitHub ↗
  2. Oct 7, 2026, 04:23 PM
    Incident with Git Operations, Pull Requests and Actions

    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.

    GitHub ↗
  3. Oct 7, 2026, 03:58 PM
    Incident with Git Operations, Pull Requests and Actions

    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.

    GitHub ↗
  4. Oct 7, 2026, 03:56 PM
    Incident with Git Operations, Pull Requests and Actions

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

    GitHub ↗
  5. Oct 7, 2026, 03:49 PM
    Incident with Git Operations, Pull Requests and Actions

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

    GitHub ↗
  6. Oct 7, 2026, 03:49 PM
    Incident with Git Operations, Pull Requests and Actions

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

    GitHub ↗
  7. Oct 7, 2026, 03:47 PM
    Incident with Git Operations, Pull Requests and Actions

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

    GitHub ↗
  8. Oct 7, 2026, 03:41 PM
    Incident with Git Operations, Pull Requests and Actions

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

    GitHub ↗
  9. Oct 7, 2026, 03:35 PM
    Incident with Git Operations, Pull Requests and Actions

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

    GitHub ↗
  10. Oct 7, 2026, 03:32 PM
    Incident with Git Operations, Pull Requests and Actions

    Actions is operating normally.

    GitHub ↗
  11. Oct 7, 2026, 03:31 PM
    Incident with Git Operations, Pull Requests and Actions

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

    GitHub ↗
  12. Oct 7, 2026, 03:27 PM
    Incident with Git Operations, Pull Requests and Actions

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

    GitHub ↗
  13. Oct 7, 2026, 03:27 PM
    Incident with Git Operations, Pull Requests and Actions

    Git Operations is operating normally.

    GitHub ↗
  14. Oct 7, 2026, 03:25 PM
    Incident with Git Operations, Pull Requests and Actions

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

    GitHub ↗
  15. Oct 7, 2026, 03:24 PM
    Incident with Git Operations, Pull Requests and Actions

    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.

    GitHub ↗
  16. Oct 7, 2026, 03:21 PM
    Incident with Git Operations, Pull Requests and Actions

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

    GitHub ↗
  17. Oct 7, 2026, 03:16 PM
    Incident with Git Operations, Pull Requests and Actions

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

    GitHub ↗
  18. Oct 7, 2026, 03:15 PM
    Incident with Git Operations, Pull Requests and Actions

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

    GitHub ↗
  19. Oct 7, 2026, 03:14 PM
    Incident with Git Operations, Pull Requests and Actions

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

    GitHub ↗
  20. Oct 7, 2026, 03:14 PM
    Incident with Git Operations, Pull Requests and Actions

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

    GitHub ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow GitHub's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.