Macroscope - Incident with Git Operations and Pull Requests – Incident details

All systems operational

Incident with Git Operations and Pull Requests

ResolvedMajor outage1 hour 44 minutes

Affected

Third Party

Operational from 4:10 PM to 4:26 PM, Degraded performance from 4:26 PM to 4:39 PM, Partial outage from 4:39 PM to 5:28 PM, Operational from 5:28 PM to 5:55 PM

GitHub Actions

Operational from 4:10 PM to 4:26 PM, Degraded performance from 4:26 PM to 4:39 PM, Partial outage from 4:39 PM to 5:28 PM, Operational from 5:28 PM to 5:55 PM

  • ResolvedUTC

    On November 10, 2026, from approximately 15:00 UTC to 17:55 UTC, GitHub experienced degraded performance affecting repository pages, pull requests, and GitHub Actions. Customers may have seen slow or failed page loads and delays processing pull request updates and merges. Some pull requests continued to display an earlier source-branch commit after the broader service degradation ended. GitHub Actions workflows were delayed for approximately 1.8% of events, peaking at about 7% between 16:30 and 16:50 UTC. Delays were typically 1.5 to 3.5 minutes, up to 10 minutes. Approximately 0.09% of pull request events did not start their workflows and needed to be re-triggered.

    The degradation resulted from overload in the shared infrastructure that supports Git operations. Recent changes increased background processing and the work required to compute pull request merges, adding pressure to the same systems used by customer-facing requests. We mitigated the incident by disabling a recent merge-processing optimization, pausing background analysis, and temporarily limiting lower-priority traffic. The temporary limits also restricted access to commit pages for users who were not signed in. Background processing continued to catch up after service health recovered.

    We have reduced repeated repository-analysis work and are adding workload-level concurrency controls to better protect customer-facing requests. We are also improving our procedures for safely reducing background load and making pull request synchronization more resilient to temporary failures.

  • UpdateUTC

    We continue to investigate elevated response times for Git operations and pull requests. Actions workflows are recovering. Pull request processing has shown some improvement, but users continue to experience delays and failures. We’re monitoring the impact and working to restore normal service.

  • UpdateUTC

    Actions is operating normally.

  • UpdateUTC

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

  • UpdateUTC

    We continue to investigate elevated response times for Git operations and pull requests. Some pull-request processing and Actions workflows are improving, but delays and failures persist. We're monitoring the impact and working to restore normal service.

  • UpdateUTC

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

  • UpdateUTC

    We're investigating elevated response times for Git operations and pull requests. GitHub Actions workflows that are triggered from Pull Requests are delayed. We're working to mitigate the impact and will share updates as we learn more.

  • UpdateUTC

    Actions and Pull Requests are experiencing degraded availability. We are continuing to investigate.

  • InvestigatingUTC

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