‹ Back to incident history

Incident with Git Operations and Pull Requests

ResolvedCritical outageGitHub
Wednesday, November 11, 2026 00:10 – Wednesday, November 11, 2026 01:55 (1 hr 44 min)
Affected components
Pull Requests
Actions
Updates
ResolvedWednesday, November 11, 2026 01:55

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

InvestigatingWednesday, November 11, 2026 01:46

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.

InvestigatingWednesday, November 11, 2026 01:28

Actions is operating normally.

InvestigatingWednesday, November 11, 2026 01:12

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

InvestigatingWednesday, November 11, 2026 01:07

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.

InvestigatingWednesday, November 11, 2026 00:39

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

InvestigatingWednesday, November 11, 2026 00:31

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.

InvestigatingWednesday, November 11, 2026 00:26

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

InvestigatingWednesday, November 11, 2026 00:10

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

Incident data from the GitHub official status page:Read the official incident

About this data

Where does the incident data for GitHub come from?

Data comes from the GitHub official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.

How do I read the component status bars?

Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.

Why is history missing for some services?

Only services with a public official status page are included.

How is duration calculated?

Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.

See the full service list and live status in the status overview