Changes GitHub Incident with Git Operations

GitHub: Incident silently edited: Incident with Git Operations

Silent editNormal progress (typesafe/jev-1.13-20260917, 85%)Changed 2026-11-06 23:44 UTCwww.githubstatus.com

Summary

GitHub’s edited report says GitHub.com HTTPS clones, fetches, and pushes were degraded on November 3, 2026, from 15:00 UTC to 22:37 UTC; SSH was unaffected. For about half of HTTPS traffic, median response time rose from under 100 milliseconds to as high as 5 seconds; errors averaged 0.65%, peaking at 1.29%.

Machine-written from the diff below (Sol; type: incident edit). Check the diff before relying on it.

Incident page: the full timeline of updates

What changed

~~Struck in red~~ is what GitHub removed; blue is what they added. Muted text is unchanged context.

ChangedUpdateresolved2026-11-03 22:41 UTC#1

~~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.~~

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.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Nov 3
Before captured 22:43 UTC
In the 2026-11-03 checkpoint, timestamped by FreeTSA and DigiCert on Nov 4, 00:42 UTC. Record hash c79403691e6ce9bf…
Download proof
Nov 6
After captured 23:44 UTC
In the 2026-11-06 checkpoint, timestamped by FreeTSA and DigiCert on Nov 7, 00:44 UTC. Record hash 32ad94b94c4c8bdd…
Download proof

History of this incident

Friday, November 6

1 rewrite

Normal progress
23:44Edited by the vendor
Incident with Git Operationsthis change
GitHub’s edited report says GitHub.com HTTPS clones, fetches, and pushes were degraded on November 3, 2026, from 15:00 UTC to 22:37 UTC; SSH was unaffected. For about half of HTTPS traffic, median response time rose from under 100 milliseconds to as high as 5 seconds; errors averaged 0.65%, peaking at 1.29%.

Tuesday, November 3

3 incident changes

Normal progress
22:43Incident
Incident updateIncident with Git Operations
Normal progress
22:13Incident
Incident updateIncident with Git Operations
Normal progress
21:43Incident
Incident updateIncident with Git Operations

Cite this

Incident silently edited: Incident with Git Operations on GitHub’s status page, changed 2026-11-06 23:44 UTC (change 4 of 4).

Title: Incident silently edited: Incident with Git Operations
Vendor: GitHub
Date: 2026-11-06 23:44 UTC
URL: https://rewindex.com/change/r6d19d6d36cd151

All GitHub changes GitHub profile Markdown JSON