Incident with Git Operations and Pull Requests

Summary

Incident with Git Operations and Pull Requests

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.

• Started

  Nov 10, 2026 · 4:10 PM

• Resolved

  Nov 10, 2026 · 5:55 PM

• Duration

  1h 44m

• Severity

  Critical

• ◐

  Investigating

  Nov 10 · 4:10 PM GitHub

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

• ◐

  Investigating

  Nov 10 · 4:26 PM GitHub

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

• ◐

  Investigating

  Nov 10 · 4:31 PM GitHub

  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.

• ◐

  Investigating

  Nov 10 · 4:39 PM GitHub

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

• ◐

  Investigating

  Nov 10 · 5:07 PM GitHub

  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.

• ◐

  Investigating

  Nov 10 · 5:12 PM GitHub

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

• ◐

  Investigating

  Nov 10 · 5:28 PM GitHub

  Actions is operating normally.

• ◐

  Investigating

  Nov 10 · 5:46 PM GitHub

  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.

• ✓

  Resolved

  Nov 10 · 5:55 PM GitHub

  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.