Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Recorded 6 Nov 2026 at 23:37 UTC. This is what ChangeIntel recorded, including the title, summary, facts and links. It is not a statement of the source's current position. See the latest record.

Incident with Git Operations

On November 3, 2026, between 15:00 UTC and 22:37 UTC, Git operations over HTTPS on GitHub.com were degraded. Clones, fetches, and pushes over HTTPS were slow, and some failed. For about half of Git HTTPS traffic, median response time rose from under 100 milliseconds to as high as 5 seconds. On average, the error rate was 0.65% and peaked at 1.29% of requests to the service. Git operations over SSH were not affected. This was due to a buildup of excess connections on the hosts that serve Git HTTPS traffic, which saturated their network capacity and caused slow and failed responses for all clients served by those hosts. We mitigated the incident by blocking a client traffic pattern at our load balancers and reloading them, which released the excess connections. The block also prevented some users of one third-party integration from performing Git operations over HTTPS until we removed it on November 4 at 13:26 UTC. We are working to alert on sustained Git HTTPS latency sooner and make load balancer mitigations take effect on existing connections immediately.

What it said

Observed state
Ended
Stage
Resolved
Posted
3 Nov 2026 20:57 UTC
Services
Git Operations

What changed

  1. Status: Monitoring → Resolved · Incident state: Ongoing → Ended
  2. Status: Investigating → Monitoring
Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (8)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 6 Nov 2026 · 23:37:21 UTC SummaryThis 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. → On November 3, 2026, between 15:00 UTC and 22:37 UTC, Git operations over HTTPS on GitHub.com were degraded. Clones, fetches, and pushes over HTTPS were slow, and some failed. For about half of Git HTTPS traffic, median response time rose from under 100 milliseconds to as high as 5 seconds. On average, the error rate was 0.65% and peaked at 1.29% of requests to the service. Git operations over SSH were not affected. This was due to a buildup of excess connections on the hosts that serve Git HTTPS traffic, which saturated their network capacity and caused slow and failed responses for all clients served by those hosts. We mitigated the incident by blocking a client traffic pattern at our load balancers and reloading them, which released the excess connections. The block also prevented some users of one third-party integration from performing Git operations over HTTPS until we removed it on November 4 at 13:26 UTC. We are working to alert on sustained Git HTTPS latency sooner and make load balancer mitigations take effect on existing connections immediately.
  2. 3 Nov 2026 · 22:50:54 UTC StageMonitoring → Resolved
  3. 3 Nov 2026 · 22:50:54 UTC Observed stateOngoing → Ended
  4. 3 Nov 2026 · 22:50:54 UTC SummaryThe degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability. → 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.
  5. 3 Nov 2026 · 22:40:45 UTC StageInvestigating → Monitoring
  6. 3 Nov 2026 · 22:40:45 UTC SummaryOur mitigation is rolled out and customers should start seeing improvements to Git Operations. We will continue to provide updates on mitigation status. → The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.
  7. 3 Nov 2026 · 22:10:21 UTC SummaryWe have identified the issue impacting Git Operations and are beginning to roll out a mitigation. We will follow up with another update when we begin to see recovery. → Our mitigation is rolled out and customers should start seeing improvements to Git Operations. We will continue to provide updates on mitigation status.
  8. 3 Nov 2026 · 21:39:55 UTC SummaryWe are investigating reports of degraded performance for Git Operations → We have identified the issue impacting Git Operations and are beginning to roll out a mitigation. We will follow up with another update when we begin to see recovery.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 18 Nov 18:55 UTC · 272 of 275 readable · 270 fully read · documentation 469/469 current