GitHub·

GitHub: Incident with Git Operations and Pull Requests

GitHub reported "Incident with Git Operations and Pull Requests" on its status page.

ResolvedEnded Nov 10, 2026
Security:
No determination
Started
Nov 10, 2026, 16:10 UTC
Provider marked resolved
Nov 10, 2026, 17:55 UTC
Duration
1 h 44 min
Full recovery
Not documented
Geographic scope
Not stated by the provider
Last verified
1 source

Created automatically from GitHub's official status updates and kept up to date from them. Not yet reviewed by an editor. Causes and security findings are added only after review.

What happened

Kind of failure
Unknown
Sector
Code hosting
Provider report
None found
Status and recovery
Resolved. The provider marked the incident resolved. Recovery beyond that is not separately documented.[1]

What caused it?

Root cause: Unknown

The provider has not stated a cause in its status updates.[1]

Provider report: None found. No incident report found yet. The archive checks for one automatically.[1]

Was it malicious?

No determination

The provider's status updates do not address malicious activity.[1]

How the failure happened

The provider's updates do not describe a step-by-step sequence.

Explanation

Both versions summarize the sourced claims on this page. Our own interpretation appears only under Independent analysis.

Plain language: what happened and why people were affected.

GitHub reported a problem: "Incident with Git Operations and Pull Requests".

Confirmed and unknown

Still unknown

  • The cause: the provider has not stated one.
  • Whether the provider will publish an incident report.

Timeline

Times in UTC. Dates without a time mean the sources give no time. Only events a source documents are listed.

  1. First observedNot documented
  2. AcknowledgedNov 10, 2026, 16:10 UTC
  3. MitigationNot documented
  4. RecoveryNot documented
  5. ResolvedNov 10, 2026, 17:55 UTC
  6. Incident reportNone found
Nov 10, 2026, 16:10 UTCNov 10, 2026, 17:55 UTC
  1. Acknowledged
    We are investigating reports of degraded performance for Actions and Pull Requests[1]
  2. Actions and Pull Requests are experiencing degraded availability.[1]
  3. We're investigating elevated response times for Git operations and pull requests.[1]
  4. Actions is experiencing degraded availability.[1]
  5. We continue to investigate elevated response times for Git operations and pull requests.[1]
  6. Pull Requests is experiencing degraded performance.[1]
  7. Actions is operating normally.[1]
  8. We continue to investigate elevated response times for Git operations and pull requests.[1]
  9. Resolved
    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.[1]
  10. Start to: Provider marked resolved1 h 44 min

Evidence and sources

Grouped by type of evidence. Numbers match the citations above.

Primary: provider and official sources

Published by the provider or agency itself: incident reports, status records, advisories, statements.

  1. 1.
    GitHub status: Incident with Git Operations and Pull Requests (opens in a new tab)
    GitHub · Official statement · Publication date not recorded · Accessed
    Official status updates, captured automatically when published.

Last verified against these sources on Nov 15, 2026.