GitHub incident affecting Git Operations, Pull Requests and Actions is resolved

GitHub says an official service incident is resolved.

Oct 7, 2026
•
3 min read
Technobezz
GitHub incident affecting Git Operations, Pull Requests and Actions is resolved

Don't Miss the Good Stuff

Get tech news that matters delivered to your inbox.

Updated 12:25 p.m. Eastern on October 7, 2026

GitHub reported an incident with Git Operations, Pull Requests and Actions. The most recent official update marks the incident as resolved.

What is affected

The official incident covers Git Operations, Webhooks, Issues, Pull Requests and Actions.

Official update timeline

, marked Investigating

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

, marked Investigating

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

, marked Investigating

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

, marked Investigating

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

, marked Investigating

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

, marked Investigating

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.

, marked Investigating

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

, marked Investigating

Git Operations is operating normally.

, marked Investigating

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

, marked Investigating

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

, marked Investigating

Actions is operating normally.

, marked Investigating

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

, marked Investigating

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

, marked Investigating

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

, marked Investigating

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

, marked Monitoring

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

, marked Monitoring

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

, marked Monitoring

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.

, marked Monitoring

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.

, marked Resolved

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Read the official GitHub status page.

Track GitHub in the Technobezz status catalog.

Share